Re: [PATCH] kernfs: kernfs_sop_show_path: don't return 0 after seq_dentry call

On Thu, May 12, 2016 at 12:29:45AM -0500, Serge E. Hallyn wrote: > Our caller expects 0 on success, not >0. > > This fixes a bug in the patch > > cgroup, kernfs: make mountinfo show properly scoped path for cgroup > namespaces > > where /sys does not show up in mountinfo, breaking criu.

Re: [PATCH] kernfs: kernfs_sop_show_path: don't return 0 after seq_dentry call

On Thu, May 12, 2016 at 12:29:45AM -0500, Serge E. Hallyn wrote: > Our caller expects 0 on success, not >0. > > This fixes a bug in the patch > > cgroup, kernfs: make mountinfo show properly scoped path for cgroup > namespaces > > where /sys does not show up in mountinfo, breaking criu.

Re: [RFC 1/3] dt-bindings: drm/mediatek: Add display binding for Mediatek SoC MT2701

On Thu, 2016-05-12 at 19:49 +0800, yt.s...@mediatek.com wrote: > From: YT Shen > > Add device tree binding documentation for the display subsystem in > Mediatek SoC MT2701 > > Signed-off-by: YT Shen > --- >

Re: [RFC 1/3] dt-bindings: drm/mediatek: Add display binding for Mediatek SoC MT2701

On Thu, 2016-05-12 at 19:49 +0800, yt.s...@mediatek.com wrote: > From: YT Shen > > Add device tree binding documentation for the display subsystem in > Mediatek SoC MT2701 > > Signed-off-by: YT Shen > --- > .../bindings/display/mediatek/mediatek,disp.txt|1 + > 1 file changed, 1

Aw: [PATCH 0/6] hv_netvsc: avoid races on mtu change/set channels

Hi, > > MTU change and set channels operations are implemented as netvsc device > re-creation destroying internal structures (struct net_device stays). This > is really unfortunate but there is no support from Hyper-V host to do it > in a different way. Such re-creation is unsurprisingly racy,

Aw: [PATCH 0/6] hv_netvsc: avoid races on mtu change/set channels

Hi, > > MTU change and set channels operations are implemented as netvsc device > re-creation destroying internal structures (struct net_device stays). This > is really unfortunate but there is no support from Hyper-V host to do it > in a different way. Such re-creation is unsurprisingly racy,

Re: [PATCH 3/4] ARM: dts: bcm2835: add the bcm2835-sdram-controller to the dt

Hi, > ker...@martin.sperl.org hat am 12. Mai 2016 um 14:38 geschrieben: > > > From: Martin Sperl > > Add the bcm2835 sdram controller to the device tree. > > Signed-off-by: Martin Sperl > --- > arch/arm/boot/dts/bcm283x.dtsi | 6 ++ > 1

Re: [PATCH 3/4] ARM: dts: bcm2835: add the bcm2835-sdram-controller to the dt

Hi, > ker...@martin.sperl.org hat am 12. Mai 2016 um 14:38 geschrieben: > > > From: Martin Sperl > > Add the bcm2835 sdram controller to the device tree. > > Signed-off-by: Martin Sperl > --- > arch/arm/boot/dts/bcm283x.dtsi | 6 ++ > 1 file changed, 6 insertions(+) > > diff --git

Re: [PATCH v7 2/6] GCC plugin infrastructure

On Wed, 11 May 2016 13:24:30 +0200 Michal Marek wrote: > On 2016-04-22 20:22, Emese Revfy wrote: > > diff --git a/Documentation/dontdiff b/Documentation/dontdiff > > index 8ea834f..5385cba 100644 > > --- a/Documentation/dontdiff > > +++ b/Documentation/dontdiff > > @@ -3,6 +3,7

Re: [PATCH v7 2/6] GCC plugin infrastructure

On Wed, 11 May 2016 13:24:30 +0200 Michal Marek wrote: > On 2016-04-22 20:22, Emese Revfy wrote: > > diff --git a/Documentation/dontdiff b/Documentation/dontdiff > > index 8ea834f..5385cba 100644 > > --- a/Documentation/dontdiff > > +++ b/Documentation/dontdiff > > @@ -3,6 +3,7 @@ > > *.bc > >

[PATCH 2/3] dmaengine: at_xdmac: fix residue corruption

An unexpected value of CUBC can lead to a corrupted residue. A more complex sequence is needed to detect an inaccurate value for NCA or CUBC. Signed-off-by: Ludovic Desroches Fixes: e1f7c9eee707 ("dmaengine: at_xdmac: creation of the atmel eXtended DMA Controller

Re: [RFC6 PATCH v6 00/21] ILP32 for ARM64

On Thu, May 12, 2016 at 05:34:15PM +0300, Yury Norov wrote: > On Thu, May 12, 2016 at 03:20:16PM +0100, Catalin Marinas wrote: > > On Thu, May 12, 2016 at 03:07:35PM +0100, Catalin Marinas wrote: > > > On Thu, May 12, 2016 at 04:44:31PM +0300, Yury Norov wrote: > > > > On Thu, May 12, 2016 at

[PATCH 3/3] dmaengine: at_xdmac: double FIFO flush needed to compute residue

Due to the way CUBC register is updated, a double flush is needed to compute an accurate residue. First flush aim is to get data from the DMA FIFO and second one ensures that we won't report data which are not in memory. Signed-off-by: Ludovic Desroches Fixes:

[PATCH 2/3] dmaengine: at_xdmac: fix residue corruption

An unexpected value of CUBC can lead to a corrupted residue. A more complex sequence is needed to detect an inaccurate value for NCA or CUBC. Signed-off-by: Ludovic Desroches Fixes: e1f7c9eee707 ("dmaengine: at_xdmac: creation of the atmel eXtended DMA Controller driver") Cc:

Re: [RFC6 PATCH v6 00/21] ILP32 for ARM64

On Thu, May 12, 2016 at 05:34:15PM +0300, Yury Norov wrote: > On Thu, May 12, 2016 at 03:20:16PM +0100, Catalin Marinas wrote: > > On Thu, May 12, 2016 at 03:07:35PM +0100, Catalin Marinas wrote: > > > On Thu, May 12, 2016 at 04:44:31PM +0300, Yury Norov wrote: > > > > On Thu, May 12, 2016 at

[PATCH 3/3] dmaengine: at_xdmac: double FIFO flush needed to compute residue

Due to the way CUBC register is updated, a double flush is needed to compute an accurate residue. First flush aim is to get data from the DMA FIFO and second one ensures that we won't report data which are not in memory. Signed-off-by: Ludovic Desroches Fixes: e1f7c9eee707 ("dmaengine: at_xdmac:

[PATCH 1/3] dmaengine: at_xdmac: align descriptors on 64 bits

Having descriptors aligned on 64 bits allows update CNDA and CUBC in an atomic way. Signed-off-by: Ludovic Desroches Fixes: e1f7c9eee707 ("dmaengine: at_xdmac: creation of the atmel eXtended DMA Controller driver") Cc: sta...@vger.kernel.org #v4.1 and later ---

[PATCH 1/3] dmaengine: at_xdmac: align descriptors on 64 bits

Having descriptors aligned on 64 bits allows update CNDA and CUBC in an atomic way. Signed-off-by: Ludovic Desroches Fixes: e1f7c9eee707 ("dmaengine: at_xdmac: creation of the atmel eXtended DMA Controller driver") Cc: sta...@vger.kernel.org #v4.1 and later --- drivers/dma/at_xdmac.c | 4 ++--

Re: [PATCH 0/4] add minimal bcm2835-sdram driver

Hi Martin, > ker...@martin.sperl.org hat am 12. Mai 2016 um 14:38 geschrieben: > > > From: Martin Sperl > > As the sdram clock is a critical clock to the system > the minimal bcm2835-sdram driver claims (and enables) > this clock and also exposes the corresponding

Re: [PATCH 0/4] add minimal bcm2835-sdram driver

Hi Martin, > ker...@martin.sperl.org hat am 12. Mai 2016 um 14:38 geschrieben: > > > From: Martin Sperl > > As the sdram clock is a critical clock to the system > the minimal bcm2835-sdram driver claims (and enables) > this clock and also exposes the corresponding sdram > registers via

Re: [PATCH v12 06/10] arm64: Treat all entry code as non-kprobe-able

Hi David, Pratyush On 27/04/16 19:53, David Long wrote: > From: Pratyush Anand > > Entry symbols are not kprobe safe. So blacklist them for kprobing. > > Signed-off-by: Pratyush Anand > diff --git a/arch/arm64/kernel/kprobes.c

Re: [PATCH v12 06/10] arm64: Treat all entry code as non-kprobe-able

Hi David, Pratyush On 27/04/16 19:53, David Long wrote: > From: Pratyush Anand > > Entry symbols are not kprobe safe. So blacklist them for kprobing. > > Signed-off-by: Pratyush Anand > diff --git a/arch/arm64/kernel/kprobes.c b/arch/arm64/kernel/kprobes.c > index dfa1b1f..6a1292b 100644 >

[PATCH 1/2] pinctrl: stm32: fix warning

From: Patrice Chotard fix compilation warning : drivers/pinctrl/stm32/pinctrl-stm32.c:823:7: warning: too many arguments for format [-Wformat-extra-args] speeds[speed], "speed"); Signed-off-by: Patrice Chotard ---

[PATCH 1/2] pinctrl: stm32: fix warning

From: Patrice Chotard fix compilation warning : drivers/pinctrl/stm32/pinctrl-stm32.c:823:7: warning: too many arguments for format [-Wformat-extra-args] speeds[speed], "speed"); Signed-off-by: Patrice Chotard --- drivers/pinctrl/stm32/pinctrl-stm32.c | 8 1 file changed,

Re: [PATCH] pinctrl: stm32: Implement .pin_config_dbg_show()

On 05/12/2016 03:40 PM, Linus Walleij wrote: On Wed, May 11, 2016 at 3:40 PM, Patrice Chotard wrote: On 05/10/2016 01:50 PM, Linus Walleij wrote: Sorry i didn't pay attention, but there is a compilation warning in this patch.

Re: [PATCH] pinctrl: stm32: Implement .pin_config_dbg_show()

On 05/12/2016 03:40 PM, Linus Walleij wrote: On Wed, May 11, 2016 at 3:40 PM, Patrice Chotard wrote: On 05/10/2016 01:50 PM, Linus Walleij wrote: Sorry i didn't pay attention, but there is a compilation warning in this patch. drivers/pinctrl/stm32/pinctrl-stm32.c:823:7: warning: too many

[PATCH 2/2] pinctrl: stm32: factorize stm32_pconf_input/output_get()

From: Patrice Chotard As these 2 functions code are 95% similar, factorize them. Signed-off-by: Patrice Chotard --- drivers/pinctrl/stm32/pinctrl-stm32.c | 31 ++- 1 file changed, 10 insertions(+), 21 deletions(-)

[PATCH 2/2] pinctrl: stm32: factorize stm32_pconf_input/output_get()

From: Patrice Chotard As these 2 functions code are 95% similar, factorize them. Signed-off-by: Patrice Chotard --- drivers/pinctrl/stm32/pinctrl-stm32.c | 31 ++- 1 file changed, 10 insertions(+), 21 deletions(-) diff --git a/drivers/pinctrl/stm32/pinctrl-stm32.c

[PATCH 0/2] pinctrl: stm32: .pin_config_dbg_show fixes

From: Patrice Chotard Patrice Chotard (2): pinctrl: stm32: fix warning pinctrl: stm32: factorize stm32_pconf_input/output_get() drivers/pinctrl/stm32/pinctrl-stm32.c | 39 +-- 1 file changed, 14 insertions(+), 25 deletions(-) --

[PATCH 0/2] pinctrl: stm32: .pin_config_dbg_show fixes

From: Patrice Chotard Patrice Chotard (2): pinctrl: stm32: fix warning pinctrl: stm32: factorize stm32_pconf_input/output_get() drivers/pinctrl/stm32/pinctrl-stm32.c | 39 +-- 1 file changed, 14 insertions(+), 25 deletions(-) -- 1.9.1

Re: next: Crashes in x86 images due to 'locking/rwsem, x86: Clean up ____down_write()'

On Thu, May 12, 2016 at 03:51:31PM +0200, Borislav Petkov wrote: > On Thu, May 12, 2016 at 06:34:29AM -0700, Guenter Roeck wrote: > > Borislav, > > > > your patch 'locking/rwsem, x86: Clean up down_write()' causes various > > crashes in x86 qemu tests. > > Thanks for the report, let me take

Re: next: Crashes in x86 images due to 'locking/rwsem, x86: Clean up ____down_write()'

On Thu, May 12, 2016 at 03:51:31PM +0200, Borislav Petkov wrote: > On Thu, May 12, 2016 at 06:34:29AM -0700, Guenter Roeck wrote: > > Borislav, > > > > your patch 'locking/rwsem, x86: Clean up down_write()' causes various > > crashes in x86 qemu tests. > > Thanks for the report, let me take

Re: [PATCH v3 1/2] drm/fb-cma-helper: Add function drm_fb_cma_create_with_funcs()

Den 12.05.2016 15:47, skrev Laurent Pinchart: Hi Noralf, Thank you for the patch. On Thursday 12 May 2016 14:53:25 Noralf Trønnes wrote: Add drm_fb_cma_create_with_funcs() for drivers that need to set the dirty() callback. Cc: laurent.pinch...@ideasonboard.com Signed-off-by: Noralf Trønnes

Re: [PATCH v3 1/2] drm/fb-cma-helper: Add function drm_fb_cma_create_with_funcs()

Den 12.05.2016 15:47, skrev Laurent Pinchart: Hi Noralf, Thank you for the patch. On Thursday 12 May 2016 14:53:25 Noralf Trønnes wrote: Add drm_fb_cma_create_with_funcs() for drivers that need to set the dirty() callback. Cc: laurent.pinch...@ideasonboard.com Signed-off-by: Noralf Trønnes

Re: [RFC6 PATCH v6 00/21] ILP32 for ARM64

On Thu, May 12, 2016 at 03:20:16PM +0100, Catalin Marinas wrote: > On Thu, May 12, 2016 at 03:07:35PM +0100, Catalin Marinas wrote: > > On Thu, May 12, 2016 at 04:44:31PM +0300, Yury Norov wrote: > > > On Thu, May 12, 2016 at 02:35:34PM +0100, Catalin Marinas wrote: > > > > On Thu, May 12, 2016 at

Re: [RFC6 PATCH v6 00/21] ILP32 for ARM64

On Thu, May 12, 2016 at 03:20:16PM +0100, Catalin Marinas wrote: > On Thu, May 12, 2016 at 03:07:35PM +0100, Catalin Marinas wrote: > > On Thu, May 12, 2016 at 04:44:31PM +0300, Yury Norov wrote: > > > On Thu, May 12, 2016 at 02:35:34PM +0100, Catalin Marinas wrote: > > > > On Thu, May 12, 2016 at

Re: [PATCH] kvm-pr: manage illegal instructions

On 12/05/2016 11:27, Alexander Graf wrote: > On 05/12/2016 11:10 AM, Laurent Vivier wrote: >> >> On 11/05/2016 13:49, Alexander Graf wrote: >>> On 05/11/2016 01:14 PM, Laurent Vivier wrote: On 11/05/2016 12:35, Alexander Graf wrote: > On 03/15/2016 09:18 PM, Laurent Vivier wrote: >>

Re: [PATCH] kvm-pr: manage illegal instructions

On 12/05/2016 11:27, Alexander Graf wrote: > On 05/12/2016 11:10 AM, Laurent Vivier wrote: >> >> On 11/05/2016 13:49, Alexander Graf wrote: >>> On 05/11/2016 01:14 PM, Laurent Vivier wrote: On 11/05/2016 12:35, Alexander Graf wrote: > On 03/15/2016 09:18 PM, Laurent Vivier wrote: >>

Re: [PATCH] tools lib traceevent: Do not reassign parg after collapse_tree()

Em Thu, May 12, 2016 at 09:57:13PM +0900, Namhyung Kim escreveu: > Hi Steve, > > On Thu, May 12, 2016 at 4:09 AM, Steven Rostedt wrote: > > > > At the end of process_filter(), collapse_tree() was changed to update the > > parg parameter, but the reassignment after the call

Re: [PATCH] tools lib traceevent: Do not reassign parg after collapse_tree()

Em Thu, May 12, 2016 at 09:57:13PM +0900, Namhyung Kim escreveu: > Hi Steve, > > On Thu, May 12, 2016 at 4:09 AM, Steven Rostedt wrote: > > > > At the end of process_filter(), collapse_tree() was changed to update the > > parg parameter, but the reassignment after the call wasn't removed. > >

[PATCH] arm64: Implement optimised IP checksum helpers

AArch64 is capable of 128-bit memory accesses without alignment restrictions, which makes it both possible and highly practical to slurp up a typical 20-byte IP header in just 2 loads. Implement our own version of ip_fast_checksum() to take advantage of that, resulting in considerably fewer

[PATCH] arm64: Implement optimised IP checksum helpers

AArch64 is capable of 128-bit memory accesses without alignment restrictions, which makes it both possible and highly practical to slurp up a typical 20-byte IP header in just 2 loads. Implement our own version of ip_fast_checksum() to take advantage of that, resulting in considerably fewer

URGENT RESPONSE NEEDED, PLEASE REPLY....

Dear Friend, Pardon me for not having the pleasure of knowing your mindset before making you this offer and it is utterly confidential and genuine by virtue of its nature I write to solicit your assistance in a funds transfer deal involving £15.2M.This fund has been stashed out of the excess

URGENT RESPONSE NEEDED, PLEASE REPLY....

Dear Friend, Pardon me for not having the pleasure of knowing your mindset before making you this offer and it is utterly confidential and genuine by virtue of its nature I write to solicit your assistance in a funds transfer deal involving £15.2M.This fund has been stashed out of the excess

Re: [RFC6 PATCH v6 00/21] ILP32 for ARM64

On Thu, May 12, 2016 at 03:07:35PM +0100, Catalin Marinas wrote: > On Thu, May 12, 2016 at 04:44:31PM +0300, Yury Norov wrote: > > On Thu, May 12, 2016 at 02:35:34PM +0100, Catalin Marinas wrote: > > > On Thu, May 12, 2016 at 03:20:00AM +0300, Yury Norov wrote: > > > > I debugged preadv02 and

Re: [RFC6 PATCH v6 00/21] ILP32 for ARM64

On Thu, May 12, 2016 at 03:07:35PM +0100, Catalin Marinas wrote: > On Thu, May 12, 2016 at 04:44:31PM +0300, Yury Norov wrote: > > On Thu, May 12, 2016 at 02:35:34PM +0100, Catalin Marinas wrote: > > > On Thu, May 12, 2016 at 03:20:00AM +0300, Yury Norov wrote: > > > > I debugged preadv02 and

Re: [PATCH] deb-pkg: add the shared header file for arm64

On 2016-05-12 11:03, Huang Shijie wrote: > The arch/arm/include/asm/opcodes.h is also used by the arm64. > This patch copies it to the arm64 deb package. > > Signed-off-by: Huang Shijie > --- > scripts/package/builddeb | 6 ++ > 1 file changed, 6 insertions(+) Hi

Re: [PATCH] deb-pkg: add the shared header file for arm64

On 2016-05-12 11:03, Huang Shijie wrote: > The arch/arm/include/asm/opcodes.h is also used by the arm64. > This patch copies it to the arm64 deb package. > > Signed-off-by: Huang Shijie > --- > scripts/package/builddeb | 6 ++ > 1 file changed, 6 insertions(+) Hi Huang, this is fixed

Re: [RFC6 PATCH v6 00/21] ILP32 for ARM64

On Thu, May 12, 2016 at 03:07:35PM +0100, Catalin Marinas wrote: > On Thu, May 12, 2016 at 04:44:31PM +0300, Yury Norov wrote: > > On Thu, May 12, 2016 at 02:35:34PM +0100, Catalin Marinas wrote: > > > On Thu, May 12, 2016 at 03:20:00AM +0300, Yury Norov wrote: > > > > I debugged preadv02 and

Re: [RFC6 PATCH v6 00/21] ILP32 for ARM64

On Thu, May 12, 2016 at 03:07:35PM +0100, Catalin Marinas wrote: > On Thu, May 12, 2016 at 04:44:31PM +0300, Yury Norov wrote: > > On Thu, May 12, 2016 at 02:35:34PM +0100, Catalin Marinas wrote: > > > On Thu, May 12, 2016 at 03:20:00AM +0300, Yury Norov wrote: > > > > I debugged preadv02 and

[PATCH 2/2] HID: multitouch: enable the Surface 3 Type Cover to report multitouch data

There is no reasons to filter out keyboard and consumer control collections in hid-multitouch. With the previous hid-input fix, there is now a full support of the Type Cover and we can remove all specific bits from hid-core and hid-microsoft. hid-multitouch will automatically set

[PATCH 2/2] HID: multitouch: enable the Surface 3 Type Cover to report multitouch data

There is no reasons to filter out keyboard and consumer control collections in hid-multitouch. With the previous hid-input fix, there is now a full support of the Type Cover and we can remove all specific bits from hid-core and hid-microsoft. hid-multitouch will automatically set

[PATCH 1/2] HID: input: rework HID_QUIRK_MULTI_INPUT

The purpose of HID_QUIRK_MULTI_INPUT is to have an input device per report id. This is useful when the HID device presents several HID collections of different device types. The current implementation of hid-input creates one input node per id per type (input or output). This is problematic for

[PATCH 1/2] HID: input: rework HID_QUIRK_MULTI_INPUT

The purpose of HID_QUIRK_MULTI_INPUT is to have an input device per report id. This is useful when the HID device presents several HID collections of different device types. The current implementation of hid-input creates one input node per id per type (input or output). This is problematic for

Re: [PATCH v2] sched/completion: convert completions to use simple wait queues

On 04/28/2016 02:57 PM, Daniel Wagner wrote: > As one can see above in the swait_stat output, the fork() path is > using completion. A histogram of a fork bomp (1000 forks) benchmark > shows a slight performance drop by 4%. > > [wagi@handman completion-test-5 (master)]$ cat forky-4.6.0-rc4.txt |

Re: [PATCH v2] sched/completion: convert completions to use simple wait queues

On 04/28/2016 02:57 PM, Daniel Wagner wrote: > As one can see above in the swait_stat output, the fork() path is > using completion. A histogram of a fork bomp (1000 forks) benchmark > shows a slight performance drop by 4%. > > [wagi@handman completion-test-5 (master)]$ cat forky-4.6.0-rc4.txt |

Re: [RFC6 PATCH v6 00/21] ILP32 for ARM64

On Thu, May 12, 2016 at 04:44:31PM +0300, Yury Norov wrote: > On Thu, May 12, 2016 at 02:35:34PM +0100, Catalin Marinas wrote: > > On Thu, May 12, 2016 at 03:20:00AM +0300, Yury Norov wrote: > > > I debugged preadv02 and pwritev02 failures and found very weird bug. > > > Test passes {iovec_base =

Re: [RFC6 PATCH v6 00/21] ILP32 for ARM64

On Thu, May 12, 2016 at 04:44:31PM +0300, Yury Norov wrote: > On Thu, May 12, 2016 at 02:35:34PM +0100, Catalin Marinas wrote: > > On Thu, May 12, 2016 at 03:20:00AM +0300, Yury Norov wrote: > > > I debugged preadv02 and pwritev02 failures and found very weird bug. > > > Test passes {iovec_base =

[PATCH] ACPI / scan: force creation of platform device for the Surface tablets

As mentioned in drivers/platform/x86/surfacepro3_button.c, the various Microsoft Surface tablets do not follow the ACPI SOC buttons specification. They present an I2C device like this: Device (WBUT) { Method (_HID, 0, NotSerialized) // _HID: Hardware ID { Return

[PATCH] ACPI / scan: force creation of platform device for the Surface tablets

As mentioned in drivers/platform/x86/surfacepro3_button.c, the various Microsoft Surface tablets do not follow the ACPI SOC buttons specification. They present an I2C device like this: Device (WBUT) { Method (_HID, 0, NotSerialized) // _HID: Hardware ID { Return

Re: [PATCH V2 1/1] perf/core: don't find side-band event from all pmus

On Thu, May 12, 2016 at 01:30:36PM +, Liang, Kan wrote: > > > > --- > > Subject: perf/core: don't find side-band event from all pmus > > From: Kan Liang > > Date: Wed, 23 Mar 2016 11:24:37 -0700 > > > Hi Peter, > > Is there something wrong with the patch? > The last

Re: [PATCH V2 1/1] perf/core: don't find side-band event from all pmus

On Thu, May 12, 2016 at 01:30:36PM +, Liang, Kan wrote: > > > > --- > > Subject: perf/core: don't find side-band event from all pmus > > From: Kan Liang > > Date: Wed, 23 Mar 2016 11:24:37 -0700 > > > Hi Peter, > > Is there something wrong with the patch? > The last time I saw this patch

Re: [PATCH v2] tpm: Fix suspend regression

On Thu, May 12, 2016 at 04:49:52PM +0300, Jarkko Sakkinen wrote: > On Wed, May 11, 2016 at 11:28:27AM -0400, Stefan Berger wrote: > > Fix the suspend regression due to the wrong way of retrieving the > > chip structure. The suspend functions are attached to the hardware > > device, not the chip

Re: [PATCH v2] tpm: Fix suspend regression

On Thu, May 12, 2016 at 04:49:52PM +0300, Jarkko Sakkinen wrote: > On Wed, May 11, 2016 at 11:28:27AM -0400, Stefan Berger wrote: > > Fix the suspend regression due to the wrong way of retrieving the > > chip structure. The suspend functions are attached to the hardware > > device, not the chip

Re: [PATCH 03/11] locking, rwsem: introduce basis for down_write_killable

On Thu, May 12, 2016 at 02:19:07PM +0200, Michal Hocko wrote: > On Thu 12-05-16 14:12:04, Peter Zijlstra wrote: > > On Wed, May 11, 2016 at 08:03:46PM +0200, Michal Hocko wrote: > > > I still cannot say I would understand why the pending > > > RWSEM_WAITING_BIAS matters but I would probably need

Re: [PATCH 03/11] locking, rwsem: introduce basis for down_write_killable

On Thu, May 12, 2016 at 02:19:07PM +0200, Michal Hocko wrote: > On Thu 12-05-16 14:12:04, Peter Zijlstra wrote: > > On Wed, May 11, 2016 at 08:03:46PM +0200, Michal Hocko wrote: > > > I still cannot say I would understand why the pending > > > RWSEM_WAITING_BIAS matters but I would probably need

[PATCH ] pinctrl: tegra: Get rid of parked_reg

Remove the use of parked_reg and use parked_bit for to know whether field is supported or not. This is fix for the patch commit 1d18a3f0f0809f6c71f1f6e9e268ee904ce0b588 "pinctrl: tegra: avoid parked_reg and parked_bank Signed-off-by: Laxman Dewangan ---

[PATCH ] pinctrl: tegra: Get rid of parked_reg

Remove the use of parked_reg and use parked_bit for to know whether field is supported or not. This is fix for the patch commit 1d18a3f0f0809f6c71f1f6e9e268ee904ce0b588 "pinctrl: tegra: avoid parked_reg and parked_bank Signed-off-by: Laxman Dewangan --- drivers/pinctrl/tegra/pinctrl-tegra20.c

Re: [Question] Missing data after DMA read transfer - mm issue with transparent huge page?

On Thu, May 12, 2016 at 03:30:24PM +0200, Nicolas Morey-Chaisemartin wrote: > Le 05/12/2016 à 11:36 AM, Jerome Glisse a écrit : > > On Thu, May 12, 2016 at 08:07:59AM +0200, Nicolas Morey-Chaisemartin wrote: > >> > >> Le 05/11/2016 à 04:51 PM, Jerome Glisse a écrit : > >>> On Wed, May 11, 2016 at

Re: [Question] Missing data after DMA read transfer - mm issue with transparent huge page?

On Thu, May 12, 2016 at 03:30:24PM +0200, Nicolas Morey-Chaisemartin wrote: > Le 05/12/2016 à 11:36 AM, Jerome Glisse a écrit : > > On Thu, May 12, 2016 at 08:07:59AM +0200, Nicolas Morey-Chaisemartin wrote: > >> > >> Le 05/11/2016 à 04:51 PM, Jerome Glisse a écrit : > >>> On Wed, May 11, 2016 at

Re: next: Crashes in x86 images due to 'locking/rwsem, x86: Clean up ____down_write()'

On Thu, May 12, 2016 at 06:34:29AM -0700, Guenter Roeck wrote: > Borislav, > > your patch 'locking/rwsem, x86: Clean up down_write()' causes various > crashes in x86 qemu tests. Thanks for the report, let me take a look. @Ingo: can you please back this one out of the lineup for the merge

Re: next: Crashes in x86 images due to 'locking/rwsem, x86: Clean up ____down_write()'

On Thu, May 12, 2016 at 06:34:29AM -0700, Guenter Roeck wrote: > Borislav, > > your patch 'locking/rwsem, x86: Clean up down_write()' causes various > crashes in x86 qemu tests. Thanks for the report, let me take a look. @Ingo: can you please back this one out of the lineup for the merge

[PATCH v4] platform:x86: Add PMC Driver for Intel Core SOC

This patch adds the Power Management Controller driver as a pci driver for Intel Core SOC architecture. This driver can utilize debugging capabilities and supported features as exposed by the Power Management Controller. Please refer to the below specification for more details on PMC features.

[PATCH v4] platform:x86: Add PMC Driver for Intel Core SOC

This patch adds the Power Management Controller driver as a pci driver for Intel Core SOC architecture. This driver can utilize debugging capabilities and supported features as exposed by the Power Management Controller. Please refer to the below specification for more details on PMC features.

Re: [PATCH v2] tpm: Fix suspend regression

On Wed, May 11, 2016 at 11:28:27AM -0400, Stefan Berger wrote: > Fix the suspend regression due to the wrong way of retrieving the > chip structure. The suspend functions are attached to the hardware > device, not the chip and thus must rely on drvdata. > > Fixes: e89f8b1ade9cc1a ("tpm: Remove

Re: [PATCH v2] tpm: Fix suspend regression

On Wed, May 11, 2016 at 11:28:27AM -0400, Stefan Berger wrote: > Fix the suspend regression due to the wrong way of retrieving the > chip structure. The suspend functions are attached to the hardware > device, not the chip and thus must rely on drvdata. > > Fixes: e89f8b1ade9cc1a ("tpm: Remove

Re: [PATCH v3 1/2] drm/fb-cma-helper: Add function drm_fb_cma_create_with_funcs()

Hi Noralf, Thank you for the patch. On Thursday 12 May 2016 14:53:25 Noralf Trønnes wrote: > Add drm_fb_cma_create_with_funcs() for drivers that need to set the > dirty() callback. > > Cc: laurent.pinch...@ideasonboard.com > Signed-off-by: Noralf Trønnes > --- > > Changes

Re: [PATCH v3 1/2] drm/fb-cma-helper: Add function drm_fb_cma_create_with_funcs()

Hi Noralf, Thank you for the patch. On Thursday 12 May 2016 14:53:25 Noralf Trønnes wrote: > Add drm_fb_cma_create_with_funcs() for drivers that need to set the > dirty() callback. > > Cc: laurent.pinch...@ideasonboard.com > Signed-off-by: Noralf Trønnes > --- > > Changes since v1: > - Expand

Re: [RFC6 PATCH v6 00/21] ILP32 for ARM64

On Thu, May 12, 2016 at 02:35:34PM +0100, Catalin Marinas wrote: > On Thu, May 12, 2016 at 03:20:00AM +0300, Yury Norov wrote: > > I debugged preadv02 and pwritev02 failures and found very weird bug. > > Test passes {iovec_base = 0x, iovec_len = 64} as one element > > of vector, and kernel

Re: [RFC6 PATCH v6 00/21] ILP32 for ARM64

On Thu, May 12, 2016 at 02:35:34PM +0100, Catalin Marinas wrote: > On Thu, May 12, 2016 at 03:20:00AM +0300, Yury Norov wrote: > > I debugged preadv02 and pwritev02 failures and found very weird bug. > > Test passes {iovec_base = 0x, iovec_len = 64} as one element > > of vector, and kernel

Re: [RFC 05/13] mm, page_alloc: make THP-specific decisions more generic

On Tue 10-05-16 09:35:55, Vlastimil Babka wrote: > Since THP allocations during page faults can be costly, extra decisions are > employed for them to avoid excessive reclaim and compaction, if the initial > compaction doesn't look promising. The detection has never been perfect as > there is no

Re: [RFC 05/13] mm, page_alloc: make THP-specific decisions more generic

On Tue 10-05-16 09:35:55, Vlastimil Babka wrote: > Since THP allocations during page faults can be costly, extra decisions are > employed for them to avoid excessive reclaim and compaction, if the initial > compaction doesn't look promising. The detection has never been perfect as > there is no

Re: [PATCH] pinctrl: stm32: Implement .pin_config_dbg_show()

On Wed, May 11, 2016 at 3:40 PM, Patrice Chotard wrote: > On 05/10/2016 01:50 PM, Linus Walleij wrote: > Sorry i didn't pay attention, but there is a compilation warning in this > patch. > > drivers/pinctrl/stm32/pinctrl-stm32.c:823:7: warning: too many arguments for >

Re: [PATCH] pinctrl: stm32: Implement .pin_config_dbg_show()

On Wed, May 11, 2016 at 3:40 PM, Patrice Chotard wrote: > On 05/10/2016 01:50 PM, Linus Walleij wrote: > Sorry i didn't pay attention, but there is a compilation warning in this > patch. > > drivers/pinctrl/stm32/pinctrl-stm32.c:823:7: warning: too many arguments for > format

Re: linux-next: build failure after merge of the pinctrl tree

Laxman, this must be due to one of the two top commits for tegra: commit 1d18a3f0f0809f6c71f1f6e9e268ee904ce0b588 "pinctrl: tegra: avoid parked_reg and parked_bank" commit b22ef2a0979f2b91cfeeabb086e4d665183a93a1 "pinctrl: tegra: Correctly check the supported configuration" Is it something you

Re: linux-next: build failure after merge of the pinctrl tree

Laxman, this must be due to one of the two top commits for tegra: commit 1d18a3f0f0809f6c71f1f6e9e268ee904ce0b588 "pinctrl: tegra: avoid parked_reg and parked_bank" commit b22ef2a0979f2b91cfeeabb086e4d665183a93a1 "pinctrl: tegra: Correctly check the supported configuration" Is it something you

Re: [PATCH 20/25] arm64:ilp32: add sys_ilp32.c and a separate table (in entry.S) to use it

On Thu, May 12, 2016 at 03:06:39PM +0200, Arnd Bergmann wrote: > On Thursday 12 May 2016 20:49:24 Zhangjian wrote: > > Hi, > > > > On 2016/5/12 17:21, Arnd Bergmann wrote: > > > On Thursday 12 May 2016 10:17:58 Catalin Marinas wrote: > > >> On Wed, May 11, 2016 at 09:30:07PM +0200, Arnd Bergmann

Re: [PATCH 20/25] arm64:ilp32: add sys_ilp32.c and a separate table (in entry.S) to use it

On Thu, May 12, 2016 at 03:06:39PM +0200, Arnd Bergmann wrote: > On Thursday 12 May 2016 20:49:24 Zhangjian wrote: > > Hi, > > > > On 2016/5/12 17:21, Arnd Bergmann wrote: > > > On Thursday 12 May 2016 10:17:58 Catalin Marinas wrote: > > >> On Wed, May 11, 2016 at 09:30:07PM +0200, Arnd Bergmann

Re: [RFC6 PATCH v6 00/21] ILP32 for ARM64

On Thu, May 12, 2016 at 03:20:00AM +0300, Yury Norov wrote: > I debugged preadv02 and pwritev02 failures and found very weird bug. > Test passes {iovec_base = 0x, iovec_len = 64} as one element > of vector, and kernel reports successful read/write. > > There are 2 problems: > 1. How

Re: [RFC6 PATCH v6 00/21] ILP32 for ARM64

On Thu, May 12, 2016 at 03:20:00AM +0300, Yury Norov wrote: > I debugged preadv02 and pwritev02 failures and found very weird bug. > Test passes {iovec_base = 0x, iovec_len = 64} as one element > of vector, and kernel reports successful read/write. > > There are 2 problems: > 1. How

Re: linux-next: manual merge of the gpio tree with the mips tree

On Thu, May 12, 2016 at 6:17 AM, Stephen Rothwell wrote: > I fixed it up (see below) and can carry the fix as necessary. This > is now fixed as far as linux-next is concerned, but any non trivial > conflicts should be mentioned to your upstream maintainer when your tree >

Re: linux-next: manual merge of the gpio tree with the mips tree

On Thu, May 12, 2016 at 6:17 AM, Stephen Rothwell wrote: > I fixed it up (see below) and can carry the fix as necessary. This > is now fixed as far as linux-next is concerned, but any non trivial > conflicts should be mentioned to your upstream maintainer when your tree > is submitted for

next: Crashes in x86 images due to 'locking/rwsem, x86: Clean up ____down_write()'

Borislav, your patch 'locking/rwsem, x86: Clean up down_write()' causes various crashes in x86 qemu tests. BUG: unable to handle kernel paging request at 8015 IP: [] down_write+0x23/0x30 Call Trace: [] crypto_larval_kill+0x15/0x70 [] crypto_wait_for_test+0x46/0x70 []

next: Crashes in x86 images due to 'locking/rwsem, x86: Clean up ____down_write()'

Borislav, your patch 'locking/rwsem, x86: Clean up down_write()' causes various crashes in x86 qemu tests. BUG: unable to handle kernel paging request at 8015 IP: [] down_write+0x23/0x30 Call Trace: [] crypto_larval_kill+0x15/0x70 [] crypto_wait_for_test+0x46/0x70 []

RE: [PATCH 1/1] perf/core: fix implicitly enable dynamic interrupt throttle

> > > Hmm, would it not be nicer to simply reject the write instead of silently > ignoring it? > Yes, I agree. Thanks, Kan > --- > kernel/events/core.c | 7 +++ > 1 file changed, 7 insertions(+) > > diff --git a/kernel/events/core.c b/kernel/events/core.c index >

RE: [PATCH 1/1] perf/core: fix implicitly enable dynamic interrupt throttle

> > > Hmm, would it not be nicer to simply reject the write instead of silently > ignoring it? > Yes, I agree. Thanks, Kan > --- > kernel/events/core.c | 7 +++ > 1 file changed, 7 insertions(+) > > diff --git a/kernel/events/core.c b/kernel/events/core.c index >

Re: [Question] Missing data after DMA read transfer - mm issue with transparent huge page?

Le 05/12/2016 à 11:36 AM, Jerome Glisse a écrit : > On Thu, May 12, 2016 at 08:07:59AM +0200, Nicolas Morey-Chaisemartin wrote: >> >> Le 05/11/2016 à 04:51 PM, Jerome Glisse a écrit : >>> On Wed, May 11, 2016 at 01:15:54PM +0200, Nicolas Morey Chaisemartin wrote: Le 05/10/2016 à 12:01 PM,

Re: usb: dwc2: regression on MyBook Live Duo / Canyonlands since 4.3.0-rc4

On Thursday, May 12, 2016 01:55:44 PM Arnd Bergmann wrote: > On Thursday 12 May 2016 11:58:18 Christian Lamparter wrote: > > > > > Detecting the endianess of the > > > > > device is probably the best future-proof solution, but it's also > > > > > considerably more work to do in the driver, and

RE: [PATCH V2 1/1] perf/core: don't find side-band event from all pmus

> --- > Subject: perf/core: don't find side-band event from all pmus > From: Kan Liang > Date: Wed, 23 Mar 2016 11:24:37 -0700 > Hi Peter, Is there something wrong with the patch? The last time I saw this patch was in your personal tree (kernel/git/peterz/queue.git). But

Re: [Question] Missing data after DMA read transfer - mm issue with transparent huge page?

Le 05/12/2016 à 11:36 AM, Jerome Glisse a écrit : > On Thu, May 12, 2016 at 08:07:59AM +0200, Nicolas Morey-Chaisemartin wrote: >> >> Le 05/11/2016 à 04:51 PM, Jerome Glisse a écrit : >>> On Wed, May 11, 2016 at 01:15:54PM +0200, Nicolas Morey Chaisemartin wrote: Le 05/10/2016 à 12:01 PM,

<    4   5   6   7   8   9   10   11   12   13   >