Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Tue 25-04-17 12:42:57, Joonsoo Kim wrote: > On Mon, Apr 24, 2017 at 03:09:36PM +0200, Michal Hocko wrote: > > On Mon 17-04-17 11:02:12, Joonsoo Kim wrote: > > > On Thu, Apr 13, 2017 at 01:56:15PM +0200, Michal Hocko wrote: > > > > On Wed 12-04-17 10:35:06, Joonsoo Kim wrote: [...] > > not for

Re: [PATCH v7 0/7] Introduce ZONE_CMA

On Tue 25-04-17 12:42:57, Joonsoo Kim wrote: > On Mon, Apr 24, 2017 at 03:09:36PM +0200, Michal Hocko wrote: > > On Mon 17-04-17 11:02:12, Joonsoo Kim wrote: > > > On Thu, Apr 13, 2017 at 01:56:15PM +0200, Michal Hocko wrote: > > > > On Wed 12-04-17 10:35:06, Joonsoo Kim wrote: [...] > > not for

Re: [PATCH] FS-Cache: print hexadecimal value for special cookies type

Jérémy Lefaure wrote: > When building object-list.o, gcc 6 raises a warning on the sprintf call > in fscache_objlist_show: > > CC fs/fscache/object-list.o > fs/fscache/object-list.c: In function ‘fscache_objlist_show’: > fs/fscache/object-list.c:265:19:

Re: [PATCH] FS-Cache: print hexadecimal value for special cookies type

Jérémy Lefaure wrote: > When building object-list.o, gcc 6 raises a warning on the sprintf call > in fscache_objlist_show: > > CC fs/fscache/object-list.o > fs/fscache/object-list.c: In function ‘fscache_objlist_show’: > fs/fscache/object-list.c:265:19: warning: ‘sprintf’ may write a >

[PATCH] staging: android: ion: fix QUOTED_WHITESPACE_BEFORE_NEWLINE

Fix checkpatch warning: unnecessary whitespace before a quoted newline. Signed-off-by: Juan Antonio Pedreira Martos --- drivers/staging/android/ion/ion_chunk_heap.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] staging: android: ion: fix QUOTED_WHITESPACE_BEFORE_NEWLINE

Fix checkpatch warning: unnecessary whitespace before a quoted newline. Signed-off-by: Juan Antonio Pedreira Martos --- drivers/staging/android/ion/ion_chunk_heap.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/android/ion/ion_chunk_heap.c

Re: [PATCH v1 8/8] ACPI: Use recently introduced uuid_le_cmp_p{p}() helpers

On Thu, Apr 27, 2017 at 04:09:56PM +0300, Andy Shevchenko wrote: > Lukas pointed to this: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68725 Yap, the same thing. Thanks. -- Regards/Gruss, Boris. SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG

Re: [PATCH v1 8/8] ACPI: Use recently introduced uuid_le_cmp_p{p}() helpers

On Thu, Apr 27, 2017 at 04:09:56PM +0300, Andy Shevchenko wrote: > Lukas pointed to this: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68725 Yap, the same thing. Thanks. -- Regards/Gruss, Boris. SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG

Re: [PATCH v5 01/10] pinctrl: generic: Add bi-directional and output-enable

On Thu, Apr 27, 2017 at 11:19 AM, Jacopo Mondi wrote: > Add bi-directional and output-enable pin configuration properties. > > bi-directional allows to specify when a pin shall operate in input and > output mode at the same time. This is particularly useful in platforms

Re: [PATCH v5 01/10] pinctrl: generic: Add bi-directional and output-enable

On Thu, Apr 27, 2017 at 11:19 AM, Jacopo Mondi wrote: > Add bi-directional and output-enable pin configuration properties. > > bi-directional allows to specify when a pin shall operate in input and > output mode at the same time. This is particularly useful in platforms > where input and output

Re: [PATCH] mtd: spi-nor: stm32: remove broken MODULE_ALIAS

Le 27/04/2017 à 13:09, Arnd Bergmann a écrit : > The MODULE_ALIAS statement refers to a macro that has never been defined > in this driver, causing a build error: > > drivers/mtd/spi-nor/stm32-quadspi.c:694:150: error: expected ',' or ';' > before 'DRIVER_NAME' > > Unless there is a specific

Re: [PATCH] mtd: spi-nor: stm32: remove broken MODULE_ALIAS

Le 27/04/2017 à 13:09, Arnd Bergmann a écrit : > The MODULE_ALIAS statement refers to a macro that has never been defined > in this driver, causing a build error: > > drivers/mtd/spi-nor/stm32-quadspi.c:694:150: error: expected ',' or ';' > before 'DRIVER_NAME' > > Unless there is a specific

Re: [PATCH v2 resend] selftests: create cpufreq kconfig fragments

On 04/26/2017 04:09 AM, naresh.kamb...@linaro.org wrote: > From: Naresh Kamboju > > For the better test coverage of cpufreq driver code these extra configurations > are needed. Enable cpufreq governors and stats. > > Signed-off-by: Naresh Kamboju

Re: [PATCH v2 resend] selftests: create cpufreq kconfig fragments

On 04/26/2017 04:09 AM, naresh.kamb...@linaro.org wrote: > From: Naresh Kamboju > > For the better test coverage of cpufreq driver code these extra configurations > are needed. Enable cpufreq governors and stats. > > Signed-off-by: Naresh Kamboju > Acked-by: Viresh Kumar Applied to

RE: [PATCH v6 1/5] skbuff: return -EMSGSIZE in skb_to_sgvec to prevent overflow

From: Jason A. Donenfeld > On Thu, Apr 27, 2017 at 1:30 PM, Sabrina Dubroca wrote: > > Hmm, I think this can actually happen: > > Alright, perhaps better to err on the side of caution, then. You only need to recurse if both pointers are set. David

RE: [PATCH v6 1/5] skbuff: return -EMSGSIZE in skb_to_sgvec to prevent overflow

From: Jason A. Donenfeld > On Thu, Apr 27, 2017 at 1:30 PM, Sabrina Dubroca wrote: > > Hmm, I think this can actually happen: > > Alright, perhaps better to err on the side of caution, then. You only need to recurse if both pointers are set. David

Re: Generic DMA-capable streaming device driver looking for home

On 4/27/2017 10:00 AM, Jon Masters wrote: > On 04/20/2017 06:10 PM, Alex Williams wrote: >> Hi all, >> >> We're writing a device driver and having some difficulty matching a >> subsystem to the driver/device properties. Can anyone help with >> direction? >> >> These are some basic properties: >>

Re: Generic DMA-capable streaming device driver looking for home

On 4/27/2017 10:00 AM, Jon Masters wrote: > On 04/20/2017 06:10 PM, Alex Williams wrote: >> Hi all, >> >> We're writing a device driver and having some difficulty matching a >> subsystem to the driver/device properties. Can anyone help with >> direction? >> >> These are some basic properties: >>

Re: [PATCH V2] x86/tboot: add an option to disable iommu force on

On Thu, Apr 27, 2017 at 10:42:07AM +0200, Joerg Roedel wrote: > On Thu, Apr 27, 2017 at 08:51:42AM +0200, Ingo Molnar wrote: > > > + tboot_noforce [Default Off] > > > + Do not force the Intel IOMMU enabled under tboot. > > > + By default, tboot will force

Re: [PATCH V2] x86/tboot: add an option to disable iommu force on

On Thu, Apr 27, 2017 at 10:42:07AM +0200, Joerg Roedel wrote: > On Thu, Apr 27, 2017 at 08:51:42AM +0200, Ingo Molnar wrote: > > > + tboot_noforce [Default Off] > > > + Do not force the Intel IOMMU enabled under tboot. > > > + By default, tboot will force

Re: [PATCH v2] acpi: fix acpi_get_table() leak / acpi-sysfs denial of service

On Wed, Apr 26, 2017 at 11:49 PM, Zheng, Lv wrote: > Hi, Rafael > >> From: linux-acpi-ow...@vger.kernel.org >> [mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Rafael J. >> Wysocki >> Subject: Re: [PATCH v2] acpi: fix acpi_get_table() leak / acpi-sysfs denial >> of

Re: [PATCH v2] acpi: fix acpi_get_table() leak / acpi-sysfs denial of service

On Wed, Apr 26, 2017 at 11:49 PM, Zheng, Lv wrote: > Hi, Rafael > >> From: linux-acpi-ow...@vger.kernel.org >> [mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Rafael J. >> Wysocki >> Subject: Re: [PATCH v2] acpi: fix acpi_get_table() leak / acpi-sysfs denial >> of service >> >> On Tue,

RE: [PATCH 3/5] ACPI / sleep: EC-based wakeup from suspend-to-idle on Dell systems

> -Original Message- > From: Rafael J. Wysocki [mailto:r...@rjwysocki.net] > Sent: Wednesday, April 26, 2017 4:24 PM > To: Linux PM > Cc: Andy Shevchenko ; Darren Hart > ; LKML

RE: [PATCH 3/5] ACPI / sleep: EC-based wakeup from suspend-to-idle on Dell systems

> -Original Message- > From: Rafael J. Wysocki [mailto:r...@rjwysocki.net] > Sent: Wednesday, April 26, 2017 4:24 PM > To: Linux PM > Cc: Andy Shevchenko ; Darren Hart > ; LKML ; Linux ACPI > a...@vger.kernel.org>; Srinivas Pandruvada > ; Thomas Gleixner ; > Mika Westerberg ;

Re: [PATCH v2] gpiolib: Add stubs for gpiod lookup table interface

On Thu, Apr 27, 2017 at 5:29 PM, Anatolij Gustschin wrote: > On Thu, 27 Apr 2017 16:25:34 +0200 > Anatolij Gustschin ag...@denx.de wrote: > >>On Thu, 27 Apr 2017 17:07:23 +0300 >>Andy Shevchenko andy.shevche...@gmail.com wrote: > ... >>>static inline void

Re: [PATCH v2] gpiolib: Add stubs for gpiod lookup table interface

On Thu, Apr 27, 2017 at 5:29 PM, Anatolij Gustschin wrote: > On Thu, 27 Apr 2017 16:25:34 +0200 > Anatolij Gustschin ag...@denx.de wrote: > >>On Thu, 27 Apr 2017 17:07:23 +0300 >>Andy Shevchenko andy.shevche...@gmail.com wrote: > ... >>>static inline void gpiod_add_lookup_table(struct

Re: [PATCH 1/3] mm: Silence vmap() allocation failures based on caller gfp_flags

On Tue 25-04-17 15:33:29, Florian Fainelli wrote: > If the caller has set __GFP_NOWARN don't print the following message: > vmap allocation for size 15736832 failed: use vmalloc= to increase > size. > > This can happen with the ARM/Linux module loader built with > CONFIG_ARM_MODULE_PLTS=y which

[PATCH v8 1/4] syscalls: Verify address limit before returning to user-mode

Ensure that a syscall does not return to user-mode with a kernel address limit. If that happens, a process can corrupt kernel-mode memory and elevate privileges [1]. The CONFIG_ADDR_LIMIT_CHECK option disables the generic check so each architecture can create optimized versions. [1]

[PATCH v8 1/4] syscalls: Verify address limit before returning to user-mode

Ensure that a syscall does not return to user-mode with a kernel address limit. If that happens, a process can corrupt kernel-mode memory and elevate privileges [1]. The CONFIG_ADDR_LIMIT_CHECK option disables the generic check so each architecture can create optimized versions. [1]

Re: [PATCH 1/3] mm: Silence vmap() allocation failures based on caller gfp_flags

On Tue 25-04-17 15:33:29, Florian Fainelli wrote: > If the caller has set __GFP_NOWARN don't print the following message: > vmap allocation for size 15736832 failed: use vmalloc= to increase > size. > > This can happen with the ARM/Linux module loader built with > CONFIG_ARM_MODULE_PLTS=y which

Re: [PATCH] [media] mtk-mdp: Fix g_/s_selection capture/compose logic

Hi, On 04/13/2017 07:18 AM, Minghsiu Tsai wrote: > From: Daniel Kurtz > > Experiments show that the: > (1) mtk-mdp uses the _MPLANE form of CAPTURE/OUTPUT > (2) CAPTURE types use CROP targets, and OUTPUT types use COMPOSE targets > > Signed-off-by: Daniel Kurtz

Re: [PATCH] [media] mtk-mdp: Fix g_/s_selection capture/compose logic

Hi, On 04/13/2017 07:18 AM, Minghsiu Tsai wrote: > From: Daniel Kurtz > > Experiments show that the: > (1) mtk-mdp uses the _MPLANE form of CAPTURE/OUTPUT > (2) CAPTURE types use CROP targets, and OUTPUT types use COMPOSE targets > > Signed-off-by: Daniel Kurtz > Signed-off-by: Minghsiu

[PATCH v3] NFC: trf7970a: Correct register settings for 27MHz clock

In prior commits the selected clock frequency does not propagate correctly to what is written the the TRF7970A_MODULATOR_SYS_CLK_CTRL register. Signed-off-by: Geoff Lansberry --- drivers/nfc/trf7970a.c | 7 +++ 1 file changed, 7 insertions(+) diff --git

[PATCH v3] NFC: trf7970a: Correct register settings for 27MHz clock

In prior commits the selected clock frequency does not propagate correctly to what is written the the TRF7970A_MODULATOR_SYS_CLK_CTRL register. Signed-off-by: Geoff Lansberry --- drivers/nfc/trf7970a.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/drivers/nfc/trf7970a.c

Re: [PATCH 1/3] ARM: at91: pm: Add sama5d2 backup mode

On 27/04/2017 at 15:34:07 +0200, Romain Izard wrote: > Hello Alexandre, > > This series might also be of interest for the linux-pm mailing list. > I don't think they care enough to review that. > 2017-04-26 18:04 GMT+02:00 Alexandre Belloni > > diff --git a/arch/arm/mach-at91/Makefile

Re: [PATCH 1/3] ARM: at91: pm: Add sama5d2 backup mode

On 27/04/2017 at 15:34:07 +0200, Romain Izard wrote: > Hello Alexandre, > > This series might also be of interest for the linux-pm mailing list. > I don't think they care enough to review that. > 2017-04-26 18:04 GMT+02:00 Alexandre Belloni > > diff --git a/arch/arm/mach-at91/Makefile

Re: [REGRESSION next-20170426] Commit 09515ef5ddad ("of/acpi: Configure dma operations at probe time for platform/amba/pci bus devices") causes oops in mvneta

On Thu, 27 Apr 2017 19:05:09 +0530 Sricharan R wrote: > Hi, > > On 4/26/2017 9:45 PM, Ralph Sennhauser wrote: > > Hi Sricharan R, > > > > Commit 09515ef5ddad ("of/acpi: Configure dma operations at probe > > time for platform/amba/pci bus devices") causes a kernel

Re: [REGRESSION next-20170426] Commit 09515ef5ddad ("of/acpi: Configure dma operations at probe time for platform/amba/pci bus devices") causes oops in mvneta

On Thu, 27 Apr 2017 19:05:09 +0530 Sricharan R wrote: > Hi, > > On 4/26/2017 9:45 PM, Ralph Sennhauser wrote: > > Hi Sricharan R, > > > > Commit 09515ef5ddad ("of/acpi: Configure dma operations at probe > > time for platform/amba/pci bus devices") causes a kernel panic as > > in the log below

Re: [PATCH v2 1/2] mm: Uncharge poisoned pages

On Tue 25-04-17 16:27:51, Laurent Dufour wrote: > When page are poisoned, they should be uncharged from the root memory > cgroup. > > This is required to avoid a BUG raised when the page is onlined back: > BUG: Bad page state in process mem-on-off-test pfn:7ae3b > page:f1eb8ec0 count:0

Re: [PATCH v2 1/2] mm: Uncharge poisoned pages

On Tue 25-04-17 16:27:51, Laurent Dufour wrote: > When page are poisoned, they should be uncharged from the root memory > cgroup. > > This is required to avoid a BUG raised when the page is onlined back: > BUG: Bad page state in process mem-on-off-test pfn:7ae3b > page:f1eb8ec0 count:0

Re: [PATCH] perf evsel: Fix to perf-stat malloc corruption on arm64 platforms

On Wed, Apr 26, 2017 at 11:49:46PM +0530, Ganapatrao Kulkarni wrote: > On Wed, Apr 26, 2017 at 10:42 PM, Mark Rutland wrote: > > diff --git a/tools/perf/builtin-stat.c b/tools/perf/builtin-stat.c > > index 13b5499..638aefa 100644 > > --- a/tools/perf/builtin-stat.c > > +++

Re: [PATCH] perf evsel: Fix to perf-stat malloc corruption on arm64 platforms

On Wed, Apr 26, 2017 at 11:49:46PM +0530, Ganapatrao Kulkarni wrote: > On Wed, Apr 26, 2017 at 10:42 PM, Mark Rutland wrote: > > diff --git a/tools/perf/builtin-stat.c b/tools/perf/builtin-stat.c > > index 13b5499..638aefa 100644 > > --- a/tools/perf/builtin-stat.c > > +++

Re: [PATCH v5 1/4] printk/nmi: generic solution for safe printk in NMI

On Thu, 27 Apr 2017 15:38:19 +0200 Petr Mladek wrote: > > by the way, > > does this `nmi_print_seq' bypass even fix anything for Steven? > > I think that this is the most important question. > > Steven, does the patch from >

Re: [PATCH v5 1/4] printk/nmi: generic solution for safe printk in NMI

On Thu, 27 Apr 2017 15:38:19 +0200 Petr Mladek wrote: > > by the way, > > does this `nmi_print_seq' bypass even fix anything for Steven? > > I think that this is the most important question. > > Steven, does the patch from > https://lkml.kernel.org/r/20170420131154.gl3...@pathway.suse.cz >

[PATCH] block, dax: use correct format string in bdev_dax_supported

The new message has an incorrect format string, causing a warning in some configurations: fs/block_dev.c: In function 'bdev_dax_supported': fs/block_dev.c:779:5: error: format '%d' expects argument of type 'int', but argument 2 has type 'long int' [-Werror=format=] "error: dax access failed

[PATCH] block, dax: use correct format string in bdev_dax_supported

The new message has an incorrect format string, causing a warning in some configurations: fs/block_dev.c: In function 'bdev_dax_supported': fs/block_dev.c:779:5: error: format '%d' expects argument of type 'int', but argument 2 has type 'long int' [-Werror=format=] "error: dax access failed

Re: [PATCH net-next] can: fix build error without CONFIG_PROC_FS

Hello Arnd, On 04/27/2017 04:21 PM, Arnd Bergmann wrote: > The procfs dir entry was added inside of an #ifdef, causing a build error > when we try to access it without CONFIG_PROC_FS set: > > net/can/bcm.c:1541:14: error: 'struct netns_can' has no member named > 'bcmproc_dir' > net/can/bcm.c:

Re: [PATCH net-next] can: fix build error without CONFIG_PROC_FS

Hello Arnd, On 04/27/2017 04:21 PM, Arnd Bergmann wrote: > The procfs dir entry was added inside of an #ifdef, causing a build error > when we try to access it without CONFIG_PROC_FS set: > > net/can/bcm.c:1541:14: error: 'struct netns_can' has no member named > 'bcmproc_dir' > net/can/bcm.c:

Re: [PATCH v2] gpiolib: Add stubs for gpiod lookup table interface

On Thu, 27 Apr 2017 16:25:34 +0200 Anatolij Gustschin ag...@denx.de wrote: >On Thu, 27 Apr 2017 17:07:23 +0300 >Andy Shevchenko andy.shevche...@gmail.com wrote: ... >>static inline void gpiod_add_lookup_table(struct gpiod_lookup_table *table) {} >>static inline void

Re: [PATCH v2] gpiolib: Add stubs for gpiod lookup table interface

On Thu, 27 Apr 2017 16:25:34 +0200 Anatolij Gustschin ag...@denx.de wrote: >On Thu, 27 Apr 2017 17:07:23 +0300 >Andy Shevchenko andy.shevche...@gmail.com wrote: ... >>static inline void gpiod_add_lookup_table(struct gpiod_lookup_table *table) {} >>static inline void

[PATCH] irqchip/gicv3-its: use IORT only if IOMMU support is enabled

When the IOMMU subsystem is disabled, we cannot build ARM64 kernels with ACPI: drivers/acpi/arm64/iort.c: In function 'iort_iommu_xlate': drivers/acpi/arm64/iort.c:647:22: error: 'struct iommu_fwspec' has no member named 'ops' This adds a Kconfig dependency to only enable ACPI_IORT when it

[PATCH] irqchip/gicv3-its: use IORT only if IOMMU support is enabled

When the IOMMU subsystem is disabled, we cannot build ARM64 kernels with ACPI: drivers/acpi/arm64/iort.c: In function 'iort_iommu_xlate': drivers/acpi/arm64/iort.c:647:22: error: 'struct iommu_fwspec' has no member named 'ops' This adds a Kconfig dependency to only enable ACPI_IORT when it

Re: [PATCH] ASoC: Intel: Skylake: fix uninitialized pointer use

On Thu, Apr 27, 2017 at 12:59:58PM +0200, Arnd Bergmann wrote: > The error handling in bxt_sst_dsp_init() got changed in a way that > it now derefences an uninitialized pointer when printing a warning > about the device not being found: > > sound/soc/intel/skylake/bxt-sst.c: In function

Re: [PATCH v2] gpiolib: Add stubs for gpiod lookup table interface

On Thu, 27 Apr 2017 17:07:23 +0300 Andy Shevchenko andy.shevche...@gmail.com wrote: >On Thu, Apr 27, 2017 at 9:52 AM, Anatolij Gustschin wrote: >> Add stubs for gpiod_add_lookup_table() and gpiod_remove_lookup_table() >> for the !GPIOLIB case to prevent build errors. Also add

Re: [PATCH] ASoC: Intel: Skylake: fix uninitialized pointer use

On Thu, Apr 27, 2017 at 12:59:58PM +0200, Arnd Bergmann wrote: > The error handling in bxt_sst_dsp_init() got changed in a way that > it now derefences an uninitialized pointer when printing a warning > about the device not being found: > > sound/soc/intel/skylake/bxt-sst.c: In function

Re: [PATCH v2] gpiolib: Add stubs for gpiod lookup table interface

On Thu, 27 Apr 2017 17:07:23 +0300 Andy Shevchenko andy.shevche...@gmail.com wrote: >On Thu, Apr 27, 2017 at 9:52 AM, Anatolij Gustschin wrote: >> Add stubs for gpiod_add_lookup_table() and gpiod_remove_lookup_table() >> for the !GPIOLIB case to prevent build errors. Also add prototypes. >> >>

[PATCH net-next] can: fix build error without CONFIG_PROC_FS

The procfs dir entry was added inside of an #ifdef, causing a build error when we try to access it without CONFIG_PROC_FS set: net/can/bcm.c:1541:14: error: 'struct netns_can' has no member named 'bcmproc_dir' net/can/bcm.c: In function 'bcm_connect': net/can/bcm.c:1601:14: error: 'struct

[tip:sched/urgent] sched/cputime: Fix ksoftirqd cputime accounting regression

Commit-ID: 25e2d8c1b9e327ed260edd13169cc22bc7a78bc6 Gitweb: http://git.kernel.org/tip/25e2d8c1b9e327ed260edd13169cc22bc7a78bc6 Author: Frederic Weisbecker AuthorDate: Tue, 25 Apr 2017 16:10:48 +0200 Committer: Ingo Molnar CommitDate: Thu, 27 Apr

[PATCH net-next] can: fix build error without CONFIG_PROC_FS

The procfs dir entry was added inside of an #ifdef, causing a build error when we try to access it without CONFIG_PROC_FS set: net/can/bcm.c:1541:14: error: 'struct netns_can' has no member named 'bcmproc_dir' net/can/bcm.c: In function 'bcm_connect': net/can/bcm.c:1601:14: error: 'struct

[tip:sched/urgent] sched/cputime: Fix ksoftirqd cputime accounting regression

Commit-ID: 25e2d8c1b9e327ed260edd13169cc22bc7a78bc6 Gitweb: http://git.kernel.org/tip/25e2d8c1b9e327ed260edd13169cc22bc7a78bc6 Author: Frederic Weisbecker AuthorDate: Tue, 25 Apr 2017 16:10:48 +0200 Committer: Ingo Molnar CommitDate: Thu, 27 Apr 2017 09:08:26 +0200 sched/cputime: Fix

[PATCHv2 3/6] blackfin: defconfig: MCP23S08 config has been renamed

The mcp23s08 driver now supports pinconf, so the config option has been renamed from CONFIG_GPIO_MCP23S08 to CONFIG_PINCTRL_MCP23S08. Signed-off-by: Sebastian Reichel --- arch/blackfin/configs/BF609-EZKIT_defconfig | 2 +- 1 file changed, 1 insertion(+), 1

[PATCHv2 3/6] blackfin: defconfig: MCP23S08 config has been renamed

The mcp23s08 driver now supports pinconf, so the config option has been renamed from CONFIG_GPIO_MCP23S08 to CONFIG_PINCTRL_MCP23S08. Signed-off-by: Sebastian Reichel --- arch/blackfin/configs/BF609-EZKIT_defconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCHv2 6/6] pinctrl: mcp23s08: drop pullup config from pdata

mcp23s08 support configuration of the pullups using the pinconf framework. This removes the custom pullup configuration from platform data, which has no upstream users. Signed-off-by: Sebastian Reichel --- drivers/pinctrl/pinctrl-mcp23s08.c | 7 ---

[PATCHv2 6/6] pinctrl: mcp23s08: drop pullup config from pdata

mcp23s08 support configuration of the pullups using the pinconf framework. This removes the custom pullup configuration from platform data, which has no upstream users. Signed-off-by: Sebastian Reichel --- drivers/pinctrl/pinctrl-mcp23s08.c | 7 --- include/linux/spi/mcp23s08.h | 1 -

[PATCHv2 5/6] pinctrl: mcp23s08: add pinconf support

mcp23xxx device have configurable 100k pullup resistors. This adds support for enabling them using pinctrl's pinconf interface. Signed-off-by: Sebastian Reichel --- drivers/pinctrl/Kconfig| 1 + drivers/pinctrl/pinctrl-mcp23s08.c | 199

[PATCHv2 0/6] mcp23s08 pinconf support

Hi, Back in January I sent patches adding pinconf support for configuring mcp23s08's pull-ups. Apart from my custom Raspberry Pi setup the pull-up support is also needed by Toby Churchill SL50. Changes since PATCHv1: * Add patch moving mcp23s08 from gpio/ to pinctrl/ * Add patches updating

[PATCHv2 5/6] pinctrl: mcp23s08: add pinconf support

mcp23xxx device have configurable 100k pullup resistors. This adds support for enabling them using pinctrl's pinconf interface. Signed-off-by: Sebastian Reichel --- drivers/pinctrl/Kconfig| 1 + drivers/pinctrl/pinctrl-mcp23s08.c | 199 - 2

[PATCHv2 0/6] mcp23s08 pinconf support

Hi, Back in January I sent patches adding pinconf support for configuring mcp23s08's pull-ups. Apart from my custom Raspberry Pi setup the pull-up support is also needed by Toby Churchill SL50. Changes since PATCHv1: * Add patch moving mcp23s08 from gpio/ to pinctrl/ * Add patches updating

[PATCHv2 1/6] gpio: mcp23s08: move to pinctrl

This moves the mcp23s08 driver from gpio to pinctrl. Actual pinctrl support for configuration of the pull-up resistors follows in its own patch. Signed-off-by: Sebastian Reichel --- drivers/gpio/Kconfig| 17 -

[PATCHv2 1/6] gpio: mcp23s08: move to pinctrl

This moves the mcp23s08 driver from gpio to pinctrl. Actual pinctrl support for configuration of the pull-up resistors follows in its own patch. Signed-off-by: Sebastian Reichel --- drivers/gpio/Kconfig| 17 - drivers/gpio/Makefile

[PATCH net] net: hns: fix ethtool_get_strings overflow in hns driver

hns_get_sset_count() returns HNS_NET_STATS_CNT and the data space allocated is not enough for ethtool_get_strings(), which will cause random memory corruption. When SLAB and DEBUG_SLAB are both enabled, memory corruptions like the the following can be observed without this patch: [ 43.115200]

[PATCH net] net: hns: fix ethtool_get_strings overflow in hns driver

hns_get_sset_count() returns HNS_NET_STATS_CNT and the data space allocated is not enough for ethtool_get_strings(), which will cause random memory corruption. When SLAB and DEBUG_SLAB are both enabled, memory corruptions like the the following can be observed without this patch: [ 43.115200]

[PATCHv2 2/6] blackfin: boards: MCP23S08 config has been renamed

The mcp23s08 driver now supports pinconf, so the config option has been renamed from CONFIG_GPIO_MCP23S08 to CONFIG_PINCTRL_MCP23S08. Signed-off-by: Sebastian Reichel --- arch/blackfin/mach-bf527/boards/tll6527m.c | 4 ++--

[PATCHv2 2/6] blackfin: boards: MCP23S08 config has been renamed

The mcp23s08 driver now supports pinconf, so the config option has been renamed from CONFIG_GPIO_MCP23S08 to CONFIG_PINCTRL_MCP23S08. Signed-off-by: Sebastian Reichel --- arch/blackfin/mach-bf527/boards/tll6527m.c | 4 ++-- arch/blackfin/mach-bf609/boards/ezkit.c| 4 ++-- 2 files changed, 4

[PATCHv2 4/6] arm: lpc32xx: defconfig: MCP23S08 config has been renamed

The mcp23s08 driver now supports pinconf, so the config option has been renamed from CONFIG_GPIO_MCP23S08 to CONFIG_PINCTRL_MCP23S08. Signed-off-by: Sebastian Reichel --- arch/arm/configs/lpc32xx_defconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCHv2 4/6] arm: lpc32xx: defconfig: MCP23S08 config has been renamed

The mcp23s08 driver now supports pinconf, so the config option has been renamed from CONFIG_GPIO_MCP23S08 to CONFIG_PINCTRL_MCP23S08. Signed-off-by: Sebastian Reichel --- arch/arm/configs/lpc32xx_defconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH v8 1/4] syscalls: Verify address limit before returning to user-mode

On Wed, Apr 26, 2017 at 11:49 PM, Ingo Molnar wrote: > > * Thomas Garnier wrote: > >> + >> +/* >> + * Called before coming back to user-mode. Returning to user-mode with an >> + * address limit different than USER_DS can allow to overwrite kernel >>

Re: [PATCH v8 1/4] syscalls: Verify address limit before returning to user-mode

On Wed, Apr 26, 2017 at 11:49 PM, Ingo Molnar wrote: > > * Thomas Garnier wrote: > >> + >> +/* >> + * Called before coming back to user-mode. Returning to user-mode with an >> + * address limit different than USER_DS can allow to overwrite kernel >> memory. >> + */ >> +static inline void

Re: [PATCH 3/4] iommu: Remove pci.h include from trace/events/iommu.h

/20170427-160734 config: tile-allmodconfig (attached as .config) compiler: tilegx-linux-gcc (GCC) 4.6.2 reproduce: wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross # save the attached .config to linux

Re: [PATCH 3/4] iommu: Remove pci.h include from trace/events/iommu.h

/20170427-160734 config: tile-allmodconfig (attached as .config) compiler: tilegx-linux-gcc (GCC) 4.6.2 reproduce: wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross # save the attached .config to linux

[PATCH man-pages 2/2] ioctl_userfaultfd.2: start adding details about userfaultfd features

Signed-off-by: Mike Rapoport --- man2/ioctl_userfaultfd.2 | 53 ++-- 1 file changed, 51 insertions(+), 2 deletions(-) diff --git a/man2/ioctl_userfaultfd.2 b/man2/ioctl_userfaultfd.2 index 42bf7a7..cdc07e0 100644 ---

[PATCH man-pages 2/2] ioctl_userfaultfd.2: start adding details about userfaultfd features

Signed-off-by: Mike Rapoport --- man2/ioctl_userfaultfd.2 | 53 ++-- 1 file changed, 51 insertions(+), 2 deletions(-) diff --git a/man2/ioctl_userfaultfd.2 b/man2/ioctl_userfaultfd.2 index 42bf7a7..cdc07e0 100644 --- a/man2/ioctl_userfaultfd.2 +++

[PATCH man-pages 0/2] some more userfault pages updates

Hi Michael, Here are some more updates to {ioctl_}userfaultfd.2 pages. Mike Rapoport (2): userfaultfd.2: start documenting non-cooperative events ioctl_userfaultfd.2: start adding details about userfaultfd features man2/ioctl_userfaultfd.2 | 53 ++- man2/userfaultfd.2

[PATCH man-pages 0/2] some more userfault pages updates

Hi Michael, Here are some more updates to {ioctl_}userfaultfd.2 pages. Mike Rapoport (2): userfaultfd.2: start documenting non-cooperative events ioctl_userfaultfd.2: start adding details about userfaultfd features man2/ioctl_userfaultfd.2 | 53 ++- man2/userfaultfd.2

[PATCH man-pages 1/2] userfaultfd.2: start documenting non-cooperative events

Signed-off-by: Mike Rapoport --- man2/userfaultfd.2 | 135 ++--- 1 file changed, 128 insertions(+), 7 deletions(-) diff --git a/man2/userfaultfd.2 b/man2/userfaultfd.2 index cfea5cb..44af3e4 100644 --- a/man2/userfaultfd.2

[PATCH man-pages 1/2] userfaultfd.2: start documenting non-cooperative events

Signed-off-by: Mike Rapoport --- man2/userfaultfd.2 | 135 ++--- 1 file changed, 128 insertions(+), 7 deletions(-) diff --git a/man2/userfaultfd.2 b/man2/userfaultfd.2 index cfea5cb..44af3e4 100644 --- a/man2/userfaultfd.2 +++ b/man2/userfaultfd.2

Re: [PATCH v2] gpiolib: Add stubs for gpiod lookup table interface

On Thu, Apr 27, 2017 at 9:52 AM, Anatolij Gustschin wrote: > Add stubs for gpiod_add_lookup_table() and gpiod_remove_lookup_table() > for the !GPIOLIB case to prevent build errors. Also add prototypes. > > Signed-off-by: Anatolij Gustschin > Reviewed-by: Andy

Re: [PATCH v2] gpiolib: Add stubs for gpiod lookup table interface

On Thu, Apr 27, 2017 at 9:52 AM, Anatolij Gustschin wrote: > Add stubs for gpiod_add_lookup_table() and gpiod_remove_lookup_table() > for the !GPIOLIB case to prevent build errors. Also add prototypes. > > Signed-off-by: Anatolij Gustschin > Reviewed-by: Andy Shevchenko Oh, has to take my tag

Re: [PATCH 1/1] Remove hardcoding of ___GFP_xxx bitmasks

On 27/04/17 16:41, Michal Hocko wrote: > On Wed 26-04-17 18:29:08, Igor Stoppa wrote: > [...] >> If you prefer to have this patch only as part of the larger patchset, >> I'm also fine with it. > > I agree that the situation is not ideal. If a larger set of changes > would benefit from this

Re: [PATCH 1/1] Remove hardcoding of ___GFP_xxx bitmasks

On 27/04/17 16:41, Michal Hocko wrote: > On Wed 26-04-17 18:29:08, Igor Stoppa wrote: > [...] >> If you prefer to have this patch only as part of the larger patchset, >> I'm also fine with it. > > I agree that the situation is not ideal. If a larger set of changes > would benefit from this

Re: [PATCH] usb: gadget: udc-xilinx: clean up a variable name

On Thu, 2017-04-27 at 12:11:18 +0300, Dan Carpenter wrote: > "ep->udc->lock" and "udc->lock" are the same thing. It confuses Smatch > if we don't use the same name consistently. > > Signed-off-by: Dan Carpenter Reviewed-by: Sören Brinkmann

Re: [PATCH] usb: gadget: udc-xilinx: clean up a variable name

On Thu, 2017-04-27 at 12:11:18 +0300, Dan Carpenter wrote: > "ep->udc->lock" and "udc->lock" are the same thing. It confuses Smatch > if we don't use the same name consistently. > > Signed-off-by: Dan Carpenter Reviewed-by: Sören Brinkmann Sören

Re: [trace-cmd Patch RFC] trace-cmd: top: A new interface to detect peak memory

Hi Steve, On Wednesday 26 April 2017 07:31 PM, Steven Rostedt wrote: Sorry for the late reply. I finally have time to start looking at trace-cmd again. Thanks a lot for your review :-) On Wed, 1 Mar 2017 20:32:37 +0530 Pratyush Anand wrote: [...] This is as nice

Re: [trace-cmd Patch RFC] trace-cmd: top: A new interface to detect peak memory

Hi Steve, On Wednesday 26 April 2017 07:31 PM, Steven Rostedt wrote: Sorry for the late reply. I finally have time to start looking at trace-cmd again. Thanks a lot for your review :-) On Wed, 1 Mar 2017 20:32:37 +0530 Pratyush Anand wrote: [...] This is as nice idea, but it needs

Re: Generic DMA-capable streaming device driver looking for home

On 04/20/2017 06:10 PM, Alex Williams wrote: > Hi all, > > We're writing a device driver and having some difficulty matching a > subsystem to the driver/device properties. Can anyone help with > direction? > > These are some basic properties: > 1) Device is used to carry generic data to/from

Re: Generic DMA-capable streaming device driver looking for home

On 04/20/2017 06:10 PM, Alex Williams wrote: > Hi all, > > We're writing a device driver and having some difficulty matching a > subsystem to the driver/device properties. Can anyone help with > direction? > > These are some basic properties: > 1) Device is used to carry generic data to/from

Dearest

Dearest , I am constrained to contact you because of the maltreatment which I am receiving from my step mother. She planned to take away all my late father's retassure and properties from me since the unexpected death of my beloved Father ,my mother died 10years ago and I was left alone with

Dearest

Dearest , I am constrained to contact you because of the maltreatment which I am receiving from my step mother. She planned to take away all my late father's retassure and properties from me since the unexpected death of my beloved Father ,my mother died 10years ago and I was left alone with

Re: [PATCH v4 4/4] KEYS: Print insert-sys-cert information to stdout instead of stderr

Mehmet Kayaalp wrote: > +#define info(format, args...) fprintf(stdout, "INFO:" format, ## args) Btw, you really ought to be using standard varargs macros: #define info(format, ...) fprintf(stdout, "INFO:" format, ##__VA_LIST__) But don't worry

Re: [PATCH v4 4/4] KEYS: Print insert-sys-cert information to stdout instead of stderr

Mehmet Kayaalp wrote: > +#define info(format, args...) fprintf(stdout, "INFO:" format, ## args) Btw, you really ought to be using standard varargs macros: #define info(format, ...) fprintf(stdout, "INFO:" format, ##__VA_LIST__) But don't worry about that for now. David

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