[PATCH 9/9] vfs: intercept fsync on overlay files

Fsync is really an inode operation (AFAICS) so a doing it on a O_RDONLY file descriptor should flush any data written through an O_WRONLY file descriptor for example. To make this work correctly in case the file is copied up after being opened for read, intercept the fsync operation, similarly to

[PATCH 9/9] vfs: intercept fsync on overlay files

Fsync is really an inode operation (AFAICS) so a doing it on a O_RDONLY file descriptor should flush any data written through an O_WRONLY file descriptor for example. To make this work correctly in case the file is copied up after being opened for read, intercept the fsync operation, similarly to

[PATCH 7/9] ovl: intercept mmap on overlay files

... in order to handle the corner case when the file is copied up after being opened read-only and mapped shared. Can be verified with the following script: - 8< - - - - - 8< - - - - - 8< - - - - - 8< - - - - cd / rm -rf /tmp/ovl-rorw-test mkdir /tmp/ovl-rorw-test cd /tmp/ovl-rorw-test cat <<

Re: [PATCH V3 3/7] mm: reclaim MADV_FREE pages

Hi Minchan, On Fri, Feb 17, 2017 at 02:45:55PM +0900, Minchan Kim wrote: > On Thu, Feb 16, 2017 at 04:27:18PM -0800, Shaohua Li wrote: > > On Thu, Feb 16, 2017 at 01:40:18PM -0500, Johannes Weiner wrote: > > > On Tue, Feb 14, 2017 at 11:36:09AM -0800, Shaohua Li wrote: > > > > @@ -1419,11

[PATCH 7/9] ovl: intercept mmap on overlay files

... in order to handle the corner case when the file is copied up after being opened read-only and mapped shared. Can be verified with the following script: - 8< - - - - - 8< - - - - - 8< - - - - - 8< - - - - cd / rm -rf /tmp/ovl-rorw-test mkdir /tmp/ovl-rorw-test cd /tmp/ovl-rorw-test cat <<

Re: [PATCH V3 3/7] mm: reclaim MADV_FREE pages

Hi Minchan, On Fri, Feb 17, 2017 at 02:45:55PM +0900, Minchan Kim wrote: > On Thu, Feb 16, 2017 at 04:27:18PM -0800, Shaohua Li wrote: > > On Thu, Feb 16, 2017 at 01:40:18PM -0500, Johannes Weiner wrote: > > > On Tue, Feb 14, 2017 at 11:36:09AM -0800, Shaohua Li wrote: > > > > @@ -1419,11

[PATCH 6/9] mm: use helper for calling f_op->mmap()

Signed-off-by: Miklos Szeredi --- drivers/gpu/drm/i915/i915_gem_dmabuf.c | 2 +- drivers/gpu/drm/vgem/vgem_drv.c| 2 +- fs/coda/file.c | 2 +- include/linux/fs.h | 5 + ipc/shm.c | 2 +-

[PATCH 6/9] mm: use helper for calling f_op->mmap()

Signed-off-by: Miklos Szeredi --- drivers/gpu/drm/i915/i915_gem_dmabuf.c | 2 +- drivers/gpu/drm/vgem/vgem_drv.c| 2 +- fs/coda/file.c | 2 +- include/linux/fs.h | 5 + ipc/shm.c | 2 +- mm/mmap.c

Re: [PATCH v2 04/10] mm, page_alloc: count movable pages when stealing from pageblock

On 02/14/2017 07:10 PM, Johannes Weiner wrote: > > That makes sense to me. I have just one nit about the patch: > >> @@ -1981,10 +1994,29 @@ static void steal_suitable_fallback(struct zone >> *zone, struct page *page, >> return; >> } >> >> -pages =

Re: [PATCH v2 04/10] mm, page_alloc: count movable pages when stealing from pageblock

On 02/14/2017 07:10 PM, Johannes Weiner wrote: > > That makes sense to me. I have just one nit about the patch: > >> @@ -1981,10 +1994,29 @@ static void steal_suitable_fallback(struct zone >> *zone, struct page *page, >> return; >> } >> >> -pages =

[PATCH 8/9] vfs: use helper for calling f_op->fsync()

Signed-off-by: Miklos Szeredi --- fs/sync.c | 2 +- include/linux/fs.h | 6 ++ ipc/shm.c | 2 +- 3 files changed, 8 insertions(+), 2 deletions(-) diff --git a/fs/sync.c b/fs/sync.c index 2a54c1f22035..11ba023434b1 100644 --- a/fs/sync.c +++ b/fs/sync.c

[PATCH 8/9] vfs: use helper for calling f_op->fsync()

Signed-off-by: Miklos Szeredi --- fs/sync.c | 2 +- include/linux/fs.h | 6 ++ ipc/shm.c | 2 +- 3 files changed, 8 insertions(+), 2 deletions(-) diff --git a/fs/sync.c b/fs/sync.c index 2a54c1f22035..11ba023434b1 100644 --- a/fs/sync.c +++ b/fs/sync.c @@ -192,7 +192,7 @@

[PATCH 0/9] overlay: fix inconsistency of ro file after copy-up

A file is opened for read-only, opened read-write (resulting in a copy up) and modified. The data read back from the the read-only fd will be stale in this case (the read-only file descriptor still refers to the lower, unmodified file). This patchset fixes issues related to this corner case.

[PATCH 4/9] vfs: intercept reads to overlay files

...in order to handle the corner case when the file is copyied up after being opened read-only. Can be verified with the following script: - 8< - - - - - 8< - - - - - 8< - - - - - 8< - - - - cd / rm -rf /tmp/ovl-rorw-test mkdir /tmp/ovl-rorw-test cd /tmp/ovl-rorw-test mkdir -p mnt lower upper

[PATCH 2/9] vfs: pass type instead of fn to do_{loop,iter}_readv_writev()

Signed-off-by: Miklos Szeredi --- fs/read_write.c | 37 ++--- 1 file changed, 18 insertions(+), 19 deletions(-) diff --git a/fs/read_write.c b/fs/read_write.c index b7cf7e2cb8c5..c9da4492a462 100644 --- a/fs/read_write.c +++ b/fs/read_write.c

[PATCH 0/9] overlay: fix inconsistency of ro file after copy-up

A file is opened for read-only, opened read-write (resulting in a copy up) and modified. The data read back from the the read-only fd will be stale in this case (the read-only file descriptor still refers to the lower, unmodified file). This patchset fixes issues related to this corner case.

[PATCH 4/9] vfs: intercept reads to overlay files

...in order to handle the corner case when the file is copyied up after being opened read-only. Can be verified with the following script: - 8< - - - - - 8< - - - - - 8< - - - - - 8< - - - - cd / rm -rf /tmp/ovl-rorw-test mkdir /tmp/ovl-rorw-test cd /tmp/ovl-rorw-test mkdir -p mnt lower upper

[PATCH 2/9] vfs: pass type instead of fn to do_{loop,iter}_readv_writev()

Signed-off-by: Miklos Szeredi --- fs/read_write.c | 37 ++--- 1 file changed, 18 insertions(+), 19 deletions(-) diff --git a/fs/read_write.c b/fs/read_write.c index b7cf7e2cb8c5..c9da4492a462 100644 --- a/fs/read_write.c +++ b/fs/read_write.c @@ -23,9 +23,6 @@

Re: [PATCH] net: nvidia: forcedeth: use new api ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Tue, 14 Feb 2017 23:36:32 +0100 > The ethtool api {get|set}_settings is deprecated. > We move this driver to new api {get|set}_link_ksettings. > > As I don't have the hardware, I'd be very pleased if > someone may test this patch. > >

Re: [PATCH] net: nvidia: forcedeth: use new api ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Tue, 14 Feb 2017 23:36:32 +0100 > The ethtool api {get|set}_settings is deprecated. > We move this driver to new api {get|set}_link_ksettings. > > As I don't have the hardware, I'd be very pleased if > someone may test this patch. > > Signed-off-by: Philippe Reynes

[RFC 3/4] dt-bindings: iio: add support for GPIO triggers

Document Industrial I/O GPIO trigger support. Signed-off-by: Fabrice Gasnier --- .../bindings/iio/trigger/iio-trig-gpio.txt | 26 ++ 1 file changed, 26 insertions(+) create mode 100644

[RFC 3/4] dt-bindings: iio: add support for GPIO triggers

Document Industrial I/O GPIO trigger support. Signed-off-by: Fabrice Gasnier --- .../bindings/iio/trigger/iio-trig-gpio.txt | 26 ++ 1 file changed, 26 insertions(+) create mode 100644 Documentation/devicetree/bindings/iio/trigger/iio-trig-gpio.txt diff --git

[RFC 2/4] iio: trigger: add OF support

Provide OF support. Device drivers can get IIO triggers from dt. Introduce IIO trigger specifiers, so there are: - IIO trigger providers, e.g. dt nodes designated with #io-trigger-cells= - IIO trigger consumers, e.g. phandles listed in io-triggers = <...>. Those can be identified by names by

Re: [PATCH v2 4/5] iio: trigger: add support for STM32 EXTI triggers

On 02/11/2017 11:29 AM, Jonathan Cameron wrote: On 06/02/17 16:01, Fabrice Gasnier wrote: On 02/04/2017 12:39 PM, Jonathan Cameron wrote: On 03/02/17 19:40, Linus Walleij wrote: On Mon, Jan 30, 2017 at 3:33 PM, Fabrice Gasnier wrote: EXTi[0..15] gpio signal can be

[RFC 2/4] iio: trigger: add OF support

Provide OF support. Device drivers can get IIO triggers from dt. Introduce IIO trigger specifiers, so there are: - IIO trigger providers, e.g. dt nodes designated with #io-trigger-cells= - IIO trigger consumers, e.g. phandles listed in io-triggers = <...>. Those can be identified by names by

Re: [PATCH v2 4/5] iio: trigger: add support for STM32 EXTI triggers

On 02/11/2017 11:29 AM, Jonathan Cameron wrote: On 06/02/17 16:01, Fabrice Gasnier wrote: On 02/04/2017 12:39 PM, Jonathan Cameron wrote: On 03/02/17 19:40, Linus Walleij wrote: On Mon, Jan 30, 2017 at 3:33 PM, Fabrice Gasnier wrote: EXTi[0..15] gpio signal can be routed internally as

[RFC 0/4] iio: trigger: Add OF support and GPIO based trigger

Hi, I send this as an RFC, as I'm digging to try to get as generic as possible GPIO based trigger support, as discussed earlier in other patchset "Add EXTI GPIO trigger support to STM32 ADC": https://www.spinics.net/lists/arm-kernel/msg559091.html Following various comments on this, I sent this

[RFC 0/4] iio: trigger: Add OF support and GPIO based trigger

Hi, I send this as an RFC, as I'm digging to try to get as generic as possible GPIO based trigger support, as discussed earlier in other patchset "Add EXTI GPIO trigger support to STM32 ADC": https://www.spinics.net/lists/arm-kernel/msg559091.html Following various comments on this, I sent this

[RFC 1/4] dt-bindings: iio: introduce trigger providers, consumers

Document iio provider and consumer bindings. Signed-off-by: Fabrice Gasnier --- .../devicetree/bindings/iio/iio-bindings.txt | 37 ++ 1 file changed, 37 insertions(+) diff --git a/Documentation/devicetree/bindings/iio/iio-bindings.txt

[RFC 4/4] iio: trigger: add GPIO trigger

GPIOs can be used to generate triggers for any IIO device. Introduce generic GPIO trigger driver. It offers some options to tune polarity (e.g. rising/falling edge), and label so trigger name may be customized. By default, gpio triggers will be named gpiotrigX, where X is gpio number as returned

[RFC 1/4] dt-bindings: iio: introduce trigger providers, consumers

Document iio provider and consumer bindings. Signed-off-by: Fabrice Gasnier --- .../devicetree/bindings/iio/iio-bindings.txt | 37 ++ 1 file changed, 37 insertions(+) diff --git a/Documentation/devicetree/bindings/iio/iio-bindings.txt

[RFC 4/4] iio: trigger: add GPIO trigger

GPIOs can be used to generate triggers for any IIO device. Introduce generic GPIO trigger driver. It offers some options to tune polarity (e.g. rising/falling edge), and label so trigger name may be customized. By default, gpio triggers will be named gpiotrigX, where X is gpio number as returned

Re: [PATCH v2 0/4] PTP attribute handling cleanup

From: Richard Cochran Date: Thu, 16 Feb 2017 21:19:29 +0100 > On Tue, Feb 14, 2017 at 10:23:30AM -0800, Dmitry Torokhov wrote: >> drivers/ptp/ptp_clock.c | 22 +++--- >> drivers/ptp/ptp_private.h | 7 +- >> drivers/ptp/ptp_sysfs.c | 167 >>

Re: [PATCH v2 0/4] PTP attribute handling cleanup

From: Richard Cochran Date: Thu, 16 Feb 2017 21:19:29 +0100 > On Tue, Feb 14, 2017 at 10:23:30AM -0800, Dmitry Torokhov wrote: >> drivers/ptp/ptp_clock.c | 22 +++--- >> drivers/ptp/ptp_private.h | 7 +- >> drivers/ptp/ptp_sysfs.c | 167 >> ++

Re: [PATCH V3 3/7] mm: reclaim MADV_FREE pages

On Thu, Feb 16, 2017 at 04:27:18PM -0800, Shaohua Li wrote: > On Thu, Feb 16, 2017 at 01:40:18PM -0500, Johannes Weiner wrote: > > On Tue, Feb 14, 2017 at 11:36:09AM -0800, Shaohua Li wrote: > > > @@ -911,7 +911,7 @@ static void page_check_dirty_writeback(struct page > > > *page, > > >*

Re: [PATCH V3 3/7] mm: reclaim MADV_FREE pages

On Thu, Feb 16, 2017 at 04:27:18PM -0800, Shaohua Li wrote: > On Thu, Feb 16, 2017 at 01:40:18PM -0500, Johannes Weiner wrote: > > On Tue, Feb 14, 2017 at 11:36:09AM -0800, Shaohua Li wrote: > > > @@ -911,7 +911,7 @@ static void page_check_dirty_writeback(struct page > > > *page, > > >*

Re: [RFC PATCH v4 19/28] swiotlb: Add warnings for use of bounce buffers with SME

On Thu, Feb 16, 2017 at 09:46:19AM -0600, Tom Lendacky wrote: > Add warnings to let the user know when bounce buffers are being used for > DMA when SME is active. Since the bounce buffers are not in encrypted > memory, these notifications are to allow the user to determine some > appropriate

Re: [RFC PATCH v4 19/28] swiotlb: Add warnings for use of bounce buffers with SME

On Thu, Feb 16, 2017 at 09:46:19AM -0600, Tom Lendacky wrote: > Add warnings to let the user know when bounce buffers are being used for > DMA when SME is active. Since the bounce buffers are not in encrypted > memory, these notifications are to allow the user to determine some > appropriate

Re: [PATCH] RDMA/bnxt_re: remove redundant initialization of rc to zero

drivers/infiniband/hw/bnxt_re/ib_verbs.c 2817 int bnxt_re_dereg_mr(struct ib_mr *ib_mr) 2818 { 2819 struct bnxt_re_mr *mr = container_of(ib_mr, struct bnxt_re_mr, ib_mr); 2820 struct bnxt_re_dev *rdev = mr->rdev; 2821 int rc = 0; It's weird that it would

Re: [PATCH] RDMA/bnxt_re: remove redundant initialization of rc to zero

drivers/infiniband/hw/bnxt_re/ib_verbs.c 2817 int bnxt_re_dereg_mr(struct ib_mr *ib_mr) 2818 { 2819 struct bnxt_re_mr *mr = container_of(ib_mr, struct bnxt_re_mr, ib_mr); 2820 struct bnxt_re_dev *rdev = mr->rdev; 2821 int rc = 0; It's weird that it would

Re: [RFC PATCH v4 26/28] x86: Allow kexec to be used with SME

On Thu, Feb 16, 2017 at 09:47:55AM -0600, Tom Lendacky wrote: > Provide support so that kexec can be used to boot a kernel when SME is > enabled. Is the point of kexec and kdump to ehh, dump memory ? But if the rest of the memory is encrypted you won't get much, will you? Would it make sense to

Re: [RFC PATCH v4 26/28] x86: Allow kexec to be used with SME

On Thu, Feb 16, 2017 at 09:47:55AM -0600, Tom Lendacky wrote: > Provide support so that kexec can be used to boot a kernel when SME is > enabled. Is the point of kexec and kdump to ehh, dump memory ? But if the rest of the memory is encrypted you won't get much, will you? Would it make sense to

[PATCH] crypto: cavium: fix leak on curr if curr->head fails to be allocated

From: Colin Ian King The exit path when curr->head cannot be allocated fails to kfree the earlier allocated curr. Fix this by kfree'ing it. Signed-off-by: Colin Ian King --- drivers/crypto/cavium/cpt/cptvf_main.c | 1 + 1 file changed, 1

[PATCH] crypto: cavium: fix leak on curr if curr->head fails to be allocated

From: Colin Ian King The exit path when curr->head cannot be allocated fails to kfree the earlier allocated curr. Fix this by kfree'ing it. Signed-off-by: Colin Ian King --- drivers/crypto/cavium/cpt/cptvf_main.c | 1 + 1 file changed, 1 insertion(+) diff --git

Re: [PATCH 0/8] ARM: sun8i: a33: Mali improvements

Alexandre Belloni wrote: > On 17/02/2017 at 13:45:44 +0100, Tobias Jakobi wrote: >>> The device tree is a representation of the hardware itself. The state >>> of the driver support doesn't change the hardware you're running on, >>> just like your BIOS/UEFI on x86 won't change the device it reports

Re: [PATCH 0/8] ARM: sun8i: a33: Mali improvements

Alexandre Belloni wrote: > On 17/02/2017 at 13:45:44 +0100, Tobias Jakobi wrote: >>> The device tree is a representation of the hardware itself. The state >>> of the driver support doesn't change the hardware you're running on, >>> just like your BIOS/UEFI on x86 won't change the device it reports

Re: [RFC PATCH v4 02/28] x86: Set the write-protect cache mode for full PAT support

On 2/17/2017 5:07 AM, Borislav Petkov wrote: On Thu, Feb 16, 2017 at 09:42:25AM -0600, Tom Lendacky wrote: For processors that support PAT, set the write-protect cache mode (_PAGE_CACHE_MODE_WP) entry to the actual write-protect value (x05). Acked-by: Borislav Petkov

Re: [RFC PATCH v4 02/28] x86: Set the write-protect cache mode for full PAT support

On 2/17/2017 5:07 AM, Borislav Petkov wrote: On Thu, Feb 16, 2017 at 09:42:25AM -0600, Tom Lendacky wrote: For processors that support PAT, set the write-protect cache mode (_PAGE_CACHE_MODE_WP) entry to the actual write-protect value (x05). Acked-by: Borislav Petkov Signed-off-by: Tom

Re: [PATCH] RDMA/bnxt_re: remove redundant initialization of rc to zero

- Original Message - > From: "Colin King" > To: "Selvin Xavier" , "Devesh Sharma" > , "Somnath Kotur" > , "Sriharsha Basavapatna" > , "Doug

Re: [PATCH] RDMA/bnxt_re: remove redundant initialization of rc to zero

- Original Message - > From: "Colin King" > To: "Selvin Xavier" , "Devesh Sharma" > , "Somnath Kotur" > , "Sriharsha Basavapatna" > , "Doug Ledford" > , "Sean Hefty" , "Hal Rosenstock" > , > linux-r...@vger.kernel.org > Cc: kernel-janit...@vger.kernel.org,

Re: [PATCH] userfaultfd: hugetlbfs: add UFFDIO_COPY support for shared mappings

On Thu, Feb 16, 2017 at 04:18:51PM -0800, Mike Kravetz wrote: > Thanks Andrea, I incorporated your suggestions into a new version of the > patch. > While changing (dst_vma->vm_flags & VM_SHARED) to integers, I noticed an issue > in the error path of __mcopy_atomic_hugetlb(). Indeed good point!

Re: [PATCH] userfaultfd: hugetlbfs: add UFFDIO_COPY support for shared mappings

On Thu, Feb 16, 2017 at 04:18:51PM -0800, Mike Kravetz wrote: > Thanks Andrea, I incorporated your suggestions into a new version of the > patch. > While changing (dst_vma->vm_flags & VM_SHARED) to integers, I noticed an issue > in the error path of __mcopy_atomic_hugetlb(). Indeed good point!

Re: [PATCH 0/8] ARM: sun8i: a33: Mali improvements

On Thu, Feb 16, 2017 at 04:54:45PM +, Emil Velikov wrote: > On 16 February 2017 at 12:43, Tobias Jakobi > wrote: > > Hello, > > > > I was wondering about the following. Wasn't there some strict > > requirement about code going upstream, which also included that

Re: [PATCH 0/8] ARM: sun8i: a33: Mali improvements

On Thu, Feb 16, 2017 at 04:54:45PM +, Emil Velikov wrote: > On 16 February 2017 at 12:43, Tobias Jakobi > wrote: > > Hello, > > > > I was wondering about the following. Wasn't there some strict > > requirement about code going upstream, which also included that there > > was a full

Re: [PATCH 0/8] ARM: sun8i: a33: Mali improvements

On Fri, Feb 17, 2017 at 01:45:44PM +0100, Tobias Jakobi wrote: > Hello Maxime, > > Maxime Ripard wrote: > > Hi, > > > > On Thu, Feb 16, 2017 at 01:43:06PM +0100, Tobias Jakobi wrote: > >> I was wondering about the following. Wasn't there some strict > >> requirement about code going upstream,

Re: [PATCH 0/8] ARM: sun8i: a33: Mali improvements

On Fri, Feb 17, 2017 at 01:45:44PM +0100, Tobias Jakobi wrote: > Hello Maxime, > > Maxime Ripard wrote: > > Hi, > > > > On Thu, Feb 16, 2017 at 01:43:06PM +0100, Tobias Jakobi wrote: > >> I was wondering about the following. Wasn't there some strict > >> requirement about code going upstream,

Re: [PATCH] platform: intel_turbo_max_3: make it explicitly non-modular

[Re: [PATCH] platform: intel_turbo_max_3: make it explicitly non-modular] On 16/02/2017 (Thu 19:37) Darren Hart wrote: > On Mon, Feb 13, 2017 at 07:37:00PM -0500, Paul Gortmaker wrote: > > The Kconfig currently controlling compilation of this code is: > > > > drivers/platform/x86/Kconfig:config

Re: [PATCH] platform: intel_turbo_max_3: make it explicitly non-modular

[Re: [PATCH] platform: intel_turbo_max_3: make it explicitly non-modular] On 16/02/2017 (Thu 19:37) Darren Hart wrote: > On Mon, Feb 13, 2017 at 07:37:00PM -0500, Paul Gortmaker wrote: > > The Kconfig currently controlling compilation of this code is: > > > > drivers/platform/x86/Kconfig:config

Re: [PATCH 0/8] ARM: sun8i: a33: Mali improvements

On 17/02/2017 at 13:45:44 +0100, Tobias Jakobi wrote: > > The device tree is a representation of the hardware itself. The state > > of the driver support doesn't change the hardware you're running on, > > just like your BIOS/UEFI on x86 won't change the device it reports to > > Linux based on

Re: [PATCH 0/8] ARM: sun8i: a33: Mali improvements

On 17/02/2017 at 13:45:44 +0100, Tobias Jakobi wrote: > > The device tree is a representation of the hardware itself. The state > > of the driver support doesn't change the hardware you're running on, > > just like your BIOS/UEFI on x86 won't change the device it reports to > > Linux based on

[PATCH trivial] selftests/timers: Spelling s/privledges/privileges/

Signed-off-by: Geert Uytterhoeven --- tools/testing/selftests/timers/Makefile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tools/testing/selftests/timers/Makefile b/tools/testing/selftests/timers/Makefile index

[PATCH trivial] selftests/timers: Spelling s/privledges/privileges/

Signed-off-by: Geert Uytterhoeven --- tools/testing/selftests/timers/Makefile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tools/testing/selftests/timers/Makefile b/tools/testing/selftests/timers/Makefile index b90e50c36f9f99a4..5fa1d7e9a9158ab6 100644 ---

[PATCH trivial 4/4] PM / Documentation: Spelling s/wrtie/write/

Signed-off-by: Geert Uytterhoeven Cc: Rafael J. Wysocki Cc: linux...@vger.kernel.org --- Documentation/power/states.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/power/states.txt

[PATCH trivial 4/4] PM / Documentation: Spelling s/wrtie/write/

Signed-off-by: Geert Uytterhoeven Cc: Rafael J. Wysocki Cc: linux...@vger.kernel.org --- Documentation/power/states.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/power/states.txt b/Documentation/power/states.txt index 008ecb588317bc1d..bc4548245a243134

[PATCH trivial 1/4] HID: picoLCD: Spelling s/REPORT_WRTIE_MEMORY/REPORT_WRITE_MEMORY/

Signed-off-by: Geert Uytterhoeven Cc: Bruno Prémont Cc: linux-in...@vger.kernel.org --- drivers/hid/hid-picolcd_debugfs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/hid/hid-picolcd_debugfs.c

[PATCH trivial 3/4] drm/amd: Spelling s/SDMA_WRTIE_SUB_OPCODE_TILED/SDMA_WRITE_SUB_OPCODE_TILED/

Signed-off-by: Geert Uytterhoeven Cc: Alex Deucher Cc: Christian König Cc: dri-devel@lists.freedesktop.orgamd-...@lists.freedesktop.org --- drivers/gpu/drm/amd/amdgpu/cikd.h | 2 +- drivers/gpu/drm/radeon/cikd.h

[PATCH trivial 2/4] rtlwifi: rtl8821ae: Spelling s/wrtie_addr/write_addr/

As per symmetry with _rtl8821ae_dbi_read(), "wrtie" is not a funky register acronym, but a simple misspelling of "write". Signed-off-by: Geert Uytterhoeven Cc: Larry Finger Cc: Chaoming Li Cc:

[PATCH trivial 1/4] HID: picoLCD: Spelling s/REPORT_WRTIE_MEMORY/REPORT_WRITE_MEMORY/

Signed-off-by: Geert Uytterhoeven Cc: Bruno Prémont Cc: linux-in...@vger.kernel.org --- drivers/hid/hid-picolcd_debugfs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/hid/hid-picolcd_debugfs.c b/drivers/hid/hid-picolcd_debugfs.c index

[PATCH trivial 3/4] drm/amd: Spelling s/SDMA_WRTIE_SUB_OPCODE_TILED/SDMA_WRITE_SUB_OPCODE_TILED/

Signed-off-by: Geert Uytterhoeven Cc: Alex Deucher Cc: Christian König Cc: dri-devel@lists.freedesktop.orgamd-...@lists.freedesktop.org --- drivers/gpu/drm/amd/amdgpu/cikd.h | 2 +- drivers/gpu/drm/radeon/cikd.h | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH trivial 2/4] rtlwifi: rtl8821ae: Spelling s/wrtie_addr/write_addr/

As per symmetry with _rtl8821ae_dbi_read(), "wrtie" is not a funky register acronym, but a simple misspelling of "write". Signed-off-by: Geert Uytterhoeven Cc: Larry Finger Cc: Chaoming Li Cc: net...@vger.kernel.org --- drivers/net/wireless/realtek/rtlwifi/rtl8821ae/hw.c | 10 +- 1

Re: [PATCH v3 2/3] perf: make build_cpu_topology skip offline/absent CPUs

Em Fri, Feb 17, 2017 at 12:10:25PM +0100, Jan Stancek escreveu: > When build_cpu_topo() encounters offline/absent CPUs, > it fails to find any sysfs entries and returns failure. > This leads to build_cpu_topology() and write_cpu_topology() > failing as well. > > Because HEADER_CPU_TOPOLOGY has

Re: [PATCH v3 2/3] perf: make build_cpu_topology skip offline/absent CPUs

Em Fri, Feb 17, 2017 at 12:10:25PM +0100, Jan Stancek escreveu: > When build_cpu_topo() encounters offline/absent CPUs, > it fails to find any sysfs entries and returns failure. > This leads to build_cpu_topology() and write_cpu_topology() > failing as well. > > Because HEADER_CPU_TOPOLOGY has

[PATCH] RDMA/bnxt_re: remove redundant initialization of rc to zero

From: Colin Ian King rc is initialized to zero but is then updated by calls to bnxt_qplib_free_fast_reg_page_list and/or bnxt_qpliob_free_mrw so the initialization is redundant and can be removed. Detected with CoverityScan, CID#1408448 ("Unused Value") Signed-off-by:

[PATCH] RDMA/bnxt_re: remove redundant initialization of rc to zero

From: Colin Ian King rc is initialized to zero but is then updated by calls to bnxt_qplib_free_fast_reg_page_list and/or bnxt_qpliob_free_mrw so the initialization is redundant and can be removed. Detected with CoverityScan, CID#1408448 ("Unused Value") Signed-off-by: Colin Ian King ---

Re: [PATCH v2 1/3] watchdog: sama5d4: Cleanup init

On 17/02/2017 at 06:48:36 -0800, Guenter Roeck wrote: > On 02/16/2017 11:30 AM, Alexandre Belloni wrote: > > .config is used to cache a part of WDT_MR at probe time and is not used > > afterwards. Also functions are used while they always return 0. Simplify > > the flow by having everything in

Re: [PATCH v2 1/3] watchdog: sama5d4: Cleanup init

On 17/02/2017 at 06:48:36 -0800, Guenter Roeck wrote: > On 02/16/2017 11:30 AM, Alexandre Belloni wrote: > > .config is used to cache a part of WDT_MR at probe time and is not used > > afterwards. Also functions are used while they always return 0. Simplify > > the flow by having everything in

Re: [PATCH] Revert "ARM: at91/dt: sama5d2: Use new compatible for ohci node"

On 17/02/2017 at 16:12:50 +0100, Romain Izard wrote: > This reverts commit cab43282682e ("ARM: at91/dt: sama5d2: Use new > compatible for ohci node") > > It depends from commit 7150bc9b4d43 ("usb: ohci-at91: Forcibly suspend > ports while USB suspend") which was reverted and implemented >

Re: [PATCH] Revert "ARM: at91/dt: sama5d2: Use new compatible for ohci node"

On 17/02/2017 at 16:12:50 +0100, Romain Izard wrote: > This reverts commit cab43282682e ("ARM: at91/dt: sama5d2: Use new > compatible for ohci node") > > It depends from commit 7150bc9b4d43 ("usb: ohci-at91: Forcibly suspend > ports while USB suspend") which was reverted and implemented >

Re: [PATCH 6/6] sysctl: Add global tunable mt_page_copy

Hi Zi, [auto build test ERROR on linus/master] [also build test ERROR on v4.10-rc8 next-20170217] [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/Anshuman-Khandual/Enable-parallel-page-migration

Re: [PATCH 6/6] sysctl: Add global tunable mt_page_copy

Hi Zi, [auto build test ERROR on linus/master] [also build test ERROR on v4.10-rc8 next-20170217] [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/Anshuman-Khandual/Enable-parallel-page-migration

Re: [PATCH] s390: crypto make ap_bus explicitly non-modular

On 02/13/2017 01:03 PM, Harald Freudenberger wrote: > On 02/09/2017 03:48 PM, Paul Gortmaker wrote: >> The Makefile in drivers/s390 has: >> >> obj-y += cio/ block/ char/ crypto/ net/ scsi/ virtio/ >> >> ..and the Makefile in crypto/ has: >> >> ap-objs := ap_bus.o ap_card.o ap_queue.o >>

Re: [PATCH] s390: crypto make ap_bus explicitly non-modular

On 02/13/2017 01:03 PM, Harald Freudenberger wrote: > On 02/09/2017 03:48 PM, Paul Gortmaker wrote: >> The Makefile in drivers/s390 has: >> >> obj-y += cio/ block/ char/ crypto/ net/ scsi/ virtio/ >> >> ..and the Makefile in crypto/ has: >> >> ap-objs := ap_bus.o ap_card.o ap_queue.o >>

Re: [PATCH net-next v2 2/2] net: mvneta: Use cacheable memory to store the rx buffer DMA address

Hi Thomas, On ven., févr. 17 2017, Thomas Petazzoni wrote: > Does not make sense, because it's not the SW that refills the RX > descriptors with the address of the RX buffers. It's done by the HW. > > With HWBM, I believe you have no choice but to read

Re: [PATCH net-next v2 2/2] net: mvneta: Use cacheable memory to store the rx buffer DMA address

Hi Thomas, On ven., févr. 17 2017, Thomas Petazzoni wrote: > Does not make sense, because it's not the SW that refills the RX > descriptors with the address of the RX buffers. It's done by the HW. > > With HWBM, I believe you have no choice but to read the physical > address from the RX

Re: [PATCH v2 00/10] try to reduce fragmenting fallbacks

On 02/16/2017 04:12 PM, Vlastimil Babka wrote: > On 02/15/2017 03:29 PM, Vlastimil Babka wrote: >> On 02/13/2017 12:07 PM, Mel Gorman wrote: >>> On Fri, Feb 10, 2017 at 06:23:33PM +0100, Vlastimil Babka wrote: >>> >>> By and large, I like the series, particularly patches 7 and 8. I cannot >>> make

Re: [PATCH v2 00/10] try to reduce fragmenting fallbacks

On 02/16/2017 04:12 PM, Vlastimil Babka wrote: > On 02/15/2017 03:29 PM, Vlastimil Babka wrote: >> On 02/13/2017 12:07 PM, Mel Gorman wrote: >>> On Fri, Feb 10, 2017 at 06:23:33PM +0100, Vlastimil Babka wrote: >>> >>> By and large, I like the series, particularly patches 7 and 8. I cannot >>> make

Re: [PATCH v2 3/3] watchdog: sama5d4: Implement resume hook

On 17/02/2017 at 06:47:03 -0800, Guenter Roeck wrote: > On 02/16/2017 11:30 AM, Alexandre Belloni wrote: > > When resuming for the deepest state on sama5d2, it is necessary to restore > > MR as the registers are lost. > > > > Signed-off-by: Alexandre Belloni

Re: [PATCH v2 3/3] watchdog: sama5d4: Implement resume hook

On 17/02/2017 at 06:47:03 -0800, Guenter Roeck wrote: > On 02/16/2017 11:30 AM, Alexandre Belloni wrote: > > When resuming for the deepest state on sama5d2, it is necessary to restore > > MR as the registers are lost. > > > > Signed-off-by: Alexandre Belloni > > --- > > Changes in v2: > > -

[PATCH] timerfd: only check CAP_WAKE_ALARM when it is needed

timerfd_create() and do_timerfd_settime() presently always call capable(CAP_WAKE_ALARM) although CAP_WAKE_ALARM is only required for CLOCK_REALTIME_ALARM and CLOCK_BOOTTIME_ALARM. This can cause extraneous audit messages when using a LSM such as SELinux, incorrectly causes PF_SUPERPRIV to be set

[PATCH] timerfd: only check CAP_WAKE_ALARM when it is needed

timerfd_create() and do_timerfd_settime() presently always call capable(CAP_WAKE_ALARM) although CAP_WAKE_ALARM is only required for CLOCK_REALTIME_ALARM and CLOCK_BOOTTIME_ALARM. This can cause extraneous audit messages when using a LSM such as SELinux, incorrectly causes PF_SUPERPRIV to be set

Re: [PATCH 18/35] drivers/ide: Convert remaining uses of pr_warning to pr_warn

From: Joe Perches Date: Thu, 16 Feb 2017 23:11:31 -0800 > To enable eventual removal of pr_warning > > This makes pr_warn use consistent for drivers/ide > > Prior to this patch, there were 2 uses of pr_warning and > 0 uses of pr_warn in drivers/ide > > Signed-off-by: Joe

Re: [PATCH 18/35] drivers/ide: Convert remaining uses of pr_warning to pr_warn

From: Joe Perches Date: Thu, 16 Feb 2017 23:11:31 -0800 > To enable eventual removal of pr_warning > > This makes pr_warn use consistent for drivers/ide > > Prior to this patch, there were 2 uses of pr_warning and > 0 uses of pr_warn in drivers/ide > > Signed-off-by: Joe Perches Acked-by:

Re: [PATCH 08/35] sparc: Convert remaining use of pr_warning to pr_warn

From: Joe Perches Date: Thu, 16 Feb 2017 23:11:21 -0800 > To enable eventual removal of pr_warning > > This makes pr_warn use consistent for arch/sparc > > Prior to this patch, there was 1 use of pr_warning and > 8 uses of pr_warn in arch/sparc > > Signed-off-by: Joe Perches

Re: [PATCH 3/4] fpga dt: bindings for Altera Partial Reconfiguraion IP.

Matthew, On Fri, Feb 17, 2017 at 5:31 AM, Dinh Nguyen wrote: > On Wed, Feb 15, 2017 at 3:10 PM, wrote: >> From: Matthew Gerlach >> >> Device Tree bindings for Altera Partial Reconfiguraion IP? >> >>

Re: [PATCH 08/35] sparc: Convert remaining use of pr_warning to pr_warn

From: Joe Perches Date: Thu, 16 Feb 2017 23:11:21 -0800 > To enable eventual removal of pr_warning > > This makes pr_warn use consistent for arch/sparc > > Prior to this patch, there was 1 use of pr_warning and > 8 uses of pr_warn in arch/sparc > > Signed-off-by: Joe Perches Acked-by: David

Re: [PATCH 3/4] fpga dt: bindings for Altera Partial Reconfiguraion IP.

Matthew, On Fri, Feb 17, 2017 at 5:31 AM, Dinh Nguyen wrote: > On Wed, Feb 15, 2017 at 3:10 PM, wrote: >> From: Matthew Gerlach >> >> Device Tree bindings for Altera Partial Reconfiguraion IP? >> >> Signed-off-by: Matthew Gerlach Acked-By: Moritz Fischer >> --- >>

Re: [PATCH v2] drm/color: Document CTM eqations

On Fri, Feb 17, 2017 at 03:05:28PM +, Lionel Landwerlin wrote: > On 17/02/17 14:56, Ville Syrjälä wrote: > > On Fri, Feb 17, 2017 at 02:42:26PM +, Lionel Landwerlin wrote: > >> On 17/02/17 13:54, Brian Starkey wrote: > >>> What's the verdict? We've got [1] which is about to become another

Re: [PATCH v2] drm/color: Document CTM eqations

On Fri, Feb 17, 2017 at 03:05:28PM +, Lionel Landwerlin wrote: > On 17/02/17 14:56, Ville Syrjälä wrote: > > On Fri, Feb 17, 2017 at 02:42:26PM +, Lionel Landwerlin wrote: > >> On 17/02/17 13:54, Brian Starkey wrote: > >>> What's the verdict? We've got [1] which is about to become another

Re: [PATCH v2 2/3] watchdog: sama5d4: Fix setting timeout when watchdog is disabled

On 17/02/2017 at 06:40:33 -0800, Guenter Roeck wrote: > On 02/16/2017 11:30 AM, Alexandre Belloni wrote: > > The datasheet states: "When setting the WDDIS bit, and while it is set, the > > fields WDV and WDD must not be modified." > > > > Ensure WDDIS is not set when changing the timeout and set

Re: [PATCH v2 2/3] watchdog: sama5d4: Fix setting timeout when watchdog is disabled

On 17/02/2017 at 06:40:33 -0800, Guenter Roeck wrote: > On 02/16/2017 11:30 AM, Alexandre Belloni wrote: > > The datasheet states: "When setting the WDDIS bit, and while it is set, the > > fields WDV and WDD must not be modified." > > > > Ensure WDDIS is not set when changing the timeout and set

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