AW: [PATCH 1/5] drm/panel: Add support for the EDT ETM0700G0BDH6

Hi Fabio, I've used git send-email and tested the patches by checkpatch.pl before without any problems. So it might have been touched by the mail server, so can you send me your checkpatch.pl log (directly)? Regards, Jan Tuerk emtrion GmbH Kreativpark - Alter Schlachthof 45 76131 Karlsruhe

AW: [PATCH 1/5] drm/panel: Add support for the EDT ETM0700G0BDH6

Hi Fabio, I've used git send-email and tested the patches by checkpatch.pl before without any problems. So it might have been touched by the mail server, so can you send me your checkpatch.pl log (directly)? Regards, Jan Tuerk emtrion GmbH Kreativpark - Alter Schlachthof 45 76131 Karlsruhe

Re: [PATCH 1/3] perf bench futex: benchmark only online CPUs

Em Wed, Nov 22, 2017 at 06:25:28PM -0600, Kim Phillips escreveu: > From: James Yang > > The "perf bench futex" benchmarks have a problem when not all CPUs in > the system are online: perf assumes the CPUs that are online are > contiguously numbered and assigns processor

Re: [PATCH 1/3] perf bench futex: benchmark only online CPUs

Em Wed, Nov 22, 2017 at 06:25:28PM -0600, Kim Phillips escreveu: > From: James Yang > > The "perf bench futex" benchmarks have a problem when not all CPUs in > the system are online: perf assumes the CPUs that are online are > contiguously numbered and assigns processor affinity to the threads

[PATCH 2/3] hwrng: exynos - add Samsung Exynos True RNG driver

Add support for True Random Number Generator found in Samsung Exynos 5250+ SoCs. Signed-off-by: Łukasz Stelmach --- MAINTAINERS | 7 + drivers/char/hw_random/Kconfig | 12 ++ drivers/char/hw_random/Makefile | 1 +

Re: [PATCH 1/3] perf bench futex: benchmark only online CPUs

Em Thu, Nov 23, 2017 at 12:09:48PM -0300, Arnaldo Carvalho de Melo escreveu: > Em Wed, Nov 22, 2017 at 06:25:28PM -0600, Kim Phillips escreveu: > > From: James Yang > > > > The "perf bench futex" benchmarks have a problem when not all CPUs in > > the system are online: perf

[PATCH 2/3] hwrng: exynos - add Samsung Exynos True RNG driver

Add support for True Random Number Generator found in Samsung Exynos 5250+ SoCs. Signed-off-by: Łukasz Stelmach --- MAINTAINERS | 7 + drivers/char/hw_random/Kconfig | 12 ++ drivers/char/hw_random/Makefile | 1 + drivers/char/hw_random/exynos-trng.c |

Re: [PATCH 1/3] perf bench futex: benchmark only online CPUs

Em Thu, Nov 23, 2017 at 12:09:48PM -0300, Arnaldo Carvalho de Melo escreveu: > Em Wed, Nov 22, 2017 at 06:25:28PM -0600, Kim Phillips escreveu: > > From: James Yang > > > > The "perf bench futex" benchmarks have a problem when not all CPUs in > > the system are online: perf assumes the CPUs

[PATCH 3/3] ARM: dts: exynos: Add nodes for True Random Number Generator

Add nodes for the True Random Number Generator found in Samsung Exynos 5250+ SoCs. Signed-off-by: Łukasz Stelmach --- arch/arm/boot/dts/exynos5.dtsi| 5 + arch/arm/boot/dts/exynos5250.dtsi | 5 + arch/arm/boot/dts/exynos5410.dtsi | 5 +

[PATCH 3/3] ARM: dts: exynos: Add nodes for True Random Number Generator

Add nodes for the True Random Number Generator found in Samsung Exynos 5250+ SoCs. Signed-off-by: Łukasz Stelmach --- arch/arm/boot/dts/exynos5.dtsi| 5 + arch/arm/boot/dts/exynos5250.dtsi | 5 + arch/arm/boot/dts/exynos5410.dtsi | 5 + arch/arm/boot/dts/exynos5420.dtsi | 5

[PATCH 1/3] dt-bindings: hwrng: Add Samsung Exynos 5250+ True RNG bindings

Add binding documentation for the True Random Number Generator found on Samsung Exynos 5250+ SoCs. Signed-off-by: Łukasz Stelmach --- .../devicetree/bindings/rng/samsung,exynos5250-trng.txt | 17 + 1 file changed, 17 insertions(+) create mode 100644

[PATCH 0/3] True RNG driver for Samsung Exynos 5250+ SoCs

Hello. The following patches add support for the true random number generator found in Samsung Exynos 5250+ SoCs. Patch #1 adds documentation for devicetree bindings. Patch #2 introduces the driver and appropriate changes in Makefile and Kconfig. Patch #3 adds nodes in devicetree files for

[PATCH 0/3] True RNG driver for Samsung Exynos 5250+ SoCs

Hello. The following patches add support for the true random number generator found in Samsung Exynos 5250+ SoCs. Patch #1 adds documentation for devicetree bindings. Patch #2 introduces the driver and appropriate changes in Makefile and Kconfig. Patch #3 adds nodes in devicetree files for

[PATCH 1/3] dt-bindings: hwrng: Add Samsung Exynos 5250+ True RNG bindings

Add binding documentation for the True Random Number Generator found on Samsung Exynos 5250+ SoCs. Signed-off-by: Łukasz Stelmach --- .../devicetree/bindings/rng/samsung,exynos5250-trng.txt | 17 + 1 file changed, 17 insertions(+) create mode 100644

Re: [PATCH] Add slowpath enter/exit trace events

On Thu, Nov 23, 2017 at 03:01:27PM +0100, Michal Hocko wrote: > On Thu 23-11-17 13:36:29, Mel Gorman wrote: > > On Thu, Nov 23, 2017 at 01:25:30PM +0100, Michal Hocko wrote: > > > On Thu 23-11-17 11:43:36, peter.enderb...@sony.com wrote: > > > > From: Peter Enderborg > >

Re: [PATCH] Add slowpath enter/exit trace events

On Thu, Nov 23, 2017 at 03:01:27PM +0100, Michal Hocko wrote: > On Thu 23-11-17 13:36:29, Mel Gorman wrote: > > On Thu, Nov 23, 2017 at 01:25:30PM +0100, Michal Hocko wrote: > > > On Thu 23-11-17 11:43:36, peter.enderb...@sony.com wrote: > > > > From: Peter Enderborg > > > > > > > > The warning

Re: [PATCH 1/5] drm/panel: Add support for the EDT ETM0700G0BDH6

Hi Jan, On Thu, Nov 23, 2017 at 10:55 AM, Jan Tuerk wrote: > The Emerging Display Technology ETM0700G0BDH6 is exactly > the same display as the ETM0700G0DH6, exept the pixelclock > polarity. Therefore re-use the ETM0700G0DH6 modes. It is > used by default on emtrion Avari

Re: [PATCH 1/5] drm/panel: Add support for the EDT ETM0700G0BDH6

Hi Jan, On Thu, Nov 23, 2017 at 10:55 AM, Jan Tuerk wrote: > The Emerging Display Technology ETM0700G0BDH6 is exactly > the same display as the ETM0700G0DH6, exept the pixelclock > polarity. Therefore re-use the ETM0700G0DH6 modes. It is > used by default on emtrion Avari based development kits.

Re: 4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk (also 4.12 stable)

Yes it seems to fix the bug. On 11/23/2017 03:34 PM, Christoph Hellwig wrote: > FYI, the patch below changes both the irq and block mappings to > always use the cpu possible map (should be split in two in due time). > > I think this is the right way forward. For every normal machine > those two

Re: 4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk (also 4.12 stable)

Yes it seems to fix the bug. On 11/23/2017 03:34 PM, Christoph Hellwig wrote: > FYI, the patch below changes both the irq and block mappings to > always use the cpu possible map (should be split in two in due time). > > I think this is the right way forward. For every normal machine > those two

Re: [PATCH v2] fs: handle shrinker registration failure insget_userns

Al Viro wrote: > On Thu, Nov 23, 2017 at 03:35:37PM +0100, Michal Hocko wrote: > > Hopefully less screwed version. But as I've said I am not really > > familiar with the code and do not feel competent to change it so please > > be very careful here. I've moved the shrinker registration to > >

Re: [PATCH v2] fs: handle shrinker registration failure insget_userns

Al Viro wrote: > On Thu, Nov 23, 2017 at 03:35:37PM +0100, Michal Hocko wrote: > > Hopefully less screwed version. But as I've said I am not really > > familiar with the code and do not feel competent to change it so please > > be very careful here. I've moved the shrinker registration to > >

Re: [PATCH v2 09/18] x86/asm: Move SYSENTER_stack to the beginning of struct tss_struct

On Thu, Nov 23, 2017 at 5:16 AM, Denys Vlasenko wrote: > On Wed, Nov 22, 2017 at 5:44 AM, Andy Lutomirski wrote: >> I want SYSENTER_stack to have reliable overflow detection, which >> means that it needs to be at the bottom of a page, not the top. >>

Re: [PATCH v2 09/18] x86/asm: Move SYSENTER_stack to the beginning of struct tss_struct

On Thu, Nov 23, 2017 at 5:16 AM, Denys Vlasenko wrote: > On Wed, Nov 22, 2017 at 5:44 AM, Andy Lutomirski wrote: >> I want SYSENTER_stack to have reliable overflow detection, which >> means that it needs to be at the bottom of a page, not the top. >> Move it to the beginning of struct tss_struct

Re: [PATCH 00/23] [v4] KAISER: unmap most of the kernel from userspace page tables

On 11/22/2017 11:32 PM, Ingo Molnar wrote: > diff --git a/arch/x86/events/intel/ds.c b/arch/x86/events/intel/ds.c > index c9f44d7ce838..61388b01962d 100644 > --- a/arch/x86/events/intel/ds.c > +++ b/arch/x86/events/intel/ds.c > @@ -3,7 +3,7 @@ > #include > #include > > -#include > +#include

Re: [PATCH 00/23] [v4] KAISER: unmap most of the kernel from userspace page tables

On 11/22/2017 11:32 PM, Ingo Molnar wrote: > diff --git a/arch/x86/events/intel/ds.c b/arch/x86/events/intel/ds.c > index c9f44d7ce838..61388b01962d 100644 > --- a/arch/x86/events/intel/ds.c > +++ b/arch/x86/events/intel/ds.c > @@ -3,7 +3,7 @@ > #include > #include > > -#include > +#include

Re: [PATCH v2] fs: handle shrinker registration failure in sget_userns

On Thu 23-11-17 14:55:40, Al Viro wrote: > On Thu, Nov 23, 2017 at 03:35:37PM +0100, Michal Hocko wrote: > > Hopefully less screwed version. But as I've said I am not really > > familiar with the code and do not feel competent to change it so please > > be very careful here. I've moved the

Re: [PATCH v2] fs: handle shrinker registration failure in sget_userns

On Thu 23-11-17 14:55:40, Al Viro wrote: > On Thu, Nov 23, 2017 at 03:35:37PM +0100, Michal Hocko wrote: > > Hopefully less screwed version. But as I've said I am not really > > familiar with the code and do not feel competent to change it so please > > be very careful here. I've moved the

Re: [PATCH] fs: handle shrinker registration failure in sget_userns

On Thu 23-11-17 14:47:35, Al Viro wrote: > On Thu, Nov 23, 2017 at 12:52:47PM +0100, Michal Hocko wrote: > > @@ -503,12 +504,18 @@ struct super_block *sget_userns(struct > > file_system_type *type, > > s = alloc_super(type, (flags & ~SB_SUBMOUNT), user_ns); > > if (!s) > >

Re: [PATCH] fs: handle shrinker registration failure in sget_userns

On Thu 23-11-17 14:47:35, Al Viro wrote: > On Thu, Nov 23, 2017 at 12:52:47PM +0100, Michal Hocko wrote: > > @@ -503,12 +504,18 @@ struct super_block *sget_userns(struct > > file_system_type *type, > > s = alloc_super(type, (flags & ~SB_SUBMOUNT), user_ns); > > if (!s) > >

Re: [PATCH 4.14 00/18] 4.14.2-stable review

On Thu, Nov 23, 2017 at 08:08:54PM +0530, Naresh Kamboju wrote: > On 22 November 2017 at 15:42, Greg Kroah-Hartman > wrote: > > This is the start of the stable review cycle for the 4.14.2 release. > > There are 18 patches in this series, all will be posted as a

Re: [PATCH 4.14 00/18] 4.14.2-stable review

On Thu, Nov 23, 2017 at 08:08:54PM +0530, Naresh Kamboju wrote: > On 22 November 2017 at 15:42, Greg Kroah-Hartman > wrote: > > This is the start of the stable review cycle for the 4.14.2 release. > > There are 18 patches in this series, all will be posted as a response > > to this one. If

Re: [PATCH v2] fs: handle shrinker registration failure in sget_userns

On Thu, Nov 23, 2017 at 03:35:37PM +0100, Michal Hocko wrote: > Hopefully less screwed version. But as I've said I am not really > familiar with the code and do not feel competent to change it so please > be very careful here. I've moved the shrinker registration to > alloc_super which turned out

Re: [PATCH v2] fs: handle shrinker registration failure in sget_userns

On Thu, Nov 23, 2017 at 03:35:37PM +0100, Michal Hocko wrote: > Hopefully less screwed version. But as I've said I am not really > familiar with the code and do not feel competent to change it so please > be very careful here. I've moved the shrinker registration to > alloc_super which turned out

Re: [PATCH PREEMPT RT] rt-mutex: fix deadlock in device mapper

On Thu, 2017-11-23 at 15:42 +0100, Sebastian Siewior wrote: > On 2017-11-21 22:20:51 [+0100], Mike Galbraith wrote: > > On Tue, 2017-11-21 at 14:56 -0500, Mikulas Patocka wrote: > > > > > > If we don't have any reason why it is needed to unplug block requests > > > when > > > a spinlock is

Re: [PATCH PREEMPT RT] rt-mutex: fix deadlock in device mapper

On Thu, 2017-11-23 at 15:42 +0100, Sebastian Siewior wrote: > On 2017-11-21 22:20:51 [+0100], Mike Galbraith wrote: > > On Tue, 2017-11-21 at 14:56 -0500, Mikulas Patocka wrote: > > > > > > If we don't have any reason why it is needed to unplug block requests > > > when > > > a spinlock is

Re: [PATCH 4.13 00/35] 4.13.16-stable review

On 22 November 2017 at 15:41, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.13.16 release. > There are 35 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied,

Re: [PATCH 4.13 00/35] 4.13.16-stable review

On 22 November 2017 at 15:41, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.13.16 release. > There are 35 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > >

Re: [PATCH v2] platform/x86: wmi-bmof: New driver to expose embedded Binary WMI MOF metadata

On Thu, Nov 23, 2017 at 6:39 AM, Pali Rohár wrote: > On Tuesday 04 July 2017 15:28:19 Pali Rohár wrote: >> On Tuesday 06 June 2017 22:50:52 Pali Rohár wrote: >> > On Tuesday 06 June 2017 19:02:01 Darren Hart wrote: >> > > On Tue, Jun 06, 2017 at 12:04:40PM +0200, Pali Rohár

Re: [PATCH v4 2/4] tpm: ignore burstcount to improve tpm_tis send() performance

On Wed, Nov 22, 2017 at 06:52:03AM +, alexander.stef...@infineon.com wrote: > > > > > This seems to fail reliably with my SPI TPM 2.0. I get EIO when > > > > > trying to > > > > send large amounts of data, e.g. with TPM2_Hash, and subsequent tests > > > > seem to take an unusual amount of

Re: [PATCH v2] platform/x86: wmi-bmof: New driver to expose embedded Binary WMI MOF metadata

On Thu, Nov 23, 2017 at 6:39 AM, Pali Rohár wrote: > On Tuesday 04 July 2017 15:28:19 Pali Rohár wrote: >> On Tuesday 06 June 2017 22:50:52 Pali Rohár wrote: >> > On Tuesday 06 June 2017 19:02:01 Darren Hart wrote: >> > > On Tue, Jun 06, 2017 at 12:04:40PM +0200, Pali Rohár wrote: >> > > > On

Re: [PATCH v4 2/4] tpm: ignore burstcount to improve tpm_tis send() performance

On Wed, Nov 22, 2017 at 06:52:03AM +, alexander.stef...@infineon.com wrote: > > > > > This seems to fail reliably with my SPI TPM 2.0. I get EIO when > > > > > trying to > > > > send large amounts of data, e.g. with TPM2_Hash, and subsequent tests > > > > seem to take an unusual amount of

Re: 4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk (also 4.12 stable)

[fullquote deleted] > What will happen for the CPU hotplug case? > Wouldn't we route I/O to a disabled CPU with this patch? Why would we route I/O to a disabled CPU (we generally route I/O to devices to start with). How would including possible but not present cpus change anything?

Re: 4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk (also 4.12 stable)

[fullquote deleted] > What will happen for the CPU hotplug case? > Wouldn't we route I/O to a disabled CPU with this patch? Why would we route I/O to a disabled CPU (we generally route I/O to devices to start with). How would including possible but not present cpus change anything?

Re: [PATCH] fs: handle shrinker registration failure in sget_userns

On Thu, Nov 23, 2017 at 12:52:47PM +0100, Michal Hocko wrote: > @@ -503,12 +504,18 @@ struct super_block *sget_userns(struct file_system_type > *type, > s = alloc_super(type, (flags & ~SB_SUBMOUNT), user_ns); > if (!s) > return ERR_PTR(-ENOMEM); >

Re: [PATCH] fs: handle shrinker registration failure in sget_userns

On Thu, Nov 23, 2017 at 12:52:47PM +0100, Michal Hocko wrote: > @@ -503,12 +504,18 @@ struct super_block *sget_userns(struct file_system_type > *type, > s = alloc_super(type, (flags & ~SB_SUBMOUNT), user_ns); > if (!s) > return ERR_PTR(-ENOMEM); >

Re: [GIT PULL REQUEST] watchdog - v4.15-rc1 Merge Window

The following changes since commit 4dd3c2e5a4225e3df85afc6033e62ce8b09f0ed2: Merge tag 'nfsd-4.15' of git://linux-nfs.org/~bfields/linux (2017-11-18 11:22:04 -0800) are available in the git repository at: git://www.linux-watchdog.org/linux-watchdog.git for you to fetch changes up to

Re: [GIT PULL REQUEST] watchdog - v4.15-rc1 Merge Window

The following changes since commit 4dd3c2e5a4225e3df85afc6033e62ce8b09f0ed2: Merge tag 'nfsd-4.15' of git://linux-nfs.org/~bfields/linux (2017-11-18 11:22:04 -0800) are available in the git repository at: git://www.linux-watchdog.org/linux-watchdog.git for you to fetch changes up to

Re: 4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk (also 4.12 stable)

On 11/23/2017 03:34 PM, Christoph Hellwig wrote: > FYI, the patch below changes both the irq and block mappings to > always use the cpu possible map (should be split in two in due time). > > I think this is the right way forward. For every normal machine > those two are the same, but for VMs

Re: 4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk (also 4.12 stable)

On 11/23/2017 03:34 PM, Christoph Hellwig wrote: > FYI, the patch below changes both the irq and block mappings to > always use the cpu possible map (should be split in two in due time). > > I think this is the right way forward. For every normal machine > those two are the same, but for VMs

Re: [PATCH PREEMPT RT] rt-mutex: fix deadlock in device mapper

On 2017-11-21 22:20:51 [+0100], Mike Galbraith wrote: > On Tue, 2017-11-21 at 14:56 -0500, Mikulas Patocka wrote: > > > > If we don't have any reason why it is needed to unplug block requests when > > a spinlock is taken - so let's not do this. > > That's perfectly fine.  I guess I shouldn't

Re: [PATCH PREEMPT RT] rt-mutex: fix deadlock in device mapper

On 2017-11-21 22:20:51 [+0100], Mike Galbraith wrote: > On Tue, 2017-11-21 at 14:56 -0500, Mikulas Patocka wrote: > > > > If we don't have any reason why it is needed to unplug block requests when > > a spinlock is taken - so let's not do this. > > That's perfectly fine.  I guess I shouldn't

[PATCH net v2] net: thunderx: Fix TCP/UDP checksum offload for IPv6 pkts

From: Sunil Goutham Don't offload IP header checksum to NIC. This fixes a previous patch which enabled checksum offloading for both IPv4 and IPv6 packets. So L3 checksum offload was getting enabled for IPv6 pkts. And HW is dropping these pkts as it assumes the pkt is IPv4

[PATCH net v2] net: thunderx: Fix TCP/UDP checksum offload for IPv6 pkts

From: Sunil Goutham Don't offload IP header checksum to NIC. This fixes a previous patch which enabled checksum offloading for both IPv4 and IPv6 packets. So L3 checksum offload was getting enabled for IPv6 pkts. And HW is dropping these pkts as it assumes the pkt is IPv4 when IP csum offload

[PATCH] power: ltc2941-battery-gauge: Disable continuous monitoring on shutdown

The driver sets the fuel gauge to continuous monitoring on startup, for the models that support this. When the board shuts down, the chip remains in that mode, causing a few mA drain on the battery every 2 or 10 seconds. This patch registers a shutdown handler that turns off the monitoring to

[PATCH] power: ltc2941-battery-gauge: Disable continuous monitoring on shutdown

The driver sets the fuel gauge to continuous monitoring on startup, for the models that support this. When the board shuts down, the chip remains in that mode, causing a few mA drain on the battery every 2 or 10 seconds. This patch registers a shutdown handler that turns off the monitoring to

Re: [PATCH 4.14 00/18] 4.14.2-stable review

On 22 November 2017 at 15:42, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.2 release. > There are 18 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied,

Re: [PATCH 4.14 00/18] 4.14.2-stable review

On 22 November 2017 at 15:42, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.2 release. > There are 18 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > >

Re: [PATCH v2] platform/x86: wmi-bmof: New driver to expose embedded Binary WMI MOF metadata

On Tuesday 04 July 2017 15:28:19 Pali Rohár wrote: > On Tuesday 06 June 2017 22:50:52 Pali Rohár wrote: > > On Tuesday 06 June 2017 19:02:01 Darren Hart wrote: > > > On Tue, Jun 06, 2017 at 12:04:40PM +0200, Pali Rohár wrote: > > > > On Monday 05 June 2017 20:16:44 Andy Lutomirski wrote: > > > > >

Re: [PATCH v2] platform/x86: wmi-bmof: New driver to expose embedded Binary WMI MOF metadata

On Tuesday 04 July 2017 15:28:19 Pali Rohár wrote: > On Tuesday 06 June 2017 22:50:52 Pali Rohár wrote: > > On Tuesday 06 June 2017 19:02:01 Darren Hart wrote: > > > On Tue, Jun 06, 2017 at 12:04:40PM +0200, Pali Rohár wrote: > > > > On Monday 05 June 2017 20:16:44 Andy Lutomirski wrote: > > > > >

Re: [PATCH v2 04/14] soundwire: Add MIPI DisCo property helpers

On Fri, Nov 10, 2017 at 05:19:06PM +0530, Vinod Koul wrote: > MIPI Discovery And Configuration (DisCo) Specification for SoundWire > specifies properties to be implemented for SoundWire Masters and > Slaves. The DisCo spec doesn't mandate these properties. However, > SDW bus cannot work without

[PATCH] kbuild: drop $(extra-y) from real-objs-y

$(real-objs-y) in only used in scripts/Makefile.build to form "targets", but $(extra-y) is added to "targets" in another line. We do not need to add $(extra-y) twice. Signed-off-by: Masahiro Yamada --- scripts/Makefile.lib | 2 +- 1 file changed, 1 insertion(+),

Re: [PATCH 2/3] perf tools: Fix build for hardened environments

On Thu, Nov 23, 2017 at 11:15:32AM -0300, Arnaldo Carvalho de Melo wrote: SNIP > > I stumbled it on a recently created perf build container for fedora 27: > > fedora:27 > Downloading http://192.168.124.1/perf/perf-4.14.0.tar.xz... > % Total% Received % Xferd Average Speed TimeTime

Re: [PATCH v2 04/14] soundwire: Add MIPI DisCo property helpers

On Fri, Nov 10, 2017 at 05:19:06PM +0530, Vinod Koul wrote: > MIPI Discovery And Configuration (DisCo) Specification for SoundWire > specifies properties to be implemented for SoundWire Masters and > Slaves. The DisCo spec doesn't mandate these properties. However, > SDW bus cannot work without

[PATCH] kbuild: drop $(extra-y) from real-objs-y

$(real-objs-y) in only used in scripts/Makefile.build to form "targets", but $(extra-y) is added to "targets" in another line. We do not need to add $(extra-y) twice. Signed-off-by: Masahiro Yamada --- scripts/Makefile.lib | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH 2/3] perf tools: Fix build for hardened environments

On Thu, Nov 23, 2017 at 11:15:32AM -0300, Arnaldo Carvalho de Melo wrote: SNIP > > I stumbled it on a recently created perf build container for fedora 27: > > fedora:27 > Downloading http://192.168.124.1/perf/perf-4.14.0.tar.xz... > % Total% Received % Xferd Average Speed TimeTime

Re: [PATCH v2] kmemleak: add scheduling point to kmemleak_scan

On Thu, Nov 23, 2017 at 08:23:08PM +0800, Yisheng Xie wrote: > kmemleak_scan will scan struct page for each node and it can be really > large and resulting in a soft lockup. We have seen a soft lockup when do > scan while compile kernel: > > [ 220.561051] watchdog: BUG: soft lockup - CPU#53

Re: [PATCH v2] kmemleak: add scheduling point to kmemleak_scan

On Thu, Nov 23, 2017 at 08:23:08PM +0800, Yisheng Xie wrote: > kmemleak_scan will scan struct page for each node and it can be really > large and resulting in a soft lockup. We have seen a soft lockup when do > scan while compile kernel: > > [ 220.561051] watchdog: BUG: soft lockup - CPU#53

Re: [PATCH v8 4/5] crash: export paddr_vmcoreinfo_note()

On Thu, Nov 23, 2017 at 03:02:05PM +0100, Marc-André Lureau wrote: > The following patch is going to use the symbol from the fw_cfg module, > to call the function and write the note location details in the > vmcoreinfo entry, so qemu can produce dumps with the vmcoreinfo note. Sounds like fw_cfg

Re: [PATCH v8 4/5] crash: export paddr_vmcoreinfo_note()

On Thu, Nov 23, 2017 at 03:02:05PM +0100, Marc-André Lureau wrote: > The following patch is going to use the symbol from the fw_cfg module, > to call the function and write the note location details in the > vmcoreinfo entry, so qemu can produce dumps with the vmcoreinfo note. Sounds like fw_cfg

[GIT PULL] UBI/UBIFS updates for 4.15-rc1

Linus, The following changes since commit bebc6082da0a9f5d47a1ea2edc099bf671058bd4: Linux 4.14 (2017-11-12 10:46:13 -0800) are available in the git repository at: git://git.infradead.org/linux-ubifs.git tags/upstream-4.15-rc1 for you to fetch changes up to

[GIT PULL] UBI/UBIFS updates for 4.15-rc1

Linus, The following changes since commit bebc6082da0a9f5d47a1ea2edc099bf671058bd4: Linux 4.14 (2017-11-12 10:46:13 -0800) are available in the git repository at: git://git.infradead.org/linux-ubifs.git tags/upstream-4.15-rc1 for you to fetch changes up to

[GIT PULL] UML updates for 4.15-rc1

Linus, The following changes since commit bebc6082da0a9f5d47a1ea2edc099bf671058bd4: Linux 4.14 (2017-11-12 10:46:13 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/rw/uml.git for-linus-4.15-rc1 for you to fetch changes up to

[GIT PULL] UML updates for 4.15-rc1

Linus, The following changes since commit bebc6082da0a9f5d47a1ea2edc099bf671058bd4: Linux 4.14 (2017-11-12 10:46:13 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/rw/uml.git for-linus-4.15-rc1 for you to fetch changes up to

Re: [PATCH v2] fs: handle shrinker registration failure in sget_userns

Hopefully less screwed version. But as I've said I am not really familiar with the code and do not feel competent to change it so please be very careful here. I've moved the shrinker registration to alloc_super which turned out to be simpler. --- >From f2a86a9dc45853149d4f29a5ecff77ec4c827b9f Mon

Re: [PATCH v2] fs: handle shrinker registration failure in sget_userns

Hopefully less screwed version. But as I've said I am not really familiar with the code and do not feel competent to change it so please be very careful here. I've moved the shrinker registration to alloc_super which turned out to be simpler. --- >From f2a86a9dc45853149d4f29a5ecff77ec4c827b9f Mon

Re: 4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk (also 4.12 stable)

FYI, the patch below changes both the irq and block mappings to always use the cpu possible map (should be split in two in due time). I think this is the right way forward. For every normal machine those two are the same, but for VMs with maxcpus above their normal count or some big iron that

Re: 4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk (also 4.12 stable)

FYI, the patch below changes both the irq and block mappings to always use the cpu possible map (should be split in two in due time). I think this is the right way forward. For every normal machine those two are the same, but for VMs with maxcpus above their normal count or some big iron that

Re: Regression in TTM driver w/Linus' master

On 11/23/17 2:58 AM, Dave Airlie wrote: On 23 November 2017 at 11:17, Laura Abbott wrote: Hi, Fedora QA testing reported a panic when booting up VMs using qmeu vga drivers (https://paste.fedoraproject.org/paste/498yRWTCJv2LKIrmj4EliQ) [ 30.108507] [ cut

Re: Regression in TTM driver w/Linus' master

On 11/23/17 2:58 AM, Dave Airlie wrote: On 23 November 2017 at 11:17, Laura Abbott wrote: Hi, Fedora QA testing reported a panic when booting up VMs using qmeu vga drivers (https://paste.fedoraproject.org/paste/498yRWTCJv2LKIrmj4EliQ) [ 30.108507] [ cut here ] [

Re: [PATCH 4.4 00/16] 4.4.101-stable review

lls-tests - pass: 956, skip: 164, * ltp-timers-tests - pass: 12, And the hikey results. Summary kernel: 4.4.101-rc1 git repo: https://git.linaro.org/lkft/arm64-stable-rc.git git tag: 4.4.101-rc1-hikey-20171123-59 git commit: 6ac5099d4

Re: [PATCH 4.4 00/16] 4.4.101-stable review

timers-tests - pass: 12, And the hikey results. Summary kernel: 4.4.101-rc1 git repo: https://git.linaro.org/lkft/arm64-stable-rc.git git tag: 4.4.101-rc1-hikey-20171123-59 git commit: 6ac5099d48384b7c967aa09727e0c98be846957a

Re: Fwd: [PATCH] arm: ensure symbol is a thumb symbol in new binutils

On 23 November 2017 at 14:02, Russell King - ARM Linux wrote: > On Thu, Nov 23, 2017 at 11:47:56AM +0100, Jason A. Donenfeld wrote: >> Hello Nick & Binutils developers, >> >> It would appear that recent changes in the binutils assembler (perhaps >>

Re: Fwd: [PATCH] arm: ensure symbol is a thumb symbol in new binutils

On 23 November 2017 at 14:02, Russell King - ARM Linux wrote: > On Thu, Nov 23, 2017 at 11:47:56AM +0100, Jason A. Donenfeld wrote: >> Hello Nick & Binutils developers, >> >> It would appear that recent changes in the binutils assembler (perhaps >> 52a86f843b6dee1de9977293da9786649b146b05?

Re: [Intel-gfx] i915: enum intel_dpll_id cast

On Wed, Nov 22, 2017 at 12:54:49PM -0800, Kees Cook wrote: > Hi, > > While doing Clang test builds, this was reported: > > drivers/gpu/drm/i915/intel_ddi.c:1481:30: warning: implicit conversion > from enumeration type 'enum port' to different enumeration type 'enum > intel_dpll_id'

Re: [Intel-gfx] i915: enum intel_dpll_id cast

On Wed, Nov 22, 2017 at 12:54:49PM -0800, Kees Cook wrote: > Hi, > > While doing Clang test builds, this was reported: > > drivers/gpu/drm/i915/intel_ddi.c:1481:30: warning: implicit conversion > from enumeration type 'enum port' to different enumeration type 'enum > intel_dpll_id'

Re: kernel BUG at crypto/asymmetric_keys/public_key.c:80

On Wed, 2017-11-22 at 15:07 -0800, Florian Fainelli wrote: > On 11/22/2017 10:42 AM, Johannes Berg wrote: > > On Wed, 2017-11-22 at 19:29 +0100, Arend van Spriel wrote: > > > + Johannes > > > > > > >>> BUG_ON(!sig->digest); > > > BUG_ON(!sig->s); > > > > I *think* this is the same

Re: kernel BUG at crypto/asymmetric_keys/public_key.c:80

On Wed, 2017-11-22 at 15:07 -0800, Florian Fainelli wrote: > On 11/22/2017 10:42 AM, Johannes Berg wrote: > > On Wed, 2017-11-22 at 19:29 +0100, Arend van Spriel wrote: > > > + Johannes > > > > > > >>> BUG_ON(!sig->digest); > > > BUG_ON(!sig->s); > > > > I *think* this is the same

Re: [PATCH 3.16 100/133] bcache: correct cache_dirty_target in __update_writeback_rate()

On Thu, 2017-11-23 at 13:08 +, Ben Hutchings wrote: > On Tue, 2017-11-21 at 19:41 -0800, Joe Perches wrote: > > On Wed, 2017-11-22 at 01:58 +, Ben Hutchings wrote: > > > 3.16.51-rc1 review patch. If anyone has any objections, please let me > > > know. > > [] > > > ---

Re: [PATCH 3.16 100/133] bcache: correct cache_dirty_target in __update_writeback_rate()

On Thu, 2017-11-23 at 13:08 +, Ben Hutchings wrote: > On Tue, 2017-11-21 at 19:41 -0800, Joe Perches wrote: > > On Wed, 2017-11-22 at 01:58 +, Ben Hutchings wrote: > > > 3.16.51-rc1 review patch. If anyone has any objections, please let me > > > know. > > [] > > > ---

Re: [PATCH] kbuild: rpm: prompt to use "rpm-pkg" if "rpm" target is used

2017-11-15 18:19 GMT+09:00 Masahiro Yamada : > The "rpm" has been kept for backward compatibility since pre-git era. > I am planning to remove it after the Linux 4.18 release. Annouce the > end of the support, prompting to use "rpm-pkg" instead. > > If you use

Re: [PATCH] kbuild: rpm: prompt to use "rpm-pkg" if "rpm" target is used

2017-11-15 18:19 GMT+09:00 Masahiro Yamada : > The "rpm" has been kept for backward compatibility since pre-git era. > I am planning to remove it after the Linux 4.18 release. Annouce the > end of the support, prompting to use "rpm-pkg" instead. > > If you use "rpm", it will work like "rpm-pkg",

Re: [PATCH 4.9 00/25] 4.9.65-stable review

On 22 November 2017 at 15:41, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.65 release. > There are 25 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied,

Re: [PATCH 4.9 00/25] 4.9.65-stable review

On 22 November 2017 at 15:41, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.65 release. > There are 25 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > >

Re: [PATCH] kbuild: package: use --transform option to prefix paths in tar

2017-11-15 18:17 GMT+09:00 Masahiro Yamada : > For rpm-pkg and deb-pkg, a source tar file is created. All paths in > the archive must be prefixed with the base name of the tar. That > means, everything is contained in the directory when you extract it. > >

Re: [PATCH] kbuild: package: use --transform option to prefix paths in tar

2017-11-15 18:17 GMT+09:00 Masahiro Yamada : > For rpm-pkg and deb-pkg, a source tar file is created. All paths in > the archive must be prefixed with the base name of the tar. That > means, everything is contained in the directory when you extract it. > > Currently, scripts/package/Makefile

Re: [PATCH] kbuild: clean up *.i and *.lst patterns by make clean

2017-11-17 1:49 GMT+09:00 Masahiro Yamada : > *.i and *.lst are supported by single targets build. Clean up them. > > Signed-off-by: Masahiro Yamada > --- > > Makefile | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > >

Re: [PATCH] kbuild: clean up *.i and *.lst patterns by make clean

2017-11-17 1:49 GMT+09:00 Masahiro Yamada : > *.i and *.lst are supported by single targets build. Clean up them. > > Signed-off-by: Masahiro Yamada > --- > > Makefile | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/Makefile b/Makefile > index 4299f94..3ea081a

Re: [PATCH v5 2/2] iio : cm32181 : cosmetic cleanup

On Thu, Nov 23, 2017 at 12:52 AM, Marc CAPDEVILLE wrote: > Somme cosmetic cleanup suggested by Peter Meerwald-Stadler. Proper way to give credit to someone is to use the Suggested-by tag above your Signed-off by tag. thanks, Daniel.

Re: [PATCH v5 2/2] iio : cm32181 : cosmetic cleanup

On Thu, Nov 23, 2017 at 12:52 AM, Marc CAPDEVILLE wrote: > Somme cosmetic cleanup suggested by Peter Meerwald-Stadler. Proper way to give credit to someone is to use the Suggested-by tag above your Signed-off by tag. thanks, Daniel.

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