RE: [PATCH v1 4/5] ARM: dts: ls1043a: add qDMA node

2016-08-30 Thread Yao Yuan
On Mon 29 August 2016 03:34:47, : Alexander Stein wrote: > On Thursday 18 August 2016 14:38:47, Yuan Yao wrote: > > From: Yuan Yao > > > > Add the QDMA node for ls1043a platform to support QDMA driver. > > > > Signed-off-by: Yuan Yao > > --- > >

RE: [PATCH v1 4/5] ARM: dts: ls1043a: add qDMA node

2016-08-30 Thread Yao Yuan
On Mon 29 August 2016 03:34:47, : Alexander Stein wrote: > On Thursday 18 August 2016 14:38:47, Yuan Yao wrote: > > From: Yuan Yao > > > > Add the QDMA node for ls1043a platform to support QDMA driver. > > > > Signed-off-by: Yuan Yao > > --- > > arch/arm64/boot/dts/freescale/fsl-ls1043a.dtsi |

Re: [PATCH v3] time: alarmtimer: Add the trcepoints for alarmtimer

2016-08-30 Thread Baolin Wang
On 31 August 2016 at 02:58, John Stultz wrote: > On Tue, Aug 30, 2016 at 4:50 AM, Baolin Wang wrote: >> Hi, >> >> On 22 August 2016 at 12:23, Baolin Wang wrote: >>> For system debugging, we usually want to know who sets one

Re: [PATCH v3] time: alarmtimer: Add the trcepoints for alarmtimer

2016-08-30 Thread Baolin Wang
On 31 August 2016 at 02:58, John Stultz wrote: > On Tue, Aug 30, 2016 at 4:50 AM, Baolin Wang wrote: >> Hi, >> >> On 22 August 2016 at 12:23, Baolin Wang wrote: >>> For system debugging, we usually want to know who sets one alarm timer, the >>> time of the timer, when the timer started and

Re: [PATCH] mmc: sdhci-msm: Add pm_runtime and system PM support

2016-08-30 Thread Pramod Gurav
Thanks Ulf for the review. On 29 August 2016 at 19:50, Ulf Hansson wrote: > On 16 June 2016 at 14:35, Pramod Gurav wrote: >> + platform_set_drvdata(pdev, msm_host); >> + >> + pm_runtime_set_active(>dev); >> +

Re: [PATCH] mmc: sdhci-msm: Add pm_runtime and system PM support

2016-08-30 Thread Pramod Gurav
Thanks Ulf for the review. On 29 August 2016 at 19:50, Ulf Hansson wrote: > On 16 June 2016 at 14:35, Pramod Gurav wrote: >> + platform_set_drvdata(pdev, msm_host); >> + >> + pm_runtime_set_active(>dev); >> + pm_runtime_enable(>dev); > > I think you need to move these a bit

Re: constification and cocci / kernel build test robot ?

2016-08-30 Thread Julia Lawall
On Tue, 30 Aug 2016, Kees Cook wrote: > On Tue, Aug 30, 2016 at 3:23 PM, Julia Lawall wrote: > > > > > > On Tue, 30 Aug 2016, Kees Cook wrote: > > > >> On Sun, Aug 28, 2016 at 9:13 AM, Julia Lawall wrote: > >> > [Adding Kees, in case it's of

Re: constification and cocci / kernel build test robot ?

2016-08-30 Thread Julia Lawall
On Tue, 30 Aug 2016, Kees Cook wrote: > On Tue, Aug 30, 2016 at 3:23 PM, Julia Lawall wrote: > > > > > > On Tue, 30 Aug 2016, Kees Cook wrote: > > > >> On Sun, Aug 28, 2016 at 9:13 AM, Julia Lawall wrote: > >> > [Adding Kees, in case it's of interest] > >> > > >> > Below is the list of types

Re: [v2] locking/percpu-rwsem: Optimize readers and reduce global impact

2016-08-30 Thread Guenter Roeck
Peter, On Tue, Aug 09, 2016 at 11:51:12AM +0200, Peter Zijlstra wrote: > Currently the percpu-rwsem switches to (global) atomic ops while a > writer is waiting; which could be quite a while and slows down > releasing the readers. > > This patch cures this problem by ordering the reader-state vs

Re: [v2] locking/percpu-rwsem: Optimize readers and reduce global impact

2016-08-30 Thread Guenter Roeck
Peter, On Tue, Aug 09, 2016 at 11:51:12AM +0200, Peter Zijlstra wrote: > Currently the percpu-rwsem switches to (global) atomic ops while a > writer is waiting; which could be quite a while and slows down > releasing the readers. > > This patch cures this problem by ordering the reader-state vs

Re: [PATCH net-next 0/8] rxrpc: Preparation for removal of use of skbs from AFS

2016-08-30 Thread David Miller
e that directly rather than getting it from the rxrpc_call > struct. ... > Tagged thusly: > > git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git > rxrpc-rewrite-20160830-1 Pulled, thanks David.

Re: [PATCH net-next 0/8] rxrpc: Preparation for removal of use of skbs from AFS

2016-08-30 Thread David Miller
getting it from the rxrpc_call > struct. ... > Tagged thusly: > > git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git > rxrpc-rewrite-20160830-1 Pulled, thanks David.

Re: trace: use-after-free in hist_unreg_all

2016-08-30 Thread amanda4ray
On Tuesday, June 28, 2016 at 8:59:10 AM UTC-4, dvyukov wrote: > Hello, > > While running tools/testing/selftests test suite with KASAN I hit the > following use-after-free report: > > > > == > BUG: KASAN: use-after-free in

Re: trace: use-after-free in hist_unreg_all

2016-08-30 Thread amanda4ray
On Tuesday, June 28, 2016 at 8:59:10 AM UTC-4, dvyukov wrote: > Hello, > > While running tools/testing/selftests test suite with KASAN I hit the > following use-after-free report: > > > > == > BUG: KASAN: use-after-free in

[PATCH v2 3/3] scsi/ncr5380: Improve interrupt latency during PIO tranfers

2016-08-30 Thread Finn Thain
Large PIO transfers are broken up into chunks to try to avoid disabling local IRQs for long periods. But IRQs are still disabled for too long and this causes SCC FIFO overruns during serial port transfers. This patch reduces the PIO chunk size to reduce interrupt latency to something on the order

[PATCH v2 3/3] scsi/ncr5380: Improve interrupt latency during PIO tranfers

2016-08-30 Thread Finn Thain
Large PIO transfers are broken up into chunks to try to avoid disabling local IRQs for long periods. But IRQs are still disabled for too long and this causes SCC FIFO overruns during serial port transfers. This patch reduces the PIO chunk size to reduce interrupt latency to something on the order

Re: [PATCH 1/4] spinlock: Document memory barrier rules

2016-08-30 Thread Manfred Spraul
On 08/29/2016 03:44 PM, Peter Zijlstra wrote: If you add a barrier, the Changelog had better be clear. And I'm still not entirely sure I get what exactly this barrier should do, nor why it defaults to a full smp_mb. If what I suspect it should do, only PPC and ARM64 need the barrier. The

Re: [PATCH 1/4] spinlock: Document memory barrier rules

2016-08-30 Thread Manfred Spraul
On 08/29/2016 03:44 PM, Peter Zijlstra wrote: If you add a barrier, the Changelog had better be clear. And I'm still not entirely sure I get what exactly this barrier should do, nor why it defaults to a full smp_mb. If what I suspect it should do, only PPC and ARM64 need the barrier. The

Re: [PATCH V3 2/2] rtc/rtc-cmos: Initialize software counters before irq is registered

2016-08-30 Thread Dave Young
Hi, Pratyush, I'm not sure who is the maintainer to review and take the patches, In MATAINERS file, x86 hpet is orphaned. rtc-cmos may go to rtc maitianer Alessandro Zummo Ccing Andrew maybe he can also take the patches for orphaned component. On 08/30/16 at 03:24pm, Pratyush Anand wrote: > Hi

Re: [PATCH V3 2/2] rtc/rtc-cmos: Initialize software counters before irq is registered

2016-08-30 Thread Dave Young
Hi, Pratyush, I'm not sure who is the maintainer to review and take the patches, In MATAINERS file, x86 hpet is orphaned. rtc-cmos may go to rtc maitianer Alessandro Zummo Ccing Andrew maybe he can also take the patches for orphaned component. On 08/30/16 at 03:24pm, Pratyush Anand wrote: > Hi

Re: [PATCH 0/7 v5] K3DMA fixes for HiKey HDMI audio

2016-08-30 Thread Vinod Koul
On Mon, Aug 29, 2016 at 10:30:46AM -0700, John Stultz wrote: > Just sending these the k3dma fixes and cyclic mode patches > needed to support audio on HiKey, hopefully one last time. :) > > Again, no code changes here, but I did re-order the Kconfig > chnage to be last to avoid a bisection build

Re: [PATCH 0/7 v5] K3DMA fixes for HiKey HDMI audio

2016-08-30 Thread Vinod Koul
On Mon, Aug 29, 2016 at 10:30:46AM -0700, John Stultz wrote: > Just sending these the k3dma fixes and cyclic mode patches > needed to support audio on HiKey, hopefully one last time. :) > > Again, no code changes here, but I did re-order the Kconfig > chnage to be last to avoid a bisection build

Re: [PATCH v2] scsi: move function declarations to scsi_priv.h

2016-08-30 Thread Martin K. Petersen
> "Baoyou" == Baoyou Xie writes: Baoyou> We get 2 warnings about global functions without a declaration Baoyou> in the scsi driver when building with W=1: Baoyou> drivers/scsi/scsi_lib.c:467:6: warning: no previous prototype Baoyou> for 'scsi_requeue_run_queue'

Re: [PATCH v2] scsi: move function declarations to scsi_priv.h

2016-08-30 Thread Martin K. Petersen
> "Baoyou" == Baoyou Xie writes: Baoyou> We get 2 warnings about global functions without a declaration Baoyou> in the scsi driver when building with W=1: Baoyou> drivers/scsi/scsi_lib.c:467:6: warning: no previous prototype Baoyou> for 'scsi_requeue_run_queue' [-Wmissing-prototypes] Baoyou>

Re: [PATCH 0/3] Small fixes and cleanup

2016-08-30 Thread Martin K. Petersen
> "Finn" == Finn Thain writes: Finn> Miscellaneous small patches for an interrupt latency issue, a Finn> compiler warning and a documentation cleanup. Applied patches 1 and 2 to 4.9/scsi-queue. -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH 0/3] Small fixes and cleanup

2016-08-30 Thread Martin K. Petersen
> "Finn" == Finn Thain writes: Finn> Miscellaneous small patches for an interrupt latency issue, a Finn> compiler warning and a documentation cleanup. Applied patches 1 and 2 to 4.9/scsi-queue. -- Martin K. Petersen Oracle Linux Engineering

[PATCH v3 1/2] regulator: pwm: Add support for a fixed delay after duty cycle changes

2016-08-30 Thread Douglas Anderson
From: Matthias Kaehlcke A change of the duty cycle doesn't necessarily cause an immediate switch to the target voltage. On many PWM regulators there is a fixed "settle time" (irrespective of the jump size) that we need to wait after an upward jump. This change introduces the

[PATCH v3 2/2] regulator: pwm: Prevent falling too fast

2016-08-30 Thread Douglas Anderson
On some boards it's possible that transitioning the PWM regulator downwards too fast will trigger the over voltage protection (OVP) on the regulator. This is because until the voltage actually falls there is a time when the requested voltage is much lower than the actual voltage. We'll fix this

[PATCH v3 1/2] regulator: pwm: Add support for a fixed delay after duty cycle changes

2016-08-30 Thread Douglas Anderson
From: Matthias Kaehlcke A change of the duty cycle doesn't necessarily cause an immediate switch to the target voltage. On many PWM regulators there is a fixed "settle time" (irrespective of the jump size) that we need to wait after an upward jump. This change introduces the device tree

[PATCH v3 2/2] regulator: pwm: Prevent falling too fast

2016-08-30 Thread Douglas Anderson
On some boards it's possible that transitioning the PWM regulator downwards too fast will trigger the over voltage protection (OVP) on the regulator. This is because until the voltage actually falls there is a time when the requested voltage is much lower than the actual voltage. We'll fix this

Re: [PATCH net] rps: flow_dissector: Fix uninitialized flow_keys used in __skb_get_hash possibly

2016-08-30 Thread Gao Feng
On Wed, Aug 31, 2016 at 12:14 PM, Eric Dumazet wrote: > On Wed, 2016-08-31 at 10:56 +0800, f...@ikuai8.com wrote: >> From: Gao Feng >> >> The original codes depend on that the function parameters are evaluated from >> left to right. But the parameter's

Re: [PATCH net] rps: flow_dissector: Fix uninitialized flow_keys used in __skb_get_hash possibly

2016-08-30 Thread Gao Feng
On Wed, Aug 31, 2016 at 12:14 PM, Eric Dumazet wrote: > On Wed, 2016-08-31 at 10:56 +0800, f...@ikuai8.com wrote: >> From: Gao Feng >> >> The original codes depend on that the function parameters are evaluated from >> left to right. But the parameter's evaluation order is not defined in C >>

Re: [PATCH] kasan: avoid overflowing quarantine size on low memory systems

2016-08-30 Thread amanda4ray
On Monday, August 1, 2016 at 10:59:29 AM UTC-4, Alexander Potapenko wrote: > If the total amount of memory assigned to quarantine is less than the > amount of memory assigned to per-cpu quarantines, |new_quarantine_size| > may overflow. Instead, set it to zero. > > Reported-by: Dmitry Vyukov

Re: [PATCH] kasan: avoid overflowing quarantine size on low memory systems

2016-08-30 Thread amanda4ray
On Monday, August 1, 2016 at 10:59:29 AM UTC-4, Alexander Potapenko wrote: > If the total amount of memory assigned to quarantine is less than the > amount of memory assigned to per-cpu quarantines, |new_quarantine_size| > may overflow. Instead, set it to zero. > > Reported-by: Dmitry Vyukov >

Re: [PATCH net] rps: flow_dissector: Fix uninitialized flow_keys used in __skb_get_hash possibly

2016-08-30 Thread Eric Dumazet
On Wed, 2016-08-31 at 10:56 +0800, f...@ikuai8.com wrote: > From: Gao Feng > > The original codes depend on that the function parameters are evaluated from > left to right. But the parameter's evaluation order is not defined in C > standard actually. > > When

Re: [PATCH net] rps: flow_dissector: Fix uninitialized flow_keys used in __skb_get_hash possibly

2016-08-30 Thread Eric Dumazet
On Wed, 2016-08-31 at 10:56 +0800, f...@ikuai8.com wrote: > From: Gao Feng > > The original codes depend on that the function parameters are evaluated from > left to right. But the parameter's evaluation order is not defined in C > standard actually. > > When flow_keys_have_l4() is invoked

Re: [PATCH V3 3/3] dmaengine: qcom_hidma: add error reporting for tx_status

2016-08-30 Thread Vinod Koul
On Tue, Aug 30, 2016 at 01:51:02PM -0400, Sinan Kaya wrote: > On 8/30/2016 1:37 PM, Sinan Kaya wrote: > > On 8/30/2016 1:04 PM, Vinod Koul wrote: > >> On Tue, Aug 23, 2016 at 12:48:11AM -0400, Sinan Kaya wrote: > >> > >>> spin_lock_init(>lock); > >>> - tasklet_init(>rst_task, hidma_ll_abort,

Re: [PATCH V3 3/3] dmaengine: qcom_hidma: add error reporting for tx_status

2016-08-30 Thread Vinod Koul
On Tue, Aug 30, 2016 at 01:51:02PM -0400, Sinan Kaya wrote: > On 8/30/2016 1:37 PM, Sinan Kaya wrote: > > On 8/30/2016 1:04 PM, Vinod Koul wrote: > >> On Tue, Aug 23, 2016 at 12:48:11AM -0400, Sinan Kaya wrote: > >> > >>> spin_lock_init(>lock); > >>> - tasklet_init(>rst_task, hidma_ll_abort,

Re: [PATCH RESEND] drm: bridge/dw-hdmi: Fix colorspace and scan information registers values

2016-08-30 Thread Archit Taneja
Hi, On 08/29/2016 03:00 PM, Jose Abreu wrote: Colorspace and scan information values were being written in wrong offsets. This patch corrects this and writes the values at the offsets specified in the databook. queued to drm-misc after cleaning up some checkpatch errors. Thanks, Archit

Re: [PATCH RESEND] drm: bridge/dw-hdmi: Fix colorspace and scan information registers values

2016-08-30 Thread Archit Taneja
Hi, On 08/29/2016 03:00 PM, Jose Abreu wrote: Colorspace and scan information values were being written in wrong offsets. This patch corrects this and writes the values at the offsets specified in the databook. queued to drm-misc after cleaning up some checkpatch errors. Thanks, Archit

Re: [PART2 PATCH v7 12/12] svm: Implements update_pi_irte hook to setup posted interrupt

2016-08-30 Thread Radim Krčmář
2016-08-23 13:52-0500, Suravee Suthikulpanit: > From: Suravee Suthikulpanit > > This patch implements update_pi_irte function hook to allow SVM > communicate to IOMMU driver regarding how to set up IRTE for handling > posted interrupt. > > In case AVIC is enabled,

Re: [PART2 PATCH v7 12/12] svm: Implements update_pi_irte hook to setup posted interrupt

2016-08-30 Thread Radim Krčmář
2016-08-23 13:52-0500, Suravee Suthikulpanit: > From: Suravee Suthikulpanit > > This patch implements update_pi_irte function hook to allow SVM > communicate to IOMMU driver regarding how to set up IRTE for handling > posted interrupt. > > In case AVIC is enabled, during vcpu_load/unload, SVM

Re: [PATCH] printk/nmi: avoid direct printk()-s from __printk_nmi_flush()

2016-08-30 Thread Sergey Senozhatsky
On (08/30/16 13:19), Petr Mladek wrote: [..] > > yes, x86 has a per-cpu nmi_state to handle the case when NMI is > > loosing its NMI context. But other arch-s, as far as I can see, > > don't do that. Does it mean that we are safe only on x86? > > My understanding is that the kernel would crash on

Re: [PATCH] printk/nmi: avoid direct printk()-s from __printk_nmi_flush()

2016-08-30 Thread Sergey Senozhatsky
On (08/30/16 13:19), Petr Mladek wrote: [..] > > yes, x86 has a per-cpu nmi_state to handle the case when NMI is > > loosing its NMI context. But other arch-s, as far as I can see, > > don't do that. Does it mean that we are safe only on x86? > > My understanding is that the kernel would crash on

Re: [PATCH] cpufreq: Drop unnecessary check from cpufreq_policy_alloc()

2016-08-30 Thread Viresh Kumar
On 31-08-16, 03:11, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > Since cpufreq_policy_alloc() doesn't use its dev variable for > anything useful, drop that variable from there along with the > NULL check against it. > > Signed-off-by: Rafael J. Wysocki

Re: [PATCH] cpufreq: Drop unnecessary check from cpufreq_policy_alloc()

2016-08-30 Thread Viresh Kumar
On 31-08-16, 03:11, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > Since cpufreq_policy_alloc() doesn't use its dev variable for > anything useful, drop that variable from there along with the > NULL check against it. > > Signed-off-by: Rafael J. Wysocki > --- >

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

2016-08-30 Thread Andy Lutomirski
On Mon, Aug 29, 2016 at 3:20 PM, Tejun Heo wrote: >> > These base-system operations are special regardless of cgroup and we >> > already have sometimes crude ways to affect their behaviors where >> > necessary through sysctl knobs, priorities on specific kernel threads >> > and

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

2016-08-30 Thread Andy Lutomirski
On Mon, Aug 29, 2016 at 3:20 PM, Tejun Heo wrote: >> > These base-system operations are special regardless of cgroup and we >> > already have sometimes crude ways to affect their behaviors where >> > necessary through sysctl knobs, priorities on specific kernel threads >> > and so on. cgroup

Re: [RFC][PATCH] Fix a race between rwsem and the scheduler

2016-08-30 Thread Balbir Singh
On 30/08/16 22:19, Peter Zijlstra wrote: > On Tue, Aug 30, 2016 at 06:49:37PM +1000, Balbir Singh wrote: >> >> >> The origin of the issue I've seen seems to be related to >> rwsem spin lock stealing. Basically I see the system deadlock'd in the >> following state > > As Nick says (good to see

Re: [RFC][PATCH] Fix a race between rwsem and the scheduler

2016-08-30 Thread Balbir Singh
On 30/08/16 22:19, Peter Zijlstra wrote: > On Tue, Aug 30, 2016 at 06:49:37PM +1000, Balbir Singh wrote: >> >> >> The origin of the issue I've seen seems to be related to >> rwsem spin lock stealing. Basically I see the system deadlock'd in the >> following state > > As Nick says (good to see

Re: [RFC][PATCH] Fix a race between rwsem and the scheduler

2016-08-30 Thread Balbir Singh
On 30/08/16 22:58, Oleg Nesterov wrote: > On 08/30, Balbir Singh wrote: >> >> The origin of the issue I've seen seems to be related to >> rwsem spin lock stealing. Basically I see the system deadlock'd in the >> following state >> >> I have a system with multiple threads and >> >> Most of the

Re: [PATCH net-next 4/6] perf, bpf: add perf events core support for BPF_PROG_TYPE_PERF_EVENT programs

2016-08-30 Thread Alexei Starovoitov
On Mon, Aug 29, 2016 at 02:17:18PM +0200, Peter Zijlstra wrote: > On Fri, Aug 26, 2016 at 07:31:22PM -0700, Alexei Starovoitov wrote: > > +static int perf_event_set_bpf_handler(struct perf_event *event, u32 > > prog_fd) > > +{ > > + struct bpf_prog *prog; > > + > > + if

Re: [RFC][PATCH] Fix a race between rwsem and the scheduler

2016-08-30 Thread Balbir Singh
On 30/08/16 22:58, Oleg Nesterov wrote: > On 08/30, Balbir Singh wrote: >> >> The origin of the issue I've seen seems to be related to >> rwsem spin lock stealing. Basically I see the system deadlock'd in the >> following state >> >> I have a system with multiple threads and >> >> Most of the

Re: [PATCH net-next 4/6] perf, bpf: add perf events core support for BPF_PROG_TYPE_PERF_EVENT programs

2016-08-30 Thread Alexei Starovoitov
On Mon, Aug 29, 2016 at 02:17:18PM +0200, Peter Zijlstra wrote: > On Fri, Aug 26, 2016 at 07:31:22PM -0700, Alexei Starovoitov wrote: > > +static int perf_event_set_bpf_handler(struct perf_event *event, u32 > > prog_fd) > > +{ > > + struct bpf_prog *prog; > > + > > + if

[PATCH v4 0/2] serial: 8250_dw: Add ACPI support for uart on Hisilicon Hip05 SoC

2016-08-30 Thread Kefeng Wang
Handle all cases of dw8250_data->clk properly in dw8250_set_termios(), then make it as the default set_termios callback for 8250 dw uart. After that, add ACPI support for uart on Hisilicon Hip05 SoC, be careful that it is not 16500 compatible, and with Heikki's patchset[1], we safely only add

Re: [PATCHV5 1/3] tracing: add a possibility of exporting function trace to other places instead of ring buffer only

2016-08-30 Thread Chunyan Zhang
On 30 August 2016 at 22:30, Steven Rostedt wrote: > On Tue, 30 Aug 2016 16:07:28 +0800 > Chunyan Zhang wrote: > >> Currently Function traces can be only exported to ring buffer, this >> patch added trace_export concept which can process traces and

[PATCH v4 0/2] serial: 8250_dw: Add ACPI support for uart on Hisilicon Hip05 SoC

2016-08-30 Thread Kefeng Wang
Handle all cases of dw8250_data->clk properly in dw8250_set_termios(), then make it as the default set_termios callback for 8250 dw uart. After that, add ACPI support for uart on Hisilicon Hip05 SoC, be careful that it is not 16500 compatible, and with Heikki's patchset[1], we safely only add

Re: [PATCHV5 1/3] tracing: add a possibility of exporting function trace to other places instead of ring buffer only

2016-08-30 Thread Chunyan Zhang
On 30 August 2016 at 22:30, Steven Rostedt wrote: > On Tue, 30 Aug 2016 16:07:28 +0800 > Chunyan Zhang wrote: > >> Currently Function traces can be only exported to ring buffer, this >> patch added trace_export concept which can process traces and export >> them to a registered destination as an

[PATCH 1/3] autofs: remove possibly misleading /* #define DEBUG */

2016-08-30 Thread Ian Kent
From: Tomohiro Kusumi Having this in autofs_i.h gives illusion that uncommenting this enables pr_debug(), but it doesn't enable all the pr_debug() in autofs because inclusion order matters. XFS has the same DEBUG macro in its core header fs/xfs/xfs.h, however XFS

[PATCH 1/3] autofs: remove possibly misleading /* #define DEBUG */

2016-08-30 Thread Ian Kent
From: Tomohiro Kusumi Having this in autofs_i.h gives illusion that uncommenting this enables pr_debug(), but it doesn't enable all the pr_debug() in autofs because inclusion order matters. XFS has the same DEBUG macro in its core header fs/xfs/xfs.h, however XFS seems to have a rule to include

[PATCH 3/3] autofs: fix "fix dev ioctl number range check"

2016-08-30 Thread Ian Kent
From: Tomohiro Kusumi 102a340f had a typo that made the count macro negative (-13). The acutal check used by ioctl is ((cmd - cmd_first) > COUNT), so it needs to be positive (13). * 102a340f is a commit in linux-next which hasn't been merged to mainline upstream.

[PATCH v4 2/2] serial: 8250_dw: add ACPI support for uart on Hisilicon Hip05 SoC

2016-08-30 Thread Kefeng Wang
Add ACPI identifier for UART on Hisilicon Hip05 SoC, be careful that it is not 16550 compatible, and "reg-io-width" and "reg-shift" need be set properly by _DSD method in DSDT. Signed-off-by: Kefeng Wang --- drivers/tty/serial/8250/8250_dw.c | 1 + 1 file changed, 1

[PATCH 2/3] autofs: refactor ioctl fn vector in iookup_dev_ioctl()

2016-08-30 Thread Ian Kent
From: Tomohiro Kusumi cmd part of this struct is the same as an index of itself within _ioctls[]. In fact this cmd is unused, so we can drop this part. Signed-off-by: Tomohiro Kusumi Signed-off-by: Ian Kent ---

[PATCH 3/3] autofs: fix "fix dev ioctl number range check"

2016-08-30 Thread Ian Kent
From: Tomohiro Kusumi 102a340f had a typo that made the count macro negative (-13). The acutal check used by ioctl is ((cmd - cmd_first) > COUNT), so it needs to be positive (13). * 102a340f is a commit in linux-next which hasn't been merged to mainline upstream. Signed-off-by: Tomohiro Kusumi

[PATCH v4 2/2] serial: 8250_dw: add ACPI support for uart on Hisilicon Hip05 SoC

2016-08-30 Thread Kefeng Wang
Add ACPI identifier for UART on Hisilicon Hip05 SoC, be careful that it is not 16550 compatible, and "reg-io-width" and "reg-shift" need be set properly by _DSD method in DSDT. Signed-off-by: Kefeng Wang --- drivers/tty/serial/8250/8250_dw.c | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH 2/3] autofs: refactor ioctl fn vector in iookup_dev_ioctl()

2016-08-30 Thread Ian Kent
From: Tomohiro Kusumi cmd part of this struct is the same as an index of itself within _ioctls[]. In fact this cmd is unused, so we can drop this part. Signed-off-by: Tomohiro Kusumi Signed-off-by: Ian Kent --- fs/autofs4/dev-ioctl.c | 49 1

[PATCH] serial: 8250_dw: Use an unified new dev variable in probe

2016-08-30 Thread Kefeng Wang
Use an unified new dev variable instead of >dev and p->dev in probe function. Signed-off-by: Kefeng Wang --- drivers/tty/serial/8250/8250_dw.c | 45 --- 1 file changed, 23 insertions(+), 22 deletions(-) diff --git

[PATCH] serial: 8250_dw: Use an unified new dev variable in probe

2016-08-30 Thread Kefeng Wang
Use an unified new dev variable instead of >dev and p->dev in probe function. Signed-off-by: Kefeng Wang --- drivers/tty/serial/8250/8250_dw.c | 45 --- 1 file changed, 23 insertions(+), 22 deletions(-) diff --git a/drivers/tty/serial/8250/8250_dw.c

[PATCH v4 1/2] serial: 8250_dw: make dw8250_set_termios as default set_termios callback

2016-08-30 Thread Kefeng Wang
Make dw8250_set_termios() handle all cases of dw8250_data->clk properly, then we can safely use dw8250_set_termios() as the default set_termios callback instead of serial8250_do_set_termios(), so do it. Signed-off-by: Kefeng Wang --- drivers/tty/serial/8250/8250_dw.c

[PATCH v4 1/2] serial: 8250_dw: make dw8250_set_termios as default set_termios callback

2016-08-30 Thread Kefeng Wang
Make dw8250_set_termios() handle all cases of dw8250_data->clk properly, then we can safely use dw8250_set_termios() as the default set_termios callback instead of serial8250_do_set_termios(), so do it. Signed-off-by: Kefeng Wang --- drivers/tty/serial/8250/8250_dw.c | 5 ++--- 1 file changed,

Re: [RFC v2 09/10] landlock: Handle cgroups (performance)

2016-08-30 Thread Andy Lutomirski
On Tue, Aug 30, 2016 at 6:36 PM, Alexei Starovoitov wrote: > On Tue, Aug 30, 2016 at 02:45:14PM -0700, Andy Lutomirski wrote: >> >> One might argue that landlock shouldn't be tied to seccomp (in theory, >> attached progs could be given access to syscall_get_xyz()),

Re: [RFC v2 09/10] landlock: Handle cgroups (performance)

2016-08-30 Thread Andy Lutomirski
On Tue, Aug 30, 2016 at 6:36 PM, Alexei Starovoitov wrote: > On Tue, Aug 30, 2016 at 02:45:14PM -0700, Andy Lutomirski wrote: >> >> One might argue that landlock shouldn't be tied to seccomp (in theory, >> attached progs could be given access to syscall_get_xyz()), but I > > proposed lsm is way

Re: [PATCH] pstore/ramoops: fixup driver removal

2016-08-30 Thread Namhyung Kim
(Resending with all recipients, sorry) On Sat, Aug 20, 2016 at 1:52 AM, Sebastian Andrzej Siewior wrote: > A basic rmmod ramoops segfaults. Let's see why. > > Since commit 34f0ec82e0a9 ("pstore: Correct the max_dump_cnt clearing of > ramoops") sets ->max_dump_cnt to zero

Re: [PATCH] sparc64 mm: Fix more TSB sizing issues

2016-08-30 Thread Mike Kravetz
On 08/30/2016 03:51 PM, kbuild test robot wrote: > Hi Mike, > > [auto build test ERROR on sparc/master] > [also build test ERROR on v4.8-rc4 next-20160825] > [cannot apply to sparc-next/master] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system]

Re: [PATCH] pstore/ramoops: fixup driver removal

2016-08-30 Thread Namhyung Kim
(Resending with all recipients, sorry) On Sat, Aug 20, 2016 at 1:52 AM, Sebastian Andrzej Siewior wrote: > A basic rmmod ramoops segfaults. Let's see why. > > Since commit 34f0ec82e0a9 ("pstore: Correct the max_dump_cnt clearing of > ramoops") sets ->max_dump_cnt to zero before looping over

Re: [PATCH] sparc64 mm: Fix more TSB sizing issues

2016-08-30 Thread Mike Kravetz
On 08/30/2016 03:51 PM, kbuild test robot wrote: > Hi Mike, > > [auto build test ERROR on sparc/master] > [also build test ERROR on v4.8-rc4 next-20160825] > [cannot apply to sparc-next/master] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system]

[PATCH 1/2] mm: Move definition of 'zone_names' array into mmzone.h

2016-08-30 Thread Anshuman Khandual
zone_names[] is used to identify any zone given it's index which can be used in many other places. So moving the definition into include/linux/mmzone.h for broader access. Signed-off-by: Anshuman Khandual --- include/linux/mmzone.h | 17 +

[PATCH 2/2] mm: Add sysfs interface to dump each node's zonelist information

2016-08-30 Thread Anshuman Khandual
Each individual node in the system has a ZONELIST_FALLBACK zonelist and a ZONELIST_NOFALLBACK zonelist. These zonelists decide fallback order of zones during memory allocations. Sometimes it helps to dump these zonelists to see the priority order of various zones in them. This change just adds a

[PATCH 1/2] mm: Move definition of 'zone_names' array into mmzone.h

2016-08-30 Thread Anshuman Khandual
zone_names[] is used to identify any zone given it's index which can be used in many other places. So moving the definition into include/linux/mmzone.h for broader access. Signed-off-by: Anshuman Khandual --- include/linux/mmzone.h | 17 + mm/page_alloc.c| 17

[PATCH 2/2] mm: Add sysfs interface to dump each node's zonelist information

2016-08-30 Thread Anshuman Khandual
Each individual node in the system has a ZONELIST_FALLBACK zonelist and a ZONELIST_NOFALLBACK zonelist. These zonelists decide fallback order of zones during memory allocations. Sometimes it helps to dump these zonelists to see the priority order of various zones in them. This change just adds a

Re: [PATCH v9 1/2] ASoC: sun4i-codec: Distinguish sun4i from sun7i

2016-08-30 Thread Chen-Yu Tsai
On Tue, Aug 30, 2016 at 1:44 PM, Danny Milosavljevic wrote: > This distinguishes sun4i from sun7i. It is necessary because they use > different registers for the audio mixer. > --- > sound/soc/sunxi/sun4i-codec.c | 44 > +-- > 1

Re: [PATCH v9 1/2] ASoC: sun4i-codec: Distinguish sun4i from sun7i

2016-08-30 Thread Chen-Yu Tsai
On Tue, Aug 30, 2016 at 1:44 PM, Danny Milosavljevic wrote: > This distinguishes sun4i from sun7i. It is necessary because they use > different registers for the audio mixer. > --- > sound/soc/sunxi/sun4i-codec.c | 44 > +-- > 1 file changed, 34

Re: [GIT PULL] bcm2835-dt-next-2016-08-29

2016-08-30 Thread Florian Fainelli
Le 29/08/2016 à 12:38, Eric Anholt a écrit : > The following changes since commit 29b4817d4018df78086157ea3a55c1d9424a7cfc: > > Linux 4.8-rc1 (2016-08-07 18:18:00 -0700) > > are available in the git repository at: > > https://github.com/anholt/linux bcm2835-dt-next-2016-08-29 > > for you

Re: [GIT PULL] bcm2835-dt-next-2016-08-29

2016-08-30 Thread Florian Fainelli
Le 29/08/2016 à 12:38, Eric Anholt a écrit : > The following changes since commit 29b4817d4018df78086157ea3a55c1d9424a7cfc: > > Linux 4.8-rc1 (2016-08-07 18:18:00 -0700) > > are available in the git repository at: > > https://github.com/anholt/linux bcm2835-dt-next-2016-08-29 > > for you

Re: [PATCH v2 2/4] mmc: sdhci-of-arasan: Control clock for accessing syscon

2016-08-30 Thread Ziyuan Xu
Hi Shawn, On 2016年08月31日 09:37, Shawn Lin wrote: In the eariler commit 65820199272d ("Documentation: mmc: sdhci-of-arasan: Add soc-ctl-syscon for corecfg regs"), we introduced syscon to control corecfg_* stuff provided by arasan. But given that we may need to ungate the clock for accessing

Re: [PATCH v2 3/4] arm64: dts: rockchip: add clk_syscon for sdhci on rk3399

2016-08-30 Thread Ziyuan Xu
Hi Shawn, On 2016年08月31日 09:37, Shawn Lin wrote: We are intent on letting the sdhci variant driver handle this optional clock on rk3399 platform now. Signed-off-by: Shawn Lin --- Thanks for your patch, we can gate aclk_emmcgrf now as soon as sdhci driver suspend.

Re: [PATCH v2 2/4] mmc: sdhci-of-arasan: Control clock for accessing syscon

2016-08-30 Thread Ziyuan Xu
Hi Shawn, On 2016年08月31日 09:37, Shawn Lin wrote: In the eariler commit 65820199272d ("Documentation: mmc: sdhci-of-arasan: Add soc-ctl-syscon for corecfg regs"), we introduced syscon to control corecfg_* stuff provided by arasan. But given that we may need to ungate the clock for accessing

Re: [PATCH v2 3/4] arm64: dts: rockchip: add clk_syscon for sdhci on rk3399

2016-08-30 Thread Ziyuan Xu
Hi Shawn, On 2016年08月31日 09:37, Shawn Lin wrote: We are intent on letting the sdhci variant driver handle this optional clock on rk3399 platform now. Signed-off-by: Shawn Lin --- Thanks for your patch, we can gate aclk_emmcgrf now as soon as sdhci driver suspend. Reviewed-by: Ziyuan Xu

Re: [PATCH v3] time: alarmtimer: Add the trcepoints for alarmtimer

2016-08-30 Thread Baolin Wang
Hi Steven, On 30 August 2016 at 23:42, Steven Rostedt wrote: > On Tue, 30 Aug 2016 19:50:20 +0800 > Baolin Wang wrote: > >> Hi, >> >> On 22 August 2016 at 12:23, Baolin Wang wrote: >> > For system debugging, we usually want

Re: [PATCH v3] time: alarmtimer: Add the trcepoints for alarmtimer

2016-08-30 Thread Baolin Wang
Hi Steven, On 30 August 2016 at 23:42, Steven Rostedt wrote: > On Tue, 30 Aug 2016 19:50:20 +0800 > Baolin Wang wrote: > >> Hi, >> >> On 22 August 2016 at 12:23, Baolin Wang wrote: >> > For system debugging, we usually want to know who sets one alarm timer, the >> > time of the timer, when the

Re: [PATCH V3 2/2] usb: phy: phy-brcm-usb: Add Broadcom STB USB Phy driver

2016-08-30 Thread kbuild test robot
ell-known) commit your patch series was built on] [Check https://git-scm.com/docs/git-format-patch for more information] url: https://github.com/0day-ci/linux/commits/Al-Cooper/soc-brcmstb-Add-Product-ID-and-Family-ID-helper-functions/20160830-224057 base: https://git.kernel.org/pub/scm/li

Re: [PATCH V3 2/2] usb: phy: phy-brcm-usb: Add Broadcom STB USB Phy driver

2016-08-30 Thread kbuild test robot
ell-known) commit your patch series was built on] [Check https://git-scm.com/docs/git-format-patch for more information] url: https://github.com/0day-ci/linux/commits/Al-Cooper/soc-brcmstb-Add-Product-ID-and-Family-ID-helper-functions/20160830-224057 base: https://git.kernel.org/pub/scm/li

Re: [PATCH v2 4/4] clk: rockchip: remove CLK_IGNORE_UNUSED flag for aclk_emmc_grf on rk3399

2016-08-30 Thread Ziyuan Xu
On 2016年08月31日 09:37, Shawn Lin wrote: aclk_emmc_grf is used for accessing corecfg_* of emmc stuff within GRF block. We don't need to add CLK_IGNORE_UNUSED for it now as the emmc driver will enable/disable it explicitly when needed. Signed-off-by: Shawn Lin This

Re: [PATCH v2 4/4] clk: rockchip: remove CLK_IGNORE_UNUSED flag for aclk_emmc_grf on rk3399

2016-08-30 Thread Ziyuan Xu
On 2016年08月31日 09:37, Shawn Lin wrote: aclk_emmc_grf is used for accessing corecfg_* of emmc stuff within GRF block. We don't need to add CLK_IGNORE_UNUSED for it now as the emmc driver will enable/disable it explicitly when needed. Signed-off-by: Shawn Lin This patchset test result:

Re: [PATCH v5 00/11] Add HW throttle for Tegra soctherm

2016-08-30 Thread Wei Ni
On 08/19/2016 03:15 PM, Zhang Rui wrote: > On 四, 2016-05-26 at 17:42 +0800, Wei Ni wrote: >> Hi, >> Does there have any comments on this series? >> Let me know if someone has suggestions. >> > I have no objections to this patch set. > As 10 patches out of 11, in this patch series, contain

Re: [PATCH v5 00/11] Add HW throttle for Tegra soctherm

2016-08-30 Thread Wei Ni
On 08/19/2016 03:15 PM, Zhang Rui wrote: > On 四, 2016-05-26 at 17:42 +0800, Wei Ni wrote: >> Hi, >> Does there have any comments on this series? >> Let me know if someone has suggestions. >> > I have no objections to this patch set. > As 10 patches out of 11, in this patch series, contain

[PATCH net] rps: flow_dissector: Fix uninitialized flow_keys used in __skb_get_hash possibly

2016-08-30 Thread fgao
From: Gao Feng The original codes depend on that the function parameters are evaluated from left to right. But the parameter's evaluation order is not defined in C standard actually. When flow_keys_have_l4() is invoked before ___skb_get_hash(skb, , hashrnd) with some compilers

[PATCH net] rps: flow_dissector: Fix uninitialized flow_keys used in __skb_get_hash possibly

2016-08-30 Thread fgao
From: Gao Feng The original codes depend on that the function parameters are evaluated from left to right. But the parameter's evaluation order is not defined in C standard actually. When flow_keys_have_l4() is invoked before ___skb_get_hash(skb, , hashrnd) with some compilers or environment,

[PATCH] pwm/atmel-hlcdc: Add BACKLIGHT_PWM to config dependency

2016-08-30 Thread Hyung Jin Jung
atmel-hlcdc-pwm working with pwm-backlight so that add dependency to avoid user falut. Signed-off-by: HyungJin Jung --- drivers/pwm/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/pwm/Kconfig b/drivers/pwm/Kconfig index 80a566a..b32b2c1 100644 ---

[PATCH] pwm/atmel-hlcdc: Add BACKLIGHT_PWM to config dependency

2016-08-30 Thread Hyung Jin Jung
atmel-hlcdc-pwm working with pwm-backlight so that add dependency to avoid user falut. Signed-off-by: HyungJin Jung --- drivers/pwm/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/pwm/Kconfig b/drivers/pwm/Kconfig index 80a566a..b32b2c1 100644 --- a/drivers/pwm/Kconfig +++

  1   2   3   4   5   6   7   8   9   10   >