Hello Oleg,
On Wed, May 13, 2015 at 01:53:35AM +, Drokin, Oleg wrote:
> Hello!
>
> On May 12, 2015, at 6:43 PM, George G. Davis wrote:
>
> > Greetings,
> >
> > Resending this using the correct version of get_maintainers.pl.
> >
> > As recommended in the thread "SPDX-License-Identifier” [1]
Shaohua Li writes:
> In a workload with discard request, the IO throughput is generally much
> higher than expected. This is quite confusing checking iostat. Discard
> request doesn't really write data to drive, so don't account it.
>
> Signed-off-by: Shaohua Li
> ---
> block/blk-core.c | 6 +++
On Tue, May 12, 2015 at 05:58:21PM -0700, j...@joshtriplett.org wrote:
> On Tue, May 12, 2015 at 03:49:13PM -0700, Paul E. McKenney wrote:
> > From: "Paul E. McKenney"
> >
> > If, at the time __rcu_process_callbacks() is invoked, there are callbacks
> > in Tiny RCU's callback list, but none of t
hi,
I'm constantly getting hard lockups on single AMD server
triggered just by kernel build.. make -j65
I cannot reproduce on any other server, so I think this might
be HW issue.. it's vanilla kernel v4.0 server with 64 CPUs:
processor : 63
vendor_id : AuthenticAMD
cpu family : 2
On 05/13/2015 06:08 AM, Mike Galbraith wrote:
> On Wed, 2015-05-13 at 04:31 -0700, Daniel Phillips wrote:
>> Third possibility: build from our repository, as Mike did.
>
> Sorry about that folks. I've lost all interest, it won't happen again.
Thanks for your valuable contribution. Now we are see
We are seeing a panic in crc32_le after kmemleak_scan(). I have pasted the
snippet of the crash log below. This is seen on 3.10 Kernel.
This issue was earlier discussed over this thread as well -
https://lkml.org/lkml/2014/2/6/287.
<4>[ 70.732606] kmemleak: Cannot allocate a kmemleak_object st
On Wed, May 13, 2015 at 03:37:12PM +0300, Dan Carpenter wrote:
> GW-BASIC style label names are annoying so we can warn about that in
> checkpatch. The warnings look like:
>
> WARNING: 'fail2' isn't informative - prefer descriptive label names
> #267: FILE: ./sound/ppc/beep.c:267:
>
I'm announcing the release of the 3.10.78 kernel.
All users of the 3.10 kernel series must upgrade.
The updated 3.10.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.10.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index 923ad8a64e3b..cf99a9b53c6f 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 10
-SUBLEVEL = 77
+SUBLEVEL = 78
EXTRAVERSION =
NAME = TOSSUG Baby Fish
diff --git a/arch/arc/kernel/signal.c b/arch/arc/kernel/signal.c
index 7e95e1
I'm announcing the release of the 3.14.42 kernel.
All users of the 3.14 kernel series must upgrade.
The updated 3.14.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.14.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index 7a60d4a1301c..b9d850d86366 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 14
-SUBLEVEL = 41
+SUBLEVEL = 42
EXTRAVERSION =
NAME = Remembering Coco
diff --git a/arch/arc/kernel/signal.c b/arch/arc/kernel/signal.c
index d68b41
I'm announcing the release of the 4.0.3 kernel.
All users of the 4.0 kernel series must upgrade.
The updated 4.0.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.0.y
and can be browsed at the normal kernel.org git web browser:
On Wed, May 13, 2015 at 11:47:56AM +0200, Ingo Molnar wrote:
> - introduce the '..' denotion (in the final table) to show features
>that cannot be supported by an architecture due to hardware
>dependencies:
>
> gcov-profile-all:---.
>
diff --git a/Documentation/kernel-parameters.txt
b/Documentation/kernel-parameters.txt
index bfcb1a62a7b4..4d68ec841304 100644
--- a/Documentation/kernel-parameters.txt
+++ b/Documentation/kernel-parameters.txt
@@ -3746,6 +3746,8 @@ bytes respectively. Such letter suffixes can also be
entirely om
On Wed, May 13, 2015 at 12:58:39PM +1000, NeilBrown wrote:
> On Tue, 12 May 2015 22:38:53 -0400 Steven Rostedt wrote:
>
> > On Tue, 12 May 2015 15:46:26 -0700
> > "Paul E. McKenney" wrote:
> >
> > > From: Patrick Marlier
> > >
> > > Signed-off-by: Patrick Marlier
> > > Signed-off-by: Paul E.
On Wed, May 13, 2015 at 03:11:46PM +0200, Jiri Olsa wrote:
> hi,
> I'm constantly getting hard lockups on single AMD server
> triggered just by kernel build.. make -j65
>
> I cannot reproduce on any other server, so I think this might
> be HW issue.. it's vanilla kernel v4.0 server with 64 CPUs:
>
On 05/13/2015 02:58 AM, Paul Bolle wrote:
On Tue, 2015-05-12 at 13:07 -0700, Guenter Roeck wrote:
On Tue, May 12, 2015 at 03:45:21PM +0200, anees wrote:
Kernel build fails with error "target elf32-or32 not found"
This is due to the change in OpenRISC compiler prefix from "or12"
to "or1k". Add c
On Tue, May 12, 2015 at 11:22:32PM -0400, Steven Rostedt wrote:
> On Tue, 12 May 2015 15:30:36 -0700
> "Paul E. McKenney" wrote:
>
> > @@ -4103,24 +4102,21 @@ static void __init rcu_init_geometry(void)
> > return;
> > }
> >
> > + /* Calculate the number of levels in the tree.
Hi Andrew,
your commit b1f10002b00a ("mailbox: Add NVIDIA Tegra XUSB mailbox
driver") is in today's linux-next tree (i.e., next-20150513) and it
adds the following lines:
+config TEGRA_XUSB_MBOX
+ tristate "NVIDIA Tegra XUSB Mailbox"
+ depends on MFD_TEGRA_X
This is the following patch for:
https://lkml.org/lkml/2015/5/5/417
which try to document the settled rdma_cap_XX().
Highlights:
There could be many missing/mistakes/misunderstanding, please don't
be hesitate to point out the issues, any suggestions to improve or
complete the description a
On 2015年05月13日 20:24, Jiang Liu wrote:
On 2015/5/13 17:29, Hanjun Guo wrote:
Hi Jiang,
On 2015年05月05日 10:46, Jiang Liu wrote:
Introduce common interface acpi_pci_root_create() and related data
structures to create PCI root bus for ACPI PCI host bridges. It will
be used to kill duplicated arch
On Tue, May 12, 2015 at 05:59:29PM -0700, j...@joshtriplett.org wrote:
> On Tue, May 12, 2015 at 03:49:12PM -0700, Paul E. McKenney wrote:
> > From: "Paul E. McKenney"
> >
> > Reported-by: "Ahmed, Iftekhar"
> > Signed-off-by: Paul E. McKenney
>
> Could you elaborate a bit more on this patch (i
On 2015年05月13日 03:22, Mark Brown wrote:
On Tue, May 12, 2015 at 05:26:34PM +0800, Xing Zheng wrote:
From: zhengxing
In most cases, we maybe use simple-card as generic machine driver
on next kernel, but there are some issue that jack detection and
widgets extandable on simple-card.
Own machine
On 2015年05月13日 03:26, Mark Brown wrote:
On Tue, May 12, 2015 at 05:26:35PM +0800, Xing Zheng wrote:
sound/soc/rockchip/Kconfig | 10 ++
sound/soc/rockchip/Makefile |2 +
sound/soc/rockchip/rockchip_machine_driver.c |6 +
sound/soc/rockchip/rockc
On Wed, May 13, 2015 at 03:20:22PM +0200, Borislav Petkov wrote:
> On Wed, May 13, 2015 at 03:11:46PM +0200, Jiri Olsa wrote:
> > hi,
> > I'm constantly getting hard lockups on single AMD server
> > triggered just by kernel build.. make -j65
> >
> > I cannot reproduce on any other server, so I thi
On Wednesday 13 May 2015 13:58:05 Daniel Thompson wrote:
> On 13/05/15 12:45, Maxime Coquelin wrote:
> > 2015-05-12 23:21 GMT+02:00 Arnd Bergmann :
> >> On Saturday 09 May 2015 09:53:56 Maxime Coquelin wrote:
> >>> +#include
> >>> +
> >>>
> >>
> >> Can you find a way to avoid this dependency?
> >
From: Rafael J. Wysocki
Signed-off-by: Rafael J. Wysocki
---
kernel/power/main.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-pm/kernel/power/main.c
===
--- linux-pm.orig/kernel/power/main.c
+++ linux-pm/k
On 5/13/15, 5:49 AM, Michal Kubecek wrote:
On Wed, May 13, 2015 at 02:28:57PM +0200, Nicolas Dichtel wrote:
Le 13/05/2015 11:50, Michal Kubecek a écrit :
If adding a nexthop of an IPv6 multipath route fails, comment in
ip6_route_multipath() says we are going to delete all nexthops already
added
On Tue, 12 May 2015 15:30:44 -0700
"Paul E. McKenney" wrote:
> From: "Paul E. McKenney"
>
> Currently, Kconfig will ask the user whether TASKS_RCU should be set.
> This is silly because Kconfig already has all the information that it
> needs to set this parameter. This commit therefore directl
On Tue, May 12, 2015 at 07:51:31PM -0400, Nicholas Krause wrote:
> This changes the function,nvme_alloc_queue to use the kernel code,
> -ENOMEM for when failing to allocate the memory required for the
> nvme_queue structure pointer,nvme in order to correctly return
> to the caller the correct reaso
On Wed, 2015-05-13 at 06:20 -0700, Guenter Roeck wrote:
> Just remembered ... or just apply https://lkml.org/lkml/2014/9/19/11 instead.
(That patch also suggests that "or12" in the patch we're discussing here
is a typo.)
This is problem is present now for none months, apparently. Your patch
was s
On 13/05/2015 at 06:04:47 -0700, Guenter Roeck wrote :
> Don't know how this is handled for rtc drivers, but in other subsystems
> we just live with the original name. I don't see a need to rename a driver
> just because it starts supporting more hardware, and xxx is weird anyway
> since it suggest
On Tue, May 12, 2015 at 09:52:09AM -0400, Sasha Levin wrote:
> Hey Peter,
>
> I seem to be hitting this warning with the latest -next (2015-05-11):
>
> [3344291.055800] WARNING: CPU: 0 PID: 9422 at kernel/time/hrtimer.c:802
> hrtimer_forward+0x1f9/0x330()
Indeed.
So I can't seem to come up wit
On Thursday, May 07, 2015 06:56:20 PM Daniel Lezcano wrote:
> The poll idle loop is useful only for the *menu* governor: when there
> is a timer about to shutdown very soon (less than 5us), then we default
> to the poll idle if no other idle state is found, otherwise the 'hlt'
> state is the defaul
On 05/13/2015 06:33 AM, Paul Bolle wrote:
On Wed, 2015-05-13 at 06:20 -0700, Guenter Roeck wrote:
Just remembered ... or just apply https://lkml.org/lkml/2014/9/19/11 instead.
(That patch also suggests that "or12" in the patch we're discussing here
is a typo.)
This is problem is present now f
Hi Sai,
On Tue, May 12, 2015 at 11:07:26PM +0100, Sai Gurrappadi wrote:
>
> On 05/12/2015 12:38 PM, Morten Rasmussen wrote:
> > Test results for ARM TC2 (2xA15+3xA7) with cpufreq enabled:
> >
> > sysbench: Single task running for 3 seconds.
> > rt-app [4]: mp3 playback use-case model
> > rt-app
On Tue, 12 May 2015 15:30:54 -0700
"Paul E. McKenney" wrote:
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -1373,6 +1373,17 @@ config RCU_TRACE
> Say Y here if you want to enable RCU tracing
> Say N if you are unsure.
>
> +config RCU_EQS_DEBUG
> + bool "Use this w
On 05/13/2015 06:37 AM, Alexandre Belloni wrote:
On 13/05/2015 at 06:04:47 -0700, Guenter Roeck wrote :
Don't know how this is handled for rtc drivers, but in other subsystems
we just live with the original name. I don't see a need to rename a driver
just because it starts supporting more hardwa
On Wed, May 13, 2015 at 5:03 AM, Sudeep Holla wrote:
>
>
> On 12/05/15 23:55, Rob Herring wrote:
>>
>> On Tue, May 12, 2015 at 12:38 PM, Sudeep Holla
>> wrote:
>>>
>>> Commit 5590f3196b29 ("drivers/core/of: Add symlink to device-tree from
>>> devices with an OF node") adds the symlink `of_node` f
You misunderstand. Although I am famous for hating out: labels, I would
not introduce a checkpatch warning to complain about it. This only
complains about GW-BASIC labels.
out3:
kfree(foo);
out2:
kfree(bar);
out:
kfree(baz);
GW-BASIC label suck because they are meaningle
At Wed, 13 May 2015 10:33:13 +0200,
Valentin Rothberg wrote:
>
> Hi Yoshinori,
>
> your commit 5befaa907481 ("h8300: devicetree source") is in today's
> linux-next tree (i.e., next-20150513) and adds the following line:
>
> +dtb-$(CONFIG_EDOSK2674) := edosk26
On Wed, May 13, 2015 at 01:33:22AM +0100, Sai Gurrappadi wrote:
> On 05/12/2015 12:38 PM, Morten Rasmussen wrote:
> > Task being dequeued for the last time (state == TASK_DEAD) are dequeued
> > with the DEQUEUE_SLEEP flag which causes their load and utilization
> > contributions to be added to the
* Borislav Petkov wrote:
> On Wed, May 13, 2015 at 11:47:56AM +0200, Ingo Molnar wrote:
> > - introduce the '..' denotion (in the final table) to show features
> >that cannot be supported by an architecture due to hardware
> >dependencies:
> >
> >gcov-profile-all:
On Wed, 13 May 2015 15:16:13 +0200
David Sterba wrote:
> On Wed, May 13, 2015 at 03:37:12PM +0300, Dan Carpenter wrote:
> > GW-BASIC style label names are annoying so we can warn about that in
> > checkpatch. The warnings look like:
> >
> > WARNING: 'fail2' isn't informative - prefer descri
Hello, Aleksa.
On Wed, May 13, 2015 at 03:44:51PM +1000, Aleksa Sarai wrote:
> I think I'll just do casting and manually make new variables where
> required. The above (and similar) doesn't work very well, generates
> warnings like crazy and breaks stuff like:
>
> if (...)
> for_each_s
On Wed, May 13, 2015 at 12:39:14PM +0200, Michal Marek wrote:
> On 2015-05-11 18:38, Josh Poimboeuf wrote:
> > Frame pointer based stack traces aren't always reliable. One big reason
> > is that most asm functions don't set up the frame pointer.
> >
> > Fix that by enforcing that all asm function
On 05/13/2015 02:29 AM, Peter Zijlstra wrote:
> On Tue, May 12, 2015 at 11:45:09AM -0400, Rik van Riel wrote:
>> I have a few poorly formed ideas on what could be done about that:
>>
>> 1) have fbq_classify_rq take the current task on the rq into account,
>>and adjust the fbq classification if
Hello, Lai.
On Wed, May 13, 2015 at 09:43:19AM +0800, Lai Jiangshan wrote:
> >> I think the workqueue.c has too much complicated and rarely used APIs
> >> and exposes too much in this way. No one can set the nice value
> >> and the cpuallowed of a task atomically.
> >
> > What do you mean no one
* Peter Zijlstra wrote:
> On Tue, May 12, 2015 at 09:52:09AM -0400, Sasha Levin wrote:
> > Hey Peter,
> >
> > I seem to be hitting this warning with the latest -next (2015-05-11):
> >
> > [3344291.055800] WARNING: CPU: 0 PID: 9422 at kernel/time/hrtimer.c:802
> > hrtimer_forward+0x1f9/0x330()
On Wed, May 13, 2015 at 09:42:47AM +0900, Kyungmin Park wrote:
> Right, it's still in freezer, just one time scheduling is happened.
> and enter freeze state again.
>
> do you think can we avoid it or it's sub-optimal to do as patch?
I mean, it's suboptimal. I'm not sure it actually matters tho.
On Fri 08-05-15 16:06:10, Eric B Munson wrote:
> On Fri, 08 May 2015, Andrew Morton wrote:
>
> > On Fri, 8 May 2015 15:33:43 -0400 Eric B Munson wrote:
> >
> > > mlock() allows a user to control page out of program memory, but this
> > > comes at the cost of faulting in the entire mapping when
On Wed, 2015-05-13 at 12:10 +0100, Mark Brown wrote:
> On Wed, May 13, 2015 at 05:26:06PM +0800, Yingjoe Chen wrote:
> > On Tue, 2015-05-12 at 17:05 +0100, Mark Brown wrote:
>
> > > > > There were three compatible strings listed in the DT binding but only
> > > > > two here.
>
> > > > And I test
Hi Valentin,
On 13/05/15 14:22, Valentin Rothberg wrote:
> Hi Andrew,
>
> your commit b1f10002b00a ("mailbox: Add NVIDIA Tegra XUSB mailbox
> driver") is in today's linux-next tree (i.e., next-20150513) and it
> adds the following lines:
>
> +config TEGRA_
From: Andrea Arcangeli
memslot->userfault_addr is set by the kernel with a mmap executed
from the kernel but the userland can still munmap it and lead to the
below oops after memslot->userfault_addr points to a host virtual
address that has no vma or mapping.
[ 327.538306] BUG: unable to handle
Hello, Dave.
On Wed, May 13, 2015 at 09:52:33AM +1000, Dave Chinner wrote:
> @@ -116,6 +121,12 @@ static inline int percpu_counter_compare(struct
> percpu_counter *fbc, s64 rhs)
> return 0;
> }
>
> +static inline int
> +percpu_counter_compare(struct percpu_counter *fbc, s64 rhs,
ailbox
>> driver") is in today's linux-next tree (i.e., next-20150513) and it
>> adds the following lines:
>>
>> +config TEGRA_XUSB_MBOX
>> + tristate "NVIDIA Tegra XUSB Mailbox"
>> + depends on MFD_TEGRA_XUSB
>>
>> At
On 05/13/2015 03:33 PM, Paul Bolle wrote:
On Wed, 2015-05-13 at 06:20 -0700, Guenter Roeck wrote:
Just remembered ... or just apply https://lkml.org/lkml/2014/9/19/11 instead.
(That patch also suggests that "or12" in the patch we're discussing here
is a typo.)
This is problem is present now fo
Hello Rob
On Wed, May 13, 2015 at 3:56 PM, Rob Herring wrote:
>
> Does this actually solve anything? What resources have parents besides
> mem or io?
It is code cleanup for the later patches. del_resource checks if the
resource is mem or io.
We either add the check here, or remove the check in
On Thu, Apr 23, 2015 at 8:58 AM, Ricardo Ribalda Delgado
wrote:
> platform_device_del only checks the type of the resource in order to
> call release_resource.
>
> On the other hand, platform_device_add calls insert_resource for any
> resource that has a parent.
>
> Make both code branches balance
On Thu, Apr 23, 2015 at 8:58 AM, Ricardo Ribalda Delgado
wrote:
> Failure path of platform_device_add was almost the same as
> platform_device_del. Refactor same code in a function.
>
> Signed-off-by: Ricardo Ribalda Delgado
Clean-ups should come first in the series. Otherwise:
Acked-by: Rob He
On Thu, Apr 23, 2015 at 8:58 AM, Ricardo Ribalda Delgado
wrote:
> of_platform_device_create_pdata() was using of_device_add() to create
> the devices, but of_platform_device_destroy was using
> of_platform_device_destroy().
You mean platform_device_destroy?
> of_device_add(), do not call insert_
Hi,
On Friday, April 03, 2015 06:43:43 PM Bartlomiej Zolnierkiewicz wrote:
> Hi,
>
> This patch series removes the use of Exynos4210 specific support
> from cpufreq-exynos driver and enables the use of cpufreq-dt driver
> for this platform.
Gentle Ping. Mike/Kukjin/Viresh could you please revi
On Wed, May 13, 2015 at 11:47:56AM +0200, Ingo Molnar wrote:
>
> (fixed the subject.)
>
> So this is the final version for now:
>
> - add a fourth table
>
> - fix errors in earlier tables, in particular I missed some PowerPC
>Kconfigs
>
> - introduce the '..' denotion (in the final tab
There is a TPM on I2C3, so set up the pinmux for that.
Signed-off-by: Simon Glass
---
configs/nyan-big.board | 4 ++--
configs/nyan-blaze.board | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/configs/nyan-big.board b/configs/nyan-big.board
index 6ebe466..18c2e52 10064
On 05/13/2015 12:43 PM, Ingo Molnar wrote:
>
> * Denys Vlasenko wrote:
>
>> On 05/13/2015 12:17 PM, Ingo Molnar wrote:
> In any case, the interesting measurement would not be -Os comparisons
> (which causes GCC to be too crazy), but to see the size effect of your
> _patch_ that alw
On 13/05/2015 10:43, Wanpeng Li wrote:
> kvm_mmu_reset_context
> kvm_mmu_unload
> mmu_free_roots
>
> The original root shadow page will be freed in mmu_free_roots, where I
> miss?
>
> Another question maybe not related to this patch:
>
> If kvm_mmu_reset_context is just called to destroy
Sorry for reviving oldish thread...
On 04/28/2015 01:54 AM, Benjamin Herrenschmidt wrote:
On Mon, 2015-04-27 at 11:48 -0500, Christoph Lameter wrote:
On Mon, 27 Apr 2015, Rik van Riel wrote:
Why would we want to avoid the sane approach that makes this thing
work with the fewest required chang
On Thu, 7 May 2015 16:20:34 -0700
Badhri Jagan Sridharan wrote:
> The timer_start event now shows whether the timer is
> deferrable in case of a low-res timer. The debug_activate
> function now includes deferrable flag while calling
> trace_timer_start event.
>
> Signed-off-by: Badhri Jagan Sri
On Wed, May 13, 2015 at 03:37:12PM +0300, Dan Carpenter wrote:
> GW-BASIC style label names are annoying so we can warn about that in
> checkpatch. The warnings look like:
>
> WARNING: 'fail2' isn't informative - prefer descriptive label names
> #267: FILE: ./sound/ppc/beep.c:267:
>
On Tue, 12 May 2015, Nicholas Krause wrote:
This changes the function,nvme_alloc_queue to use the kernel code,
-ENOMEM for when failing to allocate the memory required for the
nvme_queue structure pointer,nvme in order to correctly return
to the caller the correct reason for this function's faili
Regenerate the pinmux from the latest tegra-pinmux-scripts.
Signed-off-by: Simon Glass
---
arch/arm/boot/dts/tegra124-nyan-big.dts | 22 +++---
arch/arm/boot/dts/tegra124-nyan-blaze.dts | 30 +++---
2 files changed, 26 insertions(+), 26 deletions(-)
di
On 03/04/15 18:43, Bartlomiej Zolnierkiewicz wrote:
> This flag is needed to fix the issue with wrong dividers being setup
> by Common Clock Framework when using the new Exynos cpu clock support.
>
> The issue happens because clk_core_set_rate_nolock() calls
> clk_calc_new_rates(clk, rate) before
On 13/05/2015 08:42, Xiao Guangrong wrote:
> Changelog in v3:
> thanks for Paolo's comment:
> - do not apply for_each_rmap_spte to kvm_zap_rmapp and kvm_mmu_unlink_parents
Good idea applying my comment to kvm_mmu_unlink_parents as well. :)
> - fix a cosmetic issue in slot_handle_level_range
> -
On Tue, May 12, 2015 at 10:04:44PM +0800, Minfei Huang wrote:
> @@ -883,7 +883,7 @@ int klp_register_patch(struct klp_patch *patch)
> }
> EXPORT_SYMBOL_GPL(klp_register_patch);
>
> -static void klp_module_notify_coming(struct klp_patch *patch,
> +static int klp_module_notify_coming(struct klp_p
On Wed, 13 May 2015, Lu, Baolu wrote:
> From software point of view, the extra time it takes to ask for cache
> operation can be measured in xhci_device_suspend(). I can measure
> the data later when I complete my tasks in hand. If that data is ignorable
> comparing to the suspend time, we can si
On Wed, 13 May 2015, Michal Hocko wrote:
> On Fri 08-05-15 16:06:10, Eric B Munson wrote:
> > On Fri, 08 May 2015, Andrew Morton wrote:
> >
> > > On Fri, 8 May 2015 15:33:43 -0400 Eric B Munson
> > > wrote:
> > >
> > > > mlock() allows a user to control page out of program memory, but this
>
On Tue, 05 May 2015, Richard Fitzgerald wrote:
> The use of ifneq against 'n' to conditionally compile codec-specific
> parts is wrong and was resulting in all the codec tables being built
> even for deselected codecs.
>
> For the WM5102 there is an extra dependency on wm5102_patch() so
> it is g
On Thu, Apr 23, 2015 at 8:58 AM, Ricardo Ribalda Delgado
wrote:
> insert_resource() can fail when the resource added overlaps
> (partially or fully) with another.
>
> Device tree and AMBA devices may contain resources that overlap, so they
> could not call platform_device_add (see 02bbde7849e6 ('
The following sequence:
echo timer >/sys/class/leds//trigger
echo 1 >/sys/class/leds//brightness
should change the ON brightness for blinking.
The function led_set_brightness() was mistakenly initiating the
delayed blink stop procedure, which resulted in no blinking with
the timer trigger still ac
On 05/13/2015 09:10 AM, Jeff Moyer wrote:
Shaohua Li writes:
In a workload with discard request, the IO throughput is generally much
higher than expected. This is quite confusing checking iostat. Discard
request doesn't really write data to drive, so don't account it.
Signed-off-by: Shaohua L
*blink*
How did you end up with that in subject lines? "[\u0344PATCH ", that is...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FA
On Wed, 13 May 2015 22:14:54 +0800
"王龙" wrote:
> context. But how do we fix this problem in older version of kernel(eg, 3.10
> stable)?
> The 3.10 stable has no "switch printk routine" and "seq_buf" infrastructures.
>
> Could anyone give me some ideas?
>
Backport the necessary patches.
--
This patch is partially based on Felipe Contrera's earlier patch, that
was discussed here: https://lkml.org/lkml/2013/10/8/800
Some problems of that patch are solved, now:
1) The main obstacle for the earlier patch seemed to be the use of
virt_to_phys, which is accepted, now
2) random memory corr
Hi all,
In kernel before 3.19, when trigger_all_cpu_backtrace() is called on x86,
it will trigger an NMI on each CPU and call show_regs(). But this can lead
to a hard lock up if the NMI comes in on another printk().
The commit a9edc88093287183ac934be44f295f183b2c62dd (x86/nmi: Perform a safe
NM
On Wed, 13 May 2015, 王龙 wrote:
> Hi all,
>
> In kernel before 3.19, when trigger_all_cpu_backtrace() is called on x86,
> it will trigger an NMI on each CPU and call show_regs(). But this can lead
> to a hard lock up if the NMI comes in on another printk().
>
> The commit a9edc88093287183ac934be
On Wed, May 13, 2015 at 06:10:05AM -0400, Chen Hanxiao wrote:
> s/detemined/determined
>
> Signed-off-by: Chen Hanxiao
Applied to wq/for-4.2.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
On Wed, 2015-05-13 at 15:41 +0200, Jonas Bonn wrote:
> openrisc.net is no more long story, not worth regurgitating.
I see. What would you suggest as substitutes for:
MAINTAINERS:W:http://openrisc.net
MAINTAINERS:L:li...@lists.openrisc.net (moderated for non-subscribers)
MAI
Hello, Robert.
On Mon, May 11, 2015 at 07:18:10PM +0200, Robert Richter wrote:
> static int ahci_init_msix(struct pci_dev *pdev, unsigned int n_ports,
> struct ahci_host_priv *hpriv)
> {
> int rc, nvec;
> struct msix_entry entry = {};
>
> /* check if msix
Maxime Ripard writes:
> On Tue, May 12, 2015 at 03:35:50PM -0700, Stephen Boyd wrote:
>> On 05/08/15 03:02, Maxime Ripard wrote:
>> > On Thu, May 07, 2015 at 02:03:57PM -0700, Stephen Boyd wrote:
>> >> On 05/07/15 08:17, Kevin Hilman wrote:
>> >>> On Fri, May 1, 2015 at 4:40 PM, Stephen Boyd
>>
Operations to unflatten fdt blobs never modify the input blobs, hence
make them const. Now we no longer need to cast arbitrary const data to
"void *" when calling of_fdt_unflatten_tree().
Signed-off-by: Geert Uytterhoeven
---
drivers/of/fdt.c | 6 +++---
include/linux/of_fdt.h | 2 +-
2 fi
On Wed, May 13, 2015 at 02:51:02PM +0200, Maxime Ripard wrote:
> I'd say we're also ok because if we delegate the device driving logic
> to userspace, we should expect it to know what it does to first drive
> the device properly, but also to open the right device for this.
> What's the worst that
On Mon, 04 May 2015, Andrew Bresticker wrote:
> Add an MFD driver for the XUSB host complex found on NVIDIA Tegra124
> and later SoCs.
What else does it do besides USB?
> Signed-off-by: Andrew Bresticker
> Cc: Samuel Ortiz
> Cc: Lee Jones
> ---
> Changes from v7:
> - Have child nodes get non
On Wed, May 13, 2015 at 02:19:53PM +0200, Arnd Bergmann wrote:
> Ah, very good. Extending this one function should be fairly straightforward,
> just discuss with the PTP maintainer how to best do it.
Sorry, I deleted the original post, and I have zero clue what is is
all about. Can you give me a
Hi,
during the previous discussion
http://marc.info/?l=linux-mm&m=143022313618001&w=2
it was made clear that making mmap(MAP_LOCKED) semantic really have
mlock() semantic is too dangerous. Even though we can try to reduce the
failure space the mmap man page should make it really clear about the
su
From: Michal Hocko
MAP_LOCKED had a subtly different semantic from mmap(2)+mlock(2) since
it has been introduced.
mlock(2) fails if the memory range cannot get populated to guarantee
that no future major faults will happen on the range. mmap(MAP_LOCKED) on
the other hand silently succeeds even if
From: Michal Hocko
David Rientjes has noticed that MAP_POPULATE wording might promise much
more than the kernel actually provides and intend to provide. The
primary usage of the flag is to pre-fault the range. There is no
guarantee that no major faults will happen later on. The pages might
have b
Hello,
On Tue, May 12, 2015 at 01:46:47PM +0200, Robert Richter wrote:
> I don't think this is worth the effort as all internal and external
> drivers need to be changed basically from:
>
> ahci_host_activate(host, irq, &ahci_sht);
>
> to:
>
> host->irq = irq;
> ahci_host_activate(host, &ahc
Currently in snd_pcm_update_hw_ptr0 during interrupt,
we consider there were double acknowledged interrupts when:
1. HW reported pointer is smaller than expected, and
2. Time from last update time (hdelta) is over half a buffer time.
However, when HW reported pointer is only a few bytes smaller th
On Mon, 04 May 2015, Andrew Bresticker wrote:
> Add a binding document for the XUSB host complex on NVIDIA Tegra124
> and later SoCs. The XUSB host complex includes a mailbox for
> communication with the XUSB micro-controller and an xHCI host-controller.
>
> Signed-off-by: Andrew Bresticker
> C
On Tue, May 12, 2015 at 8:18 PM, Nicholas Mc Guire wrote:
> Return type of wait_for_completion_timeout is unsigned long not int.
> An appropriately named unsigned long is added, and the assignments
> as well as error checking fixed up.
>
> API conformance testing for completions with coccinelle sp
301 - 400 of 1014 matches
Mail list logo
