ping!
On Tue, May 06, 2014 at 10:12:48AM +0800, Robin Gong wrote:
> add "device_prep_dma_memcpy" and "device_prep_dma_sg" for memory copy by sdma.
>
> Signed-off-by: Robin Gong
>
> ---
> change:
> --v3:
> 1. remove redundant check for bus width
>
> --v2:
> 1. correct some printk format, suc
On 05/13/2014 06:05 AM, Tejun Heo wrote:
> On Mon, May 12, 2014 at 02:56:22PM +0800, Lai Jiangshan wrote:
>> There are several problems with the code that rescuers bind itself to the
>> pool'
>> cpumask
>> 1) It uses a way different from the normal workers to bind to the cpumask
>> So we ca
On 12 May 2014 15:49, Thomas Gleixner wrote:
> Does that handle_return_value() mean that you sprinkle WARN_ONs all
> over the place?
Yeah, probably it should have been done this way:
- dev->set_mode(mode, dev);
+ if (dev->set_dev_mode) {
+ int re
Hi Simon,
On Tue, May 13, 2014 at 2:04 AM, Simon Horman wrote:
> On Mon, May 12, 2014 at 09:25:21AM +0200, Geert Uytterhoeven wrote:
>> On Mon, May 12, 2014 at 9:07 AM, Simon Horman wrote:
>> > On Mon, May 12, 2014 at 08:24:03AM +0900, Magnus Damm wrote:
>> >> On Sun, May 11, 2014 at 9:46 AM, Si
Hi,
On Tuesday 13 May 2014 11:37 AM, Vivek Gautam wrote:
> Hi Kishon,
>
>
> On Mon, May 12, 2014 at 6:33 PM, Kishon Vijay Abraham I wrote:
>> Hi Gautam,
>>
>> On Friday 09 May 2014 07:27 PM, Vivek Gautam wrote:
>>> Add a new driver for the USB 3.0 PHY on Exynos5 series of SoCs.
>>> The new driv
Hi, Marek.
Since previous one has got no replies. I resend it again.
This patch purely add regex pattern only. And I've tested it, it works.
---<8---
Currently, no regular expression replacement pattern for PageCgroug*
defined, which causes quite a few pain while reading code. Just get
rid of it.
On 05/13/2014 06:01 AM, Tejun Heo wrote:
> On Mon, May 12, 2014 at 02:56:20PM +0800, Lai Jiangshan wrote:
>> manager_mutex is only used to protect the attaching for the pool
>> and the pool->workers list. It protects the pool->workers and operations
>> based on this list, such as:
>> cpu-bindi
On Fri, May 9, 2014 at 11:55 AM, Lee Jones wrote:
> Looks like it matters which order the patches are merged in - my bad!
>
> The following changes since commit 89ca3b881987f5a4be4c5dbaa7f0df12bbdde2fd:
>
> Linux 3.15-rc4 (2014-05-04 18:14:42 -0700)
>
> are available in the git repository at:
>
Hi,
On 05/12/2014 09:34 PM, Maxime Ripard wrote:
> Move the phy initialization and variables declaration to the loop itself,
> since
> it is where it really belongs. Also remove all the temporary variables, we can
> use the structure members directly.
>
> Signed-off-by: Maxime Ripard
> ---
> d
On 05/13/2014 05:40 AM, Tejun Heo wrote:
> On Mon, May 12, 2014 at 02:56:18PM +0800, Lai Jiangshan wrote:
>> @@ -1681,7 +1682,6 @@ static void worker_detach_from_pool(struct worker
>> *worker,
>> struct completion *detach_completion = NULL;
>>
>> mutex_lock(&pool->manager_mutex);
>> -
* Steven Rostedt wrote:
> >This is beyond sloppy and outright stupid.
>
> Thomas, listen to yourself. You are calling something that got in
> without updating the documentation and test case "beyond sloppy and
> outright stupid". Sure, I'll agree it was a little sloppy, and today I'm
> more
On 2014/5/10 3:32, Tejun Heo wrote:
> Hello,
>
> Changes from the last take[L] are,
>
> * 0002, 0003 and 0007 added.
>
> * Other patches are refreshed without content change.
>
> This patchset contains the following seven patches.
>
> 0001-cgroup-fix-offlining-child-waiting-in-cgroup_subtree.
On 2014/5/6 20:44, Tejun Heo wrote:
> Hello,
>
> This patchset implements a new cftype operation ->write() and replace
> ->write_string() and ->trigger() with it. ->write() is similar to
> ->write_string() but maps directly to the kernfs write operation and
> has access to all available context i
On 05/13/2014 05:20 AM, Tejun Heo wrote:
> On Mon, May 12, 2014 at 02:56:15PM +0800, Lai Jiangshan wrote:
>> /**
>> + * worker_detach_from_pool() - detach the worker from the pool
>> + * @worker: worker which is attached to its pool
>> + * @pool: attached pool
>> + *
>> + * Undo the attaching whic
(2014/05/13 2:08), Oleg Nesterov wrote:
> If the probed insn triggers a trap, ->si_addr = regs->ip is technically
> correct, but this is not what the signal handler wants; we need to pass
> the address of the probed insn, not the address of xol slot.
>
> Add the new arch-agnostic helper, uprobe_ge
> powerpc/pseries: relocate "config DTL" so KConfig nests properly
I don't know what that means. Can you describe it in more detail?
Mikey
On Mon, 2014-05-12 at 20:09 -0700, Cody P Schafer wrote:
> Signed-off-by: Cody P Schafer
> ---
> arch/powerpc/platforms/pseries/Kconfig | 20 ++--
On Tue, May 13, 2014 at 11:13 AM, Rob Herring wrote:
> On Sun, May 11, 2014 at 9:19 PM, Richard Lee wrote:
>> For the IO mapping, for the same physical address space maybe
>> mapped more than one time, for example, in some SoCs:
>> 0x2000 ~ 0x20001000: are global control IO physical map,
>> a
(2014/05/09 23:07), Oleg Nesterov wrote:
> On 05/08, Oleg Nesterov wrote:
>>
>> For example, after this series
>> we can convert math_error() into the "normal" DO_ERROR() user, and most
>> probably
>> we can do the same with do_general_protection().
>
> As for do_general_protection(), the problem
Hi Kishon,
On Mon, May 12, 2014 at 6:33 PM, Kishon Vijay Abraham I wrote:
> Hi Gautam,
>
> On Friday 09 May 2014 07:27 PM, Vivek Gautam wrote:
>> Add a new driver for the USB 3.0 PHY on Exynos5 series of SoCs.
>> The new driver uses the generic PHY framework and will interact
>> with DWC3 contro
On Tue, May 13, 2014 at 3:35 AM, Davidlohr Bueso wrote:
> On Mon, 2014-05-12 at 09:44 +0200, Michael Kerrisk (man-pages) wrote:
[...]
>> The problem is that part of your text is still broken grammatically In
>> particular, the piece "Both SHMMAX and SHMALL have their default
>> values to the maxim
> > > Maybe, in some cases yes. But not always.
> > > For example, please consider a CPU running a tight "for" loop in 100MHz
> > > for a couple of seconds. This produces a load of 100%.
> > > It will produce the same load (100%) in any other frequency.
> >
> > Still fundamentally wrong, becaus
On 05/13/2014 05:08 AM, Tejun Heo wrote:
> On Mon, May 12, 2014 at 02:56:14PM +0800, Lai Jiangshan wrote:
>> @@ -1692,9 +1691,8 @@ static struct worker *alloc_worker(void)
>> * create_worker - create a new workqueue worker
>> * @pool: pool the new worker will belong to
>> *
>> - * Create a ne
On Tue, May 13, 2014 at 01:49:25AM +0200, Matthias Brugger wrote:
> This patch adds a clock source and clock event for the timer found
> on the Mediatek SoCs.
>
> The Mediatek General Porpose Timer block provides five 32 bit timers and
> one 64 bit timer.
>
> Two 32 bit timers are used:
> TIMER1:
On 2014/5/4 19:37, Zhou Wang wrote:
> On 2014/4/23 19:51, Zhou Wang wrote:
>> set ARCH_NR_GPIO for Hisilicon Soc hip04, which has 4 GPIO
>> controllers with 32 GPIOs each.
>>
>> Signed-off-by: Zhou Wang
>> ---
>> arch/arm/Kconfig |1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/arch
On 05/13/2014 04:20 AM, Stephen Warren wrote:
On 05/07/2014 02:02 AM, FanWu wrote:
...
I think the glitch you mentioned is indeed a problem for the vendors who
define the "pinctrl-single,function-off" which will be activated when
disabling setting.
"pinctrl-single,function-off" is one specific
Hi, Thomas,
I think this patch is just a workaround, it is not the proper fix.
you need a updated deadlock-check mechanism:
- (old) skip the check when top_waiter != task_top_pi_waiter(task)
+ (new) skip the check when top_waiter->prio > task->prio
/*
* Drop out, when the task h
Thanks Lauraa for your answers.
I have few more queries below.
> Date: Mon, 12 May 2014 09:27:27 -0700
> From: lau...@codeaurora.org
> To: pint...@outlook.com; a...@arndb.de; linux-arm-ker...@lists.infradead.org
> CC: linux...@kvack.org; linux-kernel@vger.
Hi,
On Monday 12 May 2014 07:48 PM, Sebastian Hesselbarth wrote:
> On 05/12/2014 02:46 PM, Kishon Vijay Abraham I wrote:
>> Hi,
>>
>> On Monday 12 May 2014 02:46 PM, Antoine Ténart wrote:
>>> The Berlin SoC has a two SATA ports. Add a PHY driver to handle them.
>>>
>>> Signed-off-by: Antoine Ténar
Now, we can build zsmalloc as module because unmap_kernel_range
was exported.
Signed-off-by: Minchan Kim
---
mm/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/Kconfig b/mm/Kconfig
index 30cb6cb008f5..709a77a0fb55 100644
--- a/mm/Kconfig
+++ b/mm/Kconfig
@@ -558,7
Now zsmalloc needs exported unmap_kernel_range for building it
as module. In detail, here it is. https://lkml.org/lkml/2013/1/18/487
I didn't send a patch to make unmap_kernel_range exportable at that time
because zram was staging stuff and I thought VM function exporting
for staging stuff makes n
Hello Jet,
this is likely not CAN related, as
# CONFIG_CAN is not set
and all the CAN changes introduced by Marc's merge are not even compiled in
your setup.
So I assume the issue somewhere in the netlink or ipv6 stuff (see commit at
the end.
Best regards,
Oliver
On 13.05.2014 04:52, Jet Che
>> 2) Using wait-free coding techniques where readers help the writer if
>>they notice a stall. This is much hairier internal code, but makes
>>life easier on the callers. The basic procedure is:
>>
>>- A conventionally locked writer decides that the frequency is to be
>> adjuste
On Mon, May 12, 2014 at 07:08:22PM +0200, Oleg Nesterov wrote:
> On 05/08, Oleg Nesterov wrote:
> >
> > But let me send the initial changes first for review. If they pass the
> > review
> > and if nobody objects, I'd like to route them along with the pending uprobes
> > fixes.
>
> OK, nobody care
Hi Rob,
Today's linux-next merge of the dt-rh tree got a conflict in
drivers/of/selftest.c between commit 82c0f5897a87 ("of: selftest: add
deferred probe interrupt test") from Linus' tree and commit
ae7c987bc3a7 ("of/selftest: add testcase for nodes with same name and
address") from the dt-rh tree
From: Yongjian Xu
There is no case skb->len would be 0 or 'negative'.
Remove the check.
Signed-off-by: Yongjian Xu
---
drivers/net/ethernet/intel/e1000/e1000_main.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/drivers/net/ethernet/intel/e1000/e1000_main.c
b/drivers/net/ethernet/int
On 05/12/2014 11:23 AM, Viresh Kumar wrote:
> On 10 May 2014 21:47, Preeti U Murthy wrote:
>> On 05/09/2014 04:27 PM, Viresh Kumar wrote:
>>> On 9 May 2014 16:04, Preeti U Murthy wrote:
>
>>> Ideally, the device should have stopped events as we programmed it in
>>> ONESHOT mode. And should have
Hi Tejun,
On 2014/5/10 3:32, Tejun Heo wrote:
> After waiting for a child to finish offline,
> cgroup_subtree_control_write() jumps up to retry from after the input
> parsing and active protection breaking. This retry makes the
> scheduled locking update more difficult.
Could you explain this se
Thanks Lauraa for your answers.
I have few more queries below.
> Date: Mon, 12 May 2014 09:27:27 -0700
> From: lau...@codeaurora.org
> To: pint...@outlook.com; a...@arndb.de; linux-arm-ker...@lists.infradead.org
> CC: linux...@kvack.org; linux-kernel@vger.
Hi, Rafael
> From: Rafael J. Wysocki [mailto:r...@rjwysocki.net]
> Sent: Tuesday, May 13, 2014 9:31 AM
> To: Zheng, Lv
> Cc: robertbmo...@compuserve.com; Thomas Renninger (tr...@suse.de); Oswald
> Buddenhagen; ACPI Devel Maling List; Linux
> Kernel Mailing List
> Subject: Re: [PATCH] ACPICA: Reve
On Tue, May 13, 2014 at 07:16:24AM +0300, Stratos Karafotis wrote:
> On 12/05/2014 11:01 μμ, Yuyang Du wrote:
> > On Tue, May 13, 2014 at 06:59:42AM +0300, Stratos Karafotis wrote:
> >> Hi,
> >>
> >> On 12/05/2014 10:34 μμ, Yuyang Du wrote:
> >>> On Mon, May 12, 2014 at 11:30:03PM +0300, Stratos Ka
ble
> * cleaned up single bit set and masking code
> * removed statistics counters masking
> * removed unnecessary OOM message printing
> * fixed dma_map_single and dma_unmap_single size parameter
> * changed set bits macro body using new set_bits function
I just tested the v4 aga
On 12/05/2014 11:01 μμ, Yuyang Du wrote:
> On Tue, May 13, 2014 at 06:59:42AM +0300, Stratos Karafotis wrote:
>> Hi,
>>
>> On 12/05/2014 10:34 μμ, Yuyang Du wrote:
>>> On Mon, May 12, 2014 at 11:30:03PM +0300, Stratos Karafotis wrote:
On 09/05/2014 05:56 μμ, Stratos Karafotis wrote:
From: Stephen Rothwell
Date: Tue, 13 May 2014 13:53:22 +1000
> Today's linux-next merge of the net-next tree got a conflict in
> net/ipv6/xfrm6_output.c between commit 5596732fa8c1 ("xfrm: Fix crash
> with ipv6 IPsec tunnel and NAT") from the ipsec tree and commit
> 60ff746739bf ("net: rename loc
On Tue, May 13, 2014 at 06:59:42AM +0300, Stratos Karafotis wrote:
> Hi,
>
> On 12/05/2014 10:34 μμ, Yuyang Du wrote:
> > On Mon, May 12, 2014 at 11:30:03PM +0300, Stratos Karafotis wrote:
> >> On 09/05/2014 05:56 μμ, Stratos Karafotis wrote:
> >>
> >> Next performance state = min_perf + (max_perf
On Mon, May 12, 2014 at 8:53 PM, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the net-next tree got a conflict in
> net/ipv6/xfrm6_output.c between commit 5596732fa8c1 ("xfrm: Fix crash
> with ipv6 IPsec tunnel and NAT") from the ipsec tree and commit
> 60ff746739bf ("net: ren
On Tue, 2014-05-13 at 11:33 +0800, xuyongjia...@gmail.com wrote:
> From: Yongjian Xu
>
> skb->len is unsigned int, "skb->len <= 0" should be "(int)(skb->len) <= 0".
Why ?
Did you hit a case skb->len would be 0 or 'negative' ?
This test makes no sense, just remove it.
--
To unsubscribe from
Hi,
On 12/05/2014 10:34 μμ, Yuyang Du wrote:
> On Mon, May 12, 2014 at 11:30:03PM +0300, Stratos Karafotis wrote:
>> On 09/05/2014 05:56 μμ, Stratos Karafotis wrote:
>>
>> Next performance state = min_perf + (max_perf - min_perf) * load / 100
>>
> Hi,
>
> This formula is fundamentally broken. You
On Mon, May 12, 2014 at 08:45:32PM -, Thomas Gleixner wrote:
> Dave reported recently that the trinity syscall fuzzer triggers a
> warning in the rtmutex code via the futex syscall.
>
> It took me quite a while to understand the issue, until I was able to
> write a minimalistic reproducer.
>
> diff --git a/kernel/cgroup.c b/kernel/cgroup.c
> index 35daf89..b81e7c0 100644
> --- a/kernel/cgroup.c
> +++ b/kernel/cgroup.c
> @@ -2542,11 +2542,13 @@ static int cgroup_subtree_control_write(struct
> cgroup_subsys_state *dummy_css,
> int ssid, ret;
>
> /*
> - * Parse input -
Hi all,
Today's linux-next merge of the net-next tree got a conflict in
net/ipv6/xfrm6_output.c between commit 5596732fa8c1 ("xfrm: Fix crash
with ipv6 IPsec tunnel and NAT") from the ipsec tree and commit
60ff746739bf ("net: rename local_df to ignore_df") from the net-next
tree.
I fixed it up (s
On Tue, May 13, 2014 at 1:32 AM, Stephen Warren wrote:
> On 05/12/2014 02:26 AM, Alexandre Courbot wrote:
>> NVIDIA SHIELD embeds a USB controller. Compile the corresponding support
>
> USB controller or USB joystick?
I understand this sounds like "EHCI controller" here. Will reword.
>
>> as a m
On Mon, May 12, 2014 at 11:30:03PM +0300, Stratos Karafotis wrote:
> On 09/05/2014 05:56 μμ, Stratos Karafotis wrote:
>
> Next performance state = min_perf + (max_perf - min_perf) * load / 100
>
Hi,
This formula is fundamentally broken. You need to associate the load with its
frequency.
Thanks,
On 05/12/2014 07:44 PM, George Spelvin wrote:
> On Mon, 12 May 2014, John Stultz wrote:
>> First: My apologies, for some reason your mail got tagged as spam, so I
>> only saw it just now looking for another missing email.
> No problem; it happens to everyone. Curse you, Canter & Siegel!
>
>>> One
During our testing, we found that the cpu.shares doesn't work as
expected, the testing is:
X86 HOST:
12 CPU
GUEST(KVM):
6 VCPU
We create 3 GUEST, each with 1024 shares, the workload inside them is:
GUEST_1:
dbench 6
GUEST_2:
stress -c 6
GUEST_3:
stress -c
From: Yongjian Xu
skb->len is unsigned int, "skb->len <= 0" should be "(int)(skb->len) <= 0".
Signed-off-by: Yongjian Xu
---
drivers/net/ethernet/intel/e1000/e1000_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/intel/e1000/e1000_main.c
b/driver
This is the driver for the Dialog DA9211 Multi-phase 12A DC-DC Buck
Converter regulator. It communicates via an I2C bus to the device.
Signed-off-by: James Ban
---
This patch is relative to linux-next repository tag next-20140509
drivers/regulator/Kconfig| 10 +
drivers/regulator/
Hi Al,
Today's linux-next merge of the vfs tree got a conflict in
fs/cifs/cifsfs.c between commit 485c4e72d0f1 ("cifs: revalidate mapping
prior to satisfying aio_read request") from the cifs tree and commits
aad4f8bb42af ("switch simple generic_file_aio_read() users to
->read_iter()") and 3dae8750
On 05/12/2014 08:01 PM, George Spelvin wrote:
>> CONFIG_NTP_PPS not CONFIG_SMP, right?
> D'oh, yes. I just noticed that there were two versions and one was
> broken. Somehow my search for the enclosing #ifdef was completely broken.
> (I could swear I saw CONFIG_SMP, but looking now it's not even
From: Yang Wei
We do not need to trace read_sched_clock function,
so add notrace attribute for this function.
Signed-off-by: Yang Wei
---
drivers/clocksource/dw_apb_timer_of.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clocksource/dw_apb_timer_of.c
b/driver
On Sun, May 11, 2014 at 9:19 PM, Richard Lee wrote:
> For the IO mapping, for the same physical address space maybe
> mapped more than one time, for example, in some SoCs:
> 0x2000 ~ 0x20001000: are global control IO physical map,
> and this range space will be used by many drivers.
What addr
From: Yang Wei
We do not need to trace read_sched_clock function,
so add notrace attribute for this function.
Signed-off-by: Yang Wei
---
drivers/clocksource/dw_apb_timer_of.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clocksource/dw_apb_timer_of.c
b/driver
Signed-off-by: Cody P Schafer
---
arch/powerpc/platforms/pseries/Kconfig | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/arch/powerpc/platforms/pseries/Kconfig
b/arch/powerpc/platforms/pseries/Kconfig
index 2cb8b77..e00dd4d 100644
--- a/arch/powerpc/pla
Vendor ID 0x10de0071 is used by a yet-to-be-named GPU chip.
Signed-off-by: Aaron Plattner
Cc: Takashi Iwai
Cc: Jaroslav Kysela
Cc: Stephen Warren
---
I verified that the patch_nvhdmi code is still needed for this chip.
sound/pci/hda/patch_hdmi.c | 2 ++
1 file changed, 2 insertions(+)
diff
On Mon, May 12, 2014 at 10:04:29AM -0700, Laura Abbott wrote:
> Hi,
>
> On 5/7/2014 5:32 PM, Joonsoo Kim wrote:
> > CMA is introduced to provide physically contiguous pages at runtime.
> > For this purpose, it reserves memory at boot time. Although it reserve
> > memory, this reserved memory can b
> CONFIG_NTP_PPS not CONFIG_SMP, right?
D'oh, yes. I just noticed that there were two versions and one was
broken. Somehow my search for the enclosing #ifdef was completely broken.
(I could swear I saw CONFIG_SMP, but looking now it's not even mentioned
in the file; maybe I switched editor windo
Hey Joonsoo,
On Thu, May 08, 2014 at 09:32:23AM +0900, Joonsoo Kim wrote:
> CMA is introduced to provide physically contiguous pages at runtime.
> For this purpose, it reserves memory at boot time. Although it reserve
> memory, this reserved memory can be used for movable memory allocation
> reque
Add const delcarations where possible to make clear that the call chains
are not permitted to write to the structure.
It is not expected to improve generated code; the purpose is to document
the rules for who's allowed to modify the timekeeper state (and must
hold the associated locks) more clearl
read_seqlock_begin returns an int, so using "unsigned long" to
hold the return value is harmless, but a waste.
Signed-off-by: George Spelvin
---
kernel/time/timekeeping.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/kernel/time/timekeeping.c b/kernel
On Mon, 12 May 2014, John Stultz wrote:
> First: My apologies, for some reason your mail got tagged as spam, so I
> only saw it just now looking for another missing email.
No problem; it happens to everyone. Curse you, Canter & Siegel!
>> One misfeature in the timekeeping seqlock code I noticed
Hi jiri or Arnaldo,
It seems Peter really do not like the usage of
sched_wakeup(.success), and
don't plan to support it in scheduler any more. Please consider to
append this patch
too when you take the patch from Peter. Thanx :)
On 05/13/2014 10:38 AM, Dongsheng Yang wrote:
As we do not
As we do not use .success in sched_wakeup event any more, then
we can not guarantee that the task when wakeup event happen is
out of run queue. So the message of nr_state_machine_bugs is
not correct.
Signed-off-by: Dongsheng Yang
---
tools/perf/builtin-sched.c | 19 ---
1 file ch
On 12 May 05:50 PM, Brian Norris wrote:
> > There are some guidelines about attributes in
> > 'Documentation/filesystems/sysfs.txt'
> > Though it's acceptable to put array of values of the "same type" in single
> > sysfs file,
> > But I'm still not confident on having all members of 'struct ecc_s
On Mon, May 12, 2014 at 07:29:47PM -0500, Rob Herring wrote:
> From: Rob Herring
>
> Adding function type checking to CLK_OF_DECLARE found a type mismatch with
> mx35_clocks_init_dt. The function should return void.
>
> Signed-off-by: Rob Herring
> Cc: Shawn Guo
> Cc: Sascha Hauer
Acked-by:
On Fri, May 09, 2014 at 02:39:20PM +0200, Marek Szyprowski wrote:
> Hello,
>
> On 2014-05-08 02:32, Joonsoo Kim wrote:
> >This series tries to improve CMA.
> >
> >CMA is introduced to provide physically contiguous pages at runtime
> >without reserving memory area. But, current implementation works
g the latest
>>> >> -next
>>> >> kernel I've stumbled on the following spew:
>>> >>
>>> >> [ 1297.886670] WARNING: CPU: 0 PID: 190 at kernel/workqueue.c:2176
>>> >> process_one_work+0xb5/0x6f0()
>>> >
On Sun, Apr 06, 2014 at 11:37:44PM +0200, Antonio Ospite wrote:
> On Sun, 6 Apr 2014 13:24:36 -0700
> Dmitry Torokhov wrote:
>
> > On Sun, Apr 06, 2014 at 12:54:50AM +0400, Alexey Khoroshilov wrote:
> > > pcap_keys_handler() calls ezx_pcap_read() that calls mutex_lock().
> > > pcap_keys_handler()
; [ 1297.886670] WARNING: CPU: 0 PID: 190 at kernel/workqueue.c:2176
>> process_one_work+0xb5/0x6f0()
>> [ 1297.889216] Modules linked in:
>> [ 1297.890306] CPU: 0 PID: 190 Comm: kworker/3:0 Not tainted
>> 3.15.0-rc5-next-20140512-sasha-00019-ga20bc00-dirty #456
&
Hi Linus,
Please pull hwmon fixes for Linux 3.15-rc6 from signed tag:
git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git
hwmon-for-linus
Thanks,
Guenter
--
The following changes since commit d6d211db37e75de2ddc3a4f979038c40df7cc79c:
Linux 3.15-rc5 (2014-05-09 13:
Hi all,
Today's linux-next merge of the powerpc tree got a conflict in
arch/powerpc/kernel/exceptions-64s.S between commit 0be9d8b61c0c
("powerpc/ppc64: Allow allmodconfig to build (finally !)") from the
fixes tree and commits b1576fec7f4d ("powerpc: No need to use dot
symbols when branching to a
> On Mon, May 12, 2014 at 3:51 PM, Arnd Bergmann wrote:
> On Monday 12 May 2014 10:19:55 Richard Lee wrote:
>> For the IO mapping, for the same physical address space maybe
>> mapped more than one time, for example, in some SoCs:
>> 0x2000 ~ 0x20001000: are global control IO physical map,
>> a
On Thu, May 08, 2014 at 03:34:33PM -0700, Andrew Morton wrote:
> On Thu, 8 May 2014 15:19:37 +0900 Minchan Kim wrote:
>
> > > I also think that VM_DEBUG overhead isn't problem because of same
> > > reason from Vlastimil.
> >
> > Guys, please read this.
> >
> > https://lkml.org/lkml/2013/7/17/59
On Friday, May 09, 2014 10:25 AM, Tony Lindgren wrote:
>
> If the GPIO for the backlight is on an I2C chip, we currently
> get nasty warnings like this during the boot:
>
> WARNING: CPU: 0 PID: 6 at drivers/gpio/gpiolib.c:2364
> gpiod_set_raw_value+0x40/0x4c()
> Modules linked in:
> CPU: 0 PID:
On Mon, 2014-05-12 at 09:44 +0200, Michael Kerrisk (man-pages) wrote:
> Hi Davidlohr,
>
> On Sun, May 11, 2014 at 10:46 PM, Davidlohr Bueso wrote:
> > On Fri, 2014-05-09 at 10:44 +0200, Michael Kerrisk (man-pages) wrote:
> >> On Wed, May 7, 2014 at 9:17 PM, Davidlohr Bueso wrote:
> >> > This is
On Mon, May 12, 2014 at 10:28:25AM +0200, Vlastimil Babka wrote:
> On 05/08/2014 07:54 AM, Joonsoo Kim wrote:
> >On Wed, May 07, 2014 at 04:59:07PM +0200, Vlastimil Babka wrote:
> >>On 05/07/2014 03:33 AM, Minchan Kim wrote:
> >>>On Mon, May 05, 2014 at 05:50:46PM +0200, Vlastimil Babka wrote:
> >>
Quoting Maxime Ripard (2014-05-12 12:34:27)
> The A31 USB clock slightly differ from its older counterparts, mostly because
> it has a different gate for each PHY, while the older one had a single gate
> for
> all the phy.
>
> Signed-off-by: Maxime Ripard
> Reviewed-by: Hans de Goede
Acked-by:
Quoting Arnd Bergmann (2014-04-23 06:31:06)
> On Wednesday 23 April 2014 15:17:20 Maxime Ripard wrote:
> > > > +#include
> > > > #include
> > > > #include
> > > >
> > > > @@ -19,9 +20,17 @@
> > > >
> > > > static void __init sun4i_dt_init(void)
> > > > {
> > > > + struct clk *clk;
>
> On Mon, May 12, 2014 at 06:42:37PM +0900, Namjae Jeon wrote:
> >
> > > > +xfs_bmap_split_extent(
> > > > + struct xfs_inode*ip,
> > > > + xfs_fileoff_t split_fsb,
> > > > + xfs_extnum_t*split_ext)
> > > > +{
> > > > + struct xfs_mount
Signed-off-by: abdoulaye berthe
---
drivers/gpio/gpio-timberdale.c | 47 ++
1 file changed, 16 insertions(+), 31 deletions(-)
diff --git a/drivers/gpio/gpio-timberdale.c b/drivers/gpio/gpio-timberdale.c
index f9a8fbd..efc7c12 100644
--- a/drivers/gpio/gpio
On Tuesday, May 13, 2014 01:05:59 AM Zheng, Lv wrote:
> Hi,
>
> > From: Rafael J. Wysocki [mailto:r...@rjwysocki.net]
> > Sent: Tuesday, May 13, 2014 8:09 AM
> >
> > On Monday, May 12, 2014 08:51:36 AM Zheng, Lv wrote:
> > > Hi, Rafael
> > >
> > > I checked the bug.
> > >
> > > The dmesg of the k
On Mon, May 12, 2014 at 11:09:25AM +0200, Vlastimil Babka wrote:
> On 05/08/2014 07:28 AM, Joonsoo Kim wrote:
> >On Wed, May 07, 2014 at 02:09:10PM +0200, Vlastimil Babka wrote:
> >>The compaction free scanner in isolate_freepages() currently remembers PFN
> >>of
> >>the highest pageblock where it
On Mon, May 12, 2014 at 10:04:29AM -0700, Laura Abbott wrote:
> Hi,
>
> On 5/7/2014 5:32 PM, Joonsoo Kim wrote:
> > CMA is introduced to provide physically contiguous pages at runtime.
> > For this purpose, it reserves memory at boot time. Although it reserve
> > memory, this reserved memory can b
From: Rafael J. Wysocki
Currently, some subsystems (e.g. PCI and the ACPI PM domain) have to
resume all runtime-suspended devices during system suspend, mostly
because those devices may need to be reprogrammed due to different
wakeup settings for system sleep and for runtime PM.
For some devices
From: Rafael J. Wysocki
Rework the ACPI PM domain's PM callbacks to avoid resuming devices
during system suspend (in order to modify their wakeup settings etc.)
if that isn't necessary.
Signed-off-by: Rafael J. Wysocki
---
drivers/acpi/device_pm.c | 43 ---
Hi All,
We've discussed that at length here:
http://marc.info/?t=13995046903&r=1&w=4
but I'm starting a new thread to refresh things a bit.
This is about adding a mechanism allowing us to avoid runtime-suspended
devices during system suspend. The reason why it has to touch the PM core
is b
From: Rafael J. Wysocki
Move the invocation of the runtime PM barrier during system suspend
(or hibernation) from __device_suspend() to device_prepare() to make
all runtime PM transitions in progress complete before executing
->prepare() callbacks for devices.
That will allow those callbacks to
Hi,
> From: Rafael J. Wysocki [mailto:r...@rjwysocki.net]
> Sent: Tuesday, May 13, 2014 8:09 AM
>
> On Monday, May 12, 2014 08:51:36 AM Zheng, Lv wrote:
> > Hi, Rafael
> >
> > I checked the bug.
> >
> > The dmesg of the kernel without the bisected commit:
> > [0.00] ACPI BIOS Warning (bug
On 05/12/2014 02:08 PM, Josef Gajdusek wrote:
Had to fix wrong variable being printed in show_bit(). After that, everything
on the 1412 seems to work fine including alarms.
- return sprintf(buf, "%d\n", !!(retval & sda->index));
+ return sprintf(buf, "%d\n", !!(val & sda->index));
+ Greg KH, LKML
For context:
http://thread.gmane.org/gmane.linux.drivers.mtd/52517/focus=52518
On Tue, Apr 15, 2014 at 11:13:52AM +, Pekon Gupta wrote:
> >From: Ezequiel Garcia
> >>On Mar 27, Gupta, Pekon wrote:
> >> >
> >> >+static ssize_t mtd_ecc_stats_show(struct device *dev,
> >> >+
On Mon, May 12, 2014 at 04:15:11PM +0200, Vlastimil Babka wrote:
> Compaction uses compact_checklock_irqsave() function to periodically check for
> lock contention and need_resched() to either abort async compaction, or to
> free the lock, schedule and retake the lock. When aborting, cc->contended
If we don't call mutex_acquire at the beginning of console_unblank, we can run
into a lockup on the logbuf_lock between console_unlock and printk during panic.
What happens in console_unlock is:
-locks logbuf_lock
-calls mutex_release
-which calls printk
-which locks logbuf_lock
This fixes the
1 - 100 of 678 matches
Mail list logo
