[PATCH v3 10/12] sched/fair: Remove scale_load_down() for load_avg

Currently, load_avg = scale_load_down(load) * runnable%. The extra scaling down of load does not make much sense, because load_avg is primarily THE load and on top of that, we take runnable time into account. We therefore remove scale_load_down() for load_avg. But we need to carefully consider

[PATCH v3 12/12] sched/fair: Enable increased scale for kernel load

The increased scale or precision for kernel load has been disabled since the commit e4c2fb0d5776 ("sched: Disable (revert) SCHED_LOAD_SCALE increase"). But we do need it when we have task groups, especially on bigger machines. Otherwise, we probably will run out of precision for load distribution.

[PATCH v3 08/12] sched/fair: Remove SCHED_LOAD_SHIFT and SCHED_LOAD_SCALE

After cleaning up the sched metrics, these two definitions that cause ambiguity are not needed any more. Use NICE_0_LOAD_SHIFT and NICE_0_LOAD instead (the names suggest clearly who they are). Suggested-by: Ben Segall Signed-off-by: Yuyang Du --- kernel/sched/fair.c |4 ++--

[PATCH v3 09/12] sched/fair: Add introduction to the sched average metrics

These sched metrics have become complex enough. We introduce them at their definitions. Signed-off-by: Yuyang Du --- include/linux/sched.h | 60 - 1 file changed, 49 insertions(+), 11 deletions(-) diff --git a/include/linux/sched.h

[PATCH v3 10/12] sched/fair: Remove scale_load_down() for load_avg

Currently, load_avg = scale_load_down(load) * runnable%. The extra scaling down of load does not make much sense, because load_avg is primarily THE load and on top of that, we take runnable time into account. We therefore remove scale_load_down() for load_avg. But we need to carefully consider

[PATCH v3 12/12] sched/fair: Enable increased scale for kernel load

The increased scale or precision for kernel load has been disabled since the commit e4c2fb0d5776 ("sched: Disable (revert) SCHED_LOAD_SCALE increase"). But we do need it when we have task groups, especially on bigger machines. Otherwise, we probably will run out of precision for load distribution.

[PATCH v3 04/12] sched/fair: Add __always_inline compiler attribute to __accumulate_sum()

Everybody has it. If code-size is not the problem, __accumulate_sum() should have it too. Signed-off-by: Yuyang Du --- kernel/sched/fair.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c index 34ccaa3..a060ef2

[PATCH v3 01/12] sched/fair: Optimize sum computation with a lookup table

__compute_runnable_contrib() uses a loop to compute sum, whereas a table lookup can do it faster in a constant time. The program to generate the constants is located at: Documentation/scheduler/sched-avg.txt Signed-off-by: Yuyang Du Reviewed-by: Morten Rasmussen

[PATCH v3 00/12] sched/fair: Optimize and clean up sched averages

Hi Peter, This patch series combines the previous cleanup and optimization series. And as you and Ingo suggested, the increased kernel load scale is reinstated when on 64BIT and FAIR_GROUP_SCHED. This patch series should have no perceivable changes to load and util except that load's range is

[PATCH v3 02/12] sched/fair: Rename variable names for sched averages

The names of sched averages (including load_avg and util_avg) have been changed and added in the past a couple of years, some of the names are a bit confusing especially to people who first read them. This patch attempts to make the names more self-explaining. And some comments are updated too.

[PATCH v3 04/12] sched/fair: Add __always_inline compiler attribute to __accumulate_sum()

Everybody has it. If code-size is not the problem, __accumulate_sum() should have it too. Signed-off-by: Yuyang Du --- kernel/sched/fair.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c index 34ccaa3..a060ef2 100644 ---

[PATCH v3 01/12] sched/fair: Optimize sum computation with a lookup table

__compute_runnable_contrib() uses a loop to compute sum, whereas a table lookup can do it faster in a constant time. The program to generate the constants is located at: Documentation/scheduler/sched-avg.txt Signed-off-by: Yuyang Du Reviewed-by: Morten Rasmussen Acked-by: Vincent Guittot ---

[PATCH v3 00/12] sched/fair: Optimize and clean up sched averages

Hi Peter, This patch series combines the previous cleanup and optimization series. And as you and Ingo suggested, the increased kernel load scale is reinstated when on 64BIT and FAIR_GROUP_SCHED. This patch series should have no perceivable changes to load and util except that load's range is

[PATCH v3 02/12] sched/fair: Rename variable names for sched averages

The names of sched averages (including load_avg and util_avg) have been changed and added in the past a couple of years, some of the names are a bit confusing especially to people who first read them. This patch attempts to make the names more self-explaining. And some comments are updated too.

Re: [PATCH v6 09/12] usb: gadget: udc: adapt to OTG core

On Tue, May 03, 2016 at 06:44:46PM +0300, Roger Quadros wrote: > Hi, > > On 03/05/16 10:06, Jun Li wrote: > > Hi > > > > /** > > + * usb_gadget_start - start the usb gadget controller and > > +connect to bus > > + * @gadget: the gadget device to start > >

Re: [PATCH v6 09/12] usb: gadget: udc: adapt to OTG core

On Tue, May 03, 2016 at 06:44:46PM +0300, Roger Quadros wrote: > Hi, > > On 03/05/16 10:06, Jun Li wrote: > > Hi > > > > /** > > + * usb_gadget_start - start the usb gadget controller and > > +connect to bus > > + * @gadget: the gadget device to start > >

[v9, 7/7] mmc: sdhci-of-esdhc: fix host version for T4240-R1.0-R2.0

The eSDHC of T4240-R1.0-R2.0 has incorrect vender version and spec version. Acturally the right version numbers should be VVN=0x13 and SVN = 0x1. This patch adds the GUTS driver support for eSDHC driver to get SVR(System version register). And fix host version to avoid that incorrect version

Re: [RFC PATCH] livepatch: allow removal of a disabled patch

On Tue, May 03, 2016 at 09:39:48PM -0500, Josh Poimboeuf wrote: > On Wed, May 04, 2016 at 12:31:12AM +0200, Jiri Kosina wrote: > > On Tue, 3 May 2016, Josh Poimboeuf wrote: > > > > > > 1. Do we really need a completion? If I am not missing something > > > > kobject_del() always waits for sysfs

[v9, 3/7] soc: fsl: add GUTS driver for QorIQ platforms

The global utilities block controls power management, I/O device enabling, power-onreset(POR) configuration monitoring, alternate function selection for multiplexed signals,and clock control. This patch adds GUTS driver to manage and access global utilities block. Signed-off-by: Yangbo Lu

[v9, 7/7] mmc: sdhci-of-esdhc: fix host version for T4240-R1.0-R2.0

The eSDHC of T4240-R1.0-R2.0 has incorrect vender version and spec version. Acturally the right version numbers should be VVN=0x13 and SVN = 0x1. This patch adds the GUTS driver support for eSDHC driver to get SVR(System version register). And fix host version to avoid that incorrect version

Re: [RFC PATCH] livepatch: allow removal of a disabled patch

On Tue, May 03, 2016 at 09:39:48PM -0500, Josh Poimboeuf wrote: > On Wed, May 04, 2016 at 12:31:12AM +0200, Jiri Kosina wrote: > > On Tue, 3 May 2016, Josh Poimboeuf wrote: > > > > > > 1. Do we really need a completion? If I am not missing something > > > > kobject_del() always waits for sysfs

[v9, 3/7] soc: fsl: add GUTS driver for QorIQ platforms

The global utilities block controls power management, I/O device enabling, power-onreset(POR) configuration monitoring, alternate function selection for multiplexed signals,and clock control. This patch adds GUTS driver to manage and access global utilities block. Signed-off-by: Yangbo Lu

[v9, 4/7] dt: move guts devicetree doc out of powerpc directory

Move guts devicetree doc to Documentation/devicetree/bindings/soc/fsl/ since it's used by not only PowerPC but also ARM. And add a specification for 'little-endian' property. Signed-off-by: Yangbo Lu Acked-by: Scott Wood Acked-by: Rob Herring

[v9, 4/7] dt: move guts devicetree doc out of powerpc directory

Move guts devicetree doc to Documentation/devicetree/bindings/soc/fsl/ since it's used by not only PowerPC but also ARM. And add a specification for 'little-endian' property. Signed-off-by: Yangbo Lu Acked-by: Scott Wood Acked-by: Rob Herring --- Changes for v4: - Added this patch

Re: [serial] 13a7238eea: WARNING: CPU: 0 PID: 1 at drivers/tty/serial/serial_core.c:99 uart_change_pm+0x35/0x162

Hi, On 05/03/2016 08:13 PM, kernel test robot wrote: > > FYI, we noticed the following commit: > > https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tty-testing > commit 13a7238eeab5718bf968e2a835205ba659a38a77 ("serial: core: Prevent > unsafe uart port access, part 3") This

Re: [serial] 13a7238eea: WARNING: CPU: 0 PID: 1 at drivers/tty/serial/serial_core.c:99 uart_change_pm+0x35/0x162

Hi, On 05/03/2016 08:13 PM, kernel test robot wrote: > > FYI, we noticed the following commit: > > https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tty-testing > commit 13a7238eeab5718bf968e2a835205ba659a38a77 ("serial: core: Prevent > unsafe uart port access, part 3") This

Re: [PATCH v2 1/2] dmaengine: qcom-bam-dma: Add pm_runtime support

Hi Pramod >>> @@ -715,10 +724,13 @@ static int bam_resume(struct dma_chan *chan) >>> struct bam_device *bdev = bchan->bdev; >>> unsigned long flag; >>> >>> + pm_runtime_get_sync(bdev->dev); >>> spin_lock_irqsave(>vc.lock, flag); >>> writel_relaxed(0,

Re: [PATCH v2 1/2] dmaengine: qcom-bam-dma: Add pm_runtime support

Hi Pramod >>> @@ -715,10 +724,13 @@ static int bam_resume(struct dma_chan *chan) >>> struct bam_device *bdev = bchan->bdev; >>> unsigned long flag; >>> >>> + pm_runtime_get_sync(bdev->dev); >>> spin_lock_irqsave(>vc.lock, flag); >>> writel_relaxed(0,

Re: [RESEND PATCH v10 4/4] power: wm831x_power: Support USB charger current limit management

Hi Mark >> > +static const unsigned int wm831x_usb_limits[] = { >> > + 0, >> > + 2, >> > + 100, >> > + 500, >> > + 900, >> > + 1500, >> > + 1800, >> > + 550, >> > +}; > >> Just for curiosity, How these current limits are getting decided? >> Can we

Re: [RESEND PATCH v10 4/4] power: wm831x_power: Support USB charger current limit management

Hi Mark >> > +static const unsigned int wm831x_usb_limits[] = { >> > + 0, >> > + 2, >> > + 100, >> > + 500, >> > + 900, >> > + 1500, >> > + 1800, >> > + 550, >> > +}; > >> Just for curiosity, How these current limits are getting decided? >> Can we

Re: [PATCH RESEND 10/12] sh: I/O DATA HDL-U (aka landisk) support dts

On Sun, May 01, 2016 at 02:08:34PM +0900, Yoshinori Sato wrote: > Signed-off-by: Yoshinori Sato > --- > arch/sh/boot/dts/landisk.dts | 150 > +++ > 1 file changed, 150 insertions(+) > create mode 100644

Re: [PATCH RESEND 10/12] sh: I/O DATA HDL-U (aka landisk) support dts

On Sun, May 01, 2016 at 02:08:34PM +0900, Yoshinori Sato wrote: > Signed-off-by: Yoshinori Sato > --- > arch/sh/boot/dts/landisk.dts | 150 > +++ > 1 file changed, 150 insertions(+) > create mode 100644 arch/sh/boot/dts/landisk.dts > > diff --git

RE: [v8, 6/7] MAINTAINERS: add entry for Freescale SoC specific driver

Hi Leo and Scott, > -Original Message- > From: Leo Li [mailto:pku@gmail.com] > Sent: Wednesday, May 04, 2016 4:06 AM > To: Yangbo Lu > Cc: Scott Wood; Yang-Leo Li; linux-...@vger.kernel.org; linuxppc- > d...@lists.ozlabs.org; linux-arm-ker...@lists.infradead.org; linux- >

RE: [v8, 6/7] MAINTAINERS: add entry for Freescale SoC specific driver

Hi Leo and Scott, > -Original Message- > From: Leo Li [mailto:pku@gmail.com] > Sent: Wednesday, May 04, 2016 4:06 AM > To: Yangbo Lu > Cc: Scott Wood; Yang-Leo Li; linux-...@vger.kernel.org; linuxppc- > d...@lists.ozlabs.org; linux-arm-ker...@lists.infradead.org; linux- >

Re: [PATCH v2 5/5] dax: handle media errors in dax_do_io

On Tue, May 03, 2016 at 10:28:15AM -0700, Dan Williams wrote: > On Mon, May 2, 2016 at 6:51 PM, Dave Chinner wrote: > > On Mon, May 02, 2016 at 04:25:51PM -0700, Dan Williams wrote: > [..] > > Yes, I know, and it doesn't answer any of the questions I just > > asked. What you

Re: [PATCH v2 5/5] dax: handle media errors in dax_do_io

On Tue, May 03, 2016 at 10:28:15AM -0700, Dan Williams wrote: > On Mon, May 2, 2016 at 6:51 PM, Dave Chinner wrote: > > On Mon, May 02, 2016 at 04:25:51PM -0700, Dan Williams wrote: > [..] > > Yes, I know, and it doesn't answer any of the questions I just > > asked. What you just told me is that

[PATCH 1/2] Improve types abstraction for gdb python scripts

From: Dom Cote Change the read_u16 function so it accepts both 'str' and 'byte' as type for the arguments. When calling read_memory() from gdb API, depending on if it was built with 2.7 or 3.X, the format used to return the data will differ ( 'str' for 2.7, and 'byte'

[PATCH 2/2] Fix issue with dmesg.py and python 3.X

From: Dom Cote Replace the addition (+) of 2 python 'memoryview' objects with the addition of 2 'bytes' objects, convert the result back to memoryview. Tested with python 3.4 and 2.7 Tested with gdb 7.7 Signed-off-by: Dom Cote ---

[PATCH 1/2] Improve types abstraction for gdb python scripts

From: Dom Cote Change the read_u16 function so it accepts both 'str' and 'byte' as type for the arguments. When calling read_memory() from gdb API, depending on if it was built with 2.7 or 3.X, the format used to return the data will differ ( 'str' for 2.7, and 'byte' for 3.X ). Add a function

[PATCH 2/2] Fix issue with dmesg.py and python 3.X

From: Dom Cote Replace the addition (+) of 2 python 'memoryview' objects with the addition of 2 'bytes' objects, convert the result back to memoryview. Tested with python 3.4 and 2.7 Tested with gdb 7.7 Signed-off-by: Dom Cote --- scripts/gdb/linux/dmesg.py | 7 --- 1 file changed, 4

Re: [net] 5413d1babe: INFO: SOFTIRQ-safe -> SOFTIRQ-unsafe lock order detected ]

On Tue, May 3, 2016 at 7:47 PM, kernel test robot wrote: > > FYI, we noticed the following commit: > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master > commit 5413d1babe8f10de13d72496c12b862eef8ba613 ("net: do not block BH while > processing

Re: [net] 5413d1babe: INFO: SOFTIRQ-safe -> SOFTIRQ-unsafe lock order detected ]

On Tue, May 3, 2016 at 7:47 PM, kernel test robot wrote: > > FYI, we noticed the following commit: > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master > commit 5413d1babe8f10de13d72496c12b862eef8ba613 ("net: do not block BH while > processing socket backlog") > > on

Re: [PATCH RESEND 05/12] sh: DeviceTree support update

On Sun, May 01, 2016 at 02:08:29PM +0900, Yoshinori Sato wrote: > Changes bellow > - FDT setup timing fix. > - chosen/bootargs support. > - zImage support. > - DT binding helper macro. > > Signed-off-by: Yoshinori Sato > --- > arch/sh/boards/of-generic.c

Re: [PATCH RESEND 05/12] sh: DeviceTree support update

On Sun, May 01, 2016 at 02:08:29PM +0900, Yoshinori Sato wrote: > Changes bellow > - FDT setup timing fix. > - chosen/bootargs support. > - zImage support. > - DT binding helper macro. > > Signed-off-by: Yoshinori Sato > --- > arch/sh/boards/of-generic.c| 23 >

[PATCH 2/2] Fix issue with dmesg.py and python 3.X

From: Dom Cote Replace the addition (+) of 2 python 'memoryview' objects with the addition of 2 'bytes' objects, convert the result back to memoryview. Tested with python 3.4 and 2.7 Tested with gdb 7.7 Signed-off-by: Dom Cote ---

[PATCH 1/2] Improve types abstraction for gdb python scripts

From: Dom Cote Change the read_u16 function so it accepts both 'str' and 'byte' as type for the arguments. When calling read_memory() from gdb API, depending on if it was built with 2.7 or 3.X, the format used to return the data will differ ( 'str' for 2.7, and 'byte'

[PATCH 2/2] Fix issue with dmesg.py and python 3.X

From: Dom Cote Replace the addition (+) of 2 python 'memoryview' objects with the addition of 2 'bytes' objects, convert the result back to memoryview. Tested with python 3.4 and 2.7 Tested with gdb 7.7 Signed-off-by: Dom Cote --- scripts/gdb/linux/dmesg.py | 7 --- 1 file changed, 4

[PATCH 1/2] Improve types abstraction for gdb python scripts

From: Dom Cote Change the read_u16 function so it accepts both 'str' and 'byte' as type for the arguments. When calling read_memory() from gdb API, depending on if it was built with 2.7 or 3.X, the format used to return the data will differ ( 'str' for 2.7, and 'byte' for 3.X ). Add a function

linux-next: manual merge of the tip tree with the arc tree

Hi all, Today's linux-next merge of the tip tree got a conflict in: drivers/irqchip/Kconfig between commit: df1a714d52c4 ("irqchip: add nps Internal and external irqchips") from the arc tree and commit: 9e2c986cb460 ("irqchip: Add per-cpu interrupt partitioning library") from the tip

linux-next: manual merge of the tip tree with the arc tree

Hi all, Today's linux-next merge of the tip tree got a conflict in: drivers/irqchip/Kconfig between commit: df1a714d52c4 ("irqchip: add nps Internal and external irqchips") from the arc tree and commit: 9e2c986cb460 ("irqchip: Add per-cpu interrupt partitioning library") from the tip

Re: [PATCH RESEND 03/12] sh: Disable board specific code in OF mode

On Sun, May 01, 2016 at 02:08:27PM +0900, Yoshinori Sato wrote: > Board specific code conflict on of-generic. > > Signed-off-by: Yoshinori Sato > --- > arch/sh/Makefile | 11 +++ > 1 file changed, 11 insertions(+) > > diff --git a/arch/sh/Makefile

Re: [PATCH RESEND 03/12] sh: Disable board specific code in OF mode

On Sun, May 01, 2016 at 02:08:27PM +0900, Yoshinori Sato wrote: > Board specific code conflict on of-generic. > > Signed-off-by: Yoshinori Sato > --- > arch/sh/Makefile | 11 +++ > 1 file changed, 11 insertions(+) > > diff --git a/arch/sh/Makefile b/arch/sh/Makefile > index

[net] 5413d1babe: INFO: SOFTIRQ-safe -> SOFTIRQ-unsafe lock order detected ]

FYI, we noticed the following commit: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master commit 5413d1babe8f10de13d72496c12b862eef8ba613 ("net: do not block BH while processing socket backlog") on test machine: vm-lkp-wsx03-1G: 1 threads qemu-system-x86_64 -enable-kvm

[net] 5413d1babe: INFO: SOFTIRQ-safe -> SOFTIRQ-unsafe lock order detected ]

FYI, we noticed the following commit: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master commit 5413d1babe8f10de13d72496c12b862eef8ba613 ("net: do not block BH while processing socket backlog") on test machine: vm-lkp-wsx03-1G: 1 threads qemu-system-x86_64 -enable-kvm

Re: VFIO MSIX Query

Got it. Thanks Alex. I may have future queries as well on this. Will get back to you. Thanks, Nitin > On 04-May-2016, at 01:33, Alex Williamson wrote: > > Hi, > > On Tue, 3 May 2016 23:56:38 +0530 > Nitin Saxena wrote: > >> Hi, >> >> I am a

Re: VFIO MSIX Query

Got it. Thanks Alex. I may have future queries as well on this. Will get back to you. Thanks, Nitin > On 04-May-2016, at 01:33, Alex Williamson wrote: > > Hi, > > On Tue, 3 May 2016 23:56:38 +0530 > Nitin Saxena wrote: > >> Hi, >> >> I am a newbie to VFIO framework and trying to use it

Re: [PATCH] sp5100_tco: properly check for new register layouts

On 05/03/2016 10:15 AM, Lucas Stach wrote: Commits 190aa4304de6 (Add AMD Mullins platform support) and cca118fa2a0a94 (Add AMD Carrizo platform support) enabled the driver on a lot more devices, but the following commit missed a single location in the code when checking if the SB800 register

Re: [PATCH] sp5100_tco: properly check for new register layouts

On 05/03/2016 10:15 AM, Lucas Stach wrote: Commits 190aa4304de6 (Add AMD Mullins platform support) and cca118fa2a0a94 (Add AMD Carrizo platform support) enabled the driver on a lot more devices, but the following commit missed a single location in the code when checking if the SB800 register

Re: [RFC PATCH] livepatch: allow removal of a disabled patch

On Wed, May 04, 2016 at 12:31:12AM +0200, Jiri Kosina wrote: > On Tue, 3 May 2016, Josh Poimboeuf wrote: > > > > 1. Do we really need a completion? If I am not missing something > > > kobject_del() always waits for sysfs callers to leave thanks to kernfs > > > active protection. > > > > What do

Re: [RFC PATCH] livepatch: allow removal of a disabled patch

On Wed, May 04, 2016 at 12:31:12AM +0200, Jiri Kosina wrote: > On Tue, 3 May 2016, Josh Poimboeuf wrote: > > > > 1. Do we really need a completion? If I am not missing something > > > kobject_del() always waits for sysfs callers to leave thanks to kernfs > > > active protection. > > > > What do

Re: [RESEND PATCH 1/2 v6] clk/axs10x: Add I2S PLL clock driver

On Mon, May 02, 2016 at 10:39:05AM +0100, Jose Abreu wrote: > The ARC SDP I2S clock can be programmed using a > specific PLL. > > This patch has the goal of adding a clock driver > that programs this PLL. > > At this moment the rate values are hardcoded in > a table but in the future it would be

Re: [PATCH 6/6] mm/page_owner: use stackdepot to store stacktrace

On Wed, May 04, 2016 at 11:14:50AM +0900, Joonsoo Kim wrote: > On Tue, May 03, 2016 at 10:53:56AM +0200, Michal Hocko wrote: > > On Tue 03-05-16 14:23:04, Joonsoo Kim wrote: > > > From: Joonsoo Kim > > > > > > Currently, we store each page's allocation stacktrace on

Re: [RESEND PATCH 1/2 v6] clk/axs10x: Add I2S PLL clock driver

On Mon, May 02, 2016 at 10:39:05AM +0100, Jose Abreu wrote: > The ARC SDP I2S clock can be programmed using a > specific PLL. > > This patch has the goal of adding a clock driver > that programs this PLL. > > At this moment the rate values are hardcoded in > a table but in the future it would be

Re: [PATCH 6/6] mm/page_owner: use stackdepot to store stacktrace

On Wed, May 04, 2016 at 11:14:50AM +0900, Joonsoo Kim wrote: > On Tue, May 03, 2016 at 10:53:56AM +0200, Michal Hocko wrote: > > On Tue 03-05-16 14:23:04, Joonsoo Kim wrote: > > > From: Joonsoo Kim > > > > > > Currently, we store each page's allocation stacktrace on corresponding > > > page_ext

Re: [PATCH v2] lib/mpi: Fix kernel unaligned access in mpi_write_to_sgl

On Tue, May 03, 2016 at 06:19:15AM -0400, Sowmini Varadhan wrote: > On (05/03/16 16:12), Herbert Xu wrote: > > > > Sorry, but your patch doesn't apply against the current tree at all. > > Please rebase it if it is still needed. > > Hello, > > I had based my patch off of net-next, which is where

Re: [PATCH v2] lib/mpi: Fix kernel unaligned access in mpi_write_to_sgl

On Tue, May 03, 2016 at 06:19:15AM -0400, Sowmini Varadhan wrote: > On (05/03/16 16:12), Herbert Xu wrote: > > > > Sorry, but your patch doesn't apply against the current tree at all. > > Please rebase it if it is still needed. > > Hello, > > I had based my patch off of net-next, which is where

Re: [PATCH v2 5/5] vf610-soc: Add Vybrid SoC device tree binding documentation

On Mon, May 02, 2016 at 12:35:04PM +0530, Sanchayan Maity wrote: > Add device tree binding documentation for Vybrid SoC. > > Signed-off-by: Sanchayan Maity > --- > .../bindings/arm/freescale/fsl,vf610-soc.txt | 35 > ++ > 1 file changed, 35

Re: [PATCH v2 5/5] vf610-soc: Add Vybrid SoC device tree binding documentation

On Mon, May 02, 2016 at 12:35:04PM +0530, Sanchayan Maity wrote: > Add device tree binding documentation for Vybrid SoC. > > Signed-off-by: Sanchayan Maity > --- > .../bindings/arm/freescale/fsl,vf610-soc.txt | 35 > ++ > 1 file changed, 35 insertions(+) > create

Re: [PATCH 4.5 000/200] 4.5.3-stable review

On 05/03/2016 11:21 AM, Greg Kroah-Hartman wrote: On Tue, May 03, 2016 at 12:39:51AM -0700, Guenter Roeck wrote: On 05/02/2016 05:09 PM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.5.3 release. There are 200 patches in this series, all will be posted as a

Re: v4.6-rc1 regression bisected, Problem loading in-kernel X.509 certificate (-2)

David Howells wrote: > (cc'ing Tadeusz as he did the pkcs1 padding function) > > Jamie Heilman wrote: > > > > > Problem loading in-kernel X.509 certificate (-2) > > > > > > ENOENT? Hmmm... The only place that is generated is in the crypto layer. > > > That

Re: v4.6-rc1 regression bisected, Problem loading in-kernel X.509 certificate (-2)

David Howells wrote: > (cc'ing Tadeusz as he did the pkcs1 padding function) > > Jamie Heilman wrote: > > > > > Problem loading in-kernel X.509 certificate (-2) > > > > > > ENOENT? Hmmm... The only place that is generated is in the crypto layer. > > > That suggests missing crypto of some

Re: [PATCH 4.5 000/200] 4.5.3-stable review

On 05/03/2016 11:21 AM, Greg Kroah-Hartman wrote: On Tue, May 03, 2016 at 12:39:51AM -0700, Guenter Roeck wrote: On 05/02/2016 05:09 PM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.5.3 release. There are 200 patches in this series, all will be posted as a

Re: v4.6-rc1 regression bisected, Problem loading in-kernel X.509 certificate (-2)

Tadeusz Struk wrote: > Could you please check if this one fixes the problem for you: > https://patchwork.kernel.org/patch/8766361/ That patch is already present by 4.6-rc5 and the problem still exists, so no, it doesn't. -- Jamie Heilman http://audible.transient.net/~jamie/

Re: v4.6-rc1 regression bisected, Problem loading in-kernel X.509 certificate (-2)

Tadeusz Struk wrote: > Could you please check if this one fixes the problem for you: > https://patchwork.kernel.org/patch/8766361/ That patch is already present by 4.6-rc5 and the problem still exists, so no, it doesn't. -- Jamie Heilman http://audible.transient.net/~jamie/

Re: [PATCH] arm64: tegra: fix compatible string for Tegra132 fuse node

On 2016年05月03日 23:21, Thierry Reding wrote: > * PGP Signed by an unknown key > > On Tue, May 03, 2016 at 05:09:37PM +0800, Wei Ni wrote: >> This patch changes the compatible of Tegra132 fuse node >> to "nvidia,tegra132-efuse", instead of "nvidia,tegra1124-efuse". >> Because the

Re: [PATCH] arm64: tegra: fix compatible string for Tegra132 fuse node

On 2016年05月03日 23:21, Thierry Reding wrote: > * PGP Signed by an unknown key > > On Tue, May 03, 2016 at 05:09:37PM +0800, Wei Ni wrote: >> This patch changes the compatible of Tegra132 fuse node >> to "nvidia,tegra132-efuse", instead of "nvidia,tegra1124-efuse". >> Because the

[PATCH 1/3] md: set MD_CHANGE_PENDING in a atomic region

Some code waits for a metadata update by: 1. flagging that it is needed (MD_CHANGE_DEVS or MD_CHANGE_CLEAN) 2. setting MD_CHANGE_PENDING and waking the management thread 3. waiting for MD_CHANGE_PENDING to be cleared If the first two are done without locking, the code in md_update_sb() which

[PATCH 1/3] md: set MD_CHANGE_PENDING in a atomic region

Some code waits for a metadata update by: 1. flagging that it is needed (MD_CHANGE_DEVS or MD_CHANGE_CLEAN) 2. setting MD_CHANGE_PENDING and waking the management thread 3. waiting for MD_CHANGE_PENDING to be cleared If the first two are done without locking, the code in md_update_sb() which

Re: [RFC v6 1/3] gpio: dt-bindings: add wd,mbl-gpio bindings

On Sun, May 01, 2016 at 02:18:37PM +0200, Christian Lamparter wrote: > This patch adds the device tree bindings for the Western Digital's > MyBook Live memory-mapped GPIO controllers. > > The gpios will be supported by gpio-mmio code of the > GPIO generic library. > > Signed-off-by: Christian

Re: [RFC v6 1/3] gpio: dt-bindings: add wd,mbl-gpio bindings

On Sun, May 01, 2016 at 02:18:37PM +0200, Christian Lamparter wrote: > This patch adds the device tree bindings for the Western Digital's > MyBook Live memory-mapped GPIO controllers. > > The gpios will be supported by gpio-mmio code of the > GPIO generic library. > > Signed-off-by: Christian

RE: [PATCH] usb: hub: fix panic caused by NULL bos pointer during reset device

> > I think Greg is referring to commit 464ad8c43a9e ("usb: core : hub: Fix > > BOS 'NULL pointer' kernel panic"), which has already been applied > > upstream. It looks to me like that patch might have fixed the same > > problem in a different way, in which case Changbin's patch is not > >

RE: [PATCH] usb: hub: fix panic caused by NULL bos pointer during reset device

> > I think Greg is referring to commit 464ad8c43a9e ("usb: core : hub: Fix > > BOS 'NULL pointer' kernel panic"), which has already been applied > > upstream. It looks to me like that patch might have fixed the same > > problem in a different way, in which case Changbin's patch is not > >

Re: [PATCH 6/6] mm/page_owner: use stackdepot to store stacktrace

On Tue, May 03, 2016 at 10:53:56AM +0200, Michal Hocko wrote: > On Tue 03-05-16 14:23:04, Joonsoo Kim wrote: > > From: Joonsoo Kim > > > > Currently, we store each page's allocation stacktrace on corresponding > > page_ext structure and it requires a lot of memory. This

Re: [PATCH 6/6] mm/page_owner: use stackdepot to store stacktrace

On Tue, May 03, 2016 at 10:53:56AM +0200, Michal Hocko wrote: > On Tue 03-05-16 14:23:04, Joonsoo Kim wrote: > > From: Joonsoo Kim > > > > Currently, we store each page's allocation stacktrace on corresponding > > page_ext structure and it requires a lot of memory. This causes the problem > >

Re: [PATCH] watchdog: qcom: Report reboot reason

On Tue, May 3, 2016 at 7:01 PM, Guenter Roeck wrote: > On 05/03/2016 06:36 PM, Grant Grundler wrote: >> >> Ping? Did this change get accepted? >> > > Hi Grant, > > Should be. It is in my watchdog-next branch. I plan to send > a pull request to Wim early next week. Hi Guenter!

Re: [PATCH] watchdog: qcom: Report reboot reason

On Tue, May 3, 2016 at 7:01 PM, Guenter Roeck wrote: > On 05/03/2016 06:36 PM, Grant Grundler wrote: >> >> Ping? Did this change get accepted? >> > > Hi Grant, > > Should be. It is in my watchdog-next branch. I plan to send > a pull request to Wim early next week. Hi Guenter! Excellent - I just

Re: [PATCH] watchdog: qcom: Report reboot reason

On 05/03/2016 06:36 PM, Grant Grundler wrote: Ping? Did this change get accepted? Hi Grant, Should be. It is in my watchdog-next branch. I plan to send a pull request to Wim early next week. Guenter cheers, grant On Tue, Apr 5, 2016 at 12:07 PM, Grant Grundler

Re: [PATCH] watchdog: qcom: Report reboot reason

On 05/03/2016 06:36 PM, Grant Grundler wrote: Ping? Did this change get accepted? Hi Grant, Should be. It is in my watchdog-next branch. I plan to send a pull request to Wim early next week. Guenter cheers, grant On Tue, Apr 5, 2016 at 12:07 PM, Grant Grundler wrote: On Mon, Apr 4,

Re: [PATCH v6 09/12] usb: gadget: udc: adapt to OTG core

On Tue, May 03, 2016 at 06:44:46PM +0300, Roger Quadros wrote: > Hi, > > On 03/05/16 10:06, Jun Li wrote: > > Hi > > > > /** > > + * usb_gadget_start - start the usb gadget controller and > > +connect to bus > > + * @gadget: the gadget device to start > >

Re: [PATCH v6 09/12] usb: gadget: udc: adapt to OTG core

On Tue, May 03, 2016 at 06:44:46PM +0300, Roger Quadros wrote: > Hi, > > On 03/05/16 10:06, Jun Li wrote: > > Hi > > > > /** > > + * usb_gadget_start - start the usb gadget controller and > > +connect to bus > > + * @gadget: the gadget device to start > >

Re: [PATCH v2] mmc: sdhci-of-arasan: fix set_clock when a phy is supported

在 2016/4/28 18:38, Ulf Hansson 写道: On 28 April 2016 at 10:38, Shawn Lin wrote: commit 61b914eb81f8 ("mmc: sdhci-of-arasan: add phy support for sdhci-of-arasan") introduce phy support for arasan. According to the vendor's databook, we should make sure the phy is in

Re: [PATCH v2] mmc: sdhci-of-arasan: fix set_clock when a phy is supported

在 2016/4/28 18:38, Ulf Hansson 写道: On 28 April 2016 at 10:38, Shawn Lin wrote: commit 61b914eb81f8 ("mmc: sdhci-of-arasan: add phy support for sdhci-of-arasan") introduce phy support for arasan. According to the vendor's databook, we should make sure the phy is in poweroff status before we

[PATCH v3] mmc: sdhci-of-arasan: fix set_clock when a phy is supported

commit 61b914eb81f8 ("mmc: sdhci-of-arasan: add phy support for sdhci-of-arasan") introduce phy support for arasan. According to the vendor's databook, we should make sure the phy is in poweroff status before we configure the clk stuff. Otherwise it may cause some IO sample timing issues from the

[PATCH v3] mmc: sdhci-of-arasan: fix set_clock when a phy is supported

commit 61b914eb81f8 ("mmc: sdhci-of-arasan: add phy support for sdhci-of-arasan") introduce phy support for arasan. According to the vendor's databook, we should make sure the phy is in poweroff status before we configure the clk stuff. Otherwise it may cause some IO sample timing issues from the

Re: [PATCH v2 5/5] dax: handle media errors in dax_do_io

On Tue, May 03, 2016 at 06:30:04PM +, Rudoff, Andy wrote: > > > >And when the filesystem says no because the fs devs don't want to > >have to deal with broken apps because app devs learn that "this is a > >go fast knob" and data integrity be damned? It's "fsync is slow so I > >won't use it"

Re: [PATCH v2 5/5] dax: handle media errors in dax_do_io

On Tue, May 03, 2016 at 06:30:04PM +, Rudoff, Andy wrote: > > > >And when the filesystem says no because the fs devs don't want to > >have to deal with broken apps because app devs learn that "this is a > >go fast knob" and data integrity be damned? It's "fsync is slow so I > >won't use it"

Re: [PATCH] watchdog: qcom: Report reboot reason

Ping? Did this change get accepted? cheers, grant On Tue, Apr 5, 2016 at 12:07 PM, Grant Grundler wrote: > On Mon, Apr 4, 2016 at 5:37 PM, Guenter Roeck wrote: >> The Qualcom watchdog timer block reports if the system was reset by the >> watchdog.

Re: [PATCH] watchdog: qcom: Report reboot reason

Ping? Did this change get accepted? cheers, grant On Tue, Apr 5, 2016 at 12:07 PM, Grant Grundler wrote: > On Mon, Apr 4, 2016 at 5:37 PM, Guenter Roeck wrote: >> The Qualcom watchdog timer block reports if the system was reset by the >> watchdog. Pass the information to user space. >> >> Cc:

Re: [PATCH 02/11] mtd: nand_bbt: introduce BBT related data structure

Hi Boris, On Tue, Apr 19, 2016 at 3:34 PM, Boris Brezillon wrote: > Hi Peter, > > On Tue, 19 Apr 2016 08:40:40 +0800 > Peter Pan wrote: >> >> > >> >> So it's true, it >> >> should still be numchips in nand_bbt.c? I just came out this

Re: [PATCH 02/11] mtd: nand_bbt: introduce BBT related data structure

Hi Boris, On Tue, Apr 19, 2016 at 3:34 PM, Boris Brezillon wrote: > Hi Peter, > > On Tue, 19 Apr 2016 08:40:40 +0800 > Peter Pan wrote: >> >> > >> >> So it's true, it >> >> should still be numchips in nand_bbt.c? I just came out this question >> >> when >> >> making v4. :) >> > >> > BTW, I

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