Re: linux-next: manual merge of the pm tree with the imx-mxs tree

On Tue, Oct 25 2016 at 17:51 -0600, Rafael J. Wysocki wrote: On Tuesday, October 25, 2016 10:47:29 AM Stephen Rothwell wrote: Hi Rafael, Today's linux-next merge of the pm tree got a conflict in: arch/arm/mach-imx/gpc.c between commits: eef0b282bb58 ("ARM: imx: gpc: Initialize all power

linux-next: Tree for Oct 25

Hi all, There will probably be no linux-next releases next week while I attend the Kernel Summit. Changes since 20161024: The pm tree gained a conflict against the imx-mxs tree. The mali-dp tree gained a conflict against the drm-misc tree. The sunxi tree gained a build failure so I used

Re: [GIT PULL] xen: xenfs fixes for 4.9-rc2

On Mon, Oct 24, 2016 at 9:37 AM, David Vrabel wrote: > > I think the changes are trivial and uncontroversial. Hmm. Sadly, they are also buggy. This: if (files->mode & S_IFLNK) { is simply wrong. The correct test for S_IFLNK is to do if

Re: [GIT PULL] xen: xenfs fixes for 4.9-rc2

On Mon, Oct 24, 2016 at 9:37 AM, David Vrabel wrote: > > I think the changes are trivial and uncontroversial. Hmm. Sadly, they are also buggy. This: if (files->mode & S_IFLNK) { is simply wrong. The correct test for S_IFLNK is to do if ((files->mode & S_IFMT)

Re: [PATCH -next 1/2] Input: synaptics-rmi4 - add support for F55 sensor tuning

Hi Andrew, On 10/24/2016 05:59 PM, Andrew Duggan wrote: Hi Guenter, I have a couple of comments below. Thanks a lot for the feedback. On 09/30/2016 08:22 PM, Guenter Roeck wrote: Sensor tuning support is needed to determine the number of enabled tx and rx electrodes for use in F54

Re: [PATCH -next 1/2] Input: synaptics-rmi4 - add support for F55 sensor tuning

Hi Andrew, On 10/24/2016 05:59 PM, Andrew Duggan wrote: Hi Guenter, I have a couple of comments below. Thanks a lot for the feedback. On 09/30/2016 08:22 PM, Guenter Roeck wrote: Sensor tuning support is needed to determine the number of enabled tx and rx electrodes for use in F54

Re: [PATCH net-next] ethernet: fix min/max MTU typos

On Mon, Oct 24, 2016 at 02:42:26PM +0200, Stefan Richter wrote: > Fixes: d894be57ca92('ethernet: use net core MTU range checking in more > drivers') > CC: Jarod Wilson > CC: Thomas Falcon > Signed-off-by: Stefan Richter

Re: [PATCH net-next] ethernet: fix min/max MTU typos

On Mon, Oct 24, 2016 at 02:42:26PM +0200, Stefan Richter wrote: > Fixes: d894be57ca92('ethernet: use net core MTU range checking in more > drivers') > CC: Jarod Wilson > CC: Thomas Falcon > Signed-off-by: Stefan Richter Wuf. Thank you, Stefan. Way too many bleeding eyeball hours staring at

Re: [PATCH net-next 2/2 v2] firewire: net: set initial MTU = 1500 unconditionally, fix IPv6 on some CardBus cards

On Mon, Oct 24, 2016 at 02:26:13PM +0200, Stefan Richter wrote: > firewire-net, like the older eth1394 driver, reduced the initial MTU to > less than 1500 octets if the local link layer controller's asynchronous > packet reception limit was lower. > > This is bogus, since this reception limit

Re: [PATCH net-next 2/2 v2] firewire: net: set initial MTU = 1500 unconditionally, fix IPv6 on some CardBus cards

On Mon, Oct 24, 2016 at 02:26:13PM +0200, Stefan Richter wrote: > firewire-net, like the older eth1394 driver, reduced the initial MTU to > less than 1500 octets if the local link layer controller's asynchronous > packet reception limit was lower. > > This is bogus, since this reception limit

[PATCH 1/2] mm/memblock: prepare a capability to support memblock near alloc

If HAVE_MEMORYLESS_NODES is selected, and some memoryless numa nodes are actually exist. The percpu variable areas and numa control blocks of that memoryless numa nodes need to be allocated from the nearest available node to improve performance. Although memblock_alloc_try_nid and

[PATCH 1/2] mm/memblock: prepare a capability to support memblock near alloc

If HAVE_MEMORYLESS_NODES is selected, and some memoryless numa nodes are actually exist. The percpu variable areas and numa control blocks of that memoryless numa nodes need to be allocated from the nearest available node to improve performance. Although memblock_alloc_try_nid and

[PATCH 2/2] arm64/numa: support HAVE_MEMORYLESS_NODES

Some numa nodes may have no memory. For example: 1) a node has no memory bank plugged. 2) a node has no memory bank slots. To ensure percpu variable areas and numa control blocks of the memoryless numa nodes to be allocated from the nearest available node to improve performance, defined

[PATCH 0/2] to support memblock near alloc and memoryless on arm64

If HAVE_MEMORYLESS_NODES is selected, and some memoryless numa nodes are actually exist. The percpu variable areas and numa control blocks of that memoryless numa nodes need to be allocated from the nearest available node to improve performance. In the beginning, I added a new function:

[PATCH 2/2] arm64/numa: support HAVE_MEMORYLESS_NODES

Some numa nodes may have no memory. For example: 1) a node has no memory bank plugged. 2) a node has no memory bank slots. To ensure percpu variable areas and numa control blocks of the memoryless numa nodes to be allocated from the nearest available node to improve performance, defined

[PATCH 0/2] to support memblock near alloc and memoryless on arm64

If HAVE_MEMORYLESS_NODES is selected, and some memoryless numa nodes are actually exist. The percpu variable areas and numa control blocks of that memoryless numa nodes need to be allocated from the nearest available node to improve performance. In the beginning, I added a new function:

[PATCH v3] x86/msr: Add write msr notrace to avoid the debug codes splash

As Peterz pointed out: | The thing is, many many smp_reschedule_interrupt() invocations don't | actually execute anything much at all and are only send to tickle the | return to user path (which does the actual preemption). This patch add write msr notrace to avoid the debug codes splash.

Re: [PATCH 5/5] ARM: dts: Add LEGO MINDSTORTMS EV3 dts

On 10/24/2016 10:50 AM, David Lechner wrote: On 10/24/2016 06:58 AM, Sekhar Nori wrote: On Saturday 22 October 2016 12:06 AM, David Lechner wrote: +}; + + { +status = "okay"; +pinctrl-names = "default"; +pinctrl-0 = <_pins>, <_cs0_pin>; + +/* TODO: LCD Display goes here */

[PATCH v3] x86/msr: Add write msr notrace to avoid the debug codes splash

As Peterz pointed out: | The thing is, many many smp_reschedule_interrupt() invocations don't | actually execute anything much at all and are only send to tickle the | return to user path (which does the actual preemption). This patch add write msr notrace to avoid the debug codes splash.

Re: [PATCH 5/5] ARM: dts: Add LEGO MINDSTORTMS EV3 dts

On 10/24/2016 10:50 AM, David Lechner wrote: On 10/24/2016 06:58 AM, Sekhar Nori wrote: On Saturday 22 October 2016 12:06 AM, David Lechner wrote: +}; + + { +status = "okay"; +pinctrl-names = "default"; +pinctrl-0 = <_pins>, <_cs0_pin>; + +/* TODO: LCD Display goes here */

Re: [PATCH/RFT v2 07/17] ARM: davinci: da8xx: Enable the usb20 "per" clk on phy_clk_enable

On 10/24/2016 11:46 AM, ahas...@baylibre.com wrote: From: Axel Haslam While probing ochi phy with usb20 phy as a parent clock for usb11_phy, the usb20_phy clock enable would time out. This is because the usb20 module clock needs to enabled while trying to lock the

Re: [PATCH/RFT v2 07/17] ARM: davinci: da8xx: Enable the usb20 "per" clk on phy_clk_enable

On 10/24/2016 11:46 AM, ahas...@baylibre.com wrote: From: Axel Haslam While probing ochi phy with usb20 phy as a parent clock for usb11_phy, the usb20_phy clock enable would time out. This is because the usb20 module clock needs to enabled while trying to lock the usb20_phy PLL. Call clk

Re: [PATCH] x86/smp: Add irq_enter/exit() in smp_reschedule_interrupt()

2016-10-24 22:32 GMT+08:00 Paolo Bonzini : > > > On 19/10/2016 16:30, Wanpeng Li wrote: >> Cc Radim, >> 2016-10-19 22:10 GMT+08:00 Paolo Bonzini : >>> >>> >>> On 19/10/2016 16:01, Wanpeng Li wrote: 2016-10-18 8:01 GMT+08:00 Wanpeng Li

Re: [PATCH] x86/smp: Add irq_enter/exit() in smp_reschedule_interrupt()

2016-10-24 22:32 GMT+08:00 Paolo Bonzini : > > > On 19/10/2016 16:30, Wanpeng Li wrote: >> Cc Radim, >> 2016-10-19 22:10 GMT+08:00 Paolo Bonzini : >>> >>> >>> On 19/10/2016 16:01, Wanpeng Li wrote: 2016-10-18 8:01 GMT+08:00 Wanpeng Li : > 2016-10-17 18:08 GMT+08:00 Paolo Bonzini : >

Re: [PATCH] block: zoned: fix harmless maybe-uninitialized warning

On 10/24/2016 07:00 PM, Martin K. Petersen wrote: "Arnd" == Arnd Bergmann writes: Arnd> The blkdev_report_zones produces a harmless warning when Arnd> -Wmaybe-uninitialized is set, after gcc gets a little confused Arnd> about the multiple 'goto' here: Arnd> block/blk-zoned.c:

Re: [PATCH] block: zoned: fix harmless maybe-uninitialized warning

On 10/24/2016 07:00 PM, Martin K. Petersen wrote: "Arnd" == Arnd Bergmann writes: Arnd> The blkdev_report_zones produces a harmless warning when Arnd> -Wmaybe-uninitialized is set, after gcc gets a little confused Arnd> about the multiple 'goto' here: Arnd> block/blk-zoned.c: In function

Re: Linux-4.X-rcY patches can't be applied with git?

On Mon, Oct 24, 2016 at 05:06:42PM -0700, Linus Torvalds wrote: > On Mon, Oct 24, 2016 at 4:18 PM, Jarod Wilson wrote: > > > > But in that case, what if your patch generation script used a filter to > > exclude those binary files? No harm to that target audience, and it would >

Re: Linux-4.X-rcY patches can't be applied with git?

On Mon, Oct 24, 2016 at 05:06:42PM -0700, Linus Torvalds wrote: > On Mon, Oct 24, 2016 at 4:18 PM, Jarod Wilson wrote: > > > > But in that case, what if your patch generation script used a filter to > > exclude those binary files? No harm to that target audience, and it would > > actually make

xfs integer overflow in kernel >=4.4.8

Hello, I have attached the output of my findings, with the help of others. Initially reported on Gentoo Bugzilla here: https://bugs.gentoo.org/show_bug.cgi?id=584332 Thanks in advance, be well. emese, sorry for the multiple CC's, also spender's bouncing my mail for not having a valid hostname

xfs integer overflow in kernel >=4.4.8

Hello, I have attached the output of my findings, with the help of others. Initially reported on Gentoo Bugzilla here: https://bugs.gentoo.org/show_bug.cgi?id=584332 Thanks in advance, be well. emese, sorry for the multiple CC's, also spender's bouncing my mail for not having a valid hostname

Crypto Fixes for 4.9

Hi Linus: This push fixes a regression caused by the stack vmalloc change. Please pull from git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git linus Andrew Lutomirski (1): hwrng: core - Don't use a stack buffer in add_early_randomness() drivers/char/hw_random/core.c

Crypto Fixes for 4.9

Hi Linus: This push fixes a regression caused by the stack vmalloc change. Please pull from git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git linus Andrew Lutomirski (1): hwrng: core - Don't use a stack buffer in add_early_randomness() drivers/char/hw_random/core.c

RE: [PATCH] net: fec: hard phy reset on open

From: Manfred Schlaegl Sent: Monday, October 24, 2016 10:43 PM > To: Andy Duan > Cc: net...@vger.kernel.org; linux-kernel@vger.kernel.org > Subject: Re: [PATCH] net: fec: hard phy reset on open > > On 2016-10-24 16:03, Andy Duan wrote: > >

RE: [PATCH] net: fec: hard phy reset on open

From: Manfred Schlaegl Sent: Monday, October 24, 2016 10:43 PM > To: Andy Duan > Cc: net...@vger.kernel.org; linux-kernel@vger.kernel.org > Subject: Re: [PATCH] net: fec: hard phy reset on open > > On 2016-10-24 16:03, Andy Duan wrote: > > From: manfred.schla...@gmx.at Sent: > Monday, > >

RE: [PATCH V2 1/5] powerpc/mpc85xx: Update TMU device tree node for T1040/T1042

> -Original Message- > From: Shawn Guo [mailto:shawn...@kernel.org] > Sent: Monday, October 24, 2016 4:37 PM > To: Troy Jia > Cc: rui.zh...@intel.com; edubez...@gmail.com; robh...@kernel.org; Scott Wood > ; devicet...@vger.kernel.org; linuxppc- >

RE: [PATCH V2 1/5] powerpc/mpc85xx: Update TMU device tree node for T1040/T1042

> -Original Message- > From: Shawn Guo [mailto:shawn...@kernel.org] > Sent: Monday, October 24, 2016 4:37 PM > To: Troy Jia > Cc: rui.zh...@intel.com; edubez...@gmail.com; robh...@kernel.org; Scott Wood > ; devicet...@vger.kernel.org; linuxppc- > d...@lists.ozlabs.org;

Re: [PATCH v2 1/5] ARC: SMP: Use "unsigned virq" in smp_ipi_irq_setup instead of "signed irq"

On 10/24/2016 05:46 AM, Yuriy Kolerov wrote: > This function takes a cpu number and a virq number and registers an > appropriate handler per cpu. However smp_ipi_irq_setup is incorrectly > used in several places of ARC platform code - hwirq is passed instead > of virq. This patch is intended to

Re: [PATCH v2 1/5] ARC: SMP: Use "unsigned virq" in smp_ipi_irq_setup instead of "signed irq"

On 10/24/2016 05:46 AM, Yuriy Kolerov wrote: > This function takes a cpu number and a virq number and registers an > appropriate handler per cpu. However smp_ipi_irq_setup is incorrectly > used in several places of ARC platform code - hwirq is passed instead > of virq. This patch is intended to

[PATCH V3 2/2] powerpc/mpc85xx: Update TMU device tree node for T1023/T1024

From: Hongtao Jia Update #thermal-sensor-cells from 0 to 1 according to the new binding. The sensor specifier added is the monitoring site ID, and represents the "n" in TRITSRn and TRATSRn. Signed-off-by: Jia Hongtao --- Changes for V3: * Update the

[PATCH V3 1/2] powerpc/mpc85xx: Update TMU device tree node for T1040/T1042

From: Hongtao Jia Update #thermal-sensor-cells from 0 to 1 according to the new binding. The sensor specifier added is the monitoring site ID, and represents the "n" in TRITSRn and TRATSRn. Signed-off-by: Jia Hongtao --- Changes for V3: * Update the

[PATCH V3 2/2] powerpc/mpc85xx: Update TMU device tree node for T1023/T1024

From: Hongtao Jia Update #thermal-sensor-cells from 0 to 1 according to the new binding. The sensor specifier added is the monitoring site ID, and represents the "n" in TRITSRn and TRATSRn. Signed-off-by: Jia Hongtao --- Changes for V3: * Update the commit log to a better description. Changes

[PATCH V3 1/2] powerpc/mpc85xx: Update TMU device tree node for T1040/T1042

From: Hongtao Jia Update #thermal-sensor-cells from 0 to 1 according to the new binding. The sensor specifier added is the monitoring site ID, and represents the "n" in TRITSRn and TRATSRn. Signed-off-by: Jia Hongtao --- Changes for V3: * Update the commit log to a better description. Changes

Re: [PATCH v2 2/5] ARC: SMP: Pass virq to smp_ipi_irq_setup instead of hwirq

On 10/24/2016 05:46 AM, Yuriy Kolerov wrote: > This function takes a cpu number and a virq number and registers an > appropriate handler per cpu. However smp_ipi_irq_setup is incorrectly > used in several places of ARC platform code - hwirq is passed instead of > virq. There is a code with an

Re: [PATCH v2 2/5] ARC: SMP: Pass virq to smp_ipi_irq_setup instead of hwirq

On 10/24/2016 05:46 AM, Yuriy Kolerov wrote: > This function takes a cpu number and a virq number and registers an > appropriate handler per cpu. However smp_ipi_irq_setup is incorrectly > used in several places of ARC platform code - hwirq is passed instead of > virq. There is a code with an

Re: linux.git: printk() problem

On (10/25/16 10:55), Sergey Senozhatsky wrote: > I think cont_flush() should grab the logbuf_lock lock, because > it does log_store() and touches the cont.len. so something like > this perhaps > > diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c > index c7f490f..47f887c 100644 > ---

Re: linux.git: printk() problem

On (10/25/16 10:55), Sergey Senozhatsky wrote: > I think cont_flush() should grab the logbuf_lock lock, because > it does log_store() and touches the cont.len. so something like > this perhaps > > diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c > index c7f490f..47f887c 100644 > ---

Re: linux.git: printk() problem

On Mon, Oct 24, 2016 at 7:06 PM, Linus Torvalds wrote: > On Mon, Oct 24, 2016 at 6:55 PM, Sergey Senozhatsky > wrote: >> >> I think cont_flush() should grab the logbuf_lock lock, because >> it does log_store() and touches the

Re: linux.git: printk() problem

On Mon, Oct 24, 2016 at 7:06 PM, Linus Torvalds wrote: > On Mon, Oct 24, 2016 at 6:55 PM, Sergey Senozhatsky > wrote: >> >> I think cont_flush() should grab the logbuf_lock lock, because >> it does log_store() and touches the cont.len. so something like >> this perhaps > > Absolutely. Good

[PATCH v2] net: skip genenerating uevents for network namespaces that are exiting

No one can see these events, because a network namespace can not be destroyed, if it has sockets. Unlike other devices, uevent-s for network devices are generated only inside their network namespaces. They are filtered in kobj_bcast_filter() My experiments shows that net namespaces are destroyed

[PATCH v2] net: skip genenerating uevents for network namespaces that are exiting

No one can see these events, because a network namespace can not be destroyed, if it has sockets. Unlike other devices, uevent-s for network devices are generated only inside their network namespaces. They are filtered in kobj_bcast_filter() My experiments shows that net namespaces are destroyed

Re: linux.git: printk() problem

On Mon, Oct 24, 2016 at 6:55 PM, Sergey Senozhatsky wrote: > > I think cont_flush() should grab the logbuf_lock lock, because > it does log_store() and touches the cont.len. so something like > this perhaps Absolutely. Good catch. >> - if (wake_klogd) >> +

Re: linux.git: printk() problem

On Mon, Oct 24, 2016 at 6:55 PM, Sergey Senozhatsky wrote: > > I think cont_flush() should grab the logbuf_lock lock, because > it does log_store() and touches the cont.len. so something like > this perhaps Absolutely. Good catch. >> - if (wake_klogd) >> + if (wake_klogd || cont.len) >

Re: [PATCH v2 2/8] mm/swap: Add cluster lock

Hi, Jonathan, Thanks for review. Jonathan Corbet writes: > On Thu, 20 Oct 2016 16:31:41 -0700 > Tim Chen wrote: > >> From: "Huang, Ying" >> >> This patch is to reduce the lock contention of swap_info_struct->lock >> via using

Re: [PATCH v2 2/8] mm/swap: Add cluster lock

Hi, Jonathan, Thanks for review. Jonathan Corbet writes: > On Thu, 20 Oct 2016 16:31:41 -0700 > Tim Chen wrote: > >> From: "Huang, Ying" >> >> This patch is to reduce the lock contention of swap_info_struct->lock >> via using a more fine grained lock in swap_cluster_info for some swap >>

[PATCH] PM / devfreq: Restart previous governor if new governor fails to start

If the new governor fails to start, switch back to old governor so that the devfreq state is not left if some weird limbo. Signed-off-by: Saravana Kannan --- drivers/devfreq/devfreq.c | 9 +++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git

[PATCH] PM / devfreq: Restart previous governor if new governor fails to start

If the new governor fails to start, switch back to old governor so that the devfreq state is not left if some weird limbo. Signed-off-by: Saravana Kannan --- drivers/devfreq/devfreq.c | 9 +++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/drivers/devfreq/devfreq.c

[PATCH] lib/genalloc.c: Start search from start of chunk

gen_pool_alloc_algo() iterates over all chunks of a pool trying to find a contiguous block of memory that satisfies the allocation request. The search should start at address zero of every chunk. However, as the code stands today, this is only true for the first chunk. Due to a bug, the search of

[PATCH] lib/genalloc.c: Start search from start of chunk

gen_pool_alloc_algo() iterates over all chunks of a pool trying to find a contiguous block of memory that satisfies the allocation request. The search should start at address zero of every chunk. However, as the code stands today, this is only true for the first chunk. Due to a bug, the search of

Re: linux.git: printk() problem

Hello, Cc more people report: https://marc.info/?l=linux-kernel=147721454506634=2 patch: https://marc.info/?l=linux-kernel=147733173800859 FB is using ext header a lot (afaik), so may be Tejun or Calvin will also be interested. On (10/24/16 10:55), Linus Torvalds wrote: > > Note the "totally

Re: linux.git: printk() problem

Hello, Cc more people report: https://marc.info/?l=linux-kernel=147721454506634=2 patch: https://marc.info/?l=linux-kernel=147733173800859 FB is using ext header a lot (afaik), so may be Tejun or Calvin will also be interested. On (10/24/16 10:55), Linus Torvalds wrote: > > Note the "totally

Re: BUG: unable to handle kernel NULL pointer dereference at 00000000000001e0

On Mon, 2016-10-24 at 17:28 +0200, Jiri Slaby wrote: On 10/24/2016, 04:48 PM, Borislav Petkov wrote: > Hi people, > > typing "reboot" splats the following on the serial console. Ideas? > > INIT: Sending p[ 427.863916] BUG: unable to handle kernel NULL pointer > dereference at 01e0

Re: BUG: unable to handle kernel NULL pointer dereference at 00000000000001e0

On Mon, 2016-10-24 at 17:28 +0200, Jiri Slaby wrote: On 10/24/2016, 04:48 PM, Borislav Petkov wrote: > Hi people, > > typing "reboot" splats the following on the serial console. Ideas? > > INIT: Sending p[ 427.863916] BUG: unable to handle kernel NULL pointer > dereference at 01e0

Re: [RFC PATCH] gpio: of: fix GPIO drivers with multiple gpio_chip for a single node

2016-10-25 1:58 GMT+09:00 Sylvain Lemieux : > Hi Masahiro, > > On Mon, 2016-10-24 at 16:43 +0900, Masahiro Yamada wrote: >> Sylvain Lemieux reports the LPC32xx GPIO driver is broken since >> commit 762c2e46c059 ("gpio: of: remove of_gpiochip_and_xlate() and >> struct

Re: [RFC PATCH] gpio: of: fix GPIO drivers with multiple gpio_chip for a single node

2016-10-25 1:58 GMT+09:00 Sylvain Lemieux : > Hi Masahiro, > > On Mon, 2016-10-24 at 16:43 +0900, Masahiro Yamada wrote: >> Sylvain Lemieux reports the LPC32xx GPIO driver is broken since >> commit 762c2e46c059 ("gpio: of: remove of_gpiochip_and_xlate() and >> struct gg_data"). Probably,

[PATCH v2] gpio: of: fix GPIO drivers with multiple gpio_chip for a single node

Sylvain Lemieux reports the LPC32xx GPIO driver is broken since commit 762c2e46c059 ("gpio: of: remove of_gpiochip_and_xlate() and struct gg_data"). Probably, gpio-etraxfs.c and gpio-davinci.c are broken too. Those drivers register multiple gpio_chip that are associated to a single OF node, and

[PATCH v2] gpio: of: fix GPIO drivers with multiple gpio_chip for a single node

Sylvain Lemieux reports the LPC32xx GPIO driver is broken since commit 762c2e46c059 ("gpio: of: remove of_gpiochip_and_xlate() and struct gg_data"). Probably, gpio-etraxfs.c and gpio-davinci.c are broken too. Those drivers register multiple gpio_chip that are associated to a single OF node, and

[PATCH V1] mfd: pv88080: Expand driver for GPIO function support.

erface. and contains the following components: - Regulators - Configurable GPIOs Kconfig and Makefile are updated to reflect support for PV88080 PMIC. Signed-off-by: Eric Jeong <eric.jeong.opensou...@diasemi.com> --- This patch applies against linux-next and next-20161024 Hi, This ch

[PATCH V1] mfd: pv88080: Expand driver for GPIO function support.

: - Regulators - Configurable GPIOs Kconfig and Makefile are updated to reflect support for PV88080 PMIC. Signed-off-by: Eric Jeong --- This patch applies against linux-next and next-20161024 Hi, This change is made as a single patch. Because, to ensure that kernel builds and runs

Re: [PATCH/RFT v2 12/17] USB: ochi-da8xx: Use a regulator for vbus/overcurrent

On 10/24/2016 11:46 AM, ahas...@baylibre.com wrote: From: Axel Haslam Currently, the da8xx ohci driver uses a set of gpios and callbacks in board files to handle vbus and overcurrent irqs form the power supply. However, this does not play nice when moving to a DT based

Re: [PATCH/RFT v2 12/17] USB: ochi-da8xx: Use a regulator for vbus/overcurrent

On 10/24/2016 11:46 AM, ahas...@baylibre.com wrote: From: Axel Haslam Currently, the da8xx ohci driver uses a set of gpios and callbacks in board files to handle vbus and overcurrent irqs form the power supply. However, this does not play nice when moving to a DT based boot were we wont have

Re: [PATCH v9 1/2] usb: dwc2: assert phy reset when waking up in rk3288 platform

On 10/23/2016 2:33 AM, ayaka wrote: > > > On 10/22/2016 03:27 AM, John Youn wrote: >> On 10/20/2016 11:38 AM, Randy Li wrote: >>> On the rk3288 USB host-only port (the one that's not the OTG-enabled >>> port) the PHY can get into a bad state when a wakeup is asserted (not >>> just a wakeup from

Re: [PATCH v9 1/2] usb: dwc2: assert phy reset when waking up in rk3288 platform

On 10/23/2016 2:33 AM, ayaka wrote: > > > On 10/22/2016 03:27 AM, John Youn wrote: >> On 10/20/2016 11:38 AM, Randy Li wrote: >>> On the rk3288 USB host-only port (the one that's not the OTG-enabled >>> port) the PHY can get into a bad state when a wakeup is asserted (not >>> just a wakeup from

Re: Regression in 4.9-rc1 for PPC32 - bisected to commit 05fd007e4629

I have a hack that works. Perhaps it will give a bit more understanding so that a proper patch can be created. My changes were applied on top of 4.9-rc1 with the patch from https://www.linux-mips.org/archives/linux-mips/2016-10/msg00130.html, and were as follows: Index:

Re: Regression in 4.9-rc1 for PPC32 - bisected to commit 05fd007e4629

I have a hack that works. Perhaps it will give a bit more understanding so that a proper patch can be created. My changes were applied on top of 4.9-rc1 with the patch from https://www.linux-mips.org/archives/linux-mips/2016-10/msg00130.html, and were as follows: Index:

[PATCH net-next] net: add an ioctl to get a socket network namespace

From: Andrey Vagin Each socket operates in a network namespace where it has been created, so if we want to dump and restore a socket, we have to know its network namespace. We have a socket_diag to get information about sockets, it doesn't report sockets which are not bound

[PATCH net-next] net: add an ioctl to get a socket network namespace

From: Andrey Vagin Each socket operates in a network namespace where it has been created, so if we want to dump and restore a socket, we have to know its network namespace. We have a socket_diag to get information about sockets, it doesn't report sockets which are not bound or connected. This

Re: [RFC 2/8] mm: Add specialized fallback zonelist for coherent device memory nodes

On 10/24/2016 10:40 PM, Dave Hansen wrote: > On 10/23/2016 09:31 PM, Anshuman Khandual wrote: >> +#ifdef CONFIG_COHERENT_DEVICE >> +/* >> + * Isolation requiring coherent device memory node's zones >> + * should not be part of any other node's fallback zonelist

Re: [RFC 2/8] mm: Add specialized fallback zonelist for coherent device memory nodes

On 10/24/2016 10:40 PM, Dave Hansen wrote: > On 10/23/2016 09:31 PM, Anshuman Khandual wrote: >> +#ifdef CONFIG_COHERENT_DEVICE >> +/* >> + * Isolation requiring coherent device memory node's zones >> + * should not be part of any other node's fallback zonelist

Re: [PATCH v4 5/5] x86, kvm: support vcpu preempted check

在 2016/10/24 23:18, Paolo Bonzini 写道: On 24/10/2016 17:14, Radim Krčmář wrote: 2016-10-24 16:39+0200, Paolo Bonzini: On 19/10/2016 19:24, Radim Krčmář wrote: + if (vcpu->arch.st.msr_val & KVM_MSR_ENABLED) + if (kvm_read_guest_cached(vcpu->kvm, >arch.st.stime, +

Re: [PATCH v4 5/5] x86, kvm: support vcpu preempted check

在 2016/10/24 23:18, Paolo Bonzini 写道: On 24/10/2016 17:14, Radim Krčmář wrote: 2016-10-24 16:39+0200, Paolo Bonzini: On 19/10/2016 19:24, Radim Krčmář wrote: + if (vcpu->arch.st.msr_val & KVM_MSR_ENABLED) + if (kvm_read_guest_cached(vcpu->kvm, >arch.st.stime, +

RE: [RESEND PATCH v3 kernel 3/7] mm: add a function to get the max pfn

> On 10/20/2016 11:24 PM, Liang Li wrote: > > Expose the function to get the max pfn, so it can be used in the > > virtio-balloon device driver. Simply include the 'linux/bootmem.h' > > is not enough, if the device driver is built to a module, directly > > refer the max_pfn lead to build failed. >

RE: [RESEND PATCH v3 kernel 3/7] mm: add a function to get the max pfn

> On 10/20/2016 11:24 PM, Liang Li wrote: > > Expose the function to get the max pfn, so it can be used in the > > virtio-balloon device driver. Simply include the 'linux/bootmem.h' > > is not enough, if the device driver is built to a module, directly > > refer the max_pfn lead to build failed. >

Re: [RFC 1/8] mm: Define coherent device memory node

On 10/24/2016 10:39 PM, Dave Hansen wrote: >> +#ifdef CONFIG_COHERENT_DEVICE >> > +#define node_cdm(nid) (NODE_DATA(nid)->coherent_device) >> > +#define set_cdm_isolation(nid) (node_cdm(nid) = 1) >> > +#define clr_cdm_isolation(nid) (node_cdm(nid) = 0) >> > +#define isolated_cdm_node(nid)

Re: [RFC 1/8] mm: Define coherent device memory node

On 10/24/2016 10:39 PM, Dave Hansen wrote: >> +#ifdef CONFIG_COHERENT_DEVICE >> > +#define node_cdm(nid) (NODE_DATA(nid)->coherent_device) >> > +#define set_cdm_isolation(nid) (node_cdm(nid) = 1) >> > +#define clr_cdm_isolation(nid) (node_cdm(nid) = 0) >> > +#define isolated_cdm_node(nid)

RE: [RESEND PATCH v3 kernel 2/7] virtio-balloon: define new feature bit and page bitmap head

> On 10/20/2016 11:24 PM, Liang Li wrote: > > Add a new feature which supports sending the page information with a > > bitmap. The current implementation uses PFNs array, which is not very > > efficient. Using bitmap can improve the performance of > > inflating/deflating significantly > > Why is

RE: [RESEND PATCH v3 kernel 2/7] virtio-balloon: define new feature bit and page bitmap head

> On 10/20/2016 11:24 PM, Liang Li wrote: > > Add a new feature which supports sending the page information with a > > bitmap. The current implementation uses PFNs array, which is not very > > efficient. Using bitmap can improve the performance of > > inflating/deflating significantly > > Why is

Re: [PATCH 00/10] mpt3sas driver Enhancements and

> "Suganath" == Suganath Prabu S > writes: Suganath, Suganath> Here is the change list: Posting 10 patches for mpt3sas driver Suganath> enhancements and few fixes. Suganath> * Added Device ID's for SAS35 devices and updated MPI Suganath>

Re: [PATCH 00/10] mpt3sas driver Enhancements and

> "Suganath" == Suganath Prabu S > writes: Suganath, Suganath> Here is the change list: Posting 10 patches for mpt3sas driver Suganath> enhancements and few fixes. Suganath> * Added Device ID's for SAS35 devices and updated MPI Suganath> Header. Suganath> * Support "EEDP Escape

Re: [PATCH v5 02/23] of: device: Export of_device_{get_modalias, uvent_modalias} to modules

On Mon, Oct 24, 2016 at 12:48:24PM -0700, Stephen Boyd wrote: > Quoting Chen-Yu Tsai (2016-10-24 05:19:05) > > Hi, > > > > On Tue, Oct 18, 2016 at 9:56 AM, Stephen Boyd > > wrote: > > > The ULPI bus can be built as a module, and it will soon be > > > calling these

Re: [PATCH v5 02/23] of: device: Export of_device_{get_modalias, uvent_modalias} to modules

On Mon, Oct 24, 2016 at 12:48:24PM -0700, Stephen Boyd wrote: > Quoting Chen-Yu Tsai (2016-10-24 05:19:05) > > Hi, > > > > On Tue, Oct 18, 2016 at 9:56 AM, Stephen Boyd > > wrote: > > > The ULPI bus can be built as a module, and it will soon be > > > calling these functions when it supports

RE: [RESEND PATCH v3 kernel 1/7] virtio-balloon: rework deflate to add page to a list

> On 10/20/2016 11:24 PM, Liang Li wrote: > > Will allow faster notifications using a bitmap down the road. > > balloon_pfn_to_page() can be removed because it's useless. > > This is a pretty terse description of what's going on here. Could you try to > elaborate a bit? What *is* the current

RE: [RESEND PATCH v3 kernel 1/7] virtio-balloon: rework deflate to add page to a list

> On 10/20/2016 11:24 PM, Liang Li wrote: > > Will allow faster notifications using a bitmap down the road. > > balloon_pfn_to_page() can be removed because it's useless. > > This is a pretty terse description of what's going on here. Could you try to > elaborate a bit? What *is* the current

Re: [PATCH/RFT v2 13/17] USB: da8xx: use ohci priv data instead of globals

On 10/24/2016 11:46 AM, ahas...@baylibre.com wrote: From: Axel Haslam > static const struct ohci_driver_overrides da8xx_overrides __initconst = { - .reset = ohci_da8xx_reset + .reset = ohci_da8xx_reset, + .extra_priv_size =

Re: [PATCH/RFT v2 13/17] USB: da8xx: use ohci priv data instead of globals

On 10/24/2016 11:46 AM, ahas...@baylibre.com wrote: From: Axel Haslam > static const struct ohci_driver_overrides da8xx_overrides __initconst = { - .reset = ohci_da8xx_reset + .reset = ohci_da8xx_reset, + .extra_priv_size = sizeof(struct da8xx_ohci_hcd),

Good Day

Loan Offer at 3%, Feel Free to REPLY back to us for more info

Good Day

Loan Offer at 3%, Feel Free to REPLY back to us for more info

Re: bio linked list corruption.

On Oct 24, 2016 5:00 PM, "Linus Torvalds" wrote: > > On Mon, Oct 24, 2016 at 3:42 PM, Andy Lutomirski wrote: > > > Now the fallocate thread catches up and *exits*. Dave's test makes a > > new thread that reuses the stack (the vmap area or the

Re: bio linked list corruption.

On Oct 24, 2016 5:00 PM, "Linus Torvalds" wrote: > > On Mon, Oct 24, 2016 at 3:42 PM, Andy Lutomirski wrote: > > > Now the fallocate thread catches up and *exits*. Dave's test makes a > > new thread that reuses the stack (the vmap area or the backing store). > > > > Now the shmem_fault thread

Re: [PATCH/RFT v2 15/17] usb: host: ohci-da8xx: Add devicetree bindings documentation

On 10/24/2016 11:46 AM, ahas...@baylibre.com wrote: From: Axel Haslam This patch documents the device tree bindings required for the ohci controller found in TI da8xx family of SoC's Signed-off-by: Axel Haslam ---

Re: [PATCH/RFT v2 15/17] usb: host: ohci-da8xx: Add devicetree bindings documentation

On 10/24/2016 11:46 AM, ahas...@baylibre.com wrote: From: Axel Haslam This patch documents the device tree bindings required for the ohci controller found in TI da8xx family of SoC's Signed-off-by: Axel Haslam --- .../devicetree/bindings/usb/ohci-da8xx.txt | 39

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