[tip:irq/urgent] irqchip/metag-ext: Improve function-level documentation

2016-10-05 Thread tip-bot for Julia Lawall
Commit-ID: 65543b3353e7d29d258aac4190cda6a2f49abeb3 Gitweb: http://git.kernel.org/tip/65543b3353e7d29d258aac4190cda6a2f49abeb3 Author: Julia Lawall AuthorDate: Sat, 1 Oct 2016 21:46:31 +0200 Committer: Thomas Gleixner CommitDate: Wed, 5 Oct

[tip:irq/urgent] irqchip/metag-ext: Improve function-level documentation

2016-10-05 Thread tip-bot for Julia Lawall
Commit-ID: 65543b3353e7d29d258aac4190cda6a2f49abeb3 Gitweb: http://git.kernel.org/tip/65543b3353e7d29d258aac4190cda6a2f49abeb3 Author: Julia Lawall AuthorDate: Sat, 1 Oct 2016 21:46:31 +0200 Committer: Thomas Gleixner CommitDate: Wed, 5 Oct 2016 11:53:35 +0200 irqchip/metag-ext:

[tip:irq/urgent] irqchip/vic: Improve function-level documentation

2016-10-05 Thread tip-bot for Julia Lawall
Commit-ID: 0ff4deee9cbb60b541f1b6abf53e32812cfa42ca Gitweb: http://git.kernel.org/tip/0ff4deee9cbb60b541f1b6abf53e32812cfa42ca Author: Julia Lawall AuthorDate: Sat, 1 Oct 2016 21:46:30 +0200 Committer: Thomas Gleixner CommitDate: Wed, 5 Oct

[tip:irq/urgent] irqchip/vic: Improve function-level documentation

2016-10-05 Thread tip-bot for Julia Lawall
Commit-ID: 0ff4deee9cbb60b541f1b6abf53e32812cfa42ca Gitweb: http://git.kernel.org/tip/0ff4deee9cbb60b541f1b6abf53e32812cfa42ca Author: Julia Lawall AuthorDate: Sat, 1 Oct 2016 21:46:30 +0200 Committer: Thomas Gleixner CommitDate: Wed, 5 Oct 2016 11:53:35 +0200 irqchip/vic: Improve

Re: Regression in next with ext4 oops

2016-10-05 Thread Kalle Valo
Tony Lindgren writes: > * Kalle Valo [161004 12:42]: >> Tony Lindgren writes: >> >> > And the patch below seems to fix the issue as the driver is now >> > using devm_kzalloc. Will do some more testing and then will post >> > a proper

Re: Regression in next with ext4 oops

2016-10-05 Thread Kalle Valo
Tony Lindgren writes: > * Kalle Valo [161004 12:42]: >> Tony Lindgren writes: >> >> > And the patch below seems to fix the issue as the driver is now >> > using devm_kzalloc. Will do some more testing and then will post >> > a proper patch. The same issue might be there for SPI glue also. >>

Re: [PATCH] oom: print nodemask in the oom report

2016-10-05 Thread Vlastimil Babka
On 10/04/2016 05:12 PM, Michal Hocko wrote: Ah, I wasn't clear. What I questioned is the fallback to cpusets for NULL nodemask: nodemask_t *nm = (oc->nodemask) ? oc->nodemask : _current_mems_allowed; Well no nodemask means there is no mempolicy so either all nodes can be used or they are

Re: [PATCH] oom: print nodemask in the oom report

2016-10-05 Thread Vlastimil Babka
On 10/04/2016 05:12 PM, Michal Hocko wrote: Ah, I wasn't clear. What I questioned is the fallback to cpusets for NULL nodemask: nodemask_t *nm = (oc->nodemask) ? oc->nodemask : _current_mems_allowed; Well no nodemask means there is no mempolicy so either all nodes can be used or they are

[PATCH] ARM: dt: sun8i-h3: Add sunxi-sid to dts for sun8i-h3

2016-10-05 Thread Corentin Labbe
This patch add support for the sunxi-sid driver to the device tree for sun8i-h3. Signed-off-by: Corentin Labbe --- arch/arm/boot/dts/sun8i-h3.dtsi | 5 + 1 file changed, 5 insertions(+) diff --git a/arch/arm/boot/dts/sun8i-h3.dtsi

[PATCH] ARM: dt: sun8i-h3: Add sunxi-sid to dts for sun8i-h3

2016-10-05 Thread Corentin Labbe
This patch add support for the sunxi-sid driver to the device tree for sun8i-h3. Signed-off-by: Corentin Labbe --- arch/arm/boot/dts/sun8i-h3.dtsi | 5 + 1 file changed, 5 insertions(+) diff --git a/arch/arm/boot/dts/sun8i-h3.dtsi b/arch/arm/boot/dts/sun8i-h3.dtsi index 9f58bb4..abfd29c

Re: [RFC][PATCH 6/7] printk: use alternative printk buffers

2016-10-05 Thread Petr Mladek
On Wed 2016-10-05 10:27:14, Sergey Senozhatsky wrote: > On (10/04/16 16:52), Petr Mladek wrote: > > > > > > Or is there any other catch that I do not see at the moment? > > > > And there is :-( The above logic looked at the problem only from > > one side. It was about errors starting from the

Re: [RFC][PATCH 6/7] printk: use alternative printk buffers

2016-10-05 Thread Petr Mladek
On Wed 2016-10-05 10:27:14, Sergey Senozhatsky wrote: > On (10/04/16 16:52), Petr Mladek wrote: > > > > > > Or is there any other catch that I do not see at the moment? > > > > And there is :-( The above logic looked at the problem only from > > one side. It was about errors starting from the

[tip:x86/urgent] x86/syscalls: Remove bash-isms in syscall table generator

2016-10-05 Thread tip-bot for sylvain.bertr...@gmail.com
Commit-ID: 2df0e78b44e2cbbaa1e319cbca34f23599a4daa0 Gitweb: http://git.kernel.org/tip/2df0e78b44e2cbbaa1e319cbca34f23599a4daa0 Author: sylvain.bertr...@gmail.com AuthorDate: Thu, 29 Sep 2016 16:22:34 + Committer: Thomas Gleixner

[tip:x86/urgent] x86/vmware: Skip lapic calibration on VMware

2016-10-05 Thread tip-bot for Renat Valiullin
Commit-ID: b91688f528fe96e09d17e6d87c1b2805eb0c445e Gitweb: http://git.kernel.org/tip/b91688f528fe96e09d17e6d87c1b2805eb0c445e Author: Renat Valiullin AuthorDate: Tue, 4 Oct 2016 13:11:48 -0700 Committer: Thomas Gleixner CommitDate: Wed, 5 Oct

[tip:x86/urgent] x86/syscalls: Remove bash-isms in syscall table generator

2016-10-05 Thread tip-bot for sylvain.bertr...@gmail.com
Commit-ID: 2df0e78b44e2cbbaa1e319cbca34f23599a4daa0 Gitweb: http://git.kernel.org/tip/2df0e78b44e2cbbaa1e319cbca34f23599a4daa0 Author: sylvain.bertr...@gmail.com AuthorDate: Thu, 29 Sep 2016 16:22:34 + Committer: Thomas Gleixner CommitDate: Wed, 5 Oct 2016 11:34:25 +0200

[tip:x86/urgent] x86/vmware: Skip lapic calibration on VMware

2016-10-05 Thread tip-bot for Renat Valiullin
Commit-ID: b91688f528fe96e09d17e6d87c1b2805eb0c445e Gitweb: http://git.kernel.org/tip/b91688f528fe96e09d17e6d87c1b2805eb0c445e Author: Renat Valiullin AuthorDate: Tue, 4 Oct 2016 13:11:48 -0700 Committer: Thomas Gleixner CommitDate: Wed, 5 Oct 2016 11:43:30 +0200 x86/vmware: Skip

Re: [Xen-devel] [PATCH] xen/x86: Initialize per_cpu(xen_vcpu, 0) a little earlier

2016-10-05 Thread David Vrabel
On 02/10/16 23:45, Boris Ostrovsky wrote: > xen_cpuhp_setup() calls mutex_lock() which, when CONFIG_DEBUG_MUTEXES > is defined, ends up calling xen_save_fl(). That routine expects > per_cpu(xen_vcpu, 0) to be already initialized. Applied to for-linus-4.9, thanks. David

Re: [Xen-devel] [PATCH] xen/x86: Initialize per_cpu(xen_vcpu, 0) a little earlier

2016-10-05 Thread David Vrabel
On 02/10/16 23:45, Boris Ostrovsky wrote: > xen_cpuhp_setup() calls mutex_lock() which, when CONFIG_DEBUG_MUTEXES > is defined, ends up calling xen_save_fl(). That routine expects > per_cpu(xen_vcpu, 0) to be already initialized. Applied to for-linus-4.9, thanks. David

Re: [PATCH 03/14] ASoC: sun4i-i2s: Add apb reset

2016-10-05 Thread Mylene Josserand
Hello, On 04/10/2016 17:42, Maxime Ripard wrote: Hi, On Tue, Oct 04, 2016 at 02:15:16PM +0200, Thomas Petazzoni wrote: Hello, On Tue, 4 Oct 2016 11:46:16 +0200, Mylène Josserand wrote: #include #include @@ -589,6 +590,7 @@ static int sun4i_i2s_probe(struct platform_device *pdev) {

Re: [PATCH 03/14] ASoC: sun4i-i2s: Add apb reset

2016-10-05 Thread Mylene Josserand
Hello, On 04/10/2016 17:42, Maxime Ripard wrote: Hi, On Tue, Oct 04, 2016 at 02:15:16PM +0200, Thomas Petazzoni wrote: Hello, On Tue, 4 Oct 2016 11:46:16 +0200, Mylène Josserand wrote: #include #include @@ -589,6 +590,7 @@ static int sun4i_i2s_probe(struct platform_device *pdev) {

[PATCH] gpio/gpio-mxs : Unmap region obtained by of_iomap

2016-10-05 Thread Arvind Yadav
Free memory mapping, if mxs_gpio_probe is not successful. Signed-off-by: Arvind Yadav --- drivers/gpio/gpio-mxs.c |8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/drivers/gpio/gpio-mxs.c b/drivers/gpio/gpio-mxs.c index b9daa0b..ee17248

[PATCH] gpio/gpio-mxs : Unmap region obtained by of_iomap

2016-10-05 Thread Arvind Yadav
Free memory mapping, if mxs_gpio_probe is not successful. Signed-off-by: Arvind Yadav --- drivers/gpio/gpio-mxs.c |8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/drivers/gpio/gpio-mxs.c b/drivers/gpio/gpio-mxs.c index b9daa0b..ee17248 100644 ---

Re: [PATCH 1/7 v4] sched: factorize attach entity

2016-10-05 Thread Dietmar Eggemann
On 09/26/2016 01:19 PM, Vincent Guittot wrote: Factorize post_init_entity_util_avg and part of attach_task_cfs_rq in one function attach_entity_cfs_rq Signed-off-by: Vincent Guittot --- kernel/sched/fair.c | 19 +++ 1 file changed, 11 insertions(+),

Re: [PATCH 1/7 v4] sched: factorize attach entity

2016-10-05 Thread Dietmar Eggemann
On 09/26/2016 01:19 PM, Vincent Guittot wrote: Factorize post_init_entity_util_avg and part of attach_task_cfs_rq in one function attach_entity_cfs_rq Signed-off-by: Vincent Guittot --- kernel/sched/fair.c | 19 +++ 1 file changed, 11 insertions(+), 8 deletions(-) diff --git

Re: [PATCH 02/14] clk: ccu-sun8i-a33: Add CLK_SET_RATE_PARENT to ac-dig

2016-10-05 Thread Mylene Josserand
Hello Thomas, On 04/10/2016 14:12, Thomas Petazzoni wrote: Hello, On Tue, 4 Oct 2016 11:46:15 +0200, Mylène Josserand wrote: Add the flag CLK_SET_RATE_PARENT to 'ac-dig' clock. There is no need to repeat the commit title inside the commit log itself. What would be more useful is to

Re: [PATCH 02/14] clk: ccu-sun8i-a33: Add CLK_SET_RATE_PARENT to ac-dig

2016-10-05 Thread Mylene Josserand
Hello Thomas, On 04/10/2016 14:12, Thomas Petazzoni wrote: Hello, On Tue, 4 Oct 2016 11:46:15 +0200, Mylène Josserand wrote: Add the flag CLK_SET_RATE_PARENT to 'ac-dig' clock. There is no need to repeat the commit title inside the commit log itself. What would be more useful is to

Re: [PATCH 3/4] mm, oom: do not rely on TIF_MEMDIE for exit_oom_victim

2016-10-05 Thread Michal Hocko
On Tue 04-10-16 18:21:14, Oleg Nesterov wrote: [...] > so this can't detect the multi-threaded group exit, and ... > > > list_for_each_entry_safe(p, n, , ptrace_entry) { > > list_del_init(>ptrace_entry); > > - release_task(p); > > + if (release_task(p) && p ==

Re: [PATCH 3/4] mm, oom: do not rely on TIF_MEMDIE for exit_oom_victim

2016-10-05 Thread Michal Hocko
On Tue 04-10-16 18:21:14, Oleg Nesterov wrote: [...] > so this can't detect the multi-threaded group exit, and ... > > > list_for_each_entry_safe(p, n, , ptrace_entry) { > > list_del_init(>ptrace_entry); > > - release_task(p); > > + if (release_task(p) && p ==

Re: BUG_ON() in workingset_node_shadows_dec() triggers

2016-10-05 Thread Johannes Weiner
On Wed, Oct 05, 2016 at 11:25:34AM +0200, Johannes Weiner wrote: > Patch below. NOTE: I'm traveling without access to my test rig right > now and so I have only lightly tested this on my laptop. I'm also > jetlagged like crazy, so please triple check my thinking. The patch > does fix the

Re: BUG_ON() in workingset_node_shadows_dec() triggers

2016-10-05 Thread Johannes Weiner
On Wed, Oct 05, 2016 at 11:25:34AM +0200, Johannes Weiner wrote: > Patch below. NOTE: I'm traveling without access to my test rig right > now and so I have only lightly tested this on my laptop. I'm also > jetlagged like crazy, so please triple check my thinking. The patch > does fix the

Re: [PATCH v3 2/4] drivers: iio: ti_am335x_adc: add dma support

2016-10-05 Thread Peter Ujfalusi
On 10/05/16 12:04, Mugunthan V N wrote: > This patch adds the required pieces to ti_am335x_adc driver for > DMA support > > Signed-off-by: Mugunthan V N > --- > drivers/iio/adc/ti_am335x_adc.c | 148 > ++- >

Re: [PATCH v3 2/4] drivers: iio: ti_am335x_adc: add dma support

2016-10-05 Thread Peter Ujfalusi
On 10/05/16 12:04, Mugunthan V N wrote: > This patch adds the required pieces to ti_am335x_adc driver for > DMA support > > Signed-off-by: Mugunthan V N > --- > drivers/iio/adc/ti_am335x_adc.c | 148 > ++- > include/linux/mfd/ti_am335x_tscadc.h | 7 ++ >

Re: BUG_ON() in workingset_node_shadows_dec() triggers

2016-10-05 Thread Johannes Weiner
On Tue, Oct 04, 2016 at 06:21:37PM -0700, Linus Torvalds wrote: > On Tue, Oct 4, 2016 at 2:32 AM, Johannes Weiner wrote: > > > > In the workingset code, if we detect radix tree nodes in a state in > > which they shouldn't be on the shadow node LRU, we could simply warn, > >

Re: BUG_ON() in workingset_node_shadows_dec() triggers

2016-10-05 Thread Johannes Weiner
On Tue, Oct 04, 2016 at 06:21:37PM -0700, Linus Torvalds wrote: > On Tue, Oct 4, 2016 at 2:32 AM, Johannes Weiner wrote: > > > > In the workingset code, if we detect radix tree nodes in a state in > > which they shouldn't be on the shadow node LRU, we could simply warn, > > abort the reclaim

Re: [PATCH] coredump: fix unfreezable coredumping task

2016-10-05 Thread Michal Hocko
On Tue 04-10-16 18:13:05, Oleg Nesterov wrote: > On 10/04, Michal Hocko wrote: > > > > On Fri 30-09-16 14:47:41, Oleg Nesterov wrote: > > > On 09/30, Andrey Ryabinin wrote: > > > > > > > > @@ -423,7 +424,9 @@ static int coredump_wait(int exit_code, struct > > > > core_state *core_state) > > > >

Re: [PATCH] coredump: fix unfreezable coredumping task

2016-10-05 Thread Michal Hocko
On Tue 04-10-16 18:13:05, Oleg Nesterov wrote: > On 10/04, Michal Hocko wrote: > > > > On Fri 30-09-16 14:47:41, Oleg Nesterov wrote: > > > On 09/30, Andrey Ryabinin wrote: > > > > > > > > @@ -423,7 +424,9 @@ static int coredump_wait(int exit_code, struct > > > > core_state *core_state) > > > >

Re: [PATCH V2 1/3] mfd: wm8994-core: don't split lines unnecessarily

2016-10-05 Thread Lee Jones
On Wed, 05 Oct 2016, Viresh Kumar wrote: > On 05-10-16, 09:49, Lee Jones wrote: > > You are experienced enough to know better than this. > > :) > > > a) Contentless pings have never been acceptable. If you genuinely > > think a patch has been forgotten you should resubmit with a > > [RESEND].

Re: [PATCH V2 1/3] mfd: wm8994-core: don't split lines unnecessarily

2016-10-05 Thread Lee Jones
On Wed, 05 Oct 2016, Viresh Kumar wrote: > On 05-10-16, 09:49, Lee Jones wrote: > > You are experienced enough to know better than this. > > :) > > > a) Contentless pings have never been acceptable. If you genuinely > > think a patch has been forgotten you should resubmit with a > > [RESEND].

[PATCH v3 2/4] drivers: iio: ti_am335x_adc: add dma support

2016-10-05 Thread Mugunthan V N
This patch adds the required pieces to ti_am335x_adc driver for DMA support Signed-off-by: Mugunthan V N --- drivers/iio/adc/ti_am335x_adc.c | 148 ++- include/linux/mfd/ti_am335x_tscadc.h | 7 ++ 2 files changed, 152 insertions(+), 3

[PATCH v3 2/4] drivers: iio: ti_am335x_adc: add dma support

2016-10-05 Thread Mugunthan V N
This patch adds the required pieces to ti_am335x_adc driver for DMA support Signed-off-by: Mugunthan V N --- drivers/iio/adc/ti_am335x_adc.c | 148 ++- include/linux/mfd/ti_am335x_tscadc.h | 7 ++ 2 files changed, 152 insertions(+), 3 deletions(-) diff

[PATCH v3 4/4] ARM: dts: am4372: add DMA properties for tscadc

2016-10-05 Thread Mugunthan V N
Add DMA properties for tscadc Signed-off-by: Mugunthan V N --- arch/arm/boot/dts/am4372.dtsi | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/boot/dts/am4372.dtsi b/arch/arm/boot/dts/am4372.dtsi index 0fadae5..6094d17 100644 --- a/arch/arm/boot/dts/am4372.dtsi

[PATCH v3 3/4] ARM: dts: am33xx: add DMA properties for tscadc

2016-10-05 Thread Mugunthan V N
Add DMA properties for tscadc Signed-off-by: Mugunthan V N --- arch/arm/boot/dts/am33xx.dtsi | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi index 98748c6..6d607b8 100644 --- a/arch/arm/boot/dts/am33xx.dtsi

[PATCH v3 4/4] ARM: dts: am4372: add DMA properties for tscadc

2016-10-05 Thread Mugunthan V N
Add DMA properties for tscadc Signed-off-by: Mugunthan V N --- arch/arm/boot/dts/am4372.dtsi | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/boot/dts/am4372.dtsi b/arch/arm/boot/dts/am4372.dtsi index 0fadae5..6094d17 100644 --- a/arch/arm/boot/dts/am4372.dtsi +++

[PATCH v3 3/4] ARM: dts: am33xx: add DMA properties for tscadc

2016-10-05 Thread Mugunthan V N
Add DMA properties for tscadc Signed-off-by: Mugunthan V N --- arch/arm/boot/dts/am33xx.dtsi | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/boot/dts/am33xx.dtsi b/arch/arm/boot/dts/am33xx.dtsi index 98748c6..6d607b8 100644 --- a/arch/arm/boot/dts/am33xx.dtsi +++

[PATCH v3 0/4] Add DMA support for ti_am335x_adc driver

2016-10-05 Thread Mugunthan V N
The ADC has a 64 word depth fifo length which holds the ADC data till the CPU reads. So when a user program needs a large ADC data to operate on, then it has to do multiple reads to get its buffer. Currently if the application asks for 4 samples per channel with all 8 channels are enabled, kernel

[PATCH v3 0/4] Add DMA support for ti_am335x_adc driver

2016-10-05 Thread Mugunthan V N
The ADC has a 64 word depth fifo length which holds the ADC data till the CPU reads. So when a user program needs a large ADC data to operate on, then it has to do multiple reads to get its buffer. Currently if the application asks for 4 samples per channel with all 8 channels are enabled, kernel

[PATCH v3 1/4] mfd: ti_am335x_tscadc: store physical address

2016-10-05 Thread Mugunthan V N
store the physical address of the device in its priv to use it for DMA addressing in the client drivers. Signed-off-by: Mugunthan V N --- drivers/mfd/ti_am335x_tscadc.c | 1 + include/linux/mfd/ti_am335x_tscadc.h | 1 + 2 files changed, 2 insertions(+) diff --git

[PATCH v3 1/4] mfd: ti_am335x_tscadc: store physical address

2016-10-05 Thread Mugunthan V N
store the physical address of the device in its priv to use it for DMA addressing in the client drivers. Signed-off-by: Mugunthan V N --- drivers/mfd/ti_am335x_tscadc.c | 1 + include/linux/mfd/ti_am335x_tscadc.h | 1 + 2 files changed, 2 insertions(+) diff --git

Re: Problem with VMAP_STACK=y

2016-10-05 Thread Mauro Carvalho Chehab
Em Wed, 5 Oct 2016 09:50:42 +0200 (CEST) Jiri Kosina escreveu: > On Wed, 5 Oct 2016, Patrick Boettcher wrote: > > > > > Thanks for the quick response. > > > > Drivers are: > > > > dvb_core, dvb_usb, dbv_usb_cynergyT2 > > > > > > This dbv_usb_cynergyT2 is not from Linus'

Re: Problem with VMAP_STACK=y

2016-10-05 Thread Mauro Carvalho Chehab
Em Wed, 5 Oct 2016 09:50:42 +0200 (CEST) Jiri Kosina escreveu: > On Wed, 5 Oct 2016, Patrick Boettcher wrote: > > > > > Thanks for the quick response. > > > > Drivers are: > > > > dvb_core, dvb_usb, dbv_usb_cynergyT2 > > > > > > This dbv_usb_cynergyT2 is not from Linus' tree, is it? I

Re: kernel v4.8: iptables logs are truncated with the 4.8 kernel?

2016-10-05 Thread Justin Piszcz
On Tue, Oct 4, 2016 at 8:58 PM, Liping Zhang wrote: > Hi Justin, > > 2016-10-05 6:02 GMT+08:00 Justin Piszcz : >> Hello, >> [ .. ] > > Which one are you using? iptables or nftables? # iptables -V iptables v1.6.0 > > Could you please paste the

Re: kernel v4.8: iptables logs are truncated with the 4.8 kernel?

2016-10-05 Thread Justin Piszcz
On Tue, Oct 4, 2016 at 8:58 PM, Liping Zhang wrote: > Hi Justin, > > 2016-10-05 6:02 GMT+08:00 Justin Piszcz : >> Hello, >> [ .. ] > > Which one are you using? iptables or nftables? # iptables -V iptables v1.6.0 > > Could you please paste the related iptables/nftables rules here? Rules:

Re: [PATCH V2 1/3] mfd: wm8994-core: don't split lines unnecessarily

2016-10-05 Thread Viresh Kumar
On 05-10-16, 09:49, Lee Jones wrote: > You are experienced enough to know better than this. :) > a) Contentless pings have never been acceptable. If you genuinely > think a patch has been forgotten you should resubmit with a > [RESEND]. That is their entire purpose. Sure, but I really believe

Re: [PATCH V2 1/3] mfd: wm8994-core: don't split lines unnecessarily

2016-10-05 Thread Viresh Kumar
On 05-10-16, 09:49, Lee Jones wrote: > You are experienced enough to know better than this. :) > a) Contentless pings have never been acceptable. If you genuinely > think a patch has been forgotten you should resubmit with a > [RESEND]. That is their entire purpose. Sure, but I really believe

Re: [PATCH v2 2/4] drivers: iio: ti_am335x_adc: add dma support

2016-10-05 Thread Mugunthan V N
On Wednesday 05 October 2016 02:16 PM, Peter Ujfalusi wrote: > On 10/05/16 11:17, Mugunthan V N wrote: >> On Wednesday 05 October 2016 12:01 PM, Peter Ujfalusi wrote: >>> On 10/05/16 09:21, Mugunthan V N wrote: On Tuesday 04 October 2016 02:02 PM, Peter Ujfalusi wrote: > On 10/03/16

Re: [PATCH v2 2/4] drivers: iio: ti_am335x_adc: add dma support

2016-10-05 Thread Mugunthan V N
On Wednesday 05 October 2016 02:16 PM, Peter Ujfalusi wrote: > On 10/05/16 11:17, Mugunthan V N wrote: >> On Wednesday 05 October 2016 12:01 PM, Peter Ujfalusi wrote: >>> On 10/05/16 09:21, Mugunthan V N wrote: On Tuesday 04 October 2016 02:02 PM, Peter Ujfalusi wrote: > On 10/03/16

Re: [PATCH v2 2/4] drivers: iio: ti_am335x_adc: add dma support

2016-10-05 Thread Peter Ujfalusi
On 10/05/16 11:17, Mugunthan V N wrote: > On Wednesday 05 October 2016 12:01 PM, Peter Ujfalusi wrote: >> On 10/05/16 09:21, Mugunthan V N wrote: >>> On Tuesday 04 October 2016 02:02 PM, Peter Ujfalusi wrote: On 10/03/16 16:03, Mugunthan V N wrote: > +static int tiadc_request_dma(struct

Re: [PATCH v2 2/4] drivers: iio: ti_am335x_adc: add dma support

2016-10-05 Thread Peter Ujfalusi
On 10/05/16 11:17, Mugunthan V N wrote: > On Wednesday 05 October 2016 12:01 PM, Peter Ujfalusi wrote: >> On 10/05/16 09:21, Mugunthan V N wrote: >>> On Tuesday 04 October 2016 02:02 PM, Peter Ujfalusi wrote: On 10/03/16 16:03, Mugunthan V N wrote: > +static int tiadc_request_dma(struct

Re: [PATCH V2 1/3] mfd: wm8994-core: don't split lines unnecessarily

2016-10-05 Thread Lee Jones
On Wed, 05 Oct 2016, Viresh Kumar wrote: > On 04-10-16, 15:41, Lee Jones wrote: > > On Mon, 03 Oct 2016, Viresh Kumar wrote: > > > > > On 16-09-16, 08:56, Viresh Kumar wrote: > > > > These can fit in a single line (80 columns), don't split lines > > > > unnecessarily. > > > > > > > >

Re: [PATCH V2 1/3] mfd: wm8994-core: don't split lines unnecessarily

2016-10-05 Thread Lee Jones
On Wed, 05 Oct 2016, Viresh Kumar wrote: > On 04-10-16, 15:41, Lee Jones wrote: > > On Mon, 03 Oct 2016, Viresh Kumar wrote: > > > > > On 16-09-16, 08:56, Viresh Kumar wrote: > > > > These can fit in a single line (80 columns), don't split lines > > > > unnecessarily. > > > > > > > >

[tip:mm/pkeys] x86/pkeys: Update documentation

2016-10-05 Thread tip-bot for Dave Hansen
Commit-ID: 6679dac513fd612f34d3a3d99d7b84ed6d5eb5cc Gitweb: http://git.kernel.org/tip/6679dac513fd612f34d3a3d99d7b84ed6d5eb5cc Author: Dave Hansen AuthorDate: Tue, 4 Oct 2016 09:38:57 -0700 Committer: Thomas Gleixner CommitDate: Wed, 5 Oct

[tip:mm/pkeys] x86/pkeys: Update documentation

2016-10-05 Thread tip-bot for Dave Hansen
Commit-ID: 6679dac513fd612f34d3a3d99d7b84ed6d5eb5cc Gitweb: http://git.kernel.org/tip/6679dac513fd612f34d3a3d99d7b84ed6d5eb5cc Author: Dave Hansen AuthorDate: Tue, 4 Oct 2016 09:38:57 -0700 Committer: Thomas Gleixner CommitDate: Wed, 5 Oct 2016 10:34:55 +0200 x86/pkeys: Update

Re: [RFC][PATCH 4/4] futex: Rewrite FUTEX_UNLOCK_PI

2016-10-05 Thread Peter Zijlstra
On Wed, Oct 05, 2016 at 10:21:02AM +0200, Sebastian Andrzej Siewior wrote: > On 2016-10-05 10:09:12 [+0200], Peter Zijlstra wrote: > > On Wed, Oct 05, 2016 at 09:41:47AM +0200, Sebastian Andrzej Siewior wrote: > > > are those problems DL related? > > > > One of them, the other is that PI thing

Re: [RFC][PATCH 4/4] futex: Rewrite FUTEX_UNLOCK_PI

2016-10-05 Thread Peter Zijlstra
On Wed, Oct 05, 2016 at 10:21:02AM +0200, Sebastian Andrzej Siewior wrote: > On 2016-10-05 10:09:12 [+0200], Peter Zijlstra wrote: > > On Wed, Oct 05, 2016 at 09:41:47AM +0200, Sebastian Andrzej Siewior wrote: > > > are those problems DL related? > > > > One of them, the other is that PI thing

Re: [PATCH 6/6] ARM: da850: adjust memory settings for tilcdc

2016-10-05 Thread Peter Ujfalusi
On 10/04/16 16:02, Kevin Hilman wrote: > Peter Ujfalusi writes: > >> On 10/01/16 12:24, Sekhar Nori wrote: > > [...] > >>> In any case, to configure the PBBR, you will have to introduce a driver >>> for it in drivers/memory. Then you can set it up per board using a DT

Re: [PATCH 6/6] ARM: da850: adjust memory settings for tilcdc

2016-10-05 Thread Peter Ujfalusi
On 10/04/16 16:02, Kevin Hilman wrote: > Peter Ujfalusi writes: > >> On 10/01/16 12:24, Sekhar Nori wrote: > > [...] > >>> In any case, to configure the PBBR, you will have to introduce a driver >>> for it in drivers/memory. Then you can set it up per board using a DT >>> parameter. >> >> and

Re: [PATCH] perf powerpc: Don't call perf_event_disable from atomic context

2016-10-05 Thread Jan Stancek
- Original Message - > From: "Michael Ellerman" > To: "Jiri Olsa" , "Peter Zijlstra" > Cc: "lkml" , "Ingo Molnar" , > "Michael Neuling" , > "Paul

Re: [PATCH] perf powerpc: Don't call perf_event_disable from atomic context

2016-10-05 Thread Jan Stancek
- Original Message - > From: "Michael Ellerman" > To: "Jiri Olsa" , "Peter Zijlstra" > Cc: "lkml" , "Ingo Molnar" , > "Michael Neuling" , > "Paul Mackerras" , "Alexander Shishkin" > , "Jan Stancek" > > Sent: Tuesday, 4 October, 2016 6:08:27 AM > Subject: Re: [PATCH] perf powerpc:

Re: [RFC][PATCH 4/4] futex: Rewrite FUTEX_UNLOCK_PI

2016-10-05 Thread Sebastian Andrzej Siewior
On 2016-10-05 10:09:12 [+0200], Peter Zijlstra wrote: > On Wed, Oct 05, 2016 at 09:41:47AM +0200, Sebastian Andrzej Siewior wrote: > > are those problems DL related? > > One of them, the other is that PI thing you did that ugly nodeboost > thing for, right? this no-de-boost yes. This is probably

Re: [RFC][PATCH 4/4] futex: Rewrite FUTEX_UNLOCK_PI

2016-10-05 Thread Sebastian Andrzej Siewior
On 2016-10-05 10:09:12 [+0200], Peter Zijlstra wrote: > On Wed, Oct 05, 2016 at 09:41:47AM +0200, Sebastian Andrzej Siewior wrote: > > are those problems DL related? > > One of them, the other is that PI thing you did that ugly nodeboost > thing for, right? this no-de-boost yes. This is probably

Re: [PATCH v2 2/4] drivers: iio: ti_am335x_adc: add dma support

2016-10-05 Thread Mugunthan V N
On Wednesday 05 October 2016 12:01 PM, Peter Ujfalusi wrote: > On 10/05/16 09:21, Mugunthan V N wrote: >> On Tuesday 04 October 2016 02:02 PM, Peter Ujfalusi wrote: >>> On 10/03/16 16:03, Mugunthan V N wrote: +static int tiadc_request_dma(struct platform_device *pdev, +

Re: [PATCH v2 2/4] drivers: iio: ti_am335x_adc: add dma support

2016-10-05 Thread Mugunthan V N
On Wednesday 05 October 2016 12:01 PM, Peter Ujfalusi wrote: > On 10/05/16 09:21, Mugunthan V N wrote: >> On Tuesday 04 October 2016 02:02 PM, Peter Ujfalusi wrote: >>> On 10/03/16 16:03, Mugunthan V N wrote: +static int tiadc_request_dma(struct platform_device *pdev, +

[PATCH v2 2/2] ARM: dts: meson-gxbb: Add support for the Nexbox A95X Board

2016-10-05 Thread Neil Armstrong
Add support for the S905 (GXBB) version of the Nexbox A95X. Signed-off-by: Neil Armstrong --- arch/arm64/boot/dts/amlogic/Makefile | 1 + .../boot/dts/amlogic/meson-gxbb-nexbox-a95x.dts| 108 + 2 files changed, 109 insertions(+)

[PATCH v2 2/2] ARM: dts: meson-gxbb: Add support for the Nexbox A95X Board

2016-10-05 Thread Neil Armstrong
Add support for the S905 (GXBB) version of the Nexbox A95X. Signed-off-by: Neil Armstrong --- arch/arm64/boot/dts/amlogic/Makefile | 1 + .../boot/dts/amlogic/meson-gxbb-nexbox-a95x.dts| 108 + 2 files changed, 109 insertions(+) create mode 100644

[PATCH v2 1/2] devicetree: Add vendor prefix for Nexbox

2016-10-05 Thread Neil Armstrong
Nexbox is an IPTV set-top-box distributor, mainly with Amlogic SoCs: https://www.inexbox.com Signed-off-by: Neil Armstrong --- Documentation/devicetree/bindings/vendor-prefixes.txt | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH v2 1/2] devicetree: Add vendor prefix for Nexbox

2016-10-05 Thread Neil Armstrong
Nexbox is an IPTV set-top-box distributor, mainly with Amlogic SoCs: https://www.inexbox.com Signed-off-by: Neil Armstrong --- Documentation/devicetree/bindings/vendor-prefixes.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt

[PATCH v2 0/2] ARM64: meson-gxbb: Add support for the Nexbox A95X Board

2016-10-05 Thread Neil Armstrong
Add support for the Amlogic S905 (GXBB) version of the Nexbox A95X, an IPTV set-top-box with Ethernet, SDCard, eMMC, USB, HDMI, IR, Led, Reset button and Audio Jack. Changes since v1 at: http://lkml.kernel.org/r/1471951370-29269-1-git-send-email-narmstr...@baylibre.com - Rebase on

[PATCH v2 0/2] ARM64: meson-gxbb: Add support for the Nexbox A95X Board

2016-10-05 Thread Neil Armstrong
Add support for the Amlogic S905 (GXBB) version of the Nexbox A95X, an IPTV set-top-box with Ethernet, SDCard, eMMC, USB, HDMI, IR, Led, Reset button and Audio Jack. Changes since v1 at: http://lkml.kernel.org/r/1471951370-29269-1-git-send-email-narmstr...@baylibre.com - Rebase on

Re: [PATCH] perf powerpc: Don't call perf_event_disable from atomic context

2016-10-05 Thread Jiri Olsa
On Tue, Oct 04, 2016 at 03:29:33PM +1100, Michael Ellerman wrote: SNIP > Which is where we cope with the possibility that we couldn't emulate the > instruction that hit the breakpoint. Seems that is not an issue on x86, > or it's handled elsewhere? > > We should fix emulate_step() if it failed

Re: [PATCH] perf powerpc: Don't call perf_event_disable from atomic context

2016-10-05 Thread Jiri Olsa
On Tue, Oct 04, 2016 at 03:29:33PM +1100, Michael Ellerman wrote: SNIP > Which is where we cope with the possibility that we couldn't emulate the > instruction that hit the breakpoint. Seems that is not an issue on x86, > or it's handled elsewhere? > > We should fix emulate_step() if it failed

Re: [RFC][PATCH 4/4] futex: Rewrite FUTEX_UNLOCK_PI

2016-10-05 Thread Peter Zijlstra
On Wed, Oct 05, 2016 at 09:41:47AM +0200, Sebastian Andrzej Siewior wrote: > On 2016-10-03 11:12:38 [+0200], Peter Zijlstra wrote: > > There's a number of 'interesting' problems with FUTEX_UNLOCK_PI, all > > caused by holding hb->lock while doing the rt_mutex_unlock() > > equivalient. > > are

Re: [RFC][PATCH 4/4] futex: Rewrite FUTEX_UNLOCK_PI

2016-10-05 Thread Peter Zijlstra
On Wed, Oct 05, 2016 at 09:41:47AM +0200, Sebastian Andrzej Siewior wrote: > On 2016-10-03 11:12:38 [+0200], Peter Zijlstra wrote: > > There's a number of 'interesting' problems with FUTEX_UNLOCK_PI, all > > caused by holding hb->lock while doing the rt_mutex_unlock() > > equivalient. > > are

Re: [PATCH] perf powerpc: Don't call perf_event_disable from atomic context

2016-10-05 Thread Jiri Olsa
On Tue, Oct 04, 2016 at 03:08:27PM +1100, Michael Ellerman wrote: > Jiri Olsa writes: > > > The trinity syscall fuzzer triggered following WARN on powerpc: > > WARNING: CPU: 9 PID: 2998 at arch/powerpc/kernel/hw_breakpoint.c:278 > > ... > > NIP [c093aedc]

Re: [PATCH] perf powerpc: Don't call perf_event_disable from atomic context

2016-10-05 Thread Jiri Olsa
On Tue, Oct 04, 2016 at 03:08:27PM +1100, Michael Ellerman wrote: > Jiri Olsa writes: > > > The trinity syscall fuzzer triggered following WARN on powerpc: > > WARNING: CPU: 9 PID: 2998 at arch/powerpc/kernel/hw_breakpoint.c:278 > > ... > > NIP [c093aedc]

Re: [Documentation] State of CPU controller in cgroup v2

2016-10-05 Thread Peter Zijlstra
On Tue, Oct 04, 2016 at 10:47:17AM -0400, Tejun Heo wrote: > > cgroup-v2, by placing the system style controllers first and foremost, > > completely renders that scenario impossible. Note also that any proposed > > rgroup would not work for this, since that, per design, is a subtree, > > and

Re: [Documentation] State of CPU controller in cgroup v2

2016-10-05 Thread Peter Zijlstra
On Tue, Oct 04, 2016 at 10:47:17AM -0400, Tejun Heo wrote: > > cgroup-v2, by placing the system style controllers first and foremost, > > completely renders that scenario impossible. Note also that any proposed > > rgroup would not work for this, since that, per design, is a subtree, > > and

Re: [PATCH 6/6] ARM: da850: adjust memory settings for tilcdc

2016-10-05 Thread Peter Ujfalusi
On 10/04/16 12:20, Bartosz Golaszewski wrote: > 2016-09-30 21:19 GMT+02:00 Peter Ujfalusi : >> On 09/30/2016 06:06 PM, Bartosz Golaszewski wrote: >>> >>> Just ran a quick test with speaker-test -c2 -twav. Besides the fact >>> that the left and right channels are inverted

Re: [PATCH 6/6] ARM: da850: adjust memory settings for tilcdc

2016-10-05 Thread Peter Ujfalusi
On 10/04/16 12:20, Bartosz Golaszewski wrote: > 2016-09-30 21:19 GMT+02:00 Peter Ujfalusi : >> On 09/30/2016 06:06 PM, Bartosz Golaszewski wrote: >>> >>> Just ran a quick test with speaker-test -c2 -twav. Besides the fact >>> that the left and right channels are inverted (I'm looking into that),

Re: [PATCH v16 0/4] Introduce usb charger framework to deal with the usb gadget power negotation

2016-10-05 Thread Baolin Wang
Hi Felipe, On 5 October 2016 at 15:47, Felipe Balbi wrote: > > Hi Baolin, > > Baolin Wang writes: But you do! The mA number from the USB configuration is passed to usb_gadget_vbus_draw. Your patch passes that to

Re: [PATCH v16 0/4] Introduce usb charger framework to deal with the usb gadget power negotation

2016-10-05 Thread Baolin Wang
Hi Felipe, On 5 October 2016 at 15:47, Felipe Balbi wrote: > > Hi Baolin, > > Baolin Wang writes: But you do! The mA number from the USB configuration is passed to usb_gadget_vbus_draw. Your patch passes that to usb_charger_set_cur_limit_by_type() which calls

Re: Problem with VMAP_STACK=y

2016-10-05 Thread Jiri Kosina
On Wed, 5 Oct 2016, Patrick Boettcher wrote: > > > Thanks for the quick response. > > > Drivers are: > > > dvb_core, dvb_usb, dbv_usb_cynergyT2 > > > > This dbv_usb_cynergyT2 is not from Linus' tree, is it? I don't seem > > to be able to find it, and the only google hit I am getting is your >

Re: Problem with VMAP_STACK=y

2016-10-05 Thread Jiri Kosina
On Wed, 5 Oct 2016, Patrick Boettcher wrote: > > > Thanks for the quick response. > > > Drivers are: > > > dvb_core, dvb_usb, dbv_usb_cynergyT2 > > > > This dbv_usb_cynergyT2 is not from Linus' tree, is it? I don't seem > > to be able to find it, and the only google hit I am getting is your >

Re: PROBLEM: DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422

2016-10-05 Thread Anand Moon
Hi Vivek, On 5 October 2016 at 10:15, Vivek Gautam wrote: > Hi Anand, > > > On Tue, Oct 4, 2016 at 8:39 PM, Anand Moon wrote: >> Hi Vivek, >> > > [snip] > >> >> What I feel is that their need to be some reset of usb phy so that >> device are

Re: PROBLEM: DWC3 USB 3.0 not working on Odroid-XU4 with Exynos 5422

2016-10-05 Thread Anand Moon
Hi Vivek, On 5 October 2016 at 10:15, Vivek Gautam wrote: > Hi Anand, > > > On Tue, Oct 4, 2016 at 8:39 PM, Anand Moon wrote: >> Hi Vivek, >> > > [snip] > >> >> What I feel is that their need to be some reset of usb phy so that >> device are assigned to respective bus ports. > > The phy resets

RE: [PATCH] tpm: don't destroy chip device prematurely

2016-10-05 Thread Winkler, Tomas
> > > > > On Tue, Oct 04, 2016 at 08:19:46AM +0300, Jarkko Sakkinen wrote: > > > > > > > > Make the driver uncallable first. The worst race that can happen > > > > > is that open("/dev/tpm0", ...) returns -EPIPE. I do not consider > > > > > this fatal at all. > > > > > > > > No responses for this

RE: [PATCH] tpm: don't destroy chip device prematurely

2016-10-05 Thread Winkler, Tomas
> > > > > On Tue, Oct 04, 2016 at 08:19:46AM +0300, Jarkko Sakkinen wrote: > > > > > > > > Make the driver uncallable first. The worst race that can happen > > > > > is that open("/dev/tpm0", ...) returns -EPIPE. I do not consider > > > > > this fatal at all. > > > > > > > > No responses for this

Re: [PATCH v16 0/4] Introduce usb charger framework to deal with the usb gadget power negotation

2016-10-05 Thread Felipe Balbi
Hi Baolin, Baolin Wang writes: >>> But you do! >>> The mA number from the USB configuration is passed to usb_gadget_vbus_draw. >>> Your patch passes that to usb_charger_set_cur_limit_by_type() >>> which calls __usb_charger_set_cur_limit_by_type() which will set the >>>

Re: [PATCH v16 0/4] Introduce usb charger framework to deal with the usb gadget power negotation

2016-10-05 Thread Felipe Balbi
Hi Baolin, Baolin Wang writes: >>> But you do! >>> The mA number from the USB configuration is passed to usb_gadget_vbus_draw. >>> Your patch passes that to usb_charger_set_cur_limit_by_type() >>> which calls __usb_charger_set_cur_limit_by_type() which will set the >>> cur_limit for whichever

Re: [RFC][PATCH 4/4] futex: Rewrite FUTEX_UNLOCK_PI

2016-10-05 Thread Sebastian Andrzej Siewior
On 2016-10-03 11:12:38 [+0200], Peter Zijlstra wrote: > There's a number of 'interesting' problems with FUTEX_UNLOCK_PI, all > caused by holding hb->lock while doing the rt_mutex_unlock() > equivalient. are those problems DL related? Sebastian

Re: [RFC][PATCH 4/4] futex: Rewrite FUTEX_UNLOCK_PI

2016-10-05 Thread Sebastian Andrzej Siewior
On 2016-10-03 11:12:38 [+0200], Peter Zijlstra wrote: > There's a number of 'interesting' problems with FUTEX_UNLOCK_PI, all > caused by holding hb->lock while doing the rt_mutex_unlock() > equivalient. are those problems DL related? Sebastian

<    4   5   6   7   8   9   10   >