Re: Sed-opal fixups

On Thu, Feb 09, 2017 at 05:43:20PM +, David Laight wrote: > From: Scott Bauer > > Sent: 09 February 2017 17:20 > > It may be too late to change anyhting in the uapi header. When we > > switched over to using IOC_SIZE I found a bug where I had switched > > up a structure in one of the series

Re: Sed-opal fixups

On Thu, Feb 09, 2017 at 05:43:20PM +, David Laight wrote: > From: Scott Bauer > > Sent: 09 February 2017 17:20 > > It may be too late to change anyhting in the uapi header. When we > > switched over to using IOC_SIZE I found a bug where I had switched > > up a structure in one of the series

[RFC] mm/hugetlb: use mem policy when allocating surplus huge pages

Application allocating overcommitted hugepages behave differently when its mempolicy is set to bind with NUMA nodes containing CPUs and not containing CPUs. When memory is allocated on node with CPUs everything work as expected, when memory is allocated on CPU-less node: 1. Some memory is

[RFC] mm/hugetlb: use mem policy when allocating surplus huge pages

Application allocating overcommitted hugepages behave differently when its mempolicy is set to bind with NUMA nodes containing CPUs and not containing CPUs. When memory is allocated on node with CPUs everything work as expected, when memory is allocated on CPU-less node: 1. Some memory is

Re: [PATCH v4] eeprom/at24: use device_property_*() functions instead of of_get_property()

On Thu, Feb 9, 2017 at 7:36 PM, Ben Gardner wrote: > Allow the at24 driver to get configuration information from both OF and > ACPI by using the more generic device_property functions. > This change was inspired by the at25.c driver. > > I have a custom board with a ST

Re: [PATCH v4] eeprom/at24: use device_property_*() functions instead of of_get_property()

On Thu, Feb 9, 2017 at 7:36 PM, Ben Gardner wrote: > Allow the at24 driver to get configuration information from both OF and > ACPI by using the more generic device_property functions. > This change was inspired by the at25.c driver. > > I have a custom board with a ST M24C02 EEPROM attached to

Re: mm: deadlock between get_online_cpus/pcpu_alloc

On Thu, 9 Feb 2017, Christoph Lameter wrote: > On Thu, 9 Feb 2017, Thomas Gleixner wrote: > > > You are just not getting it, really. > > > > The problem is that this for_each_online_cpu() is racy against a concurrent > > hot unplug and therefor can queue stuff for a not longer online cpu. That's

Re: mm: deadlock between get_online_cpus/pcpu_alloc

On Thu, 9 Feb 2017, Christoph Lameter wrote: > On Thu, 9 Feb 2017, Thomas Gleixner wrote: > > > You are just not getting it, really. > > > > The problem is that this for_each_online_cpu() is racy against a concurrent > > hot unplug and therefor can queue stuff for a not longer online cpu. That's

Re: [PATCH v3 13/14] mm: migrate: move_pages() supports thp migration

On 9 Feb 2017, at 3:16, Naoya Horiguchi wrote: > On Sun, Feb 05, 2017 at 11:12:51AM -0500, Zi Yan wrote: >> From: Naoya Horiguchi >> >> This patch enables thp migration for move_pages(2). >> >> Signed-off-by: Naoya Horiguchi >> --- >>

Re: [PATCH v3 13/14] mm: migrate: move_pages() supports thp migration

On 9 Feb 2017, at 3:16, Naoya Horiguchi wrote: > On Sun, Feb 05, 2017 at 11:12:51AM -0500, Zi Yan wrote: >> From: Naoya Horiguchi >> >> This patch enables thp migration for move_pages(2). >> >> Signed-off-by: Naoya Horiguchi >> --- >> mm/migrate.c | 37 - >>

Re: [PATCH v3 09/14] mm: thp: check pmd migration entry in common path

On 9 Feb 2017, at 3:16, Naoya Horiguchi wrote: > On Sun, Feb 05, 2017 at 11:12:47AM -0500, Zi Yan wrote: >> From: Naoya Horiguchi >> >> If one of callers of page migration starts to handle thp, >> memory management code start to see pmd migration entry, so we need >>

Re: [PATCH v3 09/14] mm: thp: check pmd migration entry in common path

On 9 Feb 2017, at 3:16, Naoya Horiguchi wrote: > On Sun, Feb 05, 2017 at 11:12:47AM -0500, Zi Yan wrote: >> From: Naoya Horiguchi >> >> If one of callers of page migration starts to handle thp, >> memory management code start to see pmd migration entry, so we need >> to prepare for it before

[PATCH v4] eeprom/at24: use device_property_*() functions instead of of_get_property()

Allow the at24 driver to get configuration information from both OF and ACPI by using the more generic device_property functions. This change was inspired by the at25.c driver. I have a custom board with a ST M24C02 EEPROM attached to an I2C bus. With the following ACPI construct, this patch

[PATCH v4] eeprom/at24: use device_property_*() functions instead of of_get_property()

Allow the at24 driver to get configuration information from both OF and ACPI by using the more generic device_property functions. This change was inspired by the at25.c driver. I have a custom board with a ST M24C02 EEPROM attached to an I2C bus. With the following ACPI construct, this patch

Re: [PATCH] drm: Add helper macro for duplicating custom drm_*_state

On Thu, Feb 09, 2017 at 03:41:42PM +, Mihail Atanassov wrote: > Assuming a derived struct of the form: > > struct foo_bar_state > { > struct drm_bar_state bar_state; > struct foo_private priv; > struct foo_private2 *priv2; > }; > > memcpy priv and priv2 to the new instance

Re: [PATCH] drm: Add helper macro for duplicating custom drm_*_state

On Thu, Feb 09, 2017 at 03:41:42PM +, Mihail Atanassov wrote: > Assuming a derived struct of the form: > > struct foo_bar_state > { > struct drm_bar_state bar_state; > struct foo_private priv; > struct foo_private2 *priv2; > }; > > memcpy priv and priv2 to the new instance

make pdfdoc errors with 4.10-rc7

On a Fedora 25 system, make pdfdocs is failing with [jim@krebstar linux-rc]$ grep -v -i 'warning:' /tmp/make-pdfdocs.err /data/linux-rc/Documentation/doc-guide/sphinx.rst:110: ERROR: Unknown target name: "sphinx c domain". ./include/net/cfg80211.h:3154: ERROR: Unexpected indentation.

[PATCH V3 2/2] Move stack parameters for sed_ioctl to prevent oversized stack with CONFIG_KASAN

When CONFIG_KASAN is enabled, compilation fails: block/sed-opal.c: In function 'sed_ioctl': block/sed-opal.c:2447:1: error: the frame size of 2256 bytes is larger than 2048 bytes [-Werror=frame-larger-than=] Moved all the ioctl structures off the stack and dynamically activate using _IOC_SIZE()

[PATCH V3 2/2] Move stack parameters for sed_ioctl to prevent oversized stack with CONFIG_KASAN

When CONFIG_KASAN is enabled, compilation fails: block/sed-opal.c: In function 'sed_ioctl': block/sed-opal.c:2447:1: error: the frame size of 2256 bytes is larger than 2048 bytes [-Werror=frame-larger-than=] Moved all the ioctl structures off the stack and dynamically activate using _IOC_SIZE()

make pdfdoc errors with 4.10-rc7

On a Fedora 25 system, make pdfdocs is failing with [jim@krebstar linux-rc]$ grep -v -i 'warning:' /tmp/make-pdfdocs.err /data/linux-rc/Documentation/doc-guide/sphinx.rst:110: ERROR: Unknown target name: "sphinx c domain". ./include/net/cfg80211.h:3154: ERROR: Unexpected indentation.

[PATCH V3 1/2] uapi: sed-opal fix IOW for activate lsp to use correct struct

the IOW for the IOC_OPAL_ACTIVATE_LSP took the wrong strcure which would give us the wrong size when using _IOC_SIZE, switch it to the right structure. Fixes: 058f8a2 ("Include: Uapi: Add user ABI for Sed/Opal") Signed-off-by: Scott Bauer ---

[PATCH V3 1/2] uapi: sed-opal fix IOW for activate lsp to use correct struct

the IOW for the IOC_OPAL_ACTIVATE_LSP took the wrong strcure which would give us the wrong size when using _IOC_SIZE, switch it to the right structure. Fixes: 058f8a2 ("Include: Uapi: Add user ABI for Sed/Opal") Signed-off-by: Scott Bauer --- include/uapi/linux/sed-opal.h | 2 +- 1 file

Sed-opal fixups

It may be too late to change anyhting in the uapi header. When we switched over to using IOC_SIZE I found a bug where I had switched up a structure in one of the series from v4 to v5 but never changed the structure in the IOW. The structure that was in there was to small so when we kzalloc on it

Sed-opal fixups

It may be too late to change anyhting in the uapi header. When we switched over to using IOC_SIZE I found a bug where I had switched up a structure in one of the series from v4 to v5 but never changed the structure in the IOW. The structure that was in there was to small so when we kzalloc on it

Re: [PATCH v3 01/14] Documentation: dt/bindings: Document pinctrl-ingenic

Le 2017-01-31 14:09, Linus Walleij a écrit : On Tue, Jan 31, 2017 at 11:31 AM, Paul Cercueil wrote: [Rob]: From the overlapping register addresses in the examples and this description, it looks like the pinctrlr and gpio controller are 1 block. If so, then there should

Re: [PATCH v3 01/14] Documentation: dt/bindings: Document pinctrl-ingenic

Le 2017-01-31 14:09, Linus Walleij a écrit : On Tue, Jan 31, 2017 at 11:31 AM, Paul Cercueil wrote: [Rob]: From the overlapping register addresses in the examples and this description, it looks like the pinctrlr and gpio controller are 1 block. If so, then there should only be 1 node.

Re: mm: deadlock between get_online_cpus/pcpu_alloc

On Thu, 9 Feb 2017, Thomas Gleixner wrote: > You are just not getting it, really. > > The problem is that this for_each_online_cpu() is racy against a concurrent > hot unplug and therefor can queue stuff for a not longer online cpu. That's > what the mm folks tried to avoid by preventing a CPU

Re: mm: deadlock between get_online_cpus/pcpu_alloc

On Thu, 9 Feb 2017, Thomas Gleixner wrote: > You are just not getting it, really. > > The problem is that this for_each_online_cpu() is racy against a concurrent > hot unplug and therefor can queue stuff for a not longer online cpu. That's > what the mm folks tried to avoid by preventing a CPU

Re: [RFC] drm: Helper macro for drm state duplication

On Thu, Feb 09, 2017 at 03:41:41PM +, Mihail Atanassov wrote: > Hi, > > I was working on a few patches adding fields to struct malidp_crtc_state and > found myself writing memcpy multiple times in the ->atomic_duplicate_state > hook because I wanted to avoid copying the drm_crtc_state twice >

Re: [RFC] drm: Helper macro for drm state duplication

On Thu, Feb 09, 2017 at 03:41:41PM +, Mihail Atanassov wrote: > Hi, > > I was working on a few patches adding fields to struct malidp_crtc_state and > found myself writing memcpy multiple times in the ->atomic_duplicate_state > hook because I wanted to avoid copying the drm_crtc_state twice >

Re: net/sctp: null-ptr-deref in sctp_put_port/sctp_endpoint_destroy

On Thu, Feb 9, 2017 at 3:00 AM, Andrey Konovalov wrote: > Hi, > > I've got the following error report while fuzzing the kernel with syzkaller. > > On commit 926af6273fc683cd98cd0ce7bf0d04a02eed6742. > > A reproducer and .config are attached. > > general protection fault:

Re: net/sctp: null-ptr-deref in sctp_put_port/sctp_endpoint_destroy

On Thu, Feb 9, 2017 at 3:00 AM, Andrey Konovalov wrote: > Hi, > > I've got the following error report while fuzzing the kernel with syzkaller. > > On commit 926af6273fc683cd98cd0ce7bf0d04a02eed6742. > > A reproducer and .config are attached. > > general protection fault: [#1] SMP KASAN >

Re: [PATCH] [net-next] ARM: orion: fix PHYLIB dependency

> Adding a 'select' statement to something as broad as NETDEVICES sounds > really bad, it has a significant risk of introducing dependency loops > and may be confusing if you want to build a multiplatform config without > networking support (note that NETDEVICES in turn depends on NET, which > can

Re: [PATCH] [net-next] ARM: orion: fix PHYLIB dependency

> Adding a 'select' statement to something as broad as NETDEVICES sounds > really bad, it has a significant risk of introducing dependency loops > and may be confusing if you want to build a multiplatform config without > networking support (note that NETDEVICES in turn depends on NET, which > can

Alpha Kernel Regression [was Re: BRSGP relocation truncations in linking kernel for Alpha.]

On Tue, Oct 25, 2016 at 09:26:38PM +1300, Michael Cree wrote: > And while I mention libc I am seeing (rather rare) random segfaults > in programs such as cp, tar, install and dpkg ever since the upgrade > to glibc 2.23 (or maybe it was 2.24). I am struggling to get a > backtrace because it only

Alpha Kernel Regression [was Re: BRSGP relocation truncations in linking kernel for Alpha.]

On Tue, Oct 25, 2016 at 09:26:38PM +1300, Michael Cree wrote: > And while I mention libc I am seeing (rather rare) random segfaults > in programs such as cp, tar, install and dpkg ever since the upgrade > to glibc 2.23 (or maybe it was 2.24). I am struggling to get a > backtrace because it only

Re: [BUGFIX PATCH tip/master V2 3/3] kprobes/arm: Fix a possible deadlock case in kretprobe

On Fri, Feb 10, 2017 at 01:32:22AM +0900, Masami Hiramatsu wrote: > Fix a possibility of deadlock case in kretprobe on arm > implementation. There may be a chance that the kretprobe > hash table lock can cause a dead lock. > > The senario is that a user puts 2 kretprobes, one on normal > function

Re: [BUGFIX PATCH tip/master V2 3/3] kprobes/arm: Fix a possible deadlock case in kretprobe

On Fri, Feb 10, 2017 at 01:32:22AM +0900, Masami Hiramatsu wrote: > Fix a possibility of deadlock case in kretprobe on arm > implementation. There may be a chance that the kretprobe > hash table lock can cause a dead lock. > > The senario is that a user puts 2 kretprobes, one on normal > function

[PATCH 0/3] KEYS: Fixes

/linux-fs.git keys-fixes-20170209 David --- Dan Carpenter (2): KEYS: Fix an error code in request_master_key() KEYS: Use memzero_explicit() for secret data Felix Fietkau (1): sign-file: fix build error in sign-file.c with libressl scripts/sign-file.c

[PATCH 2/3] KEYS: Fix an error code in request_master_key()

From: Dan Carpenter This function has two callers and neither are able to handle a NULL return. Really, -EINVAL is the correct thing return here anyway. This fixes some static checker warnings like: security/keys/encrypted-keys/encrypted.c:709

[PATCH 0/3] KEYS: Fixes

/linux-fs.git keys-fixes-20170209 David --- Dan Carpenter (2): KEYS: Fix an error code in request_master_key() KEYS: Use memzero_explicit() for secret data Felix Fietkau (1): sign-file: fix build error in sign-file.c with libressl scripts/sign-file.c

[PATCH 2/3] KEYS: Fix an error code in request_master_key()

From: Dan Carpenter This function has two callers and neither are able to handle a NULL return. Really, -EINVAL is the correct thing return here anyway. This fixes some static checker warnings like: security/keys/encrypted-keys/encrypted.c:709 encrypted_key_decrypt() error:

Re: [RFC][PATCH 00/21] tracing: Inter-event (e.g. latency) support

On Thu, 2017-02-09 at 23:18 +0900, Masami Hiramatsu wrote: > Hi Tom, > > On Wed, 08 Feb 2017 19:14:22 -0600 > Tom Zanussi wrote: > > > > > I'm submitting the patchset (based on tracing/for-next) as an RFC not > > > > only to get comments, but because there are still

Re: [RFC][PATCH 00/21] tracing: Inter-event (e.g. latency) support

On Thu, 2017-02-09 at 23:18 +0900, Masami Hiramatsu wrote: > Hi Tom, > > On Wed, 08 Feb 2017 19:14:22 -0600 > Tom Zanussi wrote: > > > > > I'm submitting the patchset (based on tracing/for-next) as an RFC not > > > > only to get comments, but because there are still some problems I > > > >

Re: [RFC] drm: Helper macro for drm state duplication

On Thu, Feb 09, 2017 at 05:57:04PM +0100, Daniel Vetter wrote: > On Thu, Feb 09, 2017 at 03:41:41PM +, Mihail Atanassov wrote: > > Hi, > > > > I was working on a few patches adding fields to struct malidp_crtc_state and > > found myself writing memcpy multiple times in the

Re: [RFC] drm: Helper macro for drm state duplication

On Thu, Feb 09, 2017 at 05:57:04PM +0100, Daniel Vetter wrote: > On Thu, Feb 09, 2017 at 03:41:41PM +, Mihail Atanassov wrote: > > Hi, > > > > I was working on a few patches adding fields to struct malidp_crtc_state and > > found myself writing memcpy multiple times in the

Re: [PATCH v3] eeprom/at24: use device_property_*() functions instead of of_get_property()

Ignore this last patch. I should remember to test even the simplest of cut-and-paste ops. On Thu, Feb 9, 2017 at 11:09 AM, Ben Gardner wrote: > Allow the at24 driver to get configuration information from both OF and > ACPI by using the more generic device_property

Re: [PATCH v3] eeprom/at24: use device_property_*() functions instead of of_get_property()

Ignore this last patch. I should remember to test even the simplest of cut-and-paste ops. On Thu, Feb 9, 2017 at 11:09 AM, Ben Gardner wrote: > Allow the at24 driver to get configuration information from both OF and > ACPI by using the more generic device_property functions. > This change was

[PATCH 1/3] sign-file: fix build error in sign-file.c with libressl

From: Felix Fietkau The sign-file tool failed to build against libressl. Fix this by extending the PKCS7 check and thus making sign-file link against libressl without an error. Signed-off-by: John Crispin Signed-off-by: Felix Fietkau

[PATCH 1/3] sign-file: fix build error in sign-file.c with libressl

From: Felix Fietkau The sign-file tool failed to build against libressl. Fix this by extending the PKCS7 check and thus making sign-file link against libressl without an error. Signed-off-by: John Crispin Signed-off-by: Felix Fietkau Signed-off-by: David Howells --- scripts/sign-file.c |

[PATCH 3/3] KEYS: Use memzero_explicit() for secret data

From: Dan Carpenter I don't think GCC has figured out how to optimize the memset() away, but they might eventually so let's future proof this code a bit. Signed-off-by: Dan Carpenter Signed-off-by: David Howells

[PATCH 3/3] KEYS: Use memzero_explicit() for secret data

From: Dan Carpenter I don't think GCC has figured out how to optimize the memset() away, but they might eventually so let's future proof this code a bit. Signed-off-by: Dan Carpenter Signed-off-by: David Howells Acked-by: Mimi Zohar --- security/keys/encrypted-keys/encrypted.c |2 +- 1

[PATCH v2 4/4] iio: chemical: add dsm501 particle sensor driver bindings

This patch adds bindings for dsm501 particle sensor driver. Signed-off-by: Tomasz Duszynski --- Changes in v2: o add 'data' prefix to gpios property .../devicetree/bindings/iio/chemical/dsm501.txt | 16 1 file changed, 16 insertions(+) create

[PATCH v3 2/4] iio: chemical: add driver for dsm501/ppd42ns particle sensors

This patch adds support for dsm501 and ppd42ns particle sensors. Both sensors work on the same principle. Heater (resistor) heats up air in sensor chamber which induces upward flow. Particles convect up through a light beam provided by internal infra-red LED. Light scattered by particles is

[PATCH v2 4/4] iio: chemical: add dsm501 particle sensor driver bindings

This patch adds bindings for dsm501 particle sensor driver. Signed-off-by: Tomasz Duszynski --- Changes in v2: o add 'data' prefix to gpios property .../devicetree/bindings/iio/chemical/dsm501.txt | 16 1 file changed, 16 insertions(+) create mode 100644

[PATCH v3 2/4] iio: chemical: add driver for dsm501/ppd42ns particle sensors

This patch adds support for dsm501 and ppd42ns particle sensors. Both sensors work on the same principle. Heater (resistor) heats up air in sensor chamber which induces upward flow. Particles convect up through a light beam provided by internal infra-red LED. Light scattered by particles is

[PATCH][V2] Smack: fix a dereference before null check on sock->sk

From: Colin Ian King The initialisation of pointer ssp is from a dereference on sock->sk before sock-sk is null checked, hence there is a potential for a null pointer deference. Fix this by moving the assignment of ssp to just before it is used in the call to

[PATCH][V2] Smack: fix a dereference before null check on sock->sk

From: Colin Ian King The initialisation of pointer ssp is from a dereference on sock->sk before sock-sk is null checked, hence there is a potential for a null pointer deference. Fix this by moving the assignment of ssp to just before it is used in the call to smk_ipv6_check. Also minor clean

Re: [PATCH 10/10] perf, tools, stat: Output JSON MetricExpr metric

On Thu, Feb 09, 2017 at 12:39:37PM +0100, Jiri Olsa wrote: > and this makes me think, that this is not the right approach > > adding extra copy of an event when you want to add new expression? I don't want to add new expressions. I don't even need arbitrary expressions, just DividedBy to get

Re: [PATCH 10/10] perf, tools, stat: Output JSON MetricExpr metric

On Thu, Feb 09, 2017 at 12:39:37PM +0100, Jiri Olsa wrote: > and this makes me think, that this is not the right approach > > adding extra copy of an event when you want to add new expression? I don't want to add new expressions. I don't even need arbitrary expressions, just DividedBy to get

Re: [PATCH] [net-next] ARM: orion: fix PHYLIB dependency

On Thursday, February 9, 2017 4:57:51 PM CET Andrew Lunn wrote: > On Thu, Feb 09, 2017 at 04:08:11PM +0100, Arnd Bergmann wrote: > > The newly introduced mdiobus_register_board_info() function is only > > available > > as part of PHYLIB, so we get a link error when we call that from a board > >

Re: [PATCH] [net-next] ARM: orion: fix PHYLIB dependency

On Thursday, February 9, 2017 4:57:51 PM CET Andrew Lunn wrote: > On Thu, Feb 09, 2017 at 04:08:11PM +0100, Arnd Bergmann wrote: > > The newly introduced mdiobus_register_board_info() function is only > > available > > as part of PHYLIB, so we get a link error when we call that from a board > >

Re: [PATCH v3 04/14] GPIO: Add gpio-ingenic driver

Hi, What some drivers do when they just get/set a bit in a register to get/set or set the direction of a GPIO, is to select GPIO_GENERIC and just bgpio_init() with the right iomem pointers, then the core will register handlers for get, set, set_direcition callback and get_direction and your

Re: [PATCH v3 04/14] GPIO: Add gpio-ingenic driver

Hi, What some drivers do when they just get/set a bit in a register to get/set or set the direction of a GPIO, is to select GPIO_GENERIC and just bgpio_init() with the right iomem pointers, then the core will register handlers for get, set, set_direcition callback and get_direction and your

Re: [PATCH v2 1/2] drm/cma-helper: Add multi buffer support for cma fbdev

On Thu, Feb 02, 2017 at 11:31:56AM +0100, Maxime Ripard wrote: > From: Xinliang Liu > > This patch add a config to support to create multi buffer for cma fbdev. > Such as double buffer and triple buffer. > > Cma fbdev is convient to add a legency fbdev. And still many

Re: [PATCH v2 1/2] drm/cma-helper: Add multi buffer support for cma fbdev

On Thu, Feb 02, 2017 at 11:31:56AM +0100, Maxime Ripard wrote: > From: Xinliang Liu > > This patch add a config to support to create multi buffer for cma fbdev. > Such as double buffer and triple buffer. > > Cma fbdev is convient to add a legency fbdev. And still many Android > devices use

Re: [PATCHv3] arm: ftrace: Adds support for CONFIG_DYNAMIC_FTRACE_WITH_REGS

On Thu, 9 Feb 2017 16:29:56 + Russell King - ARM Linux wrote: > On Tue, Feb 07, 2017 at 10:57:55PM +, Abel Vesa wrote: > > +#ifdef CONFIG_DYNAMIC_FTRACE_WITH_REGS > > + > > +.macro __ftrace_regs_caller > > + > > + add ip, sp, #4 @ move in IP the value of

Re: [PATCHv3] arm: ftrace: Adds support for CONFIG_DYNAMIC_FTRACE_WITH_REGS

On Thu, 9 Feb 2017 16:29:56 + Russell King - ARM Linux wrote: > On Tue, Feb 07, 2017 at 10:57:55PM +, Abel Vesa wrote: > > +#ifdef CONFIG_DYNAMIC_FTRACE_WITH_REGS > > + > > +.macro __ftrace_regs_caller > > + > > + add ip, sp, #4 @ move in IP the value of SP as it was > > +

[PATCH v4 2/2] staging: omap4iss: fix coding style issue

Broke argument list so that it won't exceed 80 characters Signed-off-by: Avraham Shukron --- drivers/staging/media/omap4iss/iss_video.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/staging/media/omap4iss/iss_video.c

[PATCH v4 2/2] staging: omap4iss: fix coding style issue

Broke argument list so that it won't exceed 80 characters Signed-off-by: Avraham Shukron --- drivers/staging/media/omap4iss/iss_video.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/staging/media/omap4iss/iss_video.c b/drivers/staging/media/omap4iss/iss_video.c

Re: [PATCH] drm/vc4: Drop debug print at boot with DPI enabled.

On Wed, Feb 08, 2017 at 12:47:01PM -0800, Eric Anholt wrote: > Unlike the other encoders in the driver, I've also dropped the debug > dump function. There's only really one register to this device, and > we have the debugfs reg entry still. > > Signed-off-by: Eric Anholt Yeah,

Re: [PATCH] drm/vc4: Drop debug print at boot with DPI enabled.

On Wed, Feb 08, 2017 at 12:47:01PM -0800, Eric Anholt wrote: > Unlike the other encoders in the driver, I've also dropped the debug > dump function. There's only really one register to this device, and > we have the debugfs reg entry still. > > Signed-off-by: Eric Anholt Yeah, dmesg spew by

[PATCH v3] eeprom/at24: use device_property_*() functions instead of of_get_property()

Allow the at24 driver to get configuration information from both OF and ACPI by using the more generic device_property functions. This change was inspired by the at25.c driver. I have a custom board with a ST M24C02 EEPROM attached to an I2C bus. With the following ACPI construct, this patch

[PATCH v3] eeprom/at24: use device_property_*() functions instead of of_get_property()

Allow the at24 driver to get configuration information from both OF and ACPI by using the more generic device_property functions. This change was inspired by the at25.c driver. I have a custom board with a ST M24C02 EEPROM attached to an I2C bus. With the following ACPI construct, this patch

Re: [PATCH 2/2] x86/vdso: Add VCLOCK_HVCLOCK vDSO clock read method

On Thu, 9 Feb 2017, Vitaly Kuznetsov wrote: > +#ifdef CONFIG_HYPERV_TSCPAGE > +static notrace u64 vread_hvclock(int *mode) > +{ > + const struct ms_hyperv_tsc_page *tsc_pg = > + (const struct ms_hyperv_tsc_page *)_page; > + u64 sequence, scale, offset, current_tick, cur_tsc; >

Re: [PATCH 2/2] x86/vdso: Add VCLOCK_HVCLOCK vDSO clock read method

On Thu, 9 Feb 2017, Vitaly Kuznetsov wrote: > +#ifdef CONFIG_HYPERV_TSCPAGE > +static notrace u64 vread_hvclock(int *mode) > +{ > + const struct ms_hyperv_tsc_page *tsc_pg = > + (const struct ms_hyperv_tsc_page *)_page; > + u64 sequence, scale, offset, current_tick, cur_tsc; >

Re: [PATCH] netlink: move nla_put_{u8,u16,u32} out of line

On Thursday, February 9, 2017 4:51:25 PM CET Dmitry Vyukov wrote: > On Thu, Feb 9, 2017 at 3:33 PM, Arnd Bergmann wrote: > >>> > >>> Thanks for the list, that looks very helpful. The ones I found myself > >>> seem to be a strict (and small) subset of those, using gcc-7.0.1 on

Re: [PATCH] netlink: move nla_put_{u8,u16,u32} out of line

On Thursday, February 9, 2017 4:51:25 PM CET Dmitry Vyukov wrote: > On Thu, Feb 9, 2017 at 3:33 PM, Arnd Bergmann wrote: > >>> > >>> Thanks for the list, that looks very helpful. The ones I found myself > >>> seem to be a strict (and small) subset of those, using gcc-7.0.1 on x86-64 > >>> with

Re: [PATCH v2 2/2] drm/fb_helper: implement ioctl FBIO_WAITFORVSYNC

On Thu, Feb 02, 2017 at 11:31:57AM +0100, Maxime Ripard wrote: > From: Stefan Christ > > Implement legacy framebuffer ioctl FBIO_WAITFORVSYNC in the generic > framebuffer emulation driver. Legacy framebuffer users like non kms/drm > based OpenGL(ES)/EGL implementations may

Re: [PATCH v2 2/2] drm/fb_helper: implement ioctl FBIO_WAITFORVSYNC

On Thu, Feb 02, 2017 at 11:31:57AM +0100, Maxime Ripard wrote: > From: Stefan Christ > > Implement legacy framebuffer ioctl FBIO_WAITFORVSYNC in the generic > framebuffer emulation driver. Legacy framebuffer users like non kms/drm > based OpenGL(ES)/EGL implementations may require the ioctl to >

[PATCH v4 1/2] staging: omap4iss: fix multiline comment style

Fixed multi-line comments to their preferred style (First line empty) Signed-off-by: Avraham Shukron --- drivers/staging/media/omap4iss/iss_video.c | 38 -- 1 file changed, 25 insertions(+), 13 deletions(-) diff --git

[PATCH RT 1/2] workqueue: use rcu_readlock() in put_pwq_unlocked()

3.12.70-rt94-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior The RCU sched protection was changed to RCU only and so all IRQ-off and preempt-off disabled region were changed to the relevant

[PATCH v4 1/2] staging: omap4iss: fix multiline comment style

Fixed multi-line comments to their preferred style (First line empty) Signed-off-by: Avraham Shukron --- drivers/staging/media/omap4iss/iss_video.c | 38 -- 1 file changed, 25 insertions(+), 13 deletions(-) diff --git a/drivers/staging/media/omap4iss/iss_video.c

[PATCH RT 1/2] workqueue: use rcu_readlock() in put_pwq_unlocked()

3.12.70-rt94-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior The RCU sched protection was changed to RCU only and so all IRQ-off and preempt-off disabled region were changed to the relevant rcu-read-lock primitives.

Re: [PATCHv6 01/37] mm, shmem: swich huge tmpfs to multi-order radix-tree entries

On Wed, Feb 08, 2017 at 07:57:27PM -0800, Matthew Wilcox wrote: > On Thu, Jan 26, 2017 at 02:57:43PM +0300, Kirill A. Shutemov wrote: > > +++ b/include/linux/pagemap.h > > @@ -332,6 +332,15 @@ static inline struct page > > *grab_cache_page_nowait(struct address_space *mapping, > >

Re: [PATCHv6 01/37] mm, shmem: swich huge tmpfs to multi-order radix-tree entries

On Wed, Feb 08, 2017 at 07:57:27PM -0800, Matthew Wilcox wrote: > On Thu, Jan 26, 2017 at 02:57:43PM +0300, Kirill A. Shutemov wrote: > > +++ b/include/linux/pagemap.h > > @@ -332,6 +332,15 @@ static inline struct page > > *grab_cache_page_nowait(struct address_space *mapping, > >

[PATCH RT 0/2] Linux 3.12.70-rt94-rc1

Dear RT Folks, This is the RT stable review cycle of patch 3.12.70-rt94-rc1. Please scream at me if I messed something up. Please test the patches too. The -rc release will be uploaded to kernel.org and will be deleted when the final release is out. This is just a review release (or release

[PATCH RT 2/2] Linux 3.12.70-rt94-rc1

3.12.70-rt94-rc1 stable review patch. If anyone has any objections, please let me know. -- From: "Steven Rostedt (VMware)" --- localversion-rt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/localversion-rt b/localversion-rt index

[PATCH RT 2/2] Linux 3.12.70-rt94-rc1

3.12.70-rt94-rc1 stable review patch. If anyone has any objections, please let me know. -- From: "Steven Rostedt (VMware)" --- localversion-rt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/localversion-rt b/localversion-rt index e98a1fe050bd..dcc2fd2ca155

[PATCH RT 0/2] Linux 3.12.70-rt94-rc1

Dear RT Folks, This is the RT stable review cycle of patch 3.12.70-rt94-rc1. Please scream at me if I messed something up. Please test the patches too. The -rc release will be uploaded to kernel.org and will be deleted when the final release is out. This is just a review release (or release

Re: [PATCH] netlink: move nla_put_{u8,u16,u32} out of line

On Thu, Feb 9, 2017 at 3:33 PM, Arnd Bergmann wrote: >>> >>> Thanks for the list, that looks very helpful. The ones I found myself >>> seem to be a strict (and small) subset of those, using gcc-7.0.1 on x86-64 >>> with allmodconfig and a few hundred randconfig builds. Which

Re: [PATCH] netlink: move nla_put_{u8,u16,u32} out of line

On Thu, Feb 9, 2017 at 3:33 PM, Arnd Bergmann wrote: >>> >>> Thanks for the list, that looks very helpful. The ones I found myself >>> seem to be a strict (and small) subset of those, using gcc-7.0.1 on x86-64 >>> with allmodconfig and a few hundred randconfig builds. Which compiler >>> version

[PATCH next 1/2] crypto: atmel-sha: fix missing "return" instructions

This patch fixes a previous patch: "crypto: atmel-sha - update request queue management to make it more generic". Indeed the patch above should have replaced the "return -EINVAL;" lines by "return atmel_sha_complete(dd, -EINVAL);" but instead replaced them by a simple call of

[PATCH next 1/2] crypto: atmel-sha: fix missing "return" instructions

This patch fixes a previous patch: "crypto: atmel-sha - update request queue management to make it more generic". Indeed the patch above should have replaced the "return -EINVAL;" lines by "return atmel_sha_complete(dd, -EINVAL);" but instead replaced them by a simple call of

[PATCH next 0/2] crypto: atmel-sha: fix error management

Hi all, this series is based on next-20170209. The first patch fixes a bug reported by Dan Carpenter. I didn't put a Fixes tag since the buggy patch is only in linux-next for now so its commit ID is likely to change when entering Linus' tree. It fixes a wrong 'sed' command: many "return -E

[PATCH next 0/2] crypto: atmel-sha: fix error management

Hi all, this series is based on next-20170209. The first patch fixes a bug reported by Dan Carpenter. I didn't put a Fixes tag since the buggy patch is only in linux-next for now so its commit ID is likely to change when entering Linus' tree. It fixes a wrong 'sed' command: many "return -E

[PATCH next 2/2] crypto: atmel-sha: fix error management in atmel_sha_start()

This patch clarifies and fixes how errors should be handled by atmel_sha_start(). For update operations, the previous code wrongly assumed that (err != -EINPROGRESS) implies (err == 0). It's wrong because that doesn't take the error cases (err < 0) into account. This patch also adds many

[PATCH next 2/2] crypto: atmel-sha: fix error management in atmel_sha_start()

This patch clarifies and fixes how errors should be handled by atmel_sha_start(). For update operations, the previous code wrongly assumed that (err != -EINPROGRESS) implies (err == 0). It's wrong because that doesn't take the error cases (err < 0) into account. This patch also adds many

Intel PT decoder switch case fallthrough cases reported by gcc 7

Hi, I've updated the container with Fedora Rawhide I use to build tools/perf/ and samples/bcc/ and it now comes with gcc 7, where I get things like: CC /tmp/build/perf/tests/code-reading.o util/intel-pt-decoder/intel-pt-decoder.c: In function 'intel_pt_walk_psb':

Intel PT decoder switch case fallthrough cases reported by gcc 7

Hi, I've updated the container with Fedora Rawhide I use to build tools/perf/ and samples/bcc/ and it now comes with gcc 7, where I get things like: CC /tmp/build/perf/tests/code-reading.o util/intel-pt-decoder/intel-pt-decoder.c: In function 'intel_pt_walk_psb':

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