[PATCH] [media] v4l2: Add support for go2001 PCI codec driver

This patch adds support for the go2001 PCI codec driver. This hardware is present on ChromeOS based devices like the Acer ChromeBox and Acer/LG ChromeBase 24 devices. This driver comes from the ChromeOS v3.18 kernel tree and has been modified to support vb2_buffer restructuring introduced in

[PATCH] [media] v4l2: Add support for go2001 PCI codec driver

This patch adds support for the go2001 PCI codec driver. This hardware is present on ChromeOS based devices like the Acer ChromeBox and Acer/LG ChromeBase 24 devices. This driver comes from the ChromeOS v3.18 kernel tree and has been modified to support vb2_buffer restructuring introduced in

Re: [RFC PATCH] dax: add badblocks check to Device DAX

On Wed, May 3, 2017 at 3:41 PM, Kani, Toshimitsu wrote: > On Wed, 2017-05-03 at 14:48 -0700, Dan Williams wrote: >> On Wed, May 3, 2017 at 11:46 AM, Kani, Toshimitsu > > wrote: >> > On Wed, 2017-05-03 at 09:30 -0700, Dan Williams wrote: >> > > On Wed, May

Re: [RFC PATCH] dax: add badblocks check to Device DAX

On Wed, May 3, 2017 at 3:41 PM, Kani, Toshimitsu wrote: > On Wed, 2017-05-03 at 14:48 -0700, Dan Williams wrote: >> On Wed, May 3, 2017 at 11:46 AM, Kani, Toshimitsu > > wrote: >> > On Wed, 2017-05-03 at 09:30 -0700, Dan Williams wrote: >> > > On Wed, May 3, 2017 at 9:09 AM, Kani, Toshimitsu > >

Re: [patch v2] mm, vmscan: avoid thrashing anon lru when free + file is low

On Wed, 3 May 2017, Michal Hocko wrote: > diff --git a/mm/vmscan.c b/mm/vmscan.c > index 24efcc20af91..f3ec8760dc06 100644 > --- a/mm/vmscan.c > +++ b/mm/vmscan.c > @@ -2113,16 +2113,14 @@ static void get_scan_count(struct lruvec *lruvec, > struct mem_cgroup *memcg, > u64 denominator = 0;

Re: [patch v2] mm, vmscan: avoid thrashing anon lru when free + file is low

On Wed, 3 May 2017, Michal Hocko wrote: > diff --git a/mm/vmscan.c b/mm/vmscan.c > index 24efcc20af91..f3ec8760dc06 100644 > --- a/mm/vmscan.c > +++ b/mm/vmscan.c > @@ -2113,16 +2113,14 @@ static void get_scan_count(struct lruvec *lruvec, > struct mem_cgroup *memcg, > u64 denominator = 0;

Re: [RFC PATCH] dax: add badblocks check to Device DAX

On Wed, 2017-05-03 at 14:48 -0700, Dan Williams wrote: > On Wed, May 3, 2017 at 11:46 AM, Kani, Toshimitsu > wrote: > > On Wed, 2017-05-03 at 09:30 -0700, Dan Williams wrote: > > > On Wed, May 3, 2017 at 9:09 AM, Kani, Toshimitsu > > com> > > > wrote: > > >

Re: [RFC PATCH] dax: add badblocks check to Device DAX

On Wed, 2017-05-03 at 14:48 -0700, Dan Williams wrote: > On Wed, May 3, 2017 at 11:46 AM, Kani, Toshimitsu > wrote: > > On Wed, 2017-05-03 at 09:30 -0700, Dan Williams wrote: > > > On Wed, May 3, 2017 at 9:09 AM, Kani, Toshimitsu > > com> > > > wrote: > > > > On Wed, 2017-05-03 at 08:52 -0700,

Re: [PATCH v2 0/3] Extend the vTPM proxy driver to pass locality to emulator

On Fri, Apr 28, 2017 at 09:02:15AM -0400, Stefan Berger wrote: > The purpose of this series of patches is to enable the passing of the locality > a command is executing in to a TPM emulator. To enable this we introduce a new > flag for the device creation ioctl that requests that the locality be

Re: [PATCH v2 0/3] Extend the vTPM proxy driver to pass locality to emulator

On Fri, Apr 28, 2017 at 09:02:15AM -0400, Stefan Berger wrote: > The purpose of this series of patches is to enable the passing of the locality > a command is executing in to a TPM emulator. To enable this we introduce a new > flag for the device creation ioctl that requests that the locality be

Re: [PATCH v2 3/3] tpm: vtpm_proxy: Add ioctl to request locality prepended to command

On Fri, Apr 28, 2017 at 09:02:18AM -0400, Stefan Berger wrote: > Add an ioctl to request that the locality be prepended to every TPM > command. Don't really understand this change. Why locality is prenpended? Where is the ioctl declaration in this commit? > Signed-off-by: Stefan Berger

Re: [PATCH v2 3/3] tpm: vtpm_proxy: Add ioctl to request locality prepended to command

On Fri, Apr 28, 2017 at 09:02:18AM -0400, Stefan Berger wrote: > Add an ioctl to request that the locality be prepended to every TPM > command. Don't really understand this change. Why locality is prenpended? Where is the ioctl declaration in this commit? > Signed-off-by: Stefan Berger > --- >

linux-next: build warning after merge of the drm tree

Hi all, Sorry that I did not notice this at the time ... This is now in Linus' tree. After merging the drm tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: arch/arm/configs/multi_v7_defconfig:596:warning: symbol value 'm' invalid for ROCKCHIP_ANALOGIX_DP

linux-next: build warning after merge of the drm tree

Hi all, Sorry that I did not notice this at the time ... This is now in Linus' tree. After merging the drm tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: arch/arm/configs/multi_v7_defconfig:596:warning: symbol value 'm' invalid for ROCKCHIP_ANALOGIX_DP

Re: [PATCH v2 1/3] tpm: vtpm_proxy: Add ioctl to get supported flags

On Fri, Apr 28, 2017 at 09:02:16AM -0400, Stefan Berger wrote: > Add an ioctl to get the supported flags. > > Signed-off-by: Stefan Berger The commit message is a bit lacking on explaining things like why we need it. > --- > drivers/char/tpm/tpm_vtpm_proxy.c | 29

Re: [PATCH v2 1/3] tpm: vtpm_proxy: Add ioctl to get supported flags

On Fri, Apr 28, 2017 at 09:02:16AM -0400, Stefan Berger wrote: > Add an ioctl to get the supported flags. > > Signed-off-by: Stefan Berger The commit message is a bit lacking on explaining things like why we need it. > --- > drivers/char/tpm/tpm_vtpm_proxy.c | 29 +

Re: [PATCH v8 2/7] doc: Add documentation for Coresight CPU debug

On Tue, May 02, 2017 at 06:08:32PM +0800, Leo Yan wrote: > Update kernel-parameters.txt to add new parameter: > coresight_cpu_debug.enable is a knob to enable debugging at boot time. > > Add detailed documentation, which contains the implementation, Mike > Leach excellent summary for "clock and

Re: [PATCH 1/2] dt/bindings: Add bindings for Broadcom STB DRAM Sensors

Hi Rob, On 27 April 2017 at 15:00, Florian Fainelli wrote: > On 04/27/2017 02:57 PM, Rob Herring wrote: > +Optional properties: > + - cell-index: the index of the DPFE instance; will default to 0 if not > set >> >> Don't use cell-index. It's not a valid

Re: [PATCH v8 2/7] doc: Add documentation for Coresight CPU debug

On Tue, May 02, 2017 at 06:08:32PM +0800, Leo Yan wrote: > Update kernel-parameters.txt to add new parameter: > coresight_cpu_debug.enable is a knob to enable debugging at boot time. > > Add detailed documentation, which contains the implementation, Mike > Leach excellent summary for "clock and

Re: [PATCH 1/2] dt/bindings: Add bindings for Broadcom STB DRAM Sensors

Hi Rob, On 27 April 2017 at 15:00, Florian Fainelli wrote: > On 04/27/2017 02:57 PM, Rob Herring wrote: > +Optional properties: > + - cell-index: the index of the DPFE instance; will default to 0 if not > set >> >> Don't use cell-index. It's not a valid property for FDT (only real

Re: [PATCH 1/3] ARM: dts: imx6qdl-nitrogen6_max: fix rv4162 compatible

On 03/05/2017 at 19:14:42 -0300, Fabio Estevam wrote: > Hi Shawn, > > On Wed, May 3, 2017 at 5:50 AM, Shawn Guo wrote: > > >> rtc: rtc@68 { > >> - compatible = "st,rv4162"; > >> + compatible = "microcrystal,rv4162"; > > > > The compatible is

[PATCH v3 4/6] Documentation/dev-tools: Add kselftest

Move kselftest.txt to dev-tools/kselftest.rst . Signed-off-by: Mickaël Salaün Acked-by: Kees Cook Cc: Jonathan Corbet Cc: Shuah Khan --- Documentation/00-INDEX | 2 --

Re: [PATCH 1/3] ARM: dts: imx6qdl-nitrogen6_max: fix rv4162 compatible

On 03/05/2017 at 19:14:42 -0300, Fabio Estevam wrote: > Hi Shawn, > > On Wed, May 3, 2017 at 5:50 AM, Shawn Guo wrote: > > >> rtc: rtc@68 { > >> - compatible = "st,rv4162"; > >> + compatible = "microcrystal,rv4162"; > > > > The compatible is not documented? > >

[PATCH v3 4/6] Documentation/dev-tools: Add kselftest

Move kselftest.txt to dev-tools/kselftest.rst . Signed-off-by: Mickaël Salaün Acked-by: Kees Cook Cc: Jonathan Corbet Cc: Shuah Khan --- Documentation/00-INDEX | 2 -- Documentation/{kselftest.txt => dev-tools/kselftest.rst} | 0 2 files changed, 2

[PATCH v3 3/6] selftests/seccomp: Force rebuild according to dependencies

Rebuild the seccomp tests when kselftest_harness.h is updated. Signed-off-by: Mickaël Salaün Acked-by: Kees Cook Cc: Andy Lutomirski Cc: Shuah Khan Cc: Will Drewry ---

[PATCH v3 3/6] selftests/seccomp: Force rebuild according to dependencies

Rebuild the seccomp tests when kselftest_harness.h is updated. Signed-off-by: Mickaël Salaün Acked-by: Kees Cook Cc: Andy Lutomirski Cc: Shuah Khan Cc: Will Drewry --- tools/testing/selftests/seccomp/Makefile | 2 ++ 1 file changed, 2 insertions(+) diff --git

[PATCH v3 6/6] Documentation/dev-tools: Add kselftest_harness documentation

Add metadata to kselftest_harness.h to be able to include the comments in the Sphinx documentation. Changes since v2: * add reference to the full documentation in the header file (suggested by Kees Cook) Signed-off-by: Mickaël Salaün Acked-by: Kees Cook

[PATCH v3 6/6] Documentation/dev-tools: Add kselftest_harness documentation

Add metadata to kselftest_harness.h to be able to include the comments in the Sphinx documentation. Changes since v2: * add reference to the full documentation in the header file (suggested by Kees Cook) Signed-off-by: Mickaël Salaün Acked-by: Kees Cook Cc: Andy Lutomirski Cc: Jonathan

[PATCH v3 5/6] Documentation/dev-tools: Use reStructuredText markups for kselftest

Include and convert kselftest to the Sphinx format. Changes since v2: * lighten the modifications (suggested by Kees Cook) Signed-off-by: Mickaël Salaün Acked-by: Kees Cook Cc: Jonathan Corbet Cc: Shuah Khan ---

[PATCH v3 5/6] Documentation/dev-tools: Use reStructuredText markups for kselftest

Include and convert kselftest to the Sphinx format. Changes since v2: * lighten the modifications (suggested by Kees Cook) Signed-off-by: Mickaël Salaün Acked-by: Kees Cook Cc: Jonathan Corbet Cc: Shuah Khan --- Documentation/dev-tools/index.rst | 1 +

[PATCH v3 1/6] selftests: Make test_harness.h more generally available

The seccomp/test_harness.h file contains useful helpers to build tests. Moving it to the selftest directory should benefit to other test components. Keep seccomp maintainers for this file. Changes since v1: * rename to kselftest_harness.h (suggested by Shuah Khan) * keep maintainers

[PATCH v3 2/6] selftests: Cosmetic renames in kselftest_harness.h

Keep the content consistent with the new name. Signed-off-by: Mickaël Salaün Acked-by: Kees Cook Cc: Andy Lutomirski Cc: Shuah Khan Cc: Will Drewry ---

[PATCH v3 1/6] selftests: Make test_harness.h more generally available

The seccomp/test_harness.h file contains useful helpers to build tests. Moving it to the selftest directory should benefit to other test components. Keep seccomp maintainers for this file. Changes since v1: * rename to kselftest_harness.h (suggested by Shuah Khan) * keep maintainers

[PATCH v3 2/6] selftests: Cosmetic renames in kselftest_harness.h

Keep the content consistent with the new name. Signed-off-by: Mickaël Salaün Acked-by: Kees Cook Cc: Andy Lutomirski Cc: Shuah Khan Cc: Will Drewry --- tools/testing/selftests/kselftest_harness.h | 11 ++- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git

[PATCH v3 0/6] Add kselftest_harness.h

Hi, This third patch series make the seccomp/test_harness.h more generally available [1] and update the kselftest documentation with the Sphinx format. It also improve the Makefile of seccomp tests to take into account any kselftest_harness.h update. [1]

[PATCH v3 0/6] Add kselftest_harness.h

Hi, This third patch series make the seccomp/test_harness.h more generally available [1] and update the kselftest documentation with the Sphinx format. It also improve the Makefile of seccomp tests to take into account any kselftest_harness.h update. [1]

Re: [PATCH v8 5/7] coresight: add support for CPU debug module

On Tue, May 02, 2017 at 06:08:35PM +0800, Leo Yan wrote: > Coresight includes debug module and usually the module connects with CPU > debug logic. ARMv8 architecture reference manual (ARM DDI 0487A.k) has > description for related info in "Part H: External Debug". > > Chapter H7 "The Sample-based

Re: [PATCH v8 5/7] coresight: add support for CPU debug module

On Tue, May 02, 2017 at 06:08:35PM +0800, Leo Yan wrote: > Coresight includes debug module and usually the module connects with CPU > debug logic. ARMv8 architecture reference manual (ARM DDI 0487A.k) has > description for related info in "Part H: External Debug". > > Chapter H7 "The Sample-based

Re: powerpc/powernv: Fix TCE kill on NVLink2

On Wed, 2017-05-03 at 03:24:08 UTC, Alistair Popple wrote: > Commit 616badd2fb49 ("powerpc/powernv: Use OPAL call for TCE kill on > NVLink2") forced all TCE kills to go via the OPAL call for > NVLink2. However the PHB3 implementation of TCE kill was still being > called directly from some

Re: powerpc/powernv: Fix TCE kill on NVLink2

On Wed, 2017-05-03 at 03:24:08 UTC, Alistair Popple wrote: > Commit 616badd2fb49 ("powerpc/powernv: Use OPAL call for TCE kill on > NVLink2") forced all TCE kills to go via the OPAL call for > NVLink2. However the PHB3 implementation of TCE kill was still being > called directly from some

mmotm 2017-05-03-15-16 uploaded

The mm-of-the-moment snapshot 2017-05-03-15-16 has been uploaded to http://www.ozlabs.org/~akpm/mmotm/ mmotm-readme.txt says README for mm-of-the-moment: http://www.ozlabs.org/~akpm/mmotm/ This is a snapshot of my -mm patch queue. Uploaded at random hopefully more than once a week. You

mmotm 2017-05-03-15-16 uploaded

The mm-of-the-moment snapshot 2017-05-03-15-16 has been uploaded to http://www.ozlabs.org/~akpm/mmotm/ mmotm-readme.txt says README for mm-of-the-moment: http://www.ozlabs.org/~akpm/mmotm/ This is a snapshot of my -mm patch queue. Uploaded at random hopefully more than once a week. You

Re: [PATCH 1/3] ARM: dts: imx6qdl-nitrogen6_max: fix rv4162 compatible

On 03/05/2017 at 16:50:12 +0800, Shawn Guo wrote: > On Wed, Apr 19, 2017 at 10:22:02PM +0200, Alexandre Belloni wrote: > > The rv4162 vendor is microcrystal, not ST. > > > > Signed-off-by: Alexandre Belloni > > --- > >

Re: [PATCH 1/3] ARM: dts: imx6qdl-nitrogen6_max: fix rv4162 compatible

On 03/05/2017 at 16:50:12 +0800, Shawn Guo wrote: > On Wed, Apr 19, 2017 at 10:22:02PM +0200, Alexandre Belloni wrote: > > The rv4162 vendor is microcrystal, not ST. > > > > Signed-off-by: Alexandre Belloni > > --- > > arch/arm/boot/dts/imx6qdl-nitrogen6_max.dtsi | 2 +- > > 1 file changed, 1

[PATCH 1/3] kvm: x86: Add a hook for arch specific dirty logging emulation

When KVM updates accessed/dirty bits, this hook can be used to invoke an arch specific function that implements/emulates dirty logging such as PML. Signed-off-by: Bandan Das --- arch/x86/include/asm/kvm_host.h | 2 ++ arch/x86/kvm/mmu.c | 15 +++

[PATCH 1/3] kvm: x86: Add a hook for arch specific dirty logging emulation

When KVM updates accessed/dirty bits, this hook can be used to invoke an arch specific function that implements/emulates dirty logging such as PML. Signed-off-by: Bandan Das --- arch/x86/include/asm/kvm_host.h | 2 ++ arch/x86/kvm/mmu.c | 15 +++ arch/x86/kvm/mmu.h

[PATCH 2/3] nVMX: Implement emulated Page Modification Logging

With EPT A/D enabled, processor access to L2 guest paging structures will result in a write violation. When this happens, write the GUEST_PHYSICAL_ADDRESS to the pml buffer provided by L1 if the access is write and the dirty bit is being set. This patch also adds necessary checks during VMEntry

[PATCH 3/3] nVMX: Advertise PML to L1 hypervisor

Advertise the PML bit in vmcs12 but clear it out before running L2 since we don't depend on hardware support for PML emulation. Signed-off-by: Bandan Das --- arch/x86/kvm/vmx.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/arch/x86/kvm/vmx.c

[PATCH 2/3] nVMX: Implement emulated Page Modification Logging

With EPT A/D enabled, processor access to L2 guest paging structures will result in a write violation. When this happens, write the GUEST_PHYSICAL_ADDRESS to the pml buffer provided by L1 if the access is write and the dirty bit is being set. This patch also adds necessary checks during VMEntry

[PATCH 3/3] nVMX: Advertise PML to L1 hypervisor

Advertise the PML bit in vmcs12 but clear it out before running L2 since we don't depend on hardware support for PML emulation. Signed-off-by: Bandan Das --- arch/x86/kvm/vmx.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c index

[PATCH 0/3] nVMX: Emulated Page Modification Logging for Nested Virtualization

These patches implement PML on top of EPT A/D emulation (ae1e2d1082ae). When dirty bit is being set, we write the gpa to the buffer provided by L1. If the index overflows, we just change the exit reason before running L1. Bandan Das (3): kvm: x86: Add a hook for arch specific dirty logging

[PATCH 0/3] nVMX: Emulated Page Modification Logging for Nested Virtualization

These patches implement PML on top of EPT A/D emulation (ae1e2d1082ae). When dirty bit is being set, we write the gpa to the buffer provided by L1. If the index overflows, we just change the exit reason before running L1. Bandan Das (3): kvm: x86: Add a hook for arch specific dirty logging

Re: [PATCH 1/3] ARM: dts: imx6qdl-nitrogen6_max: fix rv4162 compatible

Hi Shawn, On Wed, May 3, 2017 at 5:50 AM, Shawn Guo wrote: >> rtc: rtc@68 { >> - compatible = "st,rv4162"; >> + compatible = "microcrystal,rv4162"; > > The compatible is not documented? This compatible has been added in a897bf138c9b443 ("rtc:

Re: [PATCH 1/3] ARM: dts: imx6qdl-nitrogen6_max: fix rv4162 compatible

Hi Shawn, On Wed, May 3, 2017 at 5:50 AM, Shawn Guo wrote: >> rtc: rtc@68 { >> - compatible = "st,rv4162"; >> + compatible = "microcrystal,rv4162"; > > The compatible is not documented? This compatible has been added in a897bf138c9b443 ("rtc: m41t80: Add proper

[GIT PULL] first round of SCSI updates for the 4.11+ merge window

This update includes the usual round of major driver updates (hisi_sas, ufs, fnic, cxlflash, be2iscsi, ipr, stex). There's also the usual amount of cosmetic and spelling stuff. The major thing you should be aware of is that there's a clash between a char dev change in the char-misc tree (adding

[GIT PULL] first round of SCSI updates for the 4.11+ merge window

This update includes the usual round of major driver updates (hisi_sas, ufs, fnic, cxlflash, be2iscsi, ipr, stex). There's also the usual amount of cosmetic and spelling stuff. The major thing you should be aware of is that there's a clash between a char dev change in the char-misc tree (adding

Re: net/ipv6: GPF in rt6_device_match

On 5/3/17 4:02 PM, Cong Wang wrote: > On Wed, May 3, 2017 at 11:22 AM, David Ahern wrote: >> On 5/3/17 11:02 AM, Cong Wang wrote: >>> A quick glance shows we need to simply check local->rt6i_idev >>> since we do the same check for sprt right above. >> >> As I recall, rt6i_idev

Re: net/ipv6: GPF in rt6_device_match

On 5/3/17 4:02 PM, Cong Wang wrote: > On Wed, May 3, 2017 at 11:22 AM, David Ahern wrote: >> On 5/3/17 11:02 AM, Cong Wang wrote: >>> A quick glance shows we need to simply check local->rt6i_idev >>> since we do the same check for sprt right above. >> >> As I recall, rt6i_idev is set for all

Re: [PATCH 03/13] sparc/PCI: Reserve legacy mmio after PCI mmio

On Thu, Apr 20, 2017 at 10:04:50PM -0700, Yinghai Lu wrote: > On one system found bunch of claim resource fail from pci device. > pci_sun4v f02b894c: PCI host bridge to bus :00 > pci_bus :00: root bus resource [io 0x2007e-0x2007e0fff] (bus > address [0x-0xfff]) >

Re: [PATCH 03/13] sparc/PCI: Reserve legacy mmio after PCI mmio

On Thu, Apr 20, 2017 at 10:04:50PM -0700, Yinghai Lu wrote: > On one system found bunch of claim resource fail from pci device. > pci_sun4v f02b894c: PCI host bridge to bus :00 > pci_bus :00: root bus resource [io 0x2007e-0x2007e0fff] (bus > address [0x-0xfff]) >

Re: net/ipv6: GPF in rt6_device_match

On Wed, May 3, 2017 at 11:22 AM, David Ahern wrote: > On 5/3/17 11:02 AM, Cong Wang wrote: >> A quick glance shows we need to simply check local->rt6i_idev >> since we do the same check for sprt right above. > > As I recall, rt6i_idev is set for all routes except null_entry and

Re: net/ipv6: GPF in rt6_device_match

On Wed, May 3, 2017 at 11:22 AM, David Ahern wrote: > On 5/3/17 11:02 AM, Cong Wang wrote: >> A quick glance shows we need to simply check local->rt6i_idev >> since we do the same check for sprt right above. > > As I recall, rt6i_idev is set for all routes except null_entry and it is > not set on

Re: [PATCH v2 1/2] drm: Introduce crtc->mode_valid() callback

On Fri, Apr 28, 2017 at 02:47:11PM +0100, Jose Abreu wrote: > Some crtc's may have restrictions in the mode they can display. In > this patch a new callback (crtc->mode_valid()) is introduced that > is called at the same stage of connector->mode_valid() callback. > > This shall be implemented if

Re: [PATCH v2 1/2] drm: Introduce crtc->mode_valid() callback

On Fri, Apr 28, 2017 at 02:47:11PM +0100, Jose Abreu wrote: > Some crtc's may have restrictions in the mode they can display. In > this patch a new callback (crtc->mode_valid()) is introduced that > is called at the same stage of connector->mode_valid() callback. > > This shall be implemented if

Re: [RFC PATCH] dax: add badblocks check to Device DAX

On 05/03/2017 02:48 PM, Dan Williams wrote: > On Wed, May 3, 2017 at 11:46 AM, Kani, Toshimitsu wrote: >> On Wed, 2017-05-03 at 09:30 -0700, Dan Williams wrote: >>> On Wed, May 3, 2017 at 9:09 AM, Kani, Toshimitsu >>> wrote: On Wed, 2017-05-03 at

Re: [RFC PATCH] dax: add badblocks check to Device DAX

On 05/03/2017 02:48 PM, Dan Williams wrote: > On Wed, May 3, 2017 at 11:46 AM, Kani, Toshimitsu wrote: >> On Wed, 2017-05-03 at 09:30 -0700, Dan Williams wrote: >>> On Wed, May 3, 2017 at 9:09 AM, Kani, Toshimitsu >>> wrote: On Wed, 2017-05-03 at 08:52 -0700, Dan Williams wrote: > On

Re: [PATCH 2/2] sched/fair: Always propagate runnable_load_avg

On Wed, May 03, 2017 at 03:09:38PM +0200, Peter Zijlstra wrote: > On Wed, May 03, 2017 at 12:37:37PM +0200, Vincent Guittot wrote: > > On 3 May 2017 at 11:37, Peter Zijlstra wrote: > > > > Of course, it could be I overlooked something, in which case, please > > > tell :-) >

Re: [PATCH 2/2] sched/fair: Always propagate runnable_load_avg

On Wed, May 03, 2017 at 03:09:38PM +0200, Peter Zijlstra wrote: > On Wed, May 03, 2017 at 12:37:37PM +0200, Vincent Guittot wrote: > > On 3 May 2017 at 11:37, Peter Zijlstra wrote: > > > > Of course, it could be I overlooked something, in which case, please > > > tell :-) > > > > That's mainly

Re: [RFC PATCH] dax: add badblocks check to Device DAX

On Wed, May 3, 2017 at 11:46 AM, Kani, Toshimitsu wrote: > On Wed, 2017-05-03 at 09:30 -0700, Dan Williams wrote: >> On Wed, May 3, 2017 at 9:09 AM, Kani, Toshimitsu >> wrote: >> > On Wed, 2017-05-03 at 08:52 -0700, Dan Williams wrote: >> > > On Wed, May

Re: [RFC PATCH] dax: add badblocks check to Device DAX

On Wed, May 3, 2017 at 11:46 AM, Kani, Toshimitsu wrote: > On Wed, 2017-05-03 at 09:30 -0700, Dan Williams wrote: >> On Wed, May 3, 2017 at 9:09 AM, Kani, Toshimitsu >> wrote: >> > On Wed, 2017-05-03 at 08:52 -0700, Dan Williams wrote: >> > > On Wed, May 3, 2017 at 8:31 AM, Toshi Kani >> > >

linux-next: incomplete commits in the ceph tree

Hi Sage, I noticed several new commits in the ceph tree today that have no Singn-off-by from their committer (Ilya). :-( -- Cheers, Stephen Rothwell

linux-next: incomplete commits in the ceph tree

Hi Sage, I noticed several new commits in the ceph tree today that have no Singn-off-by from their committer (Ilya). :-( -- Cheers, Stephen Rothwell

Re: [PATCH] arm64: Add translation functions for /dev/mem read/write

On 5/3/2017 2:18 PM, Leif Lindholm wrote: > On Wed, May 03, 2017 at 11:07:45AM -0600, Goel, Sameer wrote: >> On 5/3/2017 5:26 AM, Will Deacon wrote: >>> [adding some /dev/mem fans to cc] >>> >>> On Tue, May 02, 2017 at 02:28:05PM -0600, Sameer Goel wrote: Port architecture specific xlate

Re: [PATCH] arm64: Add translation functions for /dev/mem read/write

On 5/3/2017 2:18 PM, Leif Lindholm wrote: > On Wed, May 03, 2017 at 11:07:45AM -0600, Goel, Sameer wrote: >> On 5/3/2017 5:26 AM, Will Deacon wrote: >>> [adding some /dev/mem fans to cc] >>> >>> On Tue, May 02, 2017 at 02:28:05PM -0600, Sameer Goel wrote: Port architecture specific xlate

Re: Review request: draft ioctl_userfaultfd(2) manual page

On Fri, Apr 21, 2017 at 11:11:18AM +0200, Michael Kerrisk (man-pages) wrote: > Hello Mike, > Hello Andrea (we need your help!), Sorry for not answering sooner! (I had a vacation last week) > > On 03/22/2017 02:54 PM, Mike Rapoport wrote: > >>The various ioctl(2) operations are

Re: Review request: draft ioctl_userfaultfd(2) manual page

On Fri, Apr 21, 2017 at 11:11:18AM +0200, Michael Kerrisk (man-pages) wrote: > Hello Mike, > Hello Andrea (we need your help!), Sorry for not answering sooner! (I had a vacation last week) > > On 03/22/2017 02:54 PM, Mike Rapoport wrote: > >>The various ioctl(2) operations are

Re: [PATCH v2 1/2] sched/fair: Fix how load gets propagated from cfs_rq to its sched_entity

Hello, Peter. On Wed, May 03, 2017 at 08:00:28PM +0200, Peter Zijlstra wrote: > Just FUDGE2 on its own seems to be the best on my system and is a change > that makes sense (and something Paul recently pointed out as well). > > The implementation isn't particularly pretty or fast, but should >

Re: [PATCH v2 1/2] sched/fair: Fix how load gets propagated from cfs_rq to its sched_entity

Hello, Peter. On Wed, May 03, 2017 at 08:00:28PM +0200, Peter Zijlstra wrote: > Just FUDGE2 on its own seems to be the best on my system and is a change > that makes sense (and something Paul recently pointed out as well). > > The implementation isn't particularly pretty or fast, but should >

Re: [PATCH 3/9] VFS: Introduce a mount context

On Wed, May 03 2017, David Howells wrote: > fs_type->fsopen() is called to set it up. fs_type->mc_size says how much > should be added on to the mount context for the filesystem's use. This is repeated several times in the documentation, but the code says that ->mc_size

Re: [PATCH 3/9] VFS: Introduce a mount context

On Wed, May 03 2017, David Howells wrote: > fs_type->fsopen() is called to set it up. fs_type->mc_size says how much > should be added on to the mount context for the filesystem's use. This is repeated several times in the documentation, but the code says that ->mc_size should be the full size

Re: [PATCH 3/9] VFS: Introduce a mount context

(adding Julia Lawall and cocci) On Wed, 2017-05-03 at 13:38 -0700, Matthew Wilcox wrote: > On Wed, May 03, 2017 at 11:26:38AM -0700, Joe Perches wrote: > > On Wed, 2017-05-03 at 14:13 -0400, Jeff Layton wrote: > > > On Wed, 2017-05-03 at 17:04 +0100, David Howells wrote: > > > > +

Re: [PATCH 3/9] VFS: Introduce a mount context

(adding Julia Lawall and cocci) On Wed, 2017-05-03 at 13:38 -0700, Matthew Wilcox wrote: > On Wed, May 03, 2017 at 11:26:38AM -0700, Joe Perches wrote: > > On Wed, 2017-05-03 at 14:13 -0400, Jeff Layton wrote: > > > On Wed, 2017-05-03 at 17:04 +0100, David Howells wrote: > > > > +

[PATCH v2] perf report: distinguish between inliners in the same function

When different functions get inlined into the same function, we want to show them individually in the reports. But when we group by function, we would aggregate all IPs and would only keep the first one in that function. E.g. for C++ code like the following: ~ #include #include #include

[PATCH v2] perf report: distinguish between inliners in the same function

When different functions get inlined into the same function, we want to show them individually in the reports. But when we group by function, we would aggregate all IPs and would only keep the first one in that function. E.g. for C++ code like the following: ~ #include #include #include

Re: [RFC PATCH] mtd: spi-nor: handle signal case as failure

meout case. > > Patch was compile tested with: stm32_defconfig +CONFIG_MTD=y, > CONFIG_MTD_SPI_NOR=y, > CONFIG_SPI_STM32_QUADSPI=m > > Patch is against v4.11-rc8 (localversion-next is next-20170503) > > drivers/mtd/spi-nor/stm32-quadspi.c | 10 -- > 1

Re: [RFC PATCH] mtd: spi-nor: handle signal case as failure

gt; Patch was compile tested with: stm32_defconfig +CONFIG_MTD=y, > CONFIG_MTD_SPI_NOR=y, > CONFIG_SPI_STM32_QUADSPI=m > > Patch is against v4.11-rc8 (localversion-next is next-20170503) > > drivers/mtd/spi-nor/stm32-quadspi.c | 10 -- > 1 files changed, 10 insertions(+),

Re: [PATCH] ARM: Fix __show_regs output timestamps

On Wed, May 03, 2017 at 12:44:11PM -0700, Joe Perches wrote: > On Wed, 2017-05-03 at 20:23 +0100, Russell King - ARM Linux wrote: > > On Wed, Apr 26, 2017 at 10:39:49AM -0700, Joe Perches wrote: > > > Multiple line formats are not preferred as the second and > > > subsequent lines may not have

Re: [PATCH] ARM: Fix __show_regs output timestamps

On Wed, May 03, 2017 at 12:44:11PM -0700, Joe Perches wrote: > On Wed, 2017-05-03 at 20:23 +0100, Russell King - ARM Linux wrote: > > On Wed, Apr 26, 2017 at 10:39:49AM -0700, Joe Perches wrote: > > > Multiple line formats are not preferred as the second and > > > subsequent lines may not have

Re: [PATCH 2/5] mtd: nand: gpmi: add i.MX 7 SoC support

On 2017-05-02 04:18, Marek Vasut wrote: > On 05/02/2017 11:17 AM, Boris Brezillon wrote: >> Hi Han, >> >> On Fri, 21 Apr 2017 13:29:16 -0500 >> Han Xu wrote: >> > But then, adding the type would only require 2-3 lines of change if I add it to the

Re: [PATCH 2/5] mtd: nand: gpmi: add i.MX 7 SoC support

On 2017-05-02 04:18, Marek Vasut wrote: > On 05/02/2017 11:17 AM, Boris Brezillon wrote: >> Hi Han, >> >> On Fri, 21 Apr 2017 13:29:16 -0500 >> Han Xu wrote: >> > But then, adding the type would only require 2-3 lines of change if I add it to the GPMI_IS_MX6 macro... >>>

Re: Future of liblockdep

On Wed, 2017-05-03 at 21:00 +, alexander.le...@verizon.com wrote: > On Wed, May 03, 2017 at 09:13:57PM +0100, Ben Hutchings wrote: > > liblockdep hasn't been buildable since (I think) Linux 4.6.  I sent > > Sasha fixes for that last June and he included these in a pull request > > to Ingo, but

Re: Future of liblockdep

On Wed, 2017-05-03 at 21:00 +, alexander.le...@verizon.com wrote: > On Wed, May 03, 2017 at 09:13:57PM +0100, Ben Hutchings wrote: > > liblockdep hasn't been buildable since (I think) Linux 4.6.  I sent > > Sasha fixes for that last June and he included these in a pull request > > to Ingo, but

Re: [PATCH 3/9] VFS: Introduce a mount context

Matthew Wilcox wrote: > On Wed, May 03, 2017 at 11:26:38AM -0700, Joe Perches wrote: > > On Wed, 2017-05-03 at 14:13 -0400, Jeff Layton wrote: > > > On Wed, 2017-05-03 at 17:04 +0100, David Howells wrote: > > > > + oo = kmalloc((opts->num_mnt_opts + 1) *

Re: [PATCH 3/9] VFS: Introduce a mount context

Matthew Wilcox wrote: > On Wed, May 03, 2017 at 11:26:38AM -0700, Joe Perches wrote: > > On Wed, 2017-05-03 at 14:13 -0400, Jeff Layton wrote: > > > On Wed, 2017-05-03 at 17:04 +0100, David Howells wrote: > > > > + oo = kmalloc((opts->num_mnt_opts + 1) * sizeof(char *), > > > > +

Re: [PATCH V8 4/5] PCI/ASPM: save power on values during bridge init

On Tue, May 02, 2017 at 12:02:53PM +, Patel, Mayurkumar wrote: > >On Fri, Apr 21, 2017 at 2:46 AM, Patel, Mayurkumar > > wrote: > >>>On 4/17/2017 12:38 PM, Bjorn Helgaas wrote: > > Like you said, what do we do by default is the question. Should we opt > >

Re: [PATCH V8 4/5] PCI/ASPM: save power on values during bridge init

On Tue, May 02, 2017 at 12:02:53PM +, Patel, Mayurkumar wrote: > >On Fri, Apr 21, 2017 at 2:46 AM, Patel, Mayurkumar > > wrote: > >>>On 4/17/2017 12:38 PM, Bjorn Helgaas wrote: > > Like you said, what do we do by default is the question. Should we opt > > for safe like we are doing, or

Re: Future of liblockdep

On Wed, May 03, 2017 at 09:13:57PM +0100, Ben Hutchings wrote: > liblockdep hasn't been buildable since (I think) Linux 4.6. I sent > Sasha fixes for that last June and he included these in a pull request > to Ingo, but somehow they never reached mainline. Linux 4.8 broke > liblockdep further,

Re: Future of liblockdep

On Wed, May 03, 2017 at 09:13:57PM +0100, Ben Hutchings wrote: > liblockdep hasn't been buildable since (I think) Linux 4.6. I sent > Sasha fixes for that last June and he included these in a pull request > to Ingo, but somehow they never reached mainline. Linux 4.8 broke > liblockdep further,

Re: [PATCH v4 1/2] dt-bindings: Document the STM32 QSPI bindings

Le 02/05/2017 à 03:09, Brian Norris a écrit : > On Sun, Apr 16, 2017 at 06:53:06PM +0200, Cyrille Pitchen wrote: >> Hi all, >> >> Rob, is this version ok for you? If so, I can take it into the >> github/spi-nor tree. > > I see this was missing from your pull request. Rob has since acked, > so...

Re: [PATCH v4 1/2] dt-bindings: Document the STM32 QSPI bindings

Le 02/05/2017 à 03:09, Brian Norris a écrit : > On Sun, Apr 16, 2017 at 06:53:06PM +0200, Cyrille Pitchen wrote: >> Hi all, >> >> Rob, is this version ok for you? If so, I can take it into the >> github/spi-nor tree. > > I see this was missing from your pull request. Rob has since acked, > so...

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