Re: PROBLEM: Resume form hibernate broken by setting NX on gap

On Saturday, June 11, 2016 02:13:45 AM Rafael J. Wysocki wrote: > On Saturday, June 11, 2016 12:33:31 AM Rafael J. Wysocki wrote: > > On Friday, June 10, 2016 04:28:01 PM Logan Gunthorpe wrote: > > > > > > On 10/06/16 04:29 PM, Rafael J. Wysocki wrote: > > > > OK, I have a theory, but I need a

Re: PROBLEM: Resume form hibernate broken by setting NX on gap

On Saturday, June 11, 2016 02:13:45 AM Rafael J. Wysocki wrote: > On Saturday, June 11, 2016 12:33:31 AM Rafael J. Wysocki wrote: > > On Friday, June 10, 2016 04:28:01 PM Logan Gunthorpe wrote: > > > > > > On 10/06/16 04:29 PM, Rafael J. Wysocki wrote: > > > > OK, I have a theory, but I need a

[PATCH 1/1] kernel/sysctl.c: avoid overflow

An undetected overflow may occur in do_proc_dointvec_minmax_conv_param. Signed-off-by: Heinrich Schuchardt --- kernel/sysctl.c | 12 +++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/kernel/sysctl.c b/kernel/sysctl.c index 35f0dcb..a9e7be3 100644 ---

[PATCH 1/1] kernel/sysctl.c: avoid overflow

An undetected overflow may occur in do_proc_dointvec_minmax_conv_param. Signed-off-by: Heinrich Schuchardt --- kernel/sysctl.c | 12 +++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/kernel/sysctl.c b/kernel/sysctl.c index 35f0dcb..a9e7be3 100644 --- a/kernel/sysctl.c

[[DEBUG] force CONFIG_DEBUG_UACCESS] 4805ee99b0: BUG: tried to access memory at 0x9eaf48b while not in USER_DS

FYI, we noticed the following commit: https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git x86/uaccess commit 4805ee99b0ac1282d09545e294e218a575208b72 ("[DEBUG] force CONFIG_DEBUG_UACCESS") on test machine: vm-lkp-wsx03-quantal-i386: 1 threads qemu-system-i386 -enable-kvm with

[[DEBUG] force CONFIG_DEBUG_UACCESS] 4805ee99b0: BUG: tried to access memory at 0x9eaf48b while not in USER_DS

FYI, we noticed the following commit: https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git x86/uaccess commit 4805ee99b0ac1282d09545e294e218a575208b72 ("[DEBUG] force CONFIG_DEBUG_UACCESS") on test machine: vm-lkp-wsx03-quantal-i386: 1 threads qemu-system-i386 -enable-kvm with

Re: [PATCH] perf tools: Fix crash in build_id_cache__kallsyms_path()

On Tue, 7 Jun 2016 03:54:38 + Wang Nan wrote: > build_id_cache__kallsyms_path() accept string buffer but also alloc buffer > by itself using asnprintf. Unfortunately, the only user of it passes it > a stack-allocated buffer. Freeing it causes crash like this: > > $

Re: [PATCH] perf tools: Fix crash in build_id_cache__kallsyms_path()

On Tue, 7 Jun 2016 03:54:38 + Wang Nan wrote: > build_id_cache__kallsyms_path() accept string buffer but also alloc buffer > by itself using asnprintf. Unfortunately, the only user of it passes it > a stack-allocated buffer. Freeing it causes crash like this: > > $ perf script > *** Error

[BUG] False positive in scripts/checkpatch.pl

scripts/checkpatch.pl reports ERROR: Please use git commit description style 'commit <12+ chars of sha1> ("")'- ie: 'commit 0123456789ab ("commit description")' for this patch. On 64bit systems an undetected overflow may occur in do_proc_dointvec_minmax_conv_param as can be demonstrated with

[BUG] False positive in scripts/checkpatch.pl

scripts/checkpatch.pl reports ERROR: Please use git commit description style 'commit <12+ chars of sha1> ("")'- ie: 'commit 0123456789ab ("commit description")' for this patch. On 64bit systems an undetected overflow may occur in do_proc_dointvec_minmax_conv_param as can be demonstrated with

Re: [PATCH 48/48] ARM: dts: at91: kizbox: switch to new pwm-atmel-tcb binding

Hi, [auto build test ERROR on at91/at91-next] [also build test ERROR on v4.7-rc2 next-20160609] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 48/48] ARM: dts: at91: kizbox: switch to new pwm-atmel-tcb binding

Hi, [auto build test ERROR on at91/at91-next] [also build test ERROR on v4.7-rc2 next-20160609] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] watchdog: drop redundant 'default n' option for WATCHDOG_SYSFS

On 06/08/2016 08:16 AM, Vladimir Zapolskiy wrote: The option 'default n' and its absence are equal for kbuild, which makes explicit 'default n' redundant. Signed-off-by: Vladimir Zapolskiy Reviewed-by: Guenter Roeck ---

Re: [PATCH] watchdog: drop redundant 'default n' option for WATCHDOG_SYSFS

On 06/08/2016 08:16 AM, Vladimir Zapolskiy wrote: The option 'default n' and its absence are equal for kbuild, which makes explicit 'default n' redundant. Signed-off-by: Vladimir Zapolskiy Reviewed-by: Guenter Roeck --- drivers/watchdog/Kconfig | 1 - 1 file changed, 1 deletion(-)

Re: net: stmmac: dwmac-rk: fixes for Wake-on-Lan on RK3288

From: Vincent Palatin Date: Fri, 10 Jun 2016 18:00:36 -0700 > In order to support Wake-On-Lan when using the RK3288 integrated MAC > (with an external RGMII PHY), we need to avoid shutting down the regulator > of the external PHY when the MAC is suspended as it's currently

Re: [PATCH perf/core v10 10/23] perf probe: Remove caches when --cache is given

On Thu, 9 Jun 2016 11:28:28 -0300 Arnaldo Carvalho de Melo wrote: > > diff --git a/tools/perf/util/probe-file.c b/tools/perf/util/probe-file.c > > index a6d4a67..f687607 100644 > > --- a/tools/perf/util/probe-file.c > > +++ b/tools/perf/util/probe-file.c > > @@ -660,19 +660,39

Re: [PATCH] net: ethernet: ti: cpsw: use destroy ctlr to destroy channels

From: Ivan Khoronzhuk Date: Sat, 11 Jun 2016 01:11:54 +0300 > Based on master master... of what?

Re: net: stmmac: dwmac-rk: fixes for Wake-on-Lan on RK3288

From: Vincent Palatin Date: Fri, 10 Jun 2016 18:00:36 -0700 > In order to support Wake-On-Lan when using the RK3288 integrated MAC > (with an external RGMII PHY), we need to avoid shutting down the regulator > of the external PHY when the MAC is suspended as it's currently done in the > MAC >

Re: [PATCH perf/core v10 10/23] perf probe: Remove caches when --cache is given

On Thu, 9 Jun 2016 11:28:28 -0300 Arnaldo Carvalho de Melo wrote: > > diff --git a/tools/perf/util/probe-file.c b/tools/perf/util/probe-file.c > > index a6d4a67..f687607 100644 > > --- a/tools/perf/util/probe-file.c > > +++ b/tools/perf/util/probe-file.c > > @@ -660,19 +660,39 @@ out: > >

Re: [PATCH] net: ethernet: ti: cpsw: use destroy ctlr to destroy channels

From: Ivan Khoronzhuk Date: Sat, 11 Jun 2016 01:11:54 +0300 > Based on master master... of what?

Re: [PATCH 1/3] net: stmmac: allow to split suspend/resume from init/exit callbacks

All proper patch serieses must start with an introductory postings ala "Subject: [PATCH 0/3] ..." which explains what the patch series is doing at a high level, why, and how. Thanks.

Re: [PATCH 1/3] net: stmmac: allow to split suspend/resume from init/exit callbacks

All proper patch serieses must start with an introductory postings ala "Subject: [PATCH 0/3] ..." which explains what the patch series is doing at a high level, why, and how. Thanks.

Re: [PATCH net-next] rxrpc: Trim line-terminal whitespace

From: David Howells Date: Fri, 10 Jun 2016 22:30:27 +0100 > Trim line-terminal whitespace in net/rxrpc/ > > Signed-off-by: David Howells Applied.

Re: [PATCH net-next] rxrpc: Limit the listening backlog

From: David Howells Date: Fri, 10 Jun 2016 22:30:37 +0100 > Limit the socket incoming call backlog queue size so that a remote client > can't pump in sufficient new calls that the server runs out of memory. Note > that this is partially theoretical at the moment since

Re: [PATCH net-next] rxrpc: Trim line-terminal whitespace

From: David Howells Date: Fri, 10 Jun 2016 22:30:27 +0100 > Trim line-terminal whitespace in net/rxrpc/ > > Signed-off-by: David Howells Applied.

Re: [PATCH net-next] rxrpc: Limit the listening backlog

From: David Howells Date: Fri, 10 Jun 2016 22:30:37 +0100 > Limit the socket incoming call backlog queue size so that a remote client > can't pump in sufficient new calls that the server runs out of memory. Note > that this is partially theoretical at the moment since whilst the number of >

Re: [PATCH net-next,v2] tools: hv: Add a script to help bonding synthetic and VF NICs

From: Haiyang Zhang Date: Fri, 10 Jun 2016 14:23:12 -0700 > This script helps to create bonding network devices based on synthetic NIC > (the virtual network adapter usually provided by Hyper-V) and the matching > VF NIC (SRIOV virtual function). So the synthetic NIC and

Re: [PATCH net-next,v2] tools: hv: Add a script to help bonding synthetic and VF NICs

From: Haiyang Zhang Date: Fri, 10 Jun 2016 14:23:12 -0700 > This script helps to create bonding network devices based on synthetic NIC > (the virtual network adapter usually provided by Hyper-V) and the matching > VF NIC (SRIOV virtual function). So the synthetic NIC and VF NIC can > function as

Re: [PATCH] autofs4: Fix endless loop in autofs4_write

On Fri, 2016-06-10 at 19:07 +0200, Laurent Dufour wrote: > The 'commit e9a7c2f1a548 ("autofs4: coding style fixes")' removed the > check done on the __vfs_write()'s returned value in autofs4_write(). > This may lead to a spinning process which can't catch any signal. Yeah, sorry my bad. > >

Re: [PATCH] autofs4: Fix endless loop in autofs4_write

On Fri, 2016-06-10 at 19:07 +0200, Laurent Dufour wrote: > The 'commit e9a7c2f1a548 ("autofs4: coding style fixes")' removed the > check done on the __vfs_write()'s returned value in autofs4_write(). > This may lead to a spinning process which can't catch any signal. Yeah, sorry my bad. > >

Re: linux-next: Tree for Jun 9

On Thu, Jun 9, 2016 at 6:14 PM, Kees Cook wrote: > On Thu, Jun 9, 2016 at 3:06 PM, Sudip Mukherjee > wrote: [...] >> While trying to build x86_64 allmodconfig I am getting: >> ++ dirname ../scripts/gcc-plugin.sh >> + srctree=../scripts >> ++

Re: linux-next: Tree for Jun 9

On Thu, Jun 9, 2016 at 6:14 PM, Kees Cook wrote: > On Thu, Jun 9, 2016 at 3:06 PM, Sudip Mukherjee > wrote: [...] >> While trying to build x86_64 allmodconfig I am getting: >> ++ dirname ../scripts/gcc-plugin.sh >> + srctree=../scripts >> ++ gcc -print-file-name=plugin >> +

[PATCH 2/3] net: stmmac: dwmac-rk: keep the PHY up for WoL

When suspending the machine, do not shutdown the external PHY by cutting its regulator in the mac platform driver suspend code if Wake-on-Lan is enabled, else it cannot wake us up. In order to do this, split the suspend/resume callbacks from the init/exit callbacks, so we can condition the

[PATCH 2/3] net: stmmac: dwmac-rk: keep the PHY up for WoL

When suspending the machine, do not shutdown the external PHY by cutting its regulator in the mac platform driver suspend code if Wake-on-Lan is enabled, else it cannot wake us up. In order to do this, split the suspend/resume callbacks from the init/exit callbacks, so we can condition the

[PATCH 1/3] net: stmmac: allow to split suspend/resume from init/exit callbacks

Let the stmmac platform drivers provide dedicated suspend and resume callbacks rather than always re-using the init and exits callbacks. If the driver does not provide the suspend or resume callback, we fall back to the old behavior trying to use exit or init. This allows a specific platform to

[PATCH 3/3] ARM: dts: rockchip: add interrupt for Wake-on-Lan on RK3288

In order to use Wake-on-Lan on RK3288 integrated MAC, we need to wake-up the CPU on the PMT interrupt when the MAC and the PHY are in low power mode. Adding the interrupt declaration. Signed-off-by: Vincent Palatin --- arch/arm/boot/dts/rk3288.dtsi | 5 +++-- 1 file

[PATCH 1/3] net: stmmac: allow to split suspend/resume from init/exit callbacks

Let the stmmac platform drivers provide dedicated suspend and resume callbacks rather than always re-using the init and exits callbacks. If the driver does not provide the suspend or resume callback, we fall back to the old behavior trying to use exit or init. This allows a specific platform to

[PATCH 3/3] ARM: dts: rockchip: add interrupt for Wake-on-Lan on RK3288

In order to use Wake-on-Lan on RK3288 integrated MAC, we need to wake-up the CPU on the PMT interrupt when the MAC and the PHY are in low power mode. Adding the interrupt declaration. Signed-off-by: Vincent Palatin --- arch/arm/boot/dts/rk3288.dtsi | 5 +++-- 1 file changed, 3 insertions(+), 2

net: stmmac: dwmac-rk: fixes for Wake-on-Lan on RK3288

In order to support Wake-On-Lan when using the RK3288 integrated MAC (with an external RGMII PHY), we need to avoid shutting down the regulator of the external PHY when the MAC is suspended as it's currently done in the MAC platform code. As a first step, create independant callbacks for

net: stmmac: dwmac-rk: fixes for Wake-on-Lan on RK3288

In order to support Wake-On-Lan when using the RK3288 integrated MAC (with an external RGMII PHY), we need to avoid shutting down the regulator of the external PHY when the MAC is suspended as it's currently done in the MAC platform code. As a first step, create independant callbacks for

Re: PATCH [1/1] ipv4: Prevent malformed UFO fragments in ip_append_page

From: Steven Caron Date: Fri, 10 Jun 2016 19:21:26 + > As the ip fragment offset field counts 8-byte chunks, non-final ip > fragments must be multiples of 8 bytes of payload. Depending on > the mtu and ip option sizes, ip_append_page wasn't respecting this, >

Re: [PATCH v8 2/5] perf config: Bring declarations about config from util/cache.h to util/config.h

Good evening :) On 06/11/2016 04:06 AM, Arnaldo Carvalho de Melo wrote: Em Fri, Jun 10, 2016 at 03:20:43PM +0900, Taeung Song escreveu: On 06/09/2016 10:29 PM, Arnaldo Carvalho de Melo wrote: +++ b/tools/perf/util/cache.h @@ -7,6 +7,7 @@ #include +#include "config.h" Why have you added

Re: PATCH [1/1] ipv4: Prevent malformed UFO fragments in ip_append_page

From: Steven Caron Date: Fri, 10 Jun 2016 19:21:26 + > As the ip fragment offset field counts 8-byte chunks, non-final ip > fragments must be multiples of 8 bytes of payload. Depending on > the mtu and ip option sizes, ip_append_page wasn't respecting this, > notably when running NFS under

Re: [PATCH v8 2/5] perf config: Bring declarations about config from util/cache.h to util/config.h

Good evening :) On 06/11/2016 04:06 AM, Arnaldo Carvalho de Melo wrote: Em Fri, Jun 10, 2016 at 03:20:43PM +0900, Taeung Song escreveu: On 06/09/2016 10:29 PM, Arnaldo Carvalho de Melo wrote: +++ b/tools/perf/util/cache.h @@ -7,6 +7,7 @@ #include +#include "config.h" Why have you added

[PATCH] Documentation: tiny typo fix in usb/gadget_multi.txt

Signed-off-by: Michal Nazarewicz --- Documentation/usb/gadget_multi.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/usb/gadget_multi.txt b/Documentation/usb/gadget_multi.txt index 5faf514..b3146dd 100644 ---

[PATCH] Documentation: tiny typo fix in usb/gadget_multi.txt

Signed-off-by: Michal Nazarewicz --- Documentation/usb/gadget_multi.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/usb/gadget_multi.txt b/Documentation/usb/gadget_multi.txt index 5faf514..b3146dd 100644 --- a/Documentation/usb/gadget_multi.txt +++

Re: [PULL] lkdtm update (next)

On Fri, Jun 10, 2016 at 5:00 PM, Greg KH wrote: > On Fri, Jun 10, 2016 at 04:02:44PM -0700, Kees Cook wrote: >> Hi, >> >> Please pull these lkdtm changes for next. > > These are all for 4.8-rc1 inclusion, right? Not bugfixes for 4.7-final? Yes, that's correct.

Re: [PULL] lkdtm update (next)

On Fri, Jun 10, 2016 at 5:00 PM, Greg KH wrote: > On Fri, Jun 10, 2016 at 04:02:44PM -0700, Kees Cook wrote: >> Hi, >> >> Please pull these lkdtm changes for next. > > These are all for 4.8-rc1 inclusion, right? Not bugfixes for 4.7-final? Yes, that's correct. Thanks! -Kees -- Kees Cook

Re: [lustre-devel] [PATCH 11/21] drivers: staging: lustre: Replace CURRENT_TIME with current_fs_time()

> CURRENT_TIME macro is not appropriate for filesystems as it > doesn't use the right granularity for filesystem timestamps. > Use current_fs_time() instead. > > This is also in preparation for the patch that transitions > vfs timestamps to use 64 bit time and hence make them > y2038 safe. As

Re: [lustre-devel] [PATCH 11/21] drivers: staging: lustre: Replace CURRENT_TIME with current_fs_time()

> CURRENT_TIME macro is not appropriate for filesystems as it > doesn't use the right granularity for filesystem timestamps. > Use current_fs_time() instead. > > This is also in preparation for the patch that transitions > vfs timestamps to use 64 bit time and hence make them > y2038 safe. As

Re: [PATCH] arm64: Handle el1 synchronous instruction aborts cleanly

On 06/10/2016 02:48 AM, Mark Rutland wrote: On Thu, Jun 09, 2016 at 06:42:08PM -0700, Laura Abbott wrote: Executing from a non-executable area gives an ugly message: lkdtm: Performing direct entry EXEC_RODATA lkdtm: attempting ok execution at 084c0e08 lkdtm: attempting bad execution at

Re: [PATCH] arm64: Handle el1 synchronous instruction aborts cleanly

On 06/10/2016 02:48 AM, Mark Rutland wrote: On Thu, Jun 09, 2016 at 06:42:08PM -0700, Laura Abbott wrote: Executing from a non-executable area gives an ugly message: lkdtm: Performing direct entry EXEC_RODATA lkdtm: attempting ok execution at 084c0e08 lkdtm: attempting bad execution at

Re: [PATCH perf/core v10 09/23] perf probe: Show all cached probes

On Thu, 9 Jun 2016 11:22:55 -0300 Arnaldo Carvalho de Melo wrote: > Em Wed, Jun 08, 2016 at 06:30:30PM +0900, Masami Hiramatsu escreveu: > > +char *build_id_cache__origname(const char *sbuild_id) > > +{ > > + char *linkname; > > + char buf[PATH_MAX]; > > + char *ret =

Re: [PATCH perf/core v10 09/23] perf probe: Show all cached probes

On Thu, 9 Jun 2016 11:22:55 -0300 Arnaldo Carvalho de Melo wrote: > Em Wed, Jun 08, 2016 at 06:30:30PM +0900, Masami Hiramatsu escreveu: > > +char *build_id_cache__origname(const char *sbuild_id) > > +{ > > + char *linkname; > > + char buf[PATH_MAX]; > > + char *ret = NULL, *p; > > +

Re: [PATCH] pci: make bus_attr_resource_alignemnt static

On Thu, Jun 09, 2016 at 11:42:13AM +0100, Ben Dooks wrote: > The symbol bus_attr_resource_alignment is not exported or declared > elsewhere, so make it static to fix the following warning: > > drivers/pci/pci.c:4900:1: warning: symbol 'bus_attr_resource_alignment' was > not declared. Should it

Re: [PATCH] pci: make bus_attr_resource_alignemnt static

On Thu, Jun 09, 2016 at 11:42:13AM +0100, Ben Dooks wrote: > The symbol bus_attr_resource_alignment is not exported or declared > elsewhere, so make it static to fix the following warning: > > drivers/pci/pci.c:4900:1: warning: symbol 'bus_attr_resource_alignment' was > not declared. Should it

Re: [GIT PULL] Please pull powerpc/linux.git powerpc-4.7-3 tag

On Fri, 2016-06-10 at 12:26 -0700, Linus Torvalds wrote: > On Fri, Jun 10, 2016 at 8:48 AM, Linus Torvalds > wrote: > > On Fri, Jun 10, 2016 at 4:51 AM, Michael Ellerman > > wrote: > > > > > > powerpc fixes for 4.7 #2 > > > > This is

Re: [GIT PULL] Please pull powerpc/linux.git powerpc-4.7-3 tag

On Fri, 2016-06-10 at 12:26 -0700, Linus Torvalds wrote: > On Fri, Jun 10, 2016 at 8:48 AM, Linus Torvalds > wrote: > > On Fri, Jun 10, 2016 at 4:51 AM, Michael Ellerman > > wrote: > > > > > > powerpc fixes for 4.7 #2 > > > > This is actually #3 - and some of the things you describe came in >

Re: PROBLEM: Resume form hibernate broken by setting NX on gap

On Saturday, June 11, 2016 12:33:31 AM Rafael J. Wysocki wrote: > On Friday, June 10, 2016 04:28:01 PM Logan Gunthorpe wrote: > > > > On 10/06/16 04:29 PM, Rafael J. Wysocki wrote: > > > OK, I have a theory, but I need a bit of help. > > > > > > This may be a dumb question, but I don't quite

Re: PROBLEM: Resume form hibernate broken by setting NX on gap

On Saturday, June 11, 2016 12:33:31 AM Rafael J. Wysocki wrote: > On Friday, June 10, 2016 04:28:01 PM Logan Gunthorpe wrote: > > > > On 10/06/16 04:29 PM, Rafael J. Wysocki wrote: > > > OK, I have a theory, but I need a bit of help. > > > > > > This may be a dumb question, but I don't quite

Re: [PATCH] PCI/ASPM: Remove redundant check of pcie_set_clkpm

On Tue, May 24, 2016 at 05:32:10PM +0800, Shawn Lin wrote: > Without supporting clock PM capable, if we want to disable > clkpm, we don't need this extra check as it already be zero for > the enable argument. And it's the same for enabling clkpm here. > So let's remove this check. > >

Re: [PATCH] PCI/ASPM: Remove redundant check of pcie_set_clkpm

On Tue, May 24, 2016 at 05:32:10PM +0800, Shawn Lin wrote: > Without supporting clock PM capable, if we want to disable > clkpm, we don't need this extra check as it already be zero for > the enable argument. And it's the same for enabling clkpm here. > So let's remove this check. > >

Re: [PATCH 35/54] MAINTAINERS: Add file patterns for pci device tree bindings

On Sun, May 22, 2016 at 11:06:12AM +0200, Geert Uytterhoeven wrote: > Submitters of device tree binding documentation may forget to CC > the subsystem maintainer if this is missing. > > Signed-off-by: Geert Uytterhoeven > Cc: Bjorn Helgaas > Cc:

Re: [PATCH 35/54] MAINTAINERS: Add file patterns for pci device tree bindings

On Sun, May 22, 2016 at 11:06:12AM +0200, Geert Uytterhoeven wrote: > Submitters of device tree binding documentation may forget to CC > the subsystem maintainer if this is missing. > > Signed-off-by: Geert Uytterhoeven > Cc: Bjorn Helgaas > Cc: linux-...@vger.kernel.org Applied to pci/misc

Re: [PATCH] PCI: host-generic: select IRQ_DOMAIN

On Wed, May 18, 2016 at 04:15:53PM +0200, Arnd Bergmann wrote: > The generic PCI host controller calls of_irq_parse_and_map_pci > in its IRQ fixup, but that function is only available when > CONFIG_IRQ_DOMAIN is set: > > drivers/pci/built-in.o: In function `pci_host_common_probe': >

Re: [PATCH] PCI: host-generic: select IRQ_DOMAIN

On Wed, May 18, 2016 at 04:15:53PM +0200, Arnd Bergmann wrote: > The generic PCI host controller calls of_irq_parse_and_map_pci > in its IRQ fixup, but that function is only available when > CONFIG_IRQ_DOMAIN is set: > > drivers/pci/built-in.o: In function `pci_host_common_probe': >

Re: [PULL] lkdtm update (next)

On Fri, Jun 10, 2016 at 04:02:44PM -0700, Kees Cook wrote: > Hi, > > Please pull these lkdtm changes for next. These are all for 4.8-rc1 inclusion, right? Not bugfixes for 4.7-final? thanks, greg k-h

Re: [PULL] lkdtm update (next)

On Fri, Jun 10, 2016 at 04:02:44PM -0700, Kees Cook wrote: > Hi, > > Please pull these lkdtm changes for next. These are all for 4.8-rc1 inclusion, right? Not bugfixes for 4.7-final? thanks, greg k-h

Re: [Linaro-acpi] [PATCH V9 00/11] Support for ARM64 ACPI based PCI host controller

On 06/10/2016 07:41 PM, Bjorn Helgaas wrote: > On Fri, Jun 10, 2016 at 09:55:08PM +0200, Tomasz Nowicki wrote: >> From the functionality point of view this series may be split into the >> following logic parts: >> 1. Export ECAM API and add parent device to pci_config_window >> 2. Add IO resources

Re: [Linaro-acpi] [PATCH V9 00/11] Support for ARM64 ACPI based PCI host controller

On 06/10/2016 07:41 PM, Bjorn Helgaas wrote: > On Fri, Jun 10, 2016 at 09:55:08PM +0200, Tomasz Nowicki wrote: >> From the functionality point of view this series may be split into the >> following logic parts: >> 1. Export ECAM API and add parent device to pci_config_window >> 2. Add IO resources

Re: [PATCH 0/2] PCI: hv: fix a couple of issues in hv_pci_onchannelcallback()

On Mon, May 30, 2016 at 04:17:57PM +0200, Vitaly Kuznetsov wrote: > kmemleak helped me to identify a memory leak in hv_pci_onchannelcallback() > and while fixing it I stumbled upon an unrelated issue(s) there. > > Vitaly Kuznetsov (2): > PCI: hv: don't leak buffer in hv_pci_onchannelcallback()

Re: [PATCH 0/2] PCI: hv: fix a couple of issues in hv_pci_onchannelcallback()

On Mon, May 30, 2016 at 04:17:57PM +0200, Vitaly Kuznetsov wrote: > kmemleak helped me to identify a memory leak in hv_pci_onchannelcallback() > and while fixing it I stumbled upon an unrelated issue(s) there. > > Vitaly Kuznetsov (2): > PCI: hv: don't leak buffer in hv_pci_onchannelcallback()

Re: [PATCH v2] backlight: lp855x: Add enable regulator

On Fri, Jun 10, 2016 at 12:39 PM, Brian Norris wrote: > > The LP8556 datasheet describes an EN/VDDIO input, which serves "both as > a chip enable and as a power supply reference for PWM, SDA, and SCL > inputs." The LP8556 that I'm testing doesn't respond properly if I

Re: [PATCH v2] backlight: lp855x: Add enable regulator

On Fri, Jun 10, 2016 at 12:39 PM, Brian Norris wrote: > > The LP8556 datasheet describes an EN/VDDIO input, which serves "both as > a chip enable and as a power supply reference for PWM, SDA, and SCL > inputs." The LP8556 that I'm testing doesn't respond properly if I try > to talk I2C to it too

Re: [PATCH V9 00/11] Support for ARM64 ACPI based PCI host controller

Thank you Bjorn :) Next time we are in the same place (anyone involved in this series), beer is on me. -- Computer Architect | Sent from my 64-bit #ARM Powered phone > On Jun 10, 2016, at 18:41, Bjorn Helgaas wrote: > >> On Fri, Jun 10, 2016 at 09:55:08PM +0200, Tomasz

Re: [PATCH V9 00/11] Support for ARM64 ACPI based PCI host controller

Thank you Bjorn :) Next time we are in the same place (anyone involved in this series), beer is on me. -- Computer Architect | Sent from my 64-bit #ARM Powered phone > On Jun 10, 2016, at 18:41, Bjorn Helgaas wrote: > >> On Fri, Jun 10, 2016 at 09:55:08PM +0200, Tomasz Nowicki wrote: >>

Re: [PATCH] ARM: dts: qcom: msm8974-honami: Set DMA as remotely controlled

On Fri 10 Jun 15:15 PDT 2016, Andy Gross wrote: > This patch adds the qcom,controlled-remotely property for the blsp2_bam > controller node. This board requires this, otherwise the board fails to > boot due to access of protected registers during BAM initialization. > > Fixes: 62bc81792223 dts:

Re: [PATCH] ARM: dts: qcom: msm8974-honami: Set DMA as remotely controlled

On Fri 10 Jun 15:15 PDT 2016, Andy Gross wrote: > This patch adds the qcom,controlled-remotely property for the blsp2_bam > controller node. This board requires this, otherwise the board fails to > boot due to access of protected registers during BAM initialization. > > Fixes: 62bc81792223 dts:

Re: [PATCH V9 00/11] Support for ARM64 ACPI based PCI host controller

On Fri, Jun 10, 2016 at 09:55:08PM +0200, Tomasz Nowicki wrote: > From the functionality point of view this series may be split into the > following logic parts: > 1. Export ECAM API and add parent device to pci_config_window > 2. Add IO resources handling to PCI core code > 3. New MCFG driver >

Re: [PATCH V9 00/11] Support for ARM64 ACPI based PCI host controller

On Fri, Jun 10, 2016 at 09:55:08PM +0200, Tomasz Nowicki wrote: > From the functionality point of view this series may be split into the > following logic parts: > 1. Export ECAM API and add parent device to pci_config_window > 2. Add IO resources handling to PCI core code > 3. New MCFG driver >

Re: [PATCH V9 09/11] ARM64/PCI: ACPI support for legacy IRQs parsing and consolidation with DT code

On Fri, Jun 10, 2016 at 09:55:17PM +0200, Tomasz Nowicki wrote: > To enable PCI legacy IRQs on platforms booting with ACPI, arch code > should include ACPI specific callbacks that parse and set-up the > device IRQ number, equivalent to the DT boot path. Owing to the current > ACPI core scan

Re: [PATCH V9 09/11] ARM64/PCI: ACPI support for legacy IRQs parsing and consolidation with DT code

On Fri, Jun 10, 2016 at 09:55:17PM +0200, Tomasz Nowicki wrote: > To enable PCI legacy IRQs on platforms booting with ACPI, arch code > should include ACPI specific callbacks that parse and set-up the > device IRQ number, equivalent to the DT boot path. Owing to the current > ACPI core scan

Re: [PATCH perf/core v10 07/23] perf probe: Add --cache option to cache the probe definitions

On Thu, 9 Jun 2016 11:18:50 -0300 Arnaldo Carvalho de Melo wrote: > Em Wed, Jun 08, 2016 at 06:30:10PM +0900, Masami Hiramatsu escreveu: > > @@ -2555,6 +2556,14 @@ static int __add_probe_trace_events(struct > > perf_probe_event *pev, > > } > > if (ret == -EINVAL &&

Re: [PATCH perf/core v10 07/23] perf probe: Add --cache option to cache the probe definitions

On Thu, 9 Jun 2016 11:18:50 -0300 Arnaldo Carvalho de Melo wrote: > Em Wed, Jun 08, 2016 at 06:30:10PM +0900, Masami Hiramatsu escreveu: > > @@ -2555,6 +2556,14 @@ static int __add_probe_trace_events(struct > > perf_probe_event *pev, > > } > > if (ret == -EINVAL && pev->uprobes) > >

Re: [PATCH V9 05/11] ACPI/PCI: Add generic MCFG table handling

On Fri, Jun 10, 2016 at 09:55:13PM +0200, Tomasz Nowicki wrote: > According to PCI firmware specifications, on systems booting with ACPI, > PCI configuration for a host bridge must be set-up through the MCFG table > regions for non-hotpluggable bridges and _CBA method for hotpluggable ones. > >

Re: [PATCH V9 05/11] ACPI/PCI: Add generic MCFG table handling

On Fri, Jun 10, 2016 at 09:55:13PM +0200, Tomasz Nowicki wrote: > According to PCI firmware specifications, on systems booting with ACPI, > PCI configuration for a host bridge must be set-up through the MCFG table > regions for non-hotpluggable bridges and _CBA method for hotpluggable ones. > >

disfunctional floppy driver in kernels 4.5, 4.6 and 4.7

L.S. up to vanilla kernel 4.4.13 floppy functionality performs like it should. (On an x86 PC that is. With a 1.44MB diskette drive.) >From kernel 4.5* and up it changed to barely usable. After a virgin start (cold or warm boot) with an empty diskette drive and then loaded with a standard 720K

disfunctional floppy driver in kernels 4.5, 4.6 and 4.7

L.S. up to vanilla kernel 4.4.13 floppy functionality performs like it should. (On an x86 PC that is. With a 1.44MB diskette drive.) >From kernel 4.5* and up it changed to barely usable. After a virgin start (cold or warm boot) with an empty diskette drive and then loaded with a standard 720K

Re: [PATCH v2 0/2] net: ethernet: ti: cpsw: delete rx_descs property

On 06/08/2016 07:03 PM, Ivan Khoronzhuk wrote: On 09.06.16 02:11, Schuyler Patton wrote: On 06/08/2016 09:06 AM, Ivan Khoronzhuk wrote: On 08.06.16 17:01, Ivan Khoronzhuk wrote: Hi Schuyer, On 07.06.16 18:26, Schuyler Patton wrote: Hi, On 06/07/2016 08:59 AM, Ivan Khoronzhuk wrote:

Re: [PATCH v2 0/2] net: ethernet: ti: cpsw: delete rx_descs property

On 06/08/2016 07:03 PM, Ivan Khoronzhuk wrote: On 09.06.16 02:11, Schuyler Patton wrote: On 06/08/2016 09:06 AM, Ivan Khoronzhuk wrote: On 08.06.16 17:01, Ivan Khoronzhuk wrote: Hi Schuyer, On 07.06.16 18:26, Schuyler Patton wrote: Hi, On 06/07/2016 08:59 AM, Ivan Khoronzhuk wrote:

Re: [GIT PULL] Ceph updates for 4.7-rc1

On Friday, June 10, 2016 2:32:21 PM CEST Linus Torvalds wrote: > On Fri, Jun 10, 2016 at 1:42 PM, Arnd Bergmann wrote: > > > > What I see is that this one exported symbol has a __crc of a different > > type from all the others: > > > > $ nm net/ceph/mon_client.o | grep __crc > >

Re: [GIT PULL] Ceph updates for 4.7-rc1

On Friday, June 10, 2016 2:32:21 PM CEST Linus Torvalds wrote: > On Fri, Jun 10, 2016 at 1:42 PM, Arnd Bergmann wrote: > > > > What I see is that this one exported symbol has a __crc of a different > > type from all the others: > > > > $ nm net/ceph/mon_client.o | grep __crc > > 48c2e16e A

[PULL] lkdtm update (next)

Hi, Please pull these lkdtm changes for next. Thanks! -Kees The following changes since commit 3d0f0b6a5520878305589411b8d434fe088e4f21: Merge branch 'for-linus-4.7' of git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs (2016-06-10 14:13:27 -0700) are available in the git

[PULL] lkdtm update (next)

Hi, Please pull these lkdtm changes for next. Thanks! -Kees The following changes since commit 3d0f0b6a5520878305589411b8d434fe088e4f21: Merge branch 'for-linus-4.7' of git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs (2016-06-10 14:13:27 -0700) are available in the git

[PATCH 2/2] perf script: Support callindent

From: Andi Kleen When printing PT instruction traces with perf script it is rather useful to see some indentation for the call tree. This patch adds a new callindent field to perf script that prints spaces for the function call stack depth. We already have code to track

[PATCH 2/2] perf script: Support callindent

From: Andi Kleen When printing PT instruction traces with perf script it is rather useful to see some indentation for the call tree. This patch adds a new callindent field to perf script that prints spaces for the function call stack depth. We already have code to track the function call stack

[PATCH 1/2] perf pt: Mark PT return events as "return"

From: Andi Kleen With perf script --itrace=cr we can synthesize calls and returns out of a PT log. However both calls and returns are marked with the same event, called branches. This makes it difficult to read and post process, because calls and returns are somewhat

[PATCH 1/2] perf pt: Mark PT return events as "return"

From: Andi Kleen With perf script --itrace=cr we can synthesize calls and returns out of a PT log. However both calls and returns are marked with the same event, called branches. This makes it difficult to read and post process, because calls and returns are somewhat diffferent. Create a

[PATCH] ARM: dts: qcom: msm8974-honami: Set DMA as remotely controlled

This patch adds the qcom,controlled-remotely property for the blsp2_bam controller node. This board requires this, otherwise the board fails to boot due to access of protected registers during BAM initialization. Fixes: 62bc81792223 dts: msm8974: Add blsp2_bam dma node Signed-off-by: Andy Gross

[PATCH] ARM: dts: qcom: msm8974-honami: Set DMA as remotely controlled

This patch adds the qcom,controlled-remotely property for the blsp2_bam controller node. This board requires this, otherwise the board fails to boot due to access of protected registers during BAM initialization. Fixes: 62bc81792223 dts: msm8974: Add blsp2_bam dma node Signed-off-by: Andy Gross

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