[added to the 4.1 stable tree] MIPS: math-emu: Fix jalr emulation when rd == $0

From: Paul Burton This patch has been added to the 4.1 stable tree. If you have any objections, please let us know. === [ Upstream commit ab4a92e66741b35ca12f8497896bafbe579c28a1 ] When emulating a jalr instruction with rd == $0, the code in isBranchInstr

[GIT PULL] ACPI fixes for v4.7-rc2

Hi Linus, Please pull from git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \ acpi-4.7-rc2 to receive ACPI fixes for v4.7-rc2 with top-most commit 60c07f80b04698f6c054b675cb67ec5e7ee8db27 Merge branches 'acpica-fixes', 'acpi-video' and 'acpi-processor' on top of commit

[added to the 4.1 stable tree] SIGNAL: Move generic copy_siginfo() to signal.h

From: James Hogan This patch has been added to the 4.1 stable tree. If you have any objections, please let us know. === [ Upstream commit ca9eb49aa9562eaadf3cea071ec7018ad6800425 ] The generic copy_siginfo() is currently defined in asm-generic/siginfo.h,

Re: [PATCH 1/2] perf: allow add to change event state

On Fri, Jun 03, 2016 at 05:03:31PM -0400, Neil Leeder wrote: > When the platform-specific pmu->add function returns > an error, it may have also changed the event's state. > If so, do not override that new state. This is inadequate; it fails to what the problem is and why this is a good solution.

[GIT PULL] ACPI fixes for v4.7-rc2

Hi Linus, Please pull from git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \ acpi-4.7-rc2 to receive ACPI fixes for v4.7-rc2 with top-most commit 60c07f80b04698f6c054b675cb67ec5e7ee8db27 Merge branches 'acpica-fixes', 'acpi-video' and 'acpi-processor' on top of commit

[added to the 4.1 stable tree] SIGNAL: Move generic copy_siginfo() to signal.h

From: James Hogan This patch has been added to the 4.1 stable tree. If you have any objections, please let us know. === [ Upstream commit ca9eb49aa9562eaadf3cea071ec7018ad6800425 ] The generic copy_siginfo() is currently defined in asm-generic/siginfo.h, after including

Re: [PATCH 1/2] perf: allow add to change event state

On Fri, Jun 03, 2016 at 05:03:31PM -0400, Neil Leeder wrote: > When the platform-specific pmu->add function returns > an error, it may have also changed the event's state. > If so, do not override that new state. This is inadequate; it fails to what the problem is and why this is a good solution.

[added to the 4.1 stable tree] MIPS: math-emu: Fix jalr emulation when rd == $0

From: Paul Burton This patch has been added to the 4.1 stable tree. If you have any objections, please let us know. === [ Upstream commit ab4a92e66741b35ca12f8497896bafbe579c28a1 ] When emulating a jalr instruction with rd == $0, the code in isBranchInstr was incorrectly writing

[GIT PULL] Power management fixes for v4.7-rc2

Hi Linus, Please pull from git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \ pm-4.7-rc2 to receive power management fixes for v4.7-rc2 with top-most commit 8cd8cbd4906126951f1bd6ab8a28ee57f0dc1efc Merge branch 'pm-cpufreq-fixes' on top of commit

[added to the 4.1 stable tree] MIPS: Fix siginfo.h to use strict posix types

From: James Hogan This patch has been added to the 4.1 stable tree. If you have any objections, please let us know. === [ Upstream commit 5daebc477da4dfeb31ae193d83084def58fd2697 ] Commit 85efde6f4e0d ("make exported headers use strict posix types") changed

[added to the 4.1 stable tree] MIPS: Disable preemption during prctl(PR_SET_FP_MODE, ...)

From: Paul Burton This patch has been added to the 4.1 stable tree. If you have any objections, please let us know. === [ Upstream commit bd239f1e1429e7781096bf3884bdb1b2b1bb4f28 ] Whilst a PR_SET_FP_MODE prctl is performed there are decisions made based

[added to the 4.1 stable tree] MIPS: Fix siginfo.h to use strict posix types

From: James Hogan This patch has been added to the 4.1 stable tree. If you have any objections, please let us know. === [ Upstream commit 5daebc477da4dfeb31ae193d83084def58fd2697 ] Commit 85efde6f4e0d ("make exported headers use strict posix types") changed the asm-generic

[added to the 4.1 stable tree] MIPS: Disable preemption during prctl(PR_SET_FP_MODE, ...)

From: Paul Burton This patch has been added to the 4.1 stable tree. If you have any objections, please let us know. === [ Upstream commit bd239f1e1429e7781096bf3884bdb1b2b1bb4f28 ] Whilst a PR_SET_FP_MODE prctl is performed there are decisions made based upon whether the task is

[GIT PULL] Power management fixes for v4.7-rc2

Hi Linus, Please pull from git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \ pm-4.7-rc2 to receive power management fixes for v4.7-rc2 with top-most commit 8cd8cbd4906126951f1bd6ab8a28ee57f0dc1efc Merge branch 'pm-cpufreq-fixes' on top of commit

[added to the 4.1 stable tree] MIPS: Sync icache & dcache in set_pte_at

From: Paul Burton This patch has been added to the 4.1 stable tree. If you have any objections, please let us know. === [ Upstream commit 37d22a0d798b5c938b277d32cfd86dc231381342 ] It's possible for pages to become visible prior to update_mmu_cache running

[added to the 4.1 stable tree] MIPS: Handle highmem pages in __update_cache

From: Paul Burton This patch has been added to the 4.1 stable tree. If you have any objections, please let us know. === [ Upstream commit f4281bba818105c7c91799abe40bc05c0dbdaa25 ] The following patch will expose __update_cache to highmem pages. Handle them

[added to the 4.1 stable tree] MIPS: Sync icache & dcache in set_pte_at

From: Paul Burton This patch has been added to the 4.1 stable tree. If you have any objections, please let us know. === [ Upstream commit 37d22a0d798b5c938b277d32cfd86dc231381342 ] It's possible for pages to become visible prior to update_mmu_cache running if a thread within the

[added to the 4.1 stable tree] MIPS: Handle highmem pages in __update_cache

From: Paul Burton This patch has been added to the 4.1 stable tree. If you have any objections, please let us know. === [ Upstream commit f4281bba818105c7c91799abe40bc05c0dbdaa25 ] The following patch will expose __update_cache to highmem pages. Handle them by mapping them in for

[PATCH] iwlwifi: Remove unused array 'iwlagn_loose_lookup'

gcc-6 reports the following error if -Werror=unused-const-variable is enabled. drivers/net/wireless/intel/iwlwifi/dvm/lib.c:210:21: error: 'iwlagn_loose_lookup' defined but not used Signed-off-by: Guenter Roeck --- drivers/net/wireless/intel/iwlwifi/dvm/lib.c | 17

[PATCH] iwlwifi: Remove unused array 'iwlagn_loose_lookup'

gcc-6 reports the following error if -Werror=unused-const-variable is enabled. drivers/net/wireless/intel/iwlwifi/dvm/lib.c:210:21: error: 'iwlagn_loose_lookup' defined but not used Signed-off-by: Guenter Roeck --- drivers/net/wireless/intel/iwlwifi/dvm/lib.c | 17 - 1

Re: perf crash with tip/perf/core

On Fri, Jun 03, 2016 at 06:27:40PM -0300, Arnaldo Carvalho de Melo wrote: > Em Fri, Jun 03, 2016 at 06:15:15PM -0300, Arnaldo Carvalho de Melo escreveu: > > Hi Peter, > > > > I built what is in tip/perf/core to test the topdown patches > > from Andi but it is crashing on me, 'perf stat' was

Re: perf crash with tip/perf/core

On Fri, Jun 03, 2016 at 06:27:40PM -0300, Arnaldo Carvalho de Melo wrote: > Em Fri, Jun 03, 2016 at 06:15:15PM -0300, Arnaldo Carvalho de Melo escreveu: > > Hi Peter, > > > > I built what is in tip/perf/core to test the topdown patches > > from Andi but it is crashing on me, 'perf stat' was

Re: [PATCH] locking/qspinlock: Use this_cpu_ptr instead of this_cpu_dec

On Fri, Jun 03, 2016 at 05:20:10PM -0400, Waiman Long wrote: > On 06/03/2016 05:48 AM, Pan Xinhui wrote: > >queued_spin_lock_slowpath should not worry about interrupt change > >node->count by accident because ->count is inc and dec when we > >enter/leave queued_spin_lock_slowpath. > > > >So

Re: [PATCH] locking/qspinlock: Use this_cpu_ptr instead of this_cpu_dec

On Fri, Jun 03, 2016 at 05:20:10PM -0400, Waiman Long wrote: > On 06/03/2016 05:48 AM, Pan Xinhui wrote: > >queued_spin_lock_slowpath should not worry about interrupt change > >node->count by accident because ->count is inc and dec when we > >enter/leave queued_spin_lock_slowpath. > > > >So

RE: [PATCH 1/1] scsi: storvsc: Filter out storvsc messages CD-ROM medium not present

> -Original Message- > From: Cathy Avery [mailto:cav...@redhat.com] > Sent: Monday, May 23, 2016 7:29 AM > To: linux-s...@vger.kernel.org > Cc: KY Srinivasan ; Haiyang Zhang > ; martin.peter...@oracle.com; > j...@linux.vnet.ibm.com;

RE: [PATCH 1/1] scsi: storvsc: Filter out storvsc messages CD-ROM medium not present

> -Original Message- > From: Cathy Avery [mailto:cav...@redhat.com] > Sent: Monday, May 23, 2016 7:29 AM > To: linux-s...@vger.kernel.org > Cc: KY Srinivasan ; Haiyang Zhang > ; martin.peter...@oracle.com; > j...@linux.vnet.ibm.com; de...@linuxdriverproject.org; linux- >

[PATCH] b43: Remove unused phy_a code

gcc-6 reports the following error with -Werror=unused-const-variable. drivers/net/wireless/broadcom/b43/phy_a.c:576:40: error: 'b43_phyops_a' defined but not used Turns out a lot of code in this file is unused, so let's remove it. Reported-by: Fengguang Wu

[PATCH] b43: Remove unused phy_a code

gcc-6 reports the following error with -Werror=unused-const-variable. drivers/net/wireless/broadcom/b43/phy_a.c:576:40: error: 'b43_phyops_a' defined but not used Turns out a lot of code in this file is unused, so let's remove it. Reported-by: Fengguang Wu [0-day test robot]

Memory leak in block I/O (ext4) for 4.7-rc1 - bisected to commit 9082e87bfbf8

Several memory leaks of the type shown below are reported by kmemleak for the block I/O system, and ext4 in particular: unreferenced object 0x8801ff71f500 (size 256): comm "kworker/u16:4", pid 76, jiffies 4294707552 (age 97.892s) hex dump (first 32 bytes): c0 20 08 00 00 ea ff ff 00

Memory leak in block I/O (ext4) for 4.7-rc1 - bisected to commit 9082e87bfbf8

Several memory leaks of the type shown below are reported by kmemleak for the block I/O system, and ext4 in particular: unreferenced object 0x8801ff71f500 (size 256): comm "kworker/u16:4", pid 76, jiffies 4294707552 (age 97.892s) hex dump (first 32 bytes): c0 20 08 00 00 ea ff ff 00

Re: [PATCH v4 net-next 00/13] net: hns: add support of ACPI

On Friday, June 03, 2016 10:55:08 AM Yisen Zhuang wrote: > From: Kejian Yan > > This series adds HNS support of acpi. The routine will call some ACPI > helper functions, like acpi_dev_found() and acpi_evaluate_dsm(), which > are not included in other cases. In order to make

Re: [PATCH v4 net-next 00/13] net: hns: add support of ACPI

On Friday, June 03, 2016 10:55:08 AM Yisen Zhuang wrote: > From: Kejian Yan > > This series adds HNS support of acpi. The routine will call some ACPI > helper functions, like acpi_dev_found() and acpi_evaluate_dsm(), which > are not included in other cases. In order to make system compile >

Re: perf crash with tip/perf/core

Em Fri, Jun 03, 2016 at 06:15:15PM -0300, Arnaldo Carvalho de Melo escreveu: > Hi Peter, > > I built what is in tip/perf/core to test the topdown patches > from Andi but it is crashing on me, 'perf stat' was ok, but then I tried > 'perf trace' and got the NULL deref below, bet 'perf record'

Re: perf crash with tip/perf/core

Em Fri, Jun 03, 2016 at 06:15:15PM -0300, Arnaldo Carvalho de Melo escreveu: > Hi Peter, > > I built what is in tip/perf/core to test the topdown patches > from Andi but it is crashing on me, 'perf stat' was ok, but then I tried > 'perf trace' and got the NULL deref below, bet 'perf record'

Re: Dcache oops

On Fri, Jun 03, 2016 at 02:18:15PM -0700, Linus Torvalds wrote: > So something must have corrupted the qstr. > > The remaining length *should* in %edi, judging by the > >0x81243b82 <+306>: cmp$0x7,%edi > > in the __d_lookup() disassembly. And %rdi contains 2, so there were >

Re: [kernel-hardening] [PATCH 2/2] arm: apply more __ro_after_init

On Fri, Jun 3, 2016 at 11:51 AM, Greg KH wrote: > On Fri, Jun 03, 2016 at 11:40:24AM -0700, Kees Cook wrote: >> Guided by grsecurity's analogous __read_only markings in arch/arm, >> this applies several uses of __ro_after_init to structures that are >> only updated

Re: Dcache oops

On Fri, Jun 03, 2016 at 02:18:15PM -0700, Linus Torvalds wrote: > So something must have corrupted the qstr. > > The remaining length *should* in %edi, judging by the > >0x81243b82 <+306>: cmp$0x7,%edi > > in the __d_lookup() disassembly. And %rdi contains 2, so there were >

Re: [kernel-hardening] [PATCH 2/2] arm: apply more __ro_after_init

On Fri, Jun 3, 2016 at 11:51 AM, Greg KH wrote: > On Fri, Jun 03, 2016 at 11:40:24AM -0700, Kees Cook wrote: >> Guided by grsecurity's analogous __read_only markings in arch/arm, >> this applies several uses of __ro_after_init to structures that are >> only updated during __init. >> >>

Re: [v2, 2/2] phy: rockchip-inno-usb2: add a new driver for Rockchip usb2phy

Am Freitag, 3. Juni 2016, 12:59:22 schrieb Guenter Roeck: > On Thu, Jun 02, 2016 at 02:48:10PM +0800, Frank Wang wrote: > > The newer SoCs (rk3366, rk3399) take a different usb-phy IP block > > than rk3288 and before, and most of phy-related registers are also > > different from the past, so a new

Re: [v2, 2/2] phy: rockchip-inno-usb2: add a new driver for Rockchip usb2phy

Am Freitag, 3. Juni 2016, 12:59:22 schrieb Guenter Roeck: > On Thu, Jun 02, 2016 at 02:48:10PM +0800, Frank Wang wrote: > > The newer SoCs (rk3366, rk3399) take a different usb-phy IP block > > than rk3288 and before, and most of phy-related registers are also > > different from the past, so a new

Re: [PATCH] locking/qspinlock: Use this_cpu_ptr instead of this_cpu_dec

On 06/03/2016 05:48 AM, Pan Xinhui wrote: queued_spin_lock_slowpath should not worry about interrupt change node->count by accident because ->count is inc and dec when we enter/leave queued_spin_lock_slowpath. So this_cpu_dec() does some no point things here, lets use this_cpu_ptr for a small

Re: [PATCH] locking/qspinlock: Use this_cpu_ptr instead of this_cpu_dec

On 06/03/2016 05:48 AM, Pan Xinhui wrote: queued_spin_lock_slowpath should not worry about interrupt change node->count by accident because ->count is inc and dec when we enter/leave queued_spin_lock_slowpath. So this_cpu_dec() does some no point things here, lets use this_cpu_ptr for a small

Re: Dcache oops

On Fri, Jun 3, 2016 at 1:07 PM, Al Viro wrote: > > Aha... It's load_unaligned_zeropad() from dentry_string_cmp(), hitting > a genuinely unmapped address. That sends it into fixup, where it tries to > load an aligned word containing the address in question, in hope that

Re: Dcache oops

On Fri, Jun 3, 2016 at 1:07 PM, Al Viro wrote: > > Aha... It's load_unaligned_zeropad() from dentry_string_cmp(), hitting > a genuinely unmapped address. That sends it into fixup, where it tries to > load an aligned word containing the address in question, in hope that > fault was on attempt to

Re: Dcache oops

On Jun 3, 2016, at 4:07 PM, Al Viro wrote: > On Fri, Jun 03, 2016 at 02:35:41PM -0400, Oleg Drokin wrote: > [ 2642.364383] BUG: unable to handle kernel paging request at 880113f82000 [ 2642.365014] IP: [] bad_gs+0xd1d/0x1ba9 >>> >>> *ow* >>> Could you dump your vmlinux (and

Re: Dcache oops

On Jun 3, 2016, at 4:07 PM, Al Viro wrote: > On Fri, Jun 03, 2016 at 02:35:41PM -0400, Oleg Drokin wrote: > [ 2642.364383] BUG: unable to handle kernel paging request at 880113f82000 [ 2642.365014] IP: [] bad_gs+0xd1d/0x1ba9 >>> >>> *ow* >>> Could you dump your vmlinux (and

perf crash with tip/perf/core

Hi Peter, I built what is in tip/perf/core to test the topdown patches from Andi but it is crashing on me, 'perf stat' was ok, but then I tried 'perf trace' and got the NULL deref below, bet 'perf record' will do the same. BUG: unable to handle kernel NULL pointer dereference at

perf crash with tip/perf/core

Hi Peter, I built what is in tip/perf/core to test the topdown patches from Andi but it is crashing on me, 'perf stat' was ok, but then I tried 'perf trace' and got the NULL deref below, bet 'perf record' will do the same. BUG: unable to handle kernel NULL pointer dereference at

Re: [PATCH 3/3] sched/debug: remove unnecessary CONFIG_SCHEDSTATS checks

On Fri, Jun 03, 2016 at 03:44:41PM -0500, Josh Poimboeuf wrote: > --- a/kernel/sched/fair.c > +++ b/kernel/sched/fair.c > @@ -3447,7 +3447,7 @@ set_next_entity(struct cfs_rq *cfs_rq, struct > sched_entity *se) > > update_stats_curr_start(cfs_rq, se); > cfs_rq->curr = se; > -#ifdef

Re: [PATCH 3/3] sched/debug: remove unnecessary CONFIG_SCHEDSTATS checks

On Fri, Jun 03, 2016 at 03:44:41PM -0500, Josh Poimboeuf wrote: > --- a/kernel/sched/fair.c > +++ b/kernel/sched/fair.c > @@ -3447,7 +3447,7 @@ set_next_entity(struct cfs_rq *cfs_rq, struct > sched_entity *se) > > update_stats_curr_start(cfs_rq, se); > cfs_rq->curr = se; > -#ifdef

Re: [PATCH v2 2/4] gpio: Allow PC/104 devices on X86_64

On Fri, Jun 03, 2016 at 10:57:03PM +0200, Pavel Machek wrote: >Hi! > >> With the introduction of the ISA_BUS_API Kconfig option, ISA-style >> drivers may be built for X86_64 architectures. This patch changes the >> ISA Kconfig option dependency of the PC/104 drivers to ISA_BUS_API, thus >>

Re: [PATCH v2 2/4] gpio: Allow PC/104 devices on X86_64

On Fri, Jun 03, 2016 at 10:57:03PM +0200, Pavel Machek wrote: >Hi! > >> With the introduction of the ISA_BUS_API Kconfig option, ISA-style >> drivers may be built for X86_64 architectures. This patch changes the >> ISA Kconfig option dependency of the PC/104 drivers to ISA_BUS_API, thus >>

Re: [PATCH v9 00/14] Add support for remote unwind

Em Fri, Jun 03, 2016 at 06:06:02PM -0300, Arnaldo Carvalho de Melo escreveu: > Em Fri, Jun 03, 2016 at 04:42:05PM -0300, Arnaldo Carvalho de Melo escreveu: > > Em Fri, Jun 03, 2016 at 09:06:29AM +0200, Jiri Olsa escreveu: > > > On Fri, Jun 03, 2016 at 03:33:09AM +, He Kuang wrote: > > > > v9:

Re: [PATCH v9 00/14] Add support for remote unwind

Em Fri, Jun 03, 2016 at 06:06:02PM -0300, Arnaldo Carvalho de Melo escreveu: > Em Fri, Jun 03, 2016 at 04:42:05PM -0300, Arnaldo Carvalho de Melo escreveu: > > Em Fri, Jun 03, 2016 at 09:06:29AM +0200, Jiri Olsa escreveu: > > > On Fri, Jun 03, 2016 at 03:33:09AM +, He Kuang wrote: > > > > v9:

Re: [PATCH 14/14] regulator: pwm: Document pwm-dutycycle-unit and pwm-dutycycle-range

On Fri, Jun 03, 2016 at 10:23:12AM +0200, Boris Brezillon wrote: > Document the pwm-dutycycle-unit and pwm-dutycycle-range properties. > > Signed-off-by: Boris Brezillon > --- > .../devicetree/bindings/regulator/pwm-regulator.txt | 12 >

Re: [PATCH 14/14] regulator: pwm: Document pwm-dutycycle-unit and pwm-dutycycle-range

On Fri, Jun 03, 2016 at 10:23:12AM +0200, Boris Brezillon wrote: > Document the pwm-dutycycle-unit and pwm-dutycycle-range properties. > > Signed-off-by: Boris Brezillon > --- > .../devicetree/bindings/regulator/pwm-regulator.txt | 12 > > 1 file changed, 12 insertions(+)

Re: [PATCH v9 00/14] Add support for remote unwind

Em Fri, Jun 03, 2016 at 04:42:05PM -0300, Arnaldo Carvalho de Melo escreveu: > Em Fri, Jun 03, 2016 at 09:06:29AM +0200, Jiri Olsa escreveu: > > On Fri, Jun 03, 2016 at 03:33:09AM +, He Kuang wrote: > > > v9: > > > - Change function unwind__register_ops() to static. > > > - Move up

Re: [PATCH v9 00/14] Add support for remote unwind

Em Fri, Jun 03, 2016 at 04:42:05PM -0300, Arnaldo Carvalho de Melo escreveu: > Em Fri, Jun 03, 2016 at 09:06:29AM +0200, Jiri Olsa escreveu: > > On Fri, Jun 03, 2016 at 03:33:09AM +, He Kuang wrote: > > > v9: > > > - Change function unwind__register_ops() to static. > > > - Move up

[PATCH 2/2] soc: qcom: add l2 cache perf events driver

Adds perf events support for L2 cache PMU. The L2 cache PMU driver is named 'l2cache' and can be used with perf events to profile L2 events such as cache hits and misses. Signed-off-by: Neil Leeder --- drivers/soc/qcom/Kconfig | 10 +

[PATCH 1/2] perf: allow add to change event state

When the platform-specific pmu->add function returns an error, it may have also changed the event's state. If so, do not override that new state. Signed-off-by: Neil Leeder --- kernel/events/core.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git

[PATCH 2/2] soc: qcom: add l2 cache perf events driver

Adds perf events support for L2 cache PMU. The L2 cache PMU driver is named 'l2cache' and can be used with perf events to profile L2 events such as cache hits and misses. Signed-off-by: Neil Leeder --- drivers/soc/qcom/Kconfig | 10 + drivers/soc/qcom/Makefile | 1

[PATCH 1/2] perf: allow add to change event state

When the platform-specific pmu->add function returns an error, it may have also changed the event's state. If so, do not override that new state. Signed-off-by: Neil Leeder --- kernel/events/core.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/kernel/events/core.c

Re: [PATCH 1/3] ntb_perf: Allow limiting the size of the memory windows

On Fri, 2016-06-03 at 14:50 -0600, Logan Gunthorpe wrote: > On my system, dma_alloc_coherent won't produce memory anywhere > near the size of the BAR. So I needed a way to limit this. > > It's pretty much copied straight from ntb_transport. > > Signed-off-by: Logan Gunthorpe

Re: [PATCH 00/10] Documentation/Sphinx

On Mon, 30 May 2016 23:05:34 +0300 Jani Nikula wrote: > To be clear, the "sphinx-for-docs-next" branch of [1], [2] is what I > propose to merge at this time. There's the Sphinx configuration, kernel > build integration, Sphinx kernel-doc extension, tons of kernel-doc >

Re: [PATCH 1/3] ntb_perf: Allow limiting the size of the memory windows

On Fri, 2016-06-03 at 14:50 -0600, Logan Gunthorpe wrote: > On my system, dma_alloc_coherent won't produce memory anywhere > near the size of the BAR. So I needed a way to limit this. > > It's pretty much copied straight from ntb_transport. > > Signed-off-by: Logan Gunthorpe Acked-by: Dave

Re: [PATCH 00/10] Documentation/Sphinx

On Mon, 30 May 2016 23:05:34 +0300 Jani Nikula wrote: > To be clear, the "sphinx-for-docs-next" branch of [1], [2] is what I > propose to merge at this time. There's the Sphinx configuration, kernel > build integration, Sphinx kernel-doc extension, tons of kernel-doc > updates, etc. OK, I do

[PATCH 0/2] qcom: add l2 cache perf events driver

This adds a new dynamic PMU to the Perf Events framework to program and control the L2 cache PMUs in some Qualcomm Technologies SOCs. The driver exports formatting and event information to sysfs so it can be used by the perf user space tools with the syntax: perf stat -e l2cache/event=0x42/ One

[PATCH 0/2] qcom: add l2 cache perf events driver

This adds a new dynamic PMU to the Perf Events framework to program and control the L2 cache PMUs in some Qualcomm Technologies SOCs. The driver exports formatting and event information to sysfs so it can be used by the perf user space tools with the syntax: perf stat -e l2cache/event=0x42/ One

Re: [PATCH 13/14] regulator: pwm: Support extra continuous mode cases

Hi Boris, On Fri, Jun 03, 2016 at 10:23:11AM +0200, Boris Brezillon wrote: > The continuous mode allows one to declare a PWM regulator without having > to declare the voltage <-> dutycycle association table. It works fine as > long as your voltage(dutycycle) function is linear, but also has the >

Re: [PATCH 13/14] regulator: pwm: Support extra continuous mode cases

Hi Boris, On Fri, Jun 03, 2016 at 10:23:11AM +0200, Boris Brezillon wrote: > The continuous mode allows one to declare a PWM regulator without having > to declare the voltage <-> dutycycle association table. It works fine as > long as your voltage(dutycycle) function is linear, but also has the >

[PATCH v2] soc: qcom: provide mechanism for drivers to access L2 registers

L2 registers are accessed using a select register and data register pair. To prevent multiple concurrent writes to the select register by independent drivers, the write to the select register and the associated access of the data register are protected with a lock. All drivers accessing the L2

[PATCH v2] soc: qcom: provide mechanism for drivers to access L2 registers

L2 registers are accessed using a select register and data register pair. To prevent multiple concurrent writes to the select register by independent drivers, the write to the select register and the associated access of the data register are protected with a lock. All drivers accessing the L2

Re: [PATCH] locking/qrwlock: fix write unlock issue in big endian

On 06/03/2016 03:17 AM, xinhui wrote: On 2016年06月02日 19:02, Peter Zijlstra wrote: On Thu, Jun 02, 2016 at 12:44:51PM +0200, Arnd Bergmann wrote: On Thursday, June 2, 2016 6:09:08 PM CEST Pan Xinhui wrote: diff --git a/include/asm-generic/qrwlock.h b/include/asm-generic/qrwlock.h index

[GIT PULL] Btrfs

Hi Linus, My for-linus-4.7 branch has some fixes: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.7 I realized as I was prepping this pull that my tip commit still had Facebook task numbers and other internal metadata in it. So I had to reword the description,

Re: [PATCH] locking/qrwlock: fix write unlock issue in big endian

On 06/03/2016 03:17 AM, xinhui wrote: On 2016年06月02日 19:02, Peter Zijlstra wrote: On Thu, Jun 02, 2016 at 12:44:51PM +0200, Arnd Bergmann wrote: On Thursday, June 2, 2016 6:09:08 PM CEST Pan Xinhui wrote: diff --git a/include/asm-generic/qrwlock.h b/include/asm-generic/qrwlock.h index

[GIT PULL] Btrfs

Hi Linus, My for-linus-4.7 branch has some fixes: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.7 I realized as I was prepping this pull that my tip commit still had Facebook task numbers and other internal metadata in it. So I had to reword the description,

Re: [PATCH v2 2/4] gpio: Allow PC/104 devices on X86_64

Hi! > With the introduction of the ISA_BUS_API Kconfig option, ISA-style > drivers may be built for X86_64 architectures. This patch changes the > ISA Kconfig option dependency of the PC/104 drivers to ISA_BUS_API, thus > allowing them to build for X86_64 as they are expected to. > > Cc: Guenter

[PATCH v3] virtio-net: Add initial MTU advice feature

This commit adds the feature bit and associated mtu device entry for the virtio network device. When a virtio device comes up, it checks the feature bit for the VIRTIO_NET_F_MTU feature. If such feature bit is enabled, the driver will read the advised MTU and use it as the initial value.

Re: [PATCH v2 2/4] gpio: Allow PC/104 devices on X86_64

Hi! > With the introduction of the ISA_BUS_API Kconfig option, ISA-style > drivers may be built for X86_64 architectures. This patch changes the > ISA Kconfig option dependency of the PC/104 drivers to ISA_BUS_API, thus > allowing them to build for X86_64 as they are expected to. > > Cc: Guenter

[PATCH v3] virtio-net: Add initial MTU advice feature

This commit adds the feature bit and associated mtu device entry for the virtio network device. When a virtio device comes up, it checks the feature bit for the VIRTIO_NET_F_MTU feature. If such feature bit is enabled, the driver will read the advised MTU and use it as the initial value.

Re: [PATCH 12/14] regulator: pwm: Retrieve correct voltage

On Fri, Jun 03, 2016 at 10:23:10AM +0200, Boris Brezillon wrote: > The continuous PWM voltage regulator is caching the voltage value in > the ->volt_uV field. While most of the time this value should reflect the > real voltage, sometime it can be sightly different if the PWM device > rounded the

Re: [PATCH 12/14] regulator: pwm: Retrieve correct voltage

On Fri, Jun 03, 2016 at 10:23:10AM +0200, Boris Brezillon wrote: > The continuous PWM voltage regulator is caching the voltage value in > the ->volt_uV field. While most of the time this value should reflect the > real voltage, sometime it can be sightly different if the PWM device > rounded the

Re: [RFC PATCH 0/4] Make inotify instance/watches be accounted per userns

Nikolay Borisov writes: > On 06/02/2016 07:58 PM, Eric W. Biederman wrote: >> >> Nikolay please see my question for you at the end. [snip] >> All of that said there is definitely a practical question that needs to >> be asked. Nikolay how did you get into this situation? A

Re: [RFC PATCH 0/4] Make inotify instance/watches be accounted per userns

Nikolay Borisov writes: > On 06/02/2016 07:58 PM, Eric W. Biederman wrote: >> >> Nikolay please see my question for you at the end. [snip] >> All of that said there is definitely a practical question that needs to >> be asked. Nikolay how did you get into this situation? A typical user >>

Re: [PATCH 11/14] regulator: pwm: properly initialize the ->state field

On Fri, Jun 03, 2016 at 10:23:09AM +0200, Boris Brezillon wrote: > The ->state field is currently initialized to 0, thus referencing the > voltage selector at index 0, which might not reflect the current voltage > value. > If possible, retrieve the current voltage selector from the PWM state, else

Re: [PATCH 11/14] regulator: pwm: properly initialize the ->state field

On Fri, Jun 03, 2016 at 10:23:09AM +0200, Boris Brezillon wrote: > The ->state field is currently initialized to 0, thus referencing the > voltage selector at index 0, which might not reflect the current voltage > value. > If possible, retrieve the current voltage selector from the PWM state, else

Re: [PATCH 10/14] regulator: pwm: Switch to the atomic PWM API

+ Laxman Hi, On Fri, Jun 03, 2016 at 10:23:08AM +0200, Boris Brezillon wrote: > Use the atomic API wherever appropriate and get rid of pwm_apply_args() > call (the reference period and polarity are now explicitly set when > calling pwm_apply_state()). > > We also make use of the

Re: [PATCH 10/14] regulator: pwm: Switch to the atomic PWM API

+ Laxman Hi, On Fri, Jun 03, 2016 at 10:23:08AM +0200, Boris Brezillon wrote: > Use the atomic API wherever appropriate and get rid of pwm_apply_args() > call (the reference period and polarity are now explicitly set when > calling pwm_apply_state()). > > We also make use of the

[PATCH] libertas_tf: Drop unused variable and define

gcc-6 reports: drivers/net/wireless/marvell/libertas_tf/main.c:30:19: error: 'lbtf_driver_version' defined but not used with -Werror=unused-const-variable=. Reported-by: Fengguang Wu [0-day test robot] Signed-off-by: Guenter Roeck ---

[PATCH] libertas_tf: Drop unused variable and define

gcc-6 reports: drivers/net/wireless/marvell/libertas_tf/main.c:30:19: error: 'lbtf_driver_version' defined but not used with -Werror=unused-const-variable=. Reported-by: Fengguang Wu [0-day test robot] Signed-off-by: Guenter Roeck --- drivers/net/wireless/marvell/libertas_tf/main.c |

Re: rst2pdf (was [PATCH 00/10] Documentation/Sphinx)

On Mon, 30 May 2016 23:05:34 +0300 Jani Nikula wrote: > > I can't recommend to use rst2pdf (it is less maintained), use default > > sphinx LaTeX toolchain. > > I think we'll use whatever works, rst2pdf seemed to work for now, but we > can change if needed. I really

Re: rst2pdf (was [PATCH 00/10] Documentation/Sphinx)

On Mon, 30 May 2016 23:05:34 +0300 Jani Nikula wrote: > > I can't recommend to use rst2pdf (it is less maintained), use default > > sphinx LaTeX toolchain. > > I think we'll use whatever works, rst2pdf seemed to work for now, but we > can change if needed. I really like the idea of using

Re: [PATCH V2] checkpatch: Flag code that returns a negative number less than 1

On 06/03/2016 03:42 PM, Joe Perches wrote: > On Fri, 2016-06-03 at 15:02 -0500, Nishanth Menon wrote: >> In some functions, returning a -ve decimal value is actually a valid >> return condition when the function is returning a value, however, it >> can also be misused for returning an error value

Re: [PATCH V2] checkpatch: Flag code that returns a negative number less than 1

On 06/03/2016 03:42 PM, Joe Perches wrote: > On Fri, 2016-06-03 at 15:02 -0500, Nishanth Menon wrote: >> In some functions, returning a -ve decimal value is actually a valid >> return condition when the function is returning a value, however, it >> can also be misused for returning an error value

[PATCH 2/3] sched/debug: always show nr_migrations

The nr_migrations field is updated independently of CONFIG_SCHEDSTATS, so it can be displayed regardless. Signed-off-by: Josh Poimboeuf --- kernel/sched/debug.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/sched/debug.c b/kernel/sched/debug.c

[PATCH 3/3] sched/debug: remove unnecessary CONFIG_SCHEDSTATS checks

The schedstat_enabled() macro already has an implicit check for CONFIG_SCHEDSTATS, so these explicit checks can be removed. Signed-off-by: Josh Poimboeuf --- kernel/sched/debug.c | 7 +-- kernel/sched/fair.c | 4 ++-- 2 files changed, 3 insertions(+), 8 deletions(-)

[PATCH 2/3] sched/debug: always show nr_migrations

The nr_migrations field is updated independently of CONFIG_SCHEDSTATS, so it can be displayed regardless. Signed-off-by: Josh Poimboeuf --- kernel/sched/debug.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/sched/debug.c b/kernel/sched/debug.c index 500ea7e..cbdf208

[PATCH 3/3] sched/debug: remove unnecessary CONFIG_SCHEDSTATS checks

The schedstat_enabled() macro already has an implicit check for CONFIG_SCHEDSTATS, so these explicit checks can be removed. Signed-off-by: Josh Poimboeuf --- kernel/sched/debug.c | 7 +-- kernel/sched/fair.c | 4 ++-- 2 files changed, 3 insertions(+), 8 deletions(-) diff --git

[PATCH 1/3] sched/debug: fix /proc/sched_debug regression

Commit cb2517653fcc ("sched/debug: Make schedstats a runtime tunable that is disabled by default") introduced a bug when CONFIG_SCHEDSTATS is enabled and the runtime tunable is disabled (which is the default). The wait-time, sum-exec, and sum-sleep fields are missing from the /proc/sched_debug

[PATCH 1/3] sched/debug: fix /proc/sched_debug regression

Commit cb2517653fcc ("sched/debug: Make schedstats a runtime tunable that is disabled by default") introduced a bug when CONFIG_SCHEDSTATS is enabled and the runtime tunable is disabled (which is the default). The wait-time, sum-exec, and sum-sleep fields are missing from the /proc/sched_debug

<    1   2   3   4   5   6   7   8   9   10   >