Re: [PATCH] ARM64: dts: meson-axg: enable the eMMC controller

Hi Nan, Thank you for the patch! Yet something to improve: [auto build test ERROR on next-20180403] [cannot apply to robh/for-next v4.16 v4.16-rc7 v4.16-rc6 v4.16] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com

Re: [PATCH] ARM64: dts: meson-axg: enable the eMMC controller

Hi Nan, Thank you for the patch! Yet something to improve: [auto build test ERROR on next-20180403] [cannot apply to robh/for-next v4.16 v4.16-rc7 v4.16-rc6 v4.16] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com

Re: [PATCH v8 10/18] dax, dm: introduce ->fs_{claim, release}() dax_device infrastructure

On Fri, Mar 30, 2018 at 9:03 PM, Dan Williams wrote: > In preparation for allowing filesystems to augment the dev_pagemap > associated with a dax_device, add an ->fs_claim() callback. The > ->fs_claim() callback is leveraged by the device-mapper dax > implementation to

Re: [PATCH v8 10/18] dax, dm: introduce ->fs_{claim, release}() dax_device infrastructure

On Fri, Mar 30, 2018 at 9:03 PM, Dan Williams wrote: > In preparation for allowing filesystems to augment the dev_pagemap > associated with a dax_device, add an ->fs_claim() callback. The > ->fs_claim() callback is leveraged by the device-mapper dax > implementation to iterate all member devices

Re: [PATCH v17 01/10] LIB: Introduce a generic PIO mapping method

On 03/04/2018 18:53, Bjorn Helgaas wrote: On Tue, Apr 03, 2018 at 06:02:43PM +0100, John Garry wrote: On 03/04/2018 17:37, Thierry Reding wrote: On Tue, Apr 03, 2018 at 05:01:37PM +0100, John Garry wrote: +int logic_pio_register_range(struct logic_pio_hwaddr *new_range) +{ + struct

Re: [PATCH v17 01/10] LIB: Introduce a generic PIO mapping method

On 03/04/2018 18:53, Bjorn Helgaas wrote: On Tue, Apr 03, 2018 at 06:02:43PM +0100, John Garry wrote: On 03/04/2018 17:37, Thierry Reding wrote: On Tue, Apr 03, 2018 at 05:01:37PM +0100, John Garry wrote: +int logic_pio_register_range(struct logic_pio_hwaddr *new_range) +{ + struct

[GIT PULL] IPMI updates for 4.17

The following changes since commit e1171aca7da6407c0e65ffb1f38509ee4486a3e7:   Merge tag 'xtensa-20180225' of git://github.com/jcmvbkbc/linux-xtensa (2018-02-25 17:02:24 -0800) are available in the git repository at:   https://github.com/cminyard/linux-ipmi.git tags/for-linus-4.17 for you

[GIT PULL] IPMI updates for 4.17

The following changes since commit e1171aca7da6407c0e65ffb1f38509ee4486a3e7:   Merge tag 'xtensa-20180225' of git://github.com/jcmvbkbc/linux-xtensa (2018-02-25 17:02:24 -0800) are available in the git repository at:   https://github.com/cminyard/linux-ipmi.git tags/for-linus-4.17 for you

[v6 4/6] mm/memory_hotplug: optimize probe routine

When memory is hotplugged pages_correctly_reserved() is called to verify that the added memory is present, this routine traverses through every struct page and verifies that PageReserved() is set. This is a slow operation especially if a large amount of memory is added. Instead of checking every

[v6 4/6] mm/memory_hotplug: optimize probe routine

When memory is hotplugged pages_correctly_reserved() is called to verify that the added memory is present, this routine traverses through every struct page and verifies that PageReserved() is set. This is a slow operation especially if a large amount of memory is added. Instead of checking every

[v6 0/6] optimize memory hotplug

Changelog: v6 - v5 - Improved "mm: add uninitialized struct page poisoning sanity checking". Fixed __dump_page() to detect that page is poisoned. This should fix a panic printing issue reported by Sasha Levin. v5 - v4 - Addressed more comments

[v6 0/6] optimize memory hotplug

Changelog: v6 - v5 - Improved "mm: add uninitialized struct page poisoning sanity checking". Fixed __dump_page() to detect that page is poisoned. This should fix a panic printing issue reported by Sasha Levin. v5 - v4 - Addressed more comments

[PATCH v2] perf stat: enable 1ms interval for printing event counters values

Currently print count interval for performance counters values is limited by 10ms so reading the values at frequencies higher than 100Hz is restricted by the tool. This change makes perf stat -I possible on frequencies up to 1KHz and, to some extent, makes perf stat -I to be on-par with perf

[PATCH v2] perf stat: enable 1ms interval for printing event counters values

Currently print count interval for performance counters values is limited by 10ms so reading the values at frequencies higher than 100Hz is restricted by the tool. This change makes perf stat -I possible on frequencies up to 1KHz and, to some extent, makes perf stat -I to be on-par with perf

[v6 2/6] x86/mm/memory_hotplug: determine block size based on the end of boot memory

Memory sections are combined into "memory block" chunks. These chunks are the units upon which memory can be added and removed. On x86 the new memory may be added after the end of the boot memory, therefore, if block size does not align with end of boot memory, memory hotplugging/hotremoving can

[v6 2/6] x86/mm/memory_hotplug: determine block size based on the end of boot memory

Memory sections are combined into "memory block" chunks. These chunks are the units upon which memory can be added and removed. On x86 the new memory may be added after the end of the boot memory, therefore, if block size does not align with end of boot memory, memory hotplugging/hotremoving can

Re: How to get lockref patch merged?

On 3 April 2018 at 19:20, Greg Kroah-Hartman wrote: > On Tue, Apr 03, 2018 at 01:13:00PM +0200, Andreas Gruenbacher wrote: >> Hello, >> >> what's the best way to get the following lockref patch merged? The >> maintainers file doesn't list a maintainer. Should we go

Re: How to get lockref patch merged?

On 3 April 2018 at 19:20, Greg Kroah-Hartman wrote: > On Tue, Apr 03, 2018 at 01:13:00PM +0200, Andreas Gruenbacher wrote: >> Hello, >> >> what's the best way to get the following lockref patch merged? The >> maintainers file doesn't list a maintainer. Should we go straight to >> Linus? Does one

[v6 3/6] mm: add uninitialized struct page poisoning sanity checking

During boot we poison struct page memory in order to ensure that no one is accessing this memory until the struct pages are initialized in __init_single_page(). This patch adds more scrutiny to this checking by making sure that flags do not equal the poison pattern when they are accessed. The

[v6 5/6] mm/memory_hotplug: don't read nid from struct page during hotplug

register_mem_sect_under_node is careful to check the node id of each pfn in the memblock range to handle configurations with interleaving nodes. This is not really needed for the memory hotplug because hotadded ranges are bound to a single NUMA node. We simply cannot handle interleaving NUMA nodes

[v6 3/6] mm: add uninitialized struct page poisoning sanity checking

During boot we poison struct page memory in order to ensure that no one is accessing this memory until the struct pages are initialized in __init_single_page(). This patch adds more scrutiny to this checking by making sure that flags do not equal the poison pattern when they are accessed. The

[v6 5/6] mm/memory_hotplug: don't read nid from struct page during hotplug

register_mem_sect_under_node is careful to check the node id of each pfn in the memblock range to handle configurations with interleaving nodes. This is not really needed for the memory hotplug because hotadded ranges are bound to a single NUMA node. We simply cannot handle interleaving NUMA nodes

Re: [alsa-devel] [PATCH] ASoC: atmel_ssc_dai: fix spelling mistake: "Stoping" -> "Stopping"

On Tue, 2018-04-03 at 19:30 +0200, Ladislav Michl wrote: > On Tue, Apr 03, 2018 at 08:49:57AM -0700, Joe Perches wrote: > > On Tue, 2018-04-03 at 15:45 +0200, Ladislav Michl wrote: > > > On Fri, Mar 30, 2018 at 04:44:20PM +0100, Colin King wrote: > > > > From: Colin Ian King

[v6 1/6] mm/memory_hotplug: enforce block size aligned range check

Start qemu with the following arguments: -m 64G,slots=2,maxmem=66G -object memory-backend-ram,id=mem1,size=2G Which boots machine with 64G and adds a device mem1 with 2G that can be hotplugged later. Also make sure that .config has the following options turned on: CONFIG_MEMORY_HOTPLUG

Re: [alsa-devel] [PATCH] ASoC: atmel_ssc_dai: fix spelling mistake: "Stoping" -> "Stopping"

On Tue, 2018-04-03 at 19:30 +0200, Ladislav Michl wrote: > On Tue, Apr 03, 2018 at 08:49:57AM -0700, Joe Perches wrote: > > On Tue, 2018-04-03 at 15:45 +0200, Ladislav Michl wrote: > > > On Fri, Mar 30, 2018 at 04:44:20PM +0100, Colin King wrote: > > > > From: Colin Ian King > > > > > > Hello

[v6 1/6] mm/memory_hotplug: enforce block size aligned range check

Start qemu with the following arguments: -m 64G,slots=2,maxmem=66G -object memory-backend-ram,id=mem1,size=2G Which boots machine with 64G and adds a device mem1 with 2G that can be hotplugged later. Also make sure that .config has the following options turned on: CONFIG_MEMORY_HOTPLUG

[v6 6/6] mm/memory_hotplug: optimize memory hotplug

During memory hotplugging we traverse struct pages three times: 1. memset(0) in sparse_add_one_section() 2. loop in __add_section() to set do: set_page_node(page, nid); and SetPageReserved(page); 3. loop in memmap_init_zone() to call __init_single_pfn() This patch removes the first two loops,

[v6 6/6] mm/memory_hotplug: optimize memory hotplug

During memory hotplugging we traverse struct pages three times: 1. memset(0) in sparse_add_one_section() 2. loop in __add_section() to set do: set_page_node(page, nid); and SetPageReserved(page); 3. loop in memmap_init_zone() to call __init_single_pfn() This patch removes the first two loops,

[PATCH 0/3] SPDX to btrfs

Switch fs/btrfs/*.[ch] and fs/btrfs/tests/*.[ch] to SPDX. I've briefly verified that there are no exceptions to GPL-2.0 (ie. no 'or later'). The changes match what I've seen in other patches and I don't think ther's more needed to be done. If there are no objections I'm going to add the patches to

[PATCH 0/3] SPDX to btrfs

Switch fs/btrfs/*.[ch] and fs/btrfs/tests/*.[ch] to SPDX. I've briefly verified that there are no exceptions to GPL-2.0 (ie. no 'or later'). The changes match what I've seen in other patches and I don't think ther's more needed to be done. If there are no objections I'm going to add the patches to

[PATCH 1/3] btrfs: replace GPL boilerplate by SPDX -- headers

Remove GPL boilerplate text (long, short, one-line) and keep the rest, ie. personal, company or original source copyright statements. Add the SPDX header. Unify the include protection macros to match the file names. Signed-off-by: David Sterba --- fs/btrfs/async-thread.h

[PATCH 1/3] btrfs: replace GPL boilerplate by SPDX -- headers

Remove GPL boilerplate text (long, short, one-line) and keep the rest, ie. personal, company or original source copyright statements. Add the SPDX header. Unify the include protection macros to match the file names. Signed-off-by: David Sterba --- fs/btrfs/async-thread.h | 21

[PATCH 2/3] btrfs: replace GPL boilerplate by SPDX -- sources

Remove GPL boilerplate text (long, short, one-line) and keep the rest, ie. personal, company or original source copyright statements. Add the SPDX header. Signed-off-by: David Sterba --- fs/btrfs/acl.c | 15 +-- fs/btrfs/async-thread.c

[PATCH 2/3] btrfs: replace GPL boilerplate by SPDX -- sources

Remove GPL boilerplate text (long, short, one-line) and keep the rest, ie. personal, company or original source copyright statements. Add the SPDX header. Signed-off-by: David Sterba --- fs/btrfs/acl.c | 15 +-- fs/btrfs/async-thread.c| 15

[PATCH 3/3] btrfs: add SPDX header to Kconfig

Signed-off-by: David Sterba --- fs/btrfs/Kconfig | 2 ++ 1 file changed, 2 insertions(+) diff --git a/fs/btrfs/Kconfig b/fs/btrfs/Kconfig index 167e5dc7eadd..23537bc8c827 100644 --- a/fs/btrfs/Kconfig +++ b/fs/btrfs/Kconfig @@ -1,3 +1,5 @@ +# SPDX-License-Identifier: GPL-2.0 +

[PATCH 3/3] btrfs: add SPDX header to Kconfig

Signed-off-by: David Sterba --- fs/btrfs/Kconfig | 2 ++ 1 file changed, 2 insertions(+) diff --git a/fs/btrfs/Kconfig b/fs/btrfs/Kconfig index 167e5dc7eadd..23537bc8c827 100644 --- a/fs/btrfs/Kconfig +++ b/fs/btrfs/Kconfig @@ -1,3 +1,5 @@ +# SPDX-License-Identifier: GPL-2.0 + config BTRFS_FS

Re: [alsa-devel] [PATCH v3 0/2] ASoC: topology: Improve parsing hw_configs

On 04/03/18 19:21, Pierre-Louis Bossart wrote: > > > On 04/03/2018 12:15 AM, Kirill Marinushkin wrote: >> On 04/03/18 02:57, Pierre-Louis Bossart wrote: >>> >>> On 04/02/2018 04:17 PM, Kirill Marinushkin wrote: Hello Pierre-Louis, I explicitly clarified with Takashi: to have this

Re: [alsa-devel] [PATCH v3 0/2] ASoC: topology: Improve parsing hw_configs

On 04/03/18 19:21, Pierre-Louis Bossart wrote: > > > On 04/03/2018 12:15 AM, Kirill Marinushkin wrote: >> On 04/03/18 02:57, Pierre-Louis Bossart wrote: >>> >>> On 04/02/2018 04:17 PM, Kirill Marinushkin wrote: Hello Pierre-Louis, I explicitly clarified with Takashi: to have this

Please add 21035965f60b ("bitmap: fix memset optimization on big-endian systems") to the stable tree

Just wanted to make sure this doesn't get missed because I misspelled the stable email address in the patch. It applies to v4.13+.

Please add 21035965f60b ("bitmap: fix memset optimization on big-endian systems") to the stable tree

Just wanted to make sure this doesn't get missed because I misspelled the stable email address in the patch. It applies to v4.13+.

Re: [PATCH] memcg, thp: do not invoke oom killer on thp charges

On Tue, Apr 03, 2018 at 05:55:09PM +0200, Michal Hocko wrote: > On Tue 03-04-18 10:58:53, Johannes Weiner wrote: > > On Wed, Mar 21, 2018 at 09:59:28PM +0100, Michal Hocko wrote: > > > From: Michal Hocko > > > > > > David has noticed that THP memcg charge can trigger the oom

Re: [PATCH] memcg, thp: do not invoke oom killer on thp charges

On Tue, Apr 03, 2018 at 05:55:09PM +0200, Michal Hocko wrote: > On Tue 03-04-18 10:58:53, Johannes Weiner wrote: > > On Wed, Mar 21, 2018 at 09:59:28PM +0100, Michal Hocko wrote: > > > From: Michal Hocko > > > > > > David has noticed that THP memcg charge can trigger the oom killer > > > since

Re: [PATCH v2 0/2] iio: add unit converter

On 2018-04-03 19:41, Andrew F. Davis wrote: > On 04/03/2018 10:36 AM, Peter Rosin wrote: >> Hi! >> >> This driver implements support for voltage dividers and current >> sense circuits. It's pretty generic and should be easily adaptable >> to other linear scaling purposes... >> > > I really like

Re: [PATCH] bitmap: fix memset optimization on big-endian systems

On Mon, Apr 02, 2018 at 04:49:39PM -0700, Linus Torvalds wrote: > On Mon, Apr 2, 2018 at 4:37 PM, Linus Torvalds > wrote: > > > > We should probably have at least switched it to "unsigned long int" > > I meant just "unsigned int", of course. > > Right now we

Re: [PATCH v2 0/2] iio: add unit converter

On 2018-04-03 19:41, Andrew F. Davis wrote: > On 04/03/2018 10:36 AM, Peter Rosin wrote: >> Hi! >> >> This driver implements support for voltage dividers and current >> sense circuits. It's pretty generic and should be easily adaptable >> to other linear scaling purposes... >> > > I really like

Re: [PATCH] bitmap: fix memset optimization on big-endian systems

On Mon, Apr 02, 2018 at 04:49:39PM -0700, Linus Torvalds wrote: > On Mon, Apr 2, 2018 at 4:37 PM, Linus Torvalds > wrote: > > > > We should probably have at least switched it to "unsigned long int" > > I meant just "unsigned int", of course. > > Right now we occasionally have a silly 64-bit

Re: [PATCH 4/8] dma-buf: add peer2peer flag

On Tue, Apr 03, 2018 at 01:06:45PM -0400, Jerome Glisse wrote: > On Tue, Apr 03, 2018 at 11:09:09AM +0200, Daniel Vetter wrote: > > On Thu, Mar 29, 2018 at 01:34:24PM +0200, Christian König wrote: > > > Am 29.03.2018 um 08:57 schrieb Daniel Vetter: > > > > On Sun, Mar 25, 2018 at 12:59:56PM +0200,

Re: [PATCH 4/8] dma-buf: add peer2peer flag

On Tue, Apr 03, 2018 at 01:06:45PM -0400, Jerome Glisse wrote: > On Tue, Apr 03, 2018 at 11:09:09AM +0200, Daniel Vetter wrote: > > On Thu, Mar 29, 2018 at 01:34:24PM +0200, Christian König wrote: > > > Am 29.03.2018 um 08:57 schrieb Daniel Vetter: > > > > On Sun, Mar 25, 2018 at 12:59:56PM +0200,

Re: [PATCH 2/2] efi: Add embedded peripheral firmware support

On Tue, Apr 03, 2018 at 10:33:25AM +0200, Hans de Goede wrote: > I asked Peter Jones for suggestions how to extract this during boot and > he suggested seeing if there was a copy of the firmware in the > EFI_BOOT_SERVICES_CODE memory segment, which it turns out there is. > > My patch to add

Re: [PATCH 2/2] efi: Add embedded peripheral firmware support

On Tue, Apr 03, 2018 at 10:33:25AM +0200, Hans de Goede wrote: > I asked Peter Jones for suggestions how to extract this during boot and > he suggested seeing if there was a copy of the firmware in the > EFI_BOOT_SERVICES_CODE memory segment, which it turns out there is. > > My patch to add

Re: [GIT PULL] x86/build changes for v4.17

El Tue, Apr 03, 2018 at 11:51:18AM +0200 Ingo Molnar ha dit: > > * Peter Zijlstra wrote: > > > On Mon, Apr 02, 2018 at 02:44:48PM -0700, Linus Torvalds wrote: > > > On Mon, Apr 2, 2018 at 2:50 AM, Ingo Molnar wrote: > > > > > > > > The biggest change is

Re: [GIT PULL] x86/build changes for v4.17

El Tue, Apr 03, 2018 at 11:51:18AM +0200 Ingo Molnar ha dit: > > * Peter Zijlstra wrote: > > > On Mon, Apr 02, 2018 at 02:44:48PM -0700, Linus Torvalds wrote: > > > On Mon, Apr 2, 2018 at 2:50 AM, Ingo Molnar wrote: > > > > > > > > The biggest change is the forcing of asm-goto support on x86,

Re: [PATCH v1] perf stat: enable 1ms interval for printing event counters values

On 03.04.2018 18:22, Jiri Olsa wrote: > On Tue, Apr 03, 2018 at 06:04:13PM +0300, Alexey Budankov wrote: >> >> Currently print count interval for performance counters values is >> limited by 10ms so reading the values at frequencies higher than 100Hz >> is restricted by the tool. >> >> This

Re: [PATCH v1] perf stat: enable 1ms interval for printing event counters values

On 03.04.2018 18:22, Jiri Olsa wrote: > On Tue, Apr 03, 2018 at 06:04:13PM +0300, Alexey Budankov wrote: >> >> Currently print count interval for performance counters values is >> limited by 10ms so reading the values at frequencies higher than 100Hz >> is restricted by the tool. >> >> This

Re: [PATCH 1/2] clk: qcom: clk-rpmh: Add QCOM RPMh clock driver

Hi Taniya, On Mon, Apr 2, 2018 at 3:33 AM Taniya Das wrote: > Hello Evan, > Thanks for the review comments. > On 3/30/2018 3:19 AM, Evan Green wrote: > > Hi Taniya, > > > > On Wed, Mar 28, 2018 at 11:19 PM Taniya Das wrote: > > > >> From: Amit

Re: [PATCH 1/2] clk: qcom: clk-rpmh: Add QCOM RPMh clock driver

Hi Taniya, On Mon, Apr 2, 2018 at 3:33 AM Taniya Das wrote: > Hello Evan, > Thanks for the review comments. > On 3/30/2018 3:19 AM, Evan Green wrote: > > Hi Taniya, > > > > On Wed, Mar 28, 2018 at 11:19 PM Taniya Das wrote: > > > >> From: Amit Nischal > >> +static int

Re: [PATCH v17 01/10] LIB: Introduce a generic PIO mapping method

On Tue, Apr 03, 2018 at 06:02:43PM +0100, John Garry wrote: > On 03/04/2018 17:37, Thierry Reding wrote: > > On Tue, Apr 03, 2018 at 05:01:37PM +0100, John Garry wrote: > > > > > > +int logic_pio_register_range(struct logic_pio_hwaddr *new_range) > > > > > > +{ > > > > > > + struct

Re: [PATCH v17 01/10] LIB: Introduce a generic PIO mapping method

On Tue, Apr 03, 2018 at 06:02:43PM +0100, John Garry wrote: > On 03/04/2018 17:37, Thierry Reding wrote: > > On Tue, Apr 03, 2018 at 05:01:37PM +0100, John Garry wrote: > > > > > > +int logic_pio_register_range(struct logic_pio_hwaddr *new_range) > > > > > > +{ > > > > > > + struct

[PATCH] HID: input: fix battery level reporting on BT mice

The commit 581c4484769e ("HID: input: map digitizer battery usage") assumed that devices having input (qas opposed to feature) report for battery strength would report the data on their own, without the need to be polled by the kernel; unfortunately it is not so. Many wireless mice do not send

[PATCH] HID: input: fix battery level reporting on BT mice

The commit 581c4484769e ("HID: input: map digitizer battery usage") assumed that devices having input (qas opposed to feature) report for battery strength would report the data on their own, without the need to be polled by the kernel; unfortunately it is not so. Many wireless mice do not send

Re: [PATCH v5 3/3] RDMA/qedr: eliminate duplicate barriers on weakly-ordered archs #2

On 4/3/2018 3:42 AM, Kalderon, Michal wrote: > The wmb before writel are used to make sure the > HW observes the changes in memory before we trigger the doorbell. According to Linus, writel() guarantees observability. No extra barrier is necessary.

Re: [PATCH v5 3/3] RDMA/qedr: eliminate duplicate barriers on weakly-ordered archs #2

On 4/3/2018 3:42 AM, Kalderon, Michal wrote: > The wmb before writel are used to make sure the > HW observes the changes in memory before we trigger the doorbell. According to Linus, writel() guarantees observability. No extra barrier is necessary.

Re: [4.9, 137/145] spi: bcm-qspi: shut up warning about cfi header inclusion

On 02/23/2018 10:27 AM, gre...@linuxfoundation.org wrote: > 4.9-stable review patch. If anyone has any objections, please let me know. > > -- > > From: Arnd Bergmann > > When CONFIG_MTD_CFI is disabled, we get a warning for this spi driver: > >

Re: [4.9, 137/145] spi: bcm-qspi: shut up warning about cfi header inclusion

On 02/23/2018 10:27 AM, gre...@linuxfoundation.org wrote: > 4.9-stable review patch. If anyone has any objections, please let me know. > > -- > > From: Arnd Bergmann > > When CONFIG_MTD_CFI is disabled, we get a warning for this spi driver: > > include/linux/mtd/cfi.h:76:2:

Re: [PATCH 4.4 38/97] netfilter: xt_CT: fix refcnt leak on error path

On Fri, 2018-03-23 at 10:54 +0100, Greg Kroah-Hartman wrote: > 4.4-stable review patch.  If anyone has any objections, please let me know. > > -- > > From: Gao Feng > > > [ Upstream commit 470acf55a021713869b9bcc967268ac90c8a0fac ] [...] > ---

Re: [PATCH 4.4 38/97] netfilter: xt_CT: fix refcnt leak on error path

On Fri, 2018-03-23 at 10:54 +0100, Greg Kroah-Hartman wrote: > 4.4-stable review patch.  If anyone has any objections, please let me know. > > -- > > From: Gao Feng > > > [ Upstream commit 470acf55a021713869b9bcc967268ac90c8a0fac ] [...] > --- a/net/netfilter/xt_CT.c > +++

Re: [PATCH v2 0/2] iio: add unit converter

On 04/03/2018 10:36 AM, Peter Rosin wrote: > Hi! > > This driver implements support for voltage dividers and current > sense circuits. It's pretty generic and should be easily adaptable > to other linear scaling purposes... > I really like this idea, defining channel scaling / channel type

Re: [PATCH v2 0/2] iio: add unit converter

On 04/03/2018 10:36 AM, Peter Rosin wrote: > Hi! > > This driver implements support for voltage dividers and current > sense circuits. It's pretty generic and should be easily adaptable > to other linear scaling purposes... > I really like this idea, defining channel scaling / channel type

Re: [PATCH 4.4 068/134] usb: dwc2: Make sure we disconnect the gadget state

On Sun, Apr 01, 2018 at 04:49:45PM +0100, Ben Hutchings wrote: > On Mon, 2018-03-19 at 19:05 +0100, Greg Kroah-Hartman wrote: > > 4.4-stable review patch.  If anyone has any objections, please let me know. > > > > -- > > > > From: John Stultz > > > > >

Re: [PATCH 4.4 068/134] usb: dwc2: Make sure we disconnect the gadget state

On Sun, Apr 01, 2018 at 04:49:45PM +0100, Ben Hutchings wrote: > On Mon, 2018-03-19 at 19:05 +0100, Greg Kroah-Hartman wrote: > > 4.4-stable review patch.  If anyone has any objections, please let me know. > > > > -- > > > > From: John Stultz > > > > > > [ Upstream commit

Re: [PATCH 4.4 22/97] scsi: virtio_scsi: Always try to read VPD pages

On Tue, Apr 03, 2018 at 03:54:08PM +0100, Ben Hutchings wrote: > On Fri, 2018-03-23 at 10:54 +0100, Greg Kroah-Hartman wrote: > > 4.4-stable review patch.  If anyone has any objections, please let me know. > > > > -- > > > > From: David Gibson > > >

Re: [PATCH 4.4 22/97] scsi: virtio_scsi: Always try to read VPD pages

On Tue, Apr 03, 2018 at 03:54:08PM +0100, Ben Hutchings wrote: > On Fri, 2018-03-23 at 10:54 +0100, Greg Kroah-Hartman wrote: > > 4.4-stable review patch.  If anyone has any objections, please let me know. > > > > -- > > > > From: David Gibson > > > > > > [ Upstream commit

Re: [GIT PULL] x86/build changes for v4.17

On Tue, Apr 3, 2018 at 1:59 AM, Peter Zijlstra wrote: > > It's not just spectre, I believe you yourself wanted to use asm-goto > somewhere in the x86 code: Absolutely. But I don't want to make it impossible for clang people to get their work done. Linus

Re: [GIT PULL] x86/build changes for v4.17

On Tue, Apr 3, 2018 at 1:59 AM, Peter Zijlstra wrote: > > It's not just spectre, I believe you yourself wanted to use asm-goto > somewhere in the x86 code: Absolutely. But I don't want to make it impossible for clang people to get their work done. Linus

GFS2: Pull request (merge window)

Hi Linus, Please consider pulling the following changes for the GFS2 file system. Regards, Bob Peterson The following changes since commit 1b88accf6a659c46d5c8e68912896f112bf882bb: Merge tag 'for_linus' of

GFS2: Pull request (merge window)

Hi Linus, Please consider pulling the following changes for the GFS2 file system. Regards, Bob Peterson The following changes since commit 1b88accf6a659c46d5c8e68912896f112bf882bb: Merge tag 'for_linus' of

Re: [PATCH net] net: dsa: mt7530: Use NULL instead of plain integer

On Tue, 2018-04-03 at 10:02 -0700, Florian Fainelli wrote: > On 04/02/2018 07:18 PM, Sean Wang wrote: > > On Mon, 2018-04-02 at 16:24 -0700, Florian Fainelli wrote: > >> We would be passing 0 instead of NULL as the rsp argument to > >> mt7530_fdb_cmd(), fix that. > >> > > > > Acked-by: Sean Wang

Re: [virtio-dev] [pci PATCH v7 2/5] virtio_pci: Add support for unmanaged SR-IOV on virtio_pci devices

On Tue, Apr 3, 2018 at 6:12 AM, Michael S. Tsirkin wrote: > On Fri, Mar 16, 2018 at 09:40:34AM -0700, Alexander Duyck wrote: >> On Fri, Mar 16, 2018 at 9:34 AM, Michael S. Tsirkin wrote: >> > On Thu, Mar 15, 2018 at 11:42:41AM -0700, Alexander Duyck wrote: >> >>

Re: [PATCH net] net: dsa: mt7530: Use NULL instead of plain integer

On Tue, 2018-04-03 at 10:02 -0700, Florian Fainelli wrote: > On 04/02/2018 07:18 PM, Sean Wang wrote: > > On Mon, 2018-04-02 at 16:24 -0700, Florian Fainelli wrote: > >> We would be passing 0 instead of NULL as the rsp argument to > >> mt7530_fdb_cmd(), fix that. > >> > > > > Acked-by: Sean Wang

Re: [virtio-dev] [pci PATCH v7 2/5] virtio_pci: Add support for unmanaged SR-IOV on virtio_pci devices

On Tue, Apr 3, 2018 at 6:12 AM, Michael S. Tsirkin wrote: > On Fri, Mar 16, 2018 at 09:40:34AM -0700, Alexander Duyck wrote: >> On Fri, Mar 16, 2018 at 9:34 AM, Michael S. Tsirkin wrote: >> > On Thu, Mar 15, 2018 at 11:42:41AM -0700, Alexander Duyck wrote: >> >> From: Alexander Duyck >> >> >>

Re: [PATCH] perf: Allow suppressing AUX records

On Sat, Mar 31, 2018 at 11:35:46AM +0200, Ingo Molnar wrote: > * Peter Zijlstra wrote: > > On Mon, Jan 15, 2018 at 05:00:20PM +0200, Alexander Shishkin wrote: > > > diff --git a/include/uapi/linux/perf_event.h > > > b/include/uapi/linux/perf_event.h > > > index

Re: [PATCH] perf: Allow suppressing AUX records

On Sat, Mar 31, 2018 at 11:35:46AM +0200, Ingo Molnar wrote: > * Peter Zijlstra wrote: > > On Mon, Jan 15, 2018 at 05:00:20PM +0200, Alexander Shishkin wrote: > > > diff --git a/include/uapi/linux/perf_event.h > > > b/include/uapi/linux/perf_event.h > > > index c77c9a2e..d7a981130561 100644

Re: [alsa-devel] [PATCH] ASoC: atmel_ssc_dai: fix spelling mistake: "Stoping" -> "Stopping"

On Tue, Apr 03, 2018 at 08:49:57AM -0700, Joe Perches wrote: > On Tue, 2018-04-03 at 15:45 +0200, Ladislav Michl wrote: > > On Fri, Mar 30, 2018 at 04:44:20PM +0100, Colin King wrote: > > > From: Colin Ian King > > > > Hello Colin, > > > > > Trivial fix to spelling

Re: [alsa-devel] [PATCH] ASoC: atmel_ssc_dai: fix spelling mistake: "Stoping" -> "Stopping"

On Tue, Apr 03, 2018 at 08:49:57AM -0700, Joe Perches wrote: > On Tue, 2018-04-03 at 15:45 +0200, Ladislav Michl wrote: > > On Fri, Mar 30, 2018 at 04:44:20PM +0100, Colin King wrote: > > > From: Colin Ian King > > > > Hello Colin, > > > > > Trivial fix to spelling mistake in pr_debug message

Re: [PATCH v3 2/4] mfd: add Gateworks System Controller core driver

On Tue, Apr 3, 2018 at 9:47 AM, Andrew Lunn wrote: > On Tue, Apr 03, 2018 at 08:48:27AM -0700, Tim Harvey wrote: >> On Wed, Mar 28, 2018 at 8:14 AM, Tim Harvey wrote: >> > The Gateworks System Controller (GSC) is an I2C slave controller >> > implemented

Re: [PATCH v3 2/4] mfd: add Gateworks System Controller core driver

On Tue, Apr 3, 2018 at 9:47 AM, Andrew Lunn wrote: > On Tue, Apr 03, 2018 at 08:48:27AM -0700, Tim Harvey wrote: >> On Wed, Mar 28, 2018 at 8:14 AM, Tim Harvey wrote: >> > The Gateworks System Controller (GSC) is an I2C slave controller >> > implemented with an MSP430 micro-controller whose

Re: [GIT PULL] siginfo fix for v4.16-rc5

On Apr 03 2018, Josh Juran wrote: > On Apr 3, 2018, at 10:27 AM, Eric W. Biederman wrote: > >> Geert Uytterhoeven writes: >> >>> On Mon, Apr 2, 2018 at 10:17 PM, Eric W. Biederman >>> wrote: >>> A

Re: [GIT PULL] siginfo fix for v4.16-rc5

On Apr 03 2018, Josh Juran wrote: > On Apr 3, 2018, at 10:27 AM, Eric W. Biederman wrote: > >> Geert Uytterhoeven writes: >> >>> On Mon, Apr 2, 2018 at 10:17 PM, Eric W. Biederman >>> wrote: >>> A 2-byte alignment for 4 byte pointers. That is a new one to me. >>> >>> Not just for

[PATCH 0/2] Move kfree_rcu out of rcu code and use kfree_bulk

From: Rao Shoaib This patch moves kfree_call_rcu() out of rcu related code to mm/slab_common and updates kfree_rcu() to use new bulk memory free functions as they are more efficient. This is a resubmission of the previous patch. Changes since last submission

[PATCH 0/2] Move kfree_rcu out of rcu code and use kfree_bulk

From: Rao Shoaib This patch moves kfree_call_rcu() out of rcu related code to mm/slab_common and updates kfree_rcu() to use new bulk memory free functions as they are more efficient. This is a resubmission of the previous patch. Changes since last submission Surrounded code with

[PATCH 2/2] kfree_rcu() should use kfree_bulk() interface

From: Rao Shoaib kfree_rcu() should use the new kfree_bulk() interface for freeing rcu structures as it is more efficient. Signed-off-by: Rao Shoaib --- include/linux/mm.h | 5 ++ include/linux/rcupdate.h | 4 +- include/linux/rcutiny.h

[PATCH 1/2] Move kfree_call_rcu() to slab_common.c

From: Rao Shoaib kfree_call_rcu does not belong in linux/rcupdate.h and should be moved to slab_common.c Signed-off-by: Rao Shoaib --- include/linux/rcupdate.h | 43 +++ include/linux/rcutree.h | 2 --

[PATCH 2/2] kfree_rcu() should use kfree_bulk() interface

From: Rao Shoaib kfree_rcu() should use the new kfree_bulk() interface for freeing rcu structures as it is more efficient. Signed-off-by: Rao Shoaib --- include/linux/mm.h | 5 ++ include/linux/rcupdate.h | 4 +- include/linux/rcutiny.h | 8 ++- kernel/sysctl.c | 40

[PATCH 1/2] Move kfree_call_rcu() to slab_common.c

From: Rao Shoaib kfree_call_rcu does not belong in linux/rcupdate.h and should be moved to slab_common.c Signed-off-by: Rao Shoaib --- include/linux/rcupdate.h | 43 +++ include/linux/rcutree.h | 2 -- include/linux/slab.h | 42

Re: [PATCH v2] locks: change POSIX lock ownership on execve when files_struct is displaced

Jeff Layton writes: > On Thu, 2018-03-22 at 00:36 -0500, Eric W. Biederman wrote: >> ebied...@xmission.com (Eric W. Biederman) writes: >> >> > Jeff Layton writes: >> > >> > > From: Jeff Layton >> > > >> > > POSIX mandates that open

Re: [PATCH v2] locks: change POSIX lock ownership on execve when files_struct is displaced

Jeff Layton writes: > On Thu, 2018-03-22 at 00:36 -0500, Eric W. Biederman wrote: >> ebied...@xmission.com (Eric W. Biederman) writes: >> >> > Jeff Layton writes: >> > >> > > From: Jeff Layton >> > > >> > > POSIX mandates that open fds and their associated file locks should be >> > >

Re: [alsa-devel] [PATCH v3 0/2] ASoC: topology: Improve parsing hw_configs

On 04/03/2018 12:15 AM, Kirill Marinushkin wrote: On 04/03/18 02:57, Pierre-Louis Bossart wrote: On 04/02/2018 04:17 PM, Kirill Marinushkin wrote: Hello Pierre-Louis, I explicitly clarified with Takashi: to have this patch series merged, we need a tag "Reviewed-by" from you. I am fine

Re: [alsa-devel] [PATCH v3 0/2] ASoC: topology: Improve parsing hw_configs

On 04/03/2018 12:15 AM, Kirill Marinushkin wrote: On 04/03/18 02:57, Pierre-Louis Bossart wrote: On 04/02/2018 04:17 PM, Kirill Marinushkin wrote: Hello Pierre-Louis, I explicitly clarified with Takashi: to have this patch series merged, we need a tag "Reviewed-by" from you. I am fine

Re: How to get lockref patch merged?

On Tue, Apr 03, 2018 at 01:13:00PM +0200, Andreas Gruenbacher wrote: > Hello, > > what's the best way to get the following lockref patch merged? The > maintainers file doesn't list a maintainer. Should we go straight to > Linus? Does one of you want to take it? Andrew normally takes lib/

Re: How to get lockref patch merged?

On Tue, Apr 03, 2018 at 01:13:00PM +0200, Andreas Gruenbacher wrote: > Hello, > > what's the best way to get the following lockref patch merged? The > maintainers file doesn't list a maintainer. Should we go straight to > Linus? Does one of you want to take it? Andrew normally takes lib/

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