[PATCH] perf report: Fix broken arrow at row 0 in annotate view

When the jump instruction is displayed at the row 0 in annotate view, the arrow is broken. An example: 16.86 │ ┌──je 82 0.01 │ movsd (%rsp),%xmm0 │ movsd 0x8(%rsp),%xmm4 │ movsd 0x8(%rsp),%xmm1 │ movsd (%rsp),%xmm3 │ divsd

[PATCH] perf report: Fix broken arrow at row 0 in annotate view

When the jump instruction is displayed at the row 0 in annotate view, the arrow is broken. An example: 16.86 │ ┌──je 82 0.01 │ movsd (%rsp),%xmm0 │ movsd 0x8(%rsp),%xmm4 │ movsd 0x8(%rsp),%xmm1 │ movsd (%rsp),%xmm3 │ divsd

Re: [PATCH v2] refcount: Create unchecked atomic_t implementation

On Wed, Jun 07, 2017 at 07:58:31PM -0700, Kees Cook wrote: > Many subsystems will not use refcount_t unless there is a way to build the > kernel so that there is no regression in speed compared to atomic_t. This > adds CONFIG_REFCOUNT_FULL to enable the full refcount_t implementation > which has

Re: [PATCH v2] refcount: Create unchecked atomic_t implementation

On Wed, Jun 07, 2017 at 07:58:31PM -0700, Kees Cook wrote: > Many subsystems will not use refcount_t unless there is a way to build the > kernel so that there is no regression in speed compared to atomic_t. This > adds CONFIG_REFCOUNT_FULL to enable the full refcount_t implementation > which has

Re: [PATCH] Fix loop device flush before configure v2

On 06/08/2017 01:06 PM, Mike Galbraith wrote: > On Thu, 2017-06-08 at 10:17 +0800, James Wang wrote: >> This condition check was exist at before commit b5dd2f6047ca ("block: loop: >> improve performance via blk-mq") When add MQ support to loop device, it be >> removed because the member of

Re: [PATCH] Fix loop device flush before configure v2

On 06/08/2017 01:06 PM, Mike Galbraith wrote: > On Thu, 2017-06-08 at 10:17 +0800, James Wang wrote: >> This condition check was exist at before commit b5dd2f6047ca ("block: loop: >> improve performance via blk-mq") When add MQ support to loop device, it be >> removed because the member of

Re: [PATCH v6 25/34] swiotlb: Add warnings for use of bounce buffers with SME

Hi Tom, [auto build test ERROR on linus/master] [also build test ERROR on v4.12-rc4 next-20170607] [cannot apply to tip/x86/core] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Tom-Lendacky/x86

Re: [PATCH v6 25/34] swiotlb: Add warnings for use of bounce buffers with SME

Hi Tom, [auto build test ERROR on linus/master] [also build test ERROR on v4.12-rc4 next-20170607] [cannot apply to tip/x86/core] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Tom-Lendacky/x86

RE: [PATCH V2 2/3] watchdog: uniphier: add UniPhier watchdog driver

Hello Yamada-san, > > + > > +#include > > +#include > > +#include > > +#include > > +#include > > +#include > > +#include > > I think you should have added on the top > to keep the includes alphabetically sorted. Sorry, I will fix in v3 patch. -- Best Regards, Keiji Hayashibara

RE: [PATCH V2 2/3] watchdog: uniphier: add UniPhier watchdog driver

Hello Yamada-san, > > + > > +#include > > +#include > > +#include > > +#include > > +#include > > +#include > > +#include > > I think you should have added on the top > to keep the includes alphabetically sorted. Sorry, I will fix in v3 patch. -- Best Regards, Keiji Hayashibara

[PATCH v5 2/6] dt-bindings: qcom: Add ipq8074 bindings

Acked-by: Rob Herring Signed-off-by: Varadarajan Narayanan --- Documentation/devicetree/bindings/arm/qcom.txt | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Documentation/devicetree/bindings/arm/qcom.txt

[PATCH v5 2/6] dt-bindings: qcom: Add ipq8074 bindings

Acked-by: Rob Herring Signed-off-by: Varadarajan Narayanan --- Documentation/devicetree/bindings/arm/qcom.txt | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Documentation/devicetree/bindings/arm/qcom.txt b/Documentation/devicetree/bindings/arm/qcom.txt index 028d16e..0ed4d39 100644 ---

[PATCH v5 5/6] arm64: dts: Add ipq8074 SoC and HK01 board support

Add initial device tree support for the Qualcomm IPQ8074 SoC and HK01 evaluation board. Signed-off-by: Manoharan Vijaya Raghavan Signed-off-by: Abhishek Sahu Signed-off-by: Varadarajan Narayanan ---

[PATCH v5 5/6] arm64: dts: Add ipq8074 SoC and HK01 board support

Add initial device tree support for the Qualcomm IPQ8074 SoC and HK01 evaluation board. Signed-off-by: Manoharan Vijaya Raghavan Signed-off-by: Abhishek Sahu Signed-off-by: Varadarajan Narayanan --- arch/arm64/boot/dts/qcom/Makefile | 1 + arch/arm64/boot/dts/qcom/ipq8074-hk01.dts |

[PATCH v5 6/6] arm64: defconfig: Enable qcom ipq8074 clock and pinctrl

From: Abhishek Sahu These configs are required for booting kernel in qcom ipq8074 boards. Signed-off-by: Abhishek Sahu Signed-off-by: Varadarajan Narayanan --- arch/arm64/configs/defconfig | 2 ++ 1 file changed, 2

[PATCH v5 6/6] arm64: defconfig: Enable qcom ipq8074 clock and pinctrl

From: Abhishek Sahu These configs are required for booting kernel in qcom ipq8074 boards. Signed-off-by: Abhishek Sahu Signed-off-by: Varadarajan Narayanan --- arch/arm64/configs/defconfig | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm64/configs/defconfig

[PATCH v5 4/6] clk: qcom: Add ipq8074 Global Clock Controller support

From: Abhishek Sahu This patch adds support for the global clock controller found on the ipq8074 based devices. This includes UART, I2C, SPI etc. Signed-off-by: Abhishek Sahu Signed-off-by: Varadarajan Narayanan ---

[PATCH v5 4/6] clk: qcom: Add ipq8074 Global Clock Controller support

From: Abhishek Sahu This patch adds support for the global clock controller found on the ipq8074 based devices. This includes UART, I2C, SPI etc. Signed-off-by: Abhishek Sahu Signed-off-by: Varadarajan Narayanan --- drivers/clk/qcom/Kconfig |9 + drivers/clk/qcom/Makefile |

[PATCH v5 0/6] Add minimal boot support for IPQ8074

v5: * Removed the 'NA' binding from documentation v4: * Split the clock patch and addressed a minor comment in the clock driver as per stephen's feedback. v3: * Addressed review feedback from Bjorn for pinctrl - Unified the names for qpic pads. - Corrected the names for pwm

[PATCH v5 3/6] clk: qcom: Add DT bindings for ipq8074 gcc clock controller

From: Abhishek Sahu Add the compatible strings and the include file for ipq8074 gcc clock controller. Acked-by: Rob Herring (bindings) Signed-off-by: Varadarajan Narayanan Signed-off-by: Abhishek Sahu ---

[PATCH v5 3/6] clk: qcom: Add DT bindings for ipq8074 gcc clock controller

From: Abhishek Sahu Add the compatible strings and the include file for ipq8074 gcc clock controller. Acked-by: Rob Herring (bindings) Signed-off-by: Varadarajan Narayanan Signed-off-by: Abhishek Sahu --- .../devicetree/bindings/clock/qcom,gcc.txt | 1 +

[PATCH v5 0/6] Add minimal boot support for IPQ8074

v5: * Removed the 'NA' binding from documentation v4: * Split the clock patch and addressed a minor comment in the clock driver as per stephen's feedback. v3: * Addressed review feedback from Bjorn for pinctrl - Unified the names for qpic pads. - Corrected the names for pwm

[PATCH v5 1/6] pinctrl: qcom: Add ipq8074 pinctrl driver

Add initial pinctrl driver to support pin configuration with pinctrl framework for ipq8074. Signed-off-by: Manoharan Vijaya Raghavan Signed-off-by: Varadarajan Narayanan --- .../bindings/pinctrl/qcom,ipq8074-pinctrl.txt | 172

[PATCH v5 1/6] pinctrl: qcom: Add ipq8074 pinctrl driver

Add initial pinctrl driver to support pin configuration with pinctrl framework for ipq8074. Signed-off-by: Manoharan Vijaya Raghavan Signed-off-by: Varadarajan Narayanan --- .../bindings/pinctrl/qcom,ipq8074-pinctrl.txt | 172 drivers/pinctrl/qcom/Kconfig |

Re: [PATCH 46/58] clocksource/drivers: Add a new driver for the Atmel ARM TC blocks

Le Thu, 8 Jun 2017 01:17:15 +0200, Alexandre Belloni a écrit : > On 07/06/2017 at 23:08:48 +0200, Daniel Lezcano wrote: > > > I was going to agree but this is not flexible enough because the > > > quadrature decoder always uses the first two channels. So on

Re: [PATCH 46/58] clocksource/drivers: Add a new driver for the Atmel ARM TC blocks

Le Thu, 8 Jun 2017 01:17:15 +0200, Alexandre Belloni a écrit : > On 07/06/2017 at 23:08:48 +0200, Daniel Lezcano wrote: > > > I was going to agree but this is not flexible enough because the > > > quadrature decoder always uses the first two channels. So on some > > > products, we may have: > >

Re: [PATCH] x86/efi: fix boot panic because of invalid bgrt image address

The subject tag should be efi instead of x86/efi since the code is in general driver code now. Matt/Ard, if need resend please let me know. Please help review the patch. Maniaxx, can you verify it on your machine? It passed my test with an emulation of your wrong address. On 06/08/17 at 01:32pm,

Re: [PATCH] x86/efi: fix boot panic because of invalid bgrt image address

The subject tag should be efi instead of x86/efi since the code is in general driver code now. Matt/Ard, if need resend please let me know. Please help review the patch. Maniaxx, can you verify it on your machine? It passed my test with an emulation of your wrong address. On 06/08/17 at 01:32pm,

Re: [PATCH RFC 0/2] KVM: s390: avoid having to enable vm.alloc_pgste

On Wed, 7 Jun 2017 22:47:56 +0200 Heiko Carstens wrote: > On Wed, Jun 07, 2017 at 02:34:40PM +0200, Martin Schwidefsky wrote: > > +#define arch_elf_pt_proc(ehdr, phdr, elf, interp, state) \ > > +({ \ > > +

Re: [PATCH] include/linux/vfio.h: Guard powerpc-specific functions with CONFIG_VFIO_SPAPR_EEH

e error below, what am I missing here? > > > > On 08/06/17 02:31, kbuild test robot wrote: >> Hi Murilo, >> >> [auto build test ERROR on linus/master] >> [also build test ERROR on v4.12-rc4 next-20170607] >> [if your patch is applied to the wrong

[PATCH] staging/lustre: echo_client.c - fix sparse warning: cast removes address space of expression

The function only cares about the value of the pointer, not the contents of the pointed-to data. Adding a `__force` annotation to the cast removes this warning. Signed-off-by: Guillermo O. Freschi --- drivers/staging/lustre/lustre/obdecho/echo_client.c | 2 +- 1 file changed,

Re: [PATCH RFC 0/2] KVM: s390: avoid having to enable vm.alloc_pgste

On Wed, 7 Jun 2017 22:47:56 +0200 Heiko Carstens wrote: > On Wed, Jun 07, 2017 at 02:34:40PM +0200, Martin Schwidefsky wrote: > > +#define arch_elf_pt_proc(ehdr, phdr, elf, interp, state) \ > > +({ \ > > + struct elf64_hdr *_ehdr =

Re: [PATCH] include/linux/vfio.h: Guard powerpc-specific functions with CONFIG_VFIO_SPAPR_EEH

e error below, what am I missing here? > > > > On 08/06/17 02:31, kbuild test robot wrote: >> Hi Murilo, >> >> [auto build test ERROR on linus/master] >> [also build test ERROR on v4.12-rc4 next-20170607] >> [if your patch is applied to the wrong

[PATCH] staging/lustre: echo_client.c - fix sparse warning: cast removes address space of expression

The function only cares about the value of the pointer, not the contents of the pointed-to data. Adding a `__force` annotation to the cast removes this warning. Signed-off-by: Guillermo O. Freschi --- drivers/staging/lustre/lustre/obdecho/echo_client.c | 2 +- 1 file changed, 1 insertion(+), 1

Re: [PATCH] include/linux/vfio.h: Guard powerpc-specific functions with CONFIG_VFIO_SPAPR_EEH

Hi, How did you manage to have CONFIG_EEH=y and CONFIG_VFIO_SPAPR_EEH=n? "make oldconfig" fixes this to CONFIG_VFIO_SPAPR_EEH=y. On 08/06/17 02:31, kbuild test robot wrote: > Hi Murilo, > > [auto build test ERROR on linus/master] > [also build test ERROR on v4.12-rc4 nex

Re: [PATCH] include/linux/vfio.h: Guard powerpc-specific functions with CONFIG_VFIO_SPAPR_EEH

Hi, How did you manage to have CONFIG_EEH=y and CONFIG_VFIO_SPAPR_EEH=n? "make oldconfig" fixes this to CONFIG_VFIO_SPAPR_EEH=y. On 08/06/17 02:31, kbuild test robot wrote: > Hi Murilo, > > [auto build test ERROR on linus/master] > [also build test ERROR on v4.12-rc4 nex

Re: [PATCH v2] [media] vb2: core: Lower the log level of debug outputs

On Thu, 2017-06-08 at 14:24 +0900, Tomasz Figa wrote: > On Thu, Jun 8, 2017 at 2:16 PM, Joe Perches wrote: [] > > If there automated systems that rely on specific levels, then > > changing the levels of individual messages could also cause > > those automated systems to fail. >

Re: [PATCH v2] [media] vb2: core: Lower the log level of debug outputs

On Thu, 2017-06-08 at 14:24 +0900, Tomasz Figa wrote: > On Thu, Jun 8, 2017 at 2:16 PM, Joe Perches wrote: [] > > If there automated systems that rely on specific levels, then > > changing the levels of individual messages could also cause > > those automated systems to fail. > > Well, that

[PATCH] x86/efi: fix boot panic because of invalid bgrt image address

Maniaxx reported kernel boot panic similar to below: (emulated the panic with using same invalid phys addr in a uefi vm) There are also a bug in bugzilla.kernel.org: https://bugzilla.kernel.org/show_bug.cgi?id=195633 This happens after below commit: 7b0a911 efi/x86:

[PATCH] x86/efi: fix boot panic because of invalid bgrt image address

Maniaxx reported kernel boot panic similar to below: (emulated the panic with using same invalid phys addr in a uefi vm) There are also a bug in bugzilla.kernel.org: https://bugzilla.kernel.org/show_bug.cgi?id=195633 This happens after below commit: 7b0a911 efi/x86: Move the EFI BGRT init code

Re: [PATCH v2] [media] vb2: core: Lower the log level of debug outputs

On Thu, Jun 8, 2017 at 2:16 PM, Joe Perches wrote: > On Thu, 2017-06-08 at 13:39 +0900, Tomasz Figa wrote: >> On Thu, Jun 8, 2017 at 12:24 PM, Hirokazu Honda wrote: >> > Hi, >> > >> > I completely understand bitmask method now. >> > I agree to the idea, but

Re: [PATCH v2] [media] vb2: core: Lower the log level of debug outputs

On Thu, Jun 8, 2017 at 2:16 PM, Joe Perches wrote: > On Thu, 2017-06-08 at 13:39 +0900, Tomasz Figa wrote: >> On Thu, Jun 8, 2017 at 12:24 PM, Hirokazu Honda wrote: >> > Hi, >> > >> > I completely understand bitmask method now. >> > I agree to the idea, but it is necessary to change the

[PATCH linux-next v4 0/4] i.MX ECSPI controller slave mode support

Changes in v4: * rebased to head of linux-next to resolve conflict * optimized mx53_ecspi_rx_slave() Changes in v3: * renamed several variables for for better readability * created spi_imx_pio_transfer_slave() for slave pio transfer * added fifo_size, has_dmamode and has_slavemode in

[PATCH linux-next v4 0/4] i.MX ECSPI controller slave mode support

Changes in v4: * rebased to head of linux-next to resolve conflict * optimized mx53_ecspi_rx_slave() Changes in v3: * renamed several variables for for better readability * created spi_imx_pio_transfer_slave() for slave pio transfer * added fifo_size, has_dmamode and has_slavemode in

[PATCH linux-next v4 3/4] ARM: dts: imx: change compatibility for SPI controllers on imx53 later soc

for SPI controllers on imx53 and later SoCs, there is HW issue when work in slave mode, as new device type 'IMX53_ECSPI' has been added for these SPI controllers which is compatible with 'fsl,imx53-ecspi'. This patch updates DTS to make imx53 later SPI controller only be compatibile with

[PATCH linux-next v4 1/4] spi: imx: introduce fifo_size and has_dmamode in spi_imx_devtype_data

Different ECSPI controller has different fifosize and DMA capability, instead of calling functions to identify these information by check devtype. add fifo_size and has_dmamode to spi_imx_devtype_data. so that these information can be directly accessed. Signed-off-by: Jiada Wang

[PATCH linux-next v4 3/4] ARM: dts: imx: change compatibility for SPI controllers on imx53 later soc

for SPI controllers on imx53 and later SoCs, there is HW issue when work in slave mode, as new device type 'IMX53_ECSPI' has been added for these SPI controllers which is compatible with 'fsl,imx53-ecspi'. This patch updates DTS to make imx53 later SPI controller only be compatibile with

[PATCH linux-next v4 1/4] spi: imx: introduce fifo_size and has_dmamode in spi_imx_devtype_data

Different ECSPI controller has different fifosize and DMA capability, instead of calling functions to identify these information by check devtype. add fifo_size and has_dmamode to spi_imx_devtype_data. so that these information can be directly accessed. Signed-off-by: Jiada Wang ---

[PATCH linux-next v4 4/4] spi: imx: Add support for SPI Slave mode

Previously i.MX SPI controller only works in Master mode. This patch adds support to i.MX51, i.MX53 and i.MX6 ECSPI controller to work also in Slave mode. Currently SPI Slave mode support patch has the following limitations: 1. The stale data in RXFIFO will be dropped when the Slave does any new

Re: [PATCH v2] [media] vb2: core: Lower the log level of debug outputs

On Thu, 2017-06-08 at 13:39 +0900, Tomasz Figa wrote: > On Thu, Jun 8, 2017 at 12:24 PM, Hirokazu Honda wrote: > > Hi, > > > > I completely understand bitmask method now. > > I agree to the idea, but it is necessary to change the specification of > > a debug parameter. > >

[PATCH linux-next v4 4/4] spi: imx: Add support for SPI Slave mode

Previously i.MX SPI controller only works in Master mode. This patch adds support to i.MX51, i.MX53 and i.MX6 ECSPI controller to work also in Slave mode. Currently SPI Slave mode support patch has the following limitations: 1. The stale data in RXFIFO will be dropped when the Slave does any new

Re: [PATCH v2] [media] vb2: core: Lower the log level of debug outputs

On Thu, 2017-06-08 at 13:39 +0900, Tomasz Figa wrote: > On Thu, Jun 8, 2017 at 12:24 PM, Hirokazu Honda wrote: > > Hi, > > > > I completely understand bitmask method now. > > I agree to the idea, but it is necessary to change the specification of > > a debug parameter. > > (We probably need to

[PATCH linux-next v4 2/4] spi: imx: add selection for iMX53 and iMX6 controller

ECSPI contorller for iMX53 and iMX6 has few hardware issues comparing to iMX51. The change add possibility to detect which controller is used to apply possible workaround and limitations. Signed-off-by: Jiada Wang --- .../devicetree/bindings/spi/fsl-imx-cspi.txt |

[PATCH linux-next v4 2/4] spi: imx: add selection for iMX53 and iMX6 controller

ECSPI contorller for iMX53 and iMX6 has few hardware issues comparing to iMX51. The change add possibility to detect which controller is used to apply possible workaround and limitations. Signed-off-by: Jiada Wang --- .../devicetree/bindings/spi/fsl-imx-cspi.txt | 1 +

Re: [PATCH] Fix loop device flush before configure v2

On Thu, 2017-06-08 at 10:17 +0800, James Wang wrote: > This condition check was exist at before commit b5dd2f6047ca ("block: loop: > improve performance via blk-mq") When add MQ support to loop device, it be > removed because the member of '->lo_thread' be removed. And then upstream > add

Re: [PATCH] Fix loop device flush before configure v2

On Thu, 2017-06-08 at 10:17 +0800, James Wang wrote: > This condition check was exist at before commit b5dd2f6047ca ("block: loop: > improve performance via blk-mq") When add MQ support to loop device, it be > removed because the member of '->lo_thread' be removed. And then upstream > add

Re: [PATCH v4 12/13] bluetooth/smp: ensure RNG is properly seeded before ECDH use

Hi Ted, >> This protocol uses lots of complex cryptography that relies on securely >> generated random numbers. Thus, it's important that the RNG is actually >> seeded before use. Fortuantely, it appears we're always operating in >> process context (there are many GFP_KERNEL allocations and other

Re: [PATCH v4 12/13] bluetooth/smp: ensure RNG is properly seeded before ECDH use

Hi Ted, >> This protocol uses lots of complex cryptography that relies on securely >> generated random numbers. Thus, it's important that the RNG is actually >> seeded before use. Fortuantely, it appears we're always operating in >> process context (there are many GFP_KERNEL allocations and other

Re: [PATCH v2 03/11] drm: sun4i: ignore swapped mixer<->tcon connection for DE2

在 2017-06-07 22:38，Maxime Ripard 写道： On Wed, Jun 07, 2017 at 06:01:02PM +0800, Icenowy Zheng wrote: >I have no idea what this is supposed to be doing either. > >I might be wrong, but I really feel like there's a big mismatch >between your commit log, and what you actually implement. > >In your

Re: [PATCH v2 03/11] drm: sun4i: ignore swapped mixer<->tcon connection for DE2

在 2017-06-07 22:38，Maxime Ripard 写道： On Wed, Jun 07, 2017 at 06:01:02PM +0800, Icenowy Zheng wrote: >I have no idea what this is supposed to be doing either. > >I might be wrong, but I really feel like there's a big mismatch >between your commit log, and what you actually implement. > >In your

Re: [PATCH v3 1/2] ip_tunnel: fix potential issue in ip_tunnel_rcv

On Thu, 2017-06-08 at 12:32 +0800, Haishuang Yan wrote: > When ip_tunnel_rcv fails, the tun_dst won't be freed, so call > dst_release to free it in error code path. > > CC: Pravin B Shelar > Fixes: 2e15ea390e6f ("ip_gre: Add support to collect tunnel metadata.") >

Re: [PATCH v3 1/2] ip_tunnel: fix potential issue in ip_tunnel_rcv

On Thu, 2017-06-08 at 12:32 +0800, Haishuang Yan wrote: > When ip_tunnel_rcv fails, the tun_dst won't be freed, so call > dst_release to free it in error code path. > > CC: Pravin B Shelar > Fixes: 2e15ea390e6f ("ip_gre: Add support to collect tunnel metadata.") > Signed-off-by: Haishuang Yan >

Re: [PATCH] mm: correct the comment when reclaimed pages exceed the scanned pages

On 2017/6/7 16:31, zhongjiang wrote: > The commit e1587a494540 ("mm: vmpressure: fix sending wrong events on > underflow") declare that reclaimed pages exceed the scanned pages due > to the thp reclaim. it is incorrect because THP will be spilt to normal > page and loop again. which will result in

Re: [PATCH] mm: correct the comment when reclaimed pages exceed the scanned pages

On 2017/6/7 16:31, zhongjiang wrote: > The commit e1587a494540 ("mm: vmpressure: fix sending wrong events on > underflow") declare that reclaimed pages exceed the scanned pages due > to the thp reclaim. it is incorrect because THP will be spilt to normal > page and loop again. which will result in

[PATCH] configfs: Fix race between create_link and configfs_rmdir

From: Nicholas Bellinger This patch closes a long standing race in configfs between the creation of a new symlink in create_link(), while the symlink target's config_item is being concurrently removed via configfs_rmdir(). This can happen because the symlink target's

[PATCH] configfs: Fix race between create_link and configfs_rmdir

From: Nicholas Bellinger This patch closes a long standing race in configfs between the creation of a new symlink in create_link(), while the symlink target's config_item is being concurrently removed via configfs_rmdir(). This can happen because the symlink target's reference is obtained by

[PATCH v3 2/2] acpi/iort: numa: Add numa node mapping for smmuv3 devices

Add code to parse proximity domain in SMMUv3 IORT table to set numa node mapping for smmuv3 devices. Signed-off-by: Ganapatrao Kulkarni --- drivers/acpi/arm64/iort.c | 28 ++-- 1 file changed, 26 insertions(+), 2 deletions(-) diff --git

[PATCH v3 2/2] acpi/iort: numa: Add numa node mapping for smmuv3 devices

Add code to parse proximity domain in SMMUv3 IORT table to set numa node mapping for smmuv3 devices. Signed-off-by: Ganapatrao Kulkarni --- drivers/acpi/arm64/iort.c | 28 ++-- 1 file changed, 26 insertions(+), 2 deletions(-) diff --git a/drivers/acpi/arm64/iort.c

[PATCH v3 1/2] acpica: iort: Update SMMUv3 header for proximity domain mapping

ARM IORT specification (rev. C) has added two new fields to define proximity domain for the SMMUv3 node in the IORT table. Proximity Domain Valid: Set to 1 if the value provided in the Proximity Domain field is valid. Set to 0 otherwise. Proximity domain: If the Proximity

[PATCH v3 1/2] acpica: iort: Update SMMUv3 header for proximity domain mapping

ARM IORT specification (rev. C) has added two new fields to define proximity domain for the SMMUv3 node in the IORT table. Proximity Domain Valid: Set to 1 if the value provided in the Proximity Domain field is valid. Set to 0 otherwise. Proximity domain: If the Proximity

[PATCH v3 0/2] acpi/iort, numa: Add numa node mapping for smmuv3 devices

ARM IORT specification(rev. C) has added provision to define proximity domain in SMMUv3 IORT table. Adding required code to parse Proximity domain and set numa_node of smmv3 platform devices. v3: - Addressed Lorenzo Pieralisi comment. v2: - Changed as per Lorenzo Pieralisi and Hanjun Guo

[PATCH v3 0/2] acpi/iort, numa: Add numa node mapping for smmuv3 devices

ARM IORT specification(rev. C) has added provision to define proximity domain in SMMUv3 IORT table. Adding required code to parse Proximity domain and set numa_node of smmv3 platform devices. v3: - Addressed Lorenzo Pieralisi comment. v2: - Changed as per Lorenzo Pieralisi and Hanjun Guo

Re: [PATCH 09/16] platform/x86: wmi: Instantiate all devices before adding them

> On Mon, Jun 5, 2017 at 8:03 PM, Darren Hart wrote: > > On Thu, Jun 01, 2017 at 10:43:39PM +0200, Michał Kępień wrote: > >> I know I have probably started sounding like a broken record by now, but > >> I still have not seen any response (apart from the typos getting fixed)

Re: [PATCH 09/16] platform/x86: wmi: Instantiate all devices before adding them

> On Mon, Jun 5, 2017 at 8:03 PM, Darren Hart wrote: > > On Thu, Jun 01, 2017 at 10:43:39PM +0200, Michał Kępień wrote: > >> I know I have probably started sounding like a broken record by now, but > >> I still have not seen any response (apart from the typos getting fixed) > >> to my comments on

[RESEND PATCH] input/joystick/analog: Use get_cycles() on PPC

The analog joystick driver spits a warning at us: drivers/input/joystick/analog.c:176:2: warning: #warning Precise timer not defined for this architecture. PPC has get_cycles() so use that. Signed-off-by: Michael Ellerman --- drivers/input/joystick/analog.c | 2 +- 1

[RESEND PATCH] input/joystick/analog: Use get_cycles() on PPC

The analog joystick driver spits a warning at us: drivers/input/joystick/analog.c:176:2: warning: #warning Precise timer not defined for this architecture. PPC has get_cycles() so use that. Signed-off-by: Michael Ellerman --- drivers/input/joystick/analog.c | 2 +- 1 file changed, 1

Re: [PATCH v2] [media] vb2: core: Lower the log level of debug outputs

On Thu, Jun 8, 2017 at 12:24 PM, Hirokazu Honda wrote: > Hi, > > I completely understand bitmask method now. > I agree to the idea, but it is necessary to change the specification of > a debug parameter. > (We probably need to change a document about that?) > For example,

Re: [PATCH v2] [media] vb2: core: Lower the log level of debug outputs

On Thu, Jun 8, 2017 at 12:24 PM, Hirokazu Honda wrote: > Hi, > > I completely understand bitmask method now. > I agree to the idea, but it is necessary to change the specification of > a debug parameter. > (We probably need to change a document about that?) > For example, there is maybe a user

Re: [PATCH 1/2] clocksource/drivers: Add timer-of common init routine

/commits/Daniel-Lezcano/clocksource-drivers-Add-timer-of-common-init-routine/20170607-024801 reproduce: # apt-get install sparse make ARCH=x86_64 allmodconfig make C=1 CF=-D__CHECK_ENDIAN__ sparse warnings: (new ones prefixed by >>) include/linux/compiler.h:260:8:

Re: [PATCH 1/2] clocksource/drivers: Add timer-of common init routine

/commits/Daniel-Lezcano/clocksource-drivers-Add-timer-of-common-init-routine/20170607-024801 reproduce: # apt-get install sparse make ARCH=x86_64 allmodconfig make C=1 CF=-D__CHECK_ENDIAN__ sparse warnings: (new ones prefixed by >>) include/linux/compiler.h:260:8:

[PATCH v3 2/2] ip6_tunnel: fix potential issue in __ip6_tnl_rcv

When __ip6_tnl_rcv fails, the tun_dst won't be freed, so call dst_release to free it in error code path. CC: Alexei Starovoitov Fixes: 8d79266bc48c ("ip6_tunnel: add collect_md mode to IPv6 tunnels") Signed-off-by: Haishuang Yan --- Changes in

[PATCH v3 1/2] ip_tunnel: fix potential issue in ip_tunnel_rcv

When ip_tunnel_rcv fails, the tun_dst won't be freed, so call dst_release to free it in error code path. CC: Pravin B Shelar Fixes: 2e15ea390e6f ("ip_gre: Add support to collect tunnel metadata.") Signed-off-by: Haishuang Yan --- Changes

[PATCH v3 2/2] ip6_tunnel: fix potential issue in __ip6_tnl_rcv

When __ip6_tnl_rcv fails, the tun_dst won't be freed, so call dst_release to free it in error code path. CC: Alexei Starovoitov Fixes: 8d79266bc48c ("ip6_tunnel: add collect_md mode to IPv6 tunnels") Signed-off-by: Haishuang Yan --- Changes in v2: - Add the the missing Fixes information

[PATCH v3 1/2] ip_tunnel: fix potential issue in ip_tunnel_rcv

When ip_tunnel_rcv fails, the tun_dst won't be freed, so call dst_release to free it in error code path. CC: Pravin B Shelar Fixes: 2e15ea390e6f ("ip_gre: Add support to collect tunnel metadata.") Signed-off-by: Haishuang Yan --- Changes in v2: - Add the the missing Fixes information Changes

Re: [patch -mm] mm, hugetlb: schedule when potentially allocating many hugepages

On 06/07/2017 09:03 PM, David Rientjes wrote: > A few hugetlb allocators loop while calling the page allocator and can > potentially prevent rescheduling if the page allocator slowpath is not > utilized. > > Conditionally schedule when large numbers of hugepages can be allocated. > >

Re: [patch -mm] mm, hugetlb: schedule when potentially allocating many hugepages

On 06/07/2017 09:03 PM, David Rientjes wrote: > A few hugetlb allocators loop while calling the page allocator and can > potentially prevent rescheduling if the page allocator slowpath is not > utilized. > > Conditionally schedule when large numbers of hugepages can be allocated. > >

Re: [PATCH 3/5] mfd: tps65217: Add a dependency on OF

On Wednesday 07 June 2017 07:40 PM, Javier Martinez Canillas wrote: > Hello Keerthy, > > On Wed, Jun 7, 2017 at 3:45 PM, Keerthy wrote: > > [snip] > > I think you can remove the of_match_device checks in some drivers too i.e:

Re: [PATCH 3/5] mfd: tps65217: Add a dependency on OF

On Wednesday 07 June 2017 07:40 PM, Javier Martinez Canillas wrote: > Hello Keerthy, > > On Wed, Jun 7, 2017 at 3:45 PM, Keerthy wrote: > > [snip] > > I think you can remove the of_match_device checks in some drivers too i.e:

Re: [PATCH v6 19/34] x86/mm: Add support to access boot related data in the clear

Hi Tom, [auto build test ERROR on linus/master] [also build test ERROR on v4.12-rc4 next-20170607] [cannot apply to tip/x86/core] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Tom-Lendacky/x86

Re: [PATCH v6 19/34] x86/mm: Add support to access boot related data in the clear

Hi Tom, [auto build test ERROR on linus/master] [also build test ERROR on v4.12-rc4 next-20170607] [cannot apply to tip/x86/core] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Tom-Lendacky/x86

Re: [PATCH 3.10 000/250] 3.10.106-stable review

On Wed, Jun 07, 2017 at 05:38:36PM -0700, Guenter Roeck wrote: > Build results: > total: 121 pass: 121 fail: 0 > Qemu test results: > total: 83 pass: 83 fail: 0 Awesome! Thank you Guenter! Willy

Re: [PATCH 3.10 000/250] 3.10.106-stable review

On Wed, Jun 07, 2017 at 05:38:36PM -0700, Guenter Roeck wrote: > Build results: > total: 121 pass: 121 fail: 0 > Qemu test results: > total: 83 pass: 83 fail: 0 Awesome! Thank you Guenter! Willy

[PATCH] security: selinux: use kmem_cache for ebitmap

The allocated size for each ebitmap_node is 192byte by kzalloc(). Then, ebitmap_node size is fixed, so it's possible to use only 144byte for each object by kmem_cache_zalloc(). It can reduce some dynamic allocation size. Signed-off-by: Junil Lee ---

[PATCH] iscsi-target: Reject immediate data underflow larger than SCSI transfer length

From: Nicholas Bellinger When iscsi WRITE underflow occurs there are two different scenarios that can happen. Normally in practice, when an EDTL vs. SCSI CDB TRANSFER LENGTH underflow is detected, the iscsi immediate data payload is the smaller SCSI CDB TRANSFER LENGTH.

[PATCH] security: selinux: use kmem_cache for ebitmap

The allocated size for each ebitmap_node is 192byte by kzalloc(). Then, ebitmap_node size is fixed, so it's possible to use only 144byte for each object by kmem_cache_zalloc(). It can reduce some dynamic allocation size. Signed-off-by: Junil Lee --- security/selinux/ss/ebitmap.c | 26

[PATCH] iscsi-target: Reject immediate data underflow larger than SCSI transfer length

From: Nicholas Bellinger When iscsi WRITE underflow occurs there are two different scenarios that can happen. Normally in practice, when an EDTL vs. SCSI CDB TRANSFER LENGTH underflow is detected, the iscsi immediate data payload is the smaller SCSI CDB TRANSFER LENGTH. That is, when a host

[RFC PATCH 1/4] EDAC: mvebu: Add driver for Marvell Armada SoCs

This adds an EDAC driver for the memory controller and L2 cache used on a number of Marvell Armada SoCs. Signed-off-by: Chris Packham Cc: linux-arm-ker...@lists.infradead.org --- drivers/edac/Kconfig | 7 + drivers/edac/Makefile | 1 +

[RFC PATCH 1/4] EDAC: mvebu: Add driver for Marvell Armada SoCs

This adds an EDAC driver for the memory controller and L2 cache used on a number of Marvell Armada SoCs. Signed-off-by: Chris Packham Cc: linux-arm-ker...@lists.infradead.org --- drivers/edac/Kconfig | 7 + drivers/edac/Makefile | 1 + drivers/edac/mvebu_edac.c | 506

[RFC PATCH 3/4] ARM: l2x0: add arm,ecc-enable property for aurora

The aurora cache on the Marvell Armada-XP SoC supports ECC protection for the L2 data arrays. Add a "arm,ecc-enable" device tree property which can be used to enable this. Signed-off-by: Chris Packham --- Documentation/devicetree/bindings/arm/l2c2x0.txt | 2 ++

[RFC PATCH 3/4] ARM: l2x0: add arm,ecc-enable property for aurora

The aurora cache on the Marvell Armada-XP SoC supports ECC protection for the L2 data arrays. Add a "arm,ecc-enable" device tree property which can be used to enable this. Signed-off-by: Chris Packham --- Documentation/devicetree/bindings/arm/l2c2x0.txt | 2 ++ arch/arm/mm/cache-l2x0.c

  1   2   3   4   5   6   7   8   9   10   >