[PATCH 03/14] media: gen-errors.rst: document ENXIO error code

This error can be produced at least at the DVB subsystem. As it is generic enough, document it. Signed-off-by: Mauro Carvalho Chehab --- Documentation/media/uapi/gen-errors.rst | 5 + 1 file changed, 5 insertions(+) diff --git

[PATCH 03/14] media: gen-errors.rst: document ENXIO error code

This error can be produced at least at the DVB subsystem. As it is generic enough, document it. Signed-off-by: Mauro Carvalho Chehab --- Documentation/media/uapi/gen-errors.rst | 5 + 1 file changed, 5 insertions(+) diff --git a/Documentation/media/uapi/gen-errors.rst

[PATCH 12/14] media: dvbstb.svg: use dots for the optional parts of the hardware

The hardware description mentions that some parts are optional. Make it clearer at the drawing. Signed-off-by: Mauro Carvalho Chehab --- Documentation/media/uapi/dvb/dvbstb.svg | 31 +++ 1 file changed, 15 insertions(+), 16 deletions(-)

[PATCH 12/14] media: dvbstb.svg: use dots for the optional parts of the hardware

The hardware description mentions that some parts are optional. Make it clearer at the drawing. Signed-off-by: Mauro Carvalho Chehab --- Documentation/media/uapi/dvb/dvbstb.svg | 31 +++ 1 file changed, 15 insertions(+), 16 deletions(-) diff --git

[PATCH 02/14] media: gen-errors.rst: remove row number comments

Those are introduced by the conversion scripts and don't really help. Get rid of them. Signed-off-by: Mauro Carvalho Chehab --- Documentation/media/uapi/gen-errors.rst | 44 + 1 file changed, 11 insertions(+), 33 deletions(-) diff --git

[PATCH 02/14] media: gen-errors.rst: remove row number comments

Those are introduced by the conversion scripts and don't really help. Get rid of them. Signed-off-by: Mauro Carvalho Chehab --- Documentation/media/uapi/gen-errors.rst | 44 + 1 file changed, 11 insertions(+), 33 deletions(-) diff --git

[PATCH 01/14] media: dvb uapi docs: better organize header files

Instead of having one chapter per file, place all of them at the same chapter. That better organize the chapters at the uAPI documentation. As a side effect, now all uAPI headers are at the same page, at the html output, with makes easier to use it as a reference index for the spec.

[PATCH 01/14] media: dvb uapi docs: better organize header files

Instead of having one chapter per file, place all of them at the same chapter. That better organize the chapters at the uAPI documentation. As a side effect, now all uAPI headers are at the same page, at the html output, with makes easier to use it as a reference index for the spec.

[PATCH 07/14] media: dmx-fread.rst: specify how DMX_CHECK_CRC works

In the past, the documentation used to say that, if a CRC error was found, a "-ECRC" error would be returned. That's not true: the DVB core will just silently ignore such errors. So, add an explicit note about that. Signed-off-by: Mauro Carvalho Chehab ---

[PATCH 07/14] media: dmx-fread.rst: specify how DMX_CHECK_CRC works

In the past, the documentation used to say that, if a CRC error was found, a "-ECRC" error would be returned. That's not true: the DVB core will just silently ignore such errors. So, add an explicit note about that. Signed-off-by: Mauro Carvalho Chehab ---

[PATCH 08/14] media: dvb-frontend-parameters.rst: fix the name of a struct

The struct that contains an union of DVB parameters is called dvb_frontend_parameters (and not FrontendParameters). Fix it. Signed-off-by: Mauro Carvalho Chehab --- Documentation/media/uapi/dvb/dvb-frontend-parameters.rst | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH 14/14] media: frontend.h: Avoid the term DVB when doesn't refer to a delivery system

The DVB term can either refer to the subsystem or to a delivery system. Avoid it in the first case at the kernel-doc markups. Signed-off-by: Mauro Carvalho Chehab --- include/uapi/linux/dvb/frontend.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff

[PATCH 08/14] media: dvb-frontend-parameters.rst: fix the name of a struct

The struct that contains an union of DVB parameters is called dvb_frontend_parameters (and not FrontendParameters). Fix it. Signed-off-by: Mauro Carvalho Chehab --- Documentation/media/uapi/dvb/dvb-frontend-parameters.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 14/14] media: frontend.h: Avoid the term DVB when doesn't refer to a delivery system

The DVB term can either refer to the subsystem or to a delivery system. Avoid it in the first case at the kernel-doc markups. Signed-off-by: Mauro Carvalho Chehab --- include/uapi/linux/dvb/frontend.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

Re: [RESEND PATCH] Allow passing tid or pid in SCM_CREDENTIALS without CAP_SYS_ADMIN

Prakash Sangappa writes: > On 8/30/17 10:41 AM, ebied...@xmission.com wrote: >> Prakash Sangappa writes: >> >> >>> With regards to security, the question basically is what is the consequence >>> of passing the wrong id. As I understand

Re: [RESEND PATCH] Allow passing tid or pid in SCM_CREDENTIALS without CAP_SYS_ADMIN

Prakash Sangappa writes: > On 8/30/17 10:41 AM, ebied...@xmission.com wrote: >> Prakash Sangappa writes: >> >> >>> With regards to security, the question basically is what is the consequence >>> of passing the wrong id. As I understand it, Interpreting the id to be pid >>> or tid, the effective

Re: [patch 10/29] lockup_detector/perf: Prevent cpu hotplug deadlock

On Fri, 1 Sep 2017, Don Zickus wrote: > On Thu, Aug 31, 2017 at 09:16:08AM +0200, Thomas Gleixner wrote: > > The following deadlock is possible in the watchdog hotplug code: > > > > cpus_write_lock() > > ... > > takedown_cpu() > > smpboot_park_threads() > >

Re: [patch 10/29] lockup_detector/perf: Prevent cpu hotplug deadlock

On Fri, 1 Sep 2017, Don Zickus wrote: > On Thu, Aug 31, 2017 at 09:16:08AM +0200, Thomas Gleixner wrote: > > The following deadlock is possible in the watchdog hotplug code: > > > > cpus_write_lock() > > ... > > takedown_cpu() > > smpboot_park_threads() > >

[PATCH]drivers: cpuidle: remove checkpatch error

this commit removes the checkpatch error in cpuidle_enable_device function. With removal of error, this commit makes the calling of cpuidle_curr_governor->enable more smooth. Signed-off-by: gaurav jindal --- diff --git a/drivers/cpuidle/cpuidle.c

[PATCH]drivers: cpuidle: remove checkpatch error

this commit removes the checkpatch error in cpuidle_enable_device function. With removal of error, this commit makes the calling of cpuidle_curr_governor->enable more smooth. Signed-off-by: gaurav jindal --- diff --git a/drivers/cpuidle/cpuidle.c b/drivers/cpuidle/cpuidle.c index

Re: tip -ENOBOOT - bisected to locking/refcounts, x86/asm: Implement fast refcount overflow protection

On Fri, 2017-09-01 at 11:58 -0700, Kees Cook wrote: > > The section stuff is supposed to be a trick to push the error case off > into the .text.unlikely area to avoid needing a jmp over the handler > and with possibly some redundancy removal done by the compiler (though > this appears to be

Re: tip -ENOBOOT - bisected to locking/refcounts, x86/asm: Implement fast refcount overflow protection

On Fri, 2017-09-01 at 11:58 -0700, Kees Cook wrote: > > The section stuff is supposed to be a trick to push the error case off > into the .text.unlikely area to avoid needing a jmp over the handler > and with possibly some redundancy removal done by the compiler (though > this appears to be

Re: [PATCH 14/15] futex: convert futex_pi_state.refcount to refcount_t

On Fri, Sep 01, 2017 at 05:03:55PM +, Reshetova, Elena wrote: > > On Fri, Sep 01, 2017 at 01:24:16PM +, Reshetova, Elena wrote: > > > > > > > On Fri, Sep 01, 2017 at 11:05:33AM +, Reshetova, Elena wrote: > > > > > Actually on the second thought: does the above memory ordering > > > >

Re: [PATCH 14/15] futex: convert futex_pi_state.refcount to refcount_t

On Fri, Sep 01, 2017 at 05:03:55PM +, Reshetova, Elena wrote: > > On Fri, Sep 01, 2017 at 01:24:16PM +, Reshetova, Elena wrote: > > > > > > > On Fri, Sep 01, 2017 at 11:05:33AM +, Reshetova, Elena wrote: > > > > > Actually on the second thought: does the above memory ordering > > > >

Re: [PATCH] thermal: tegra: dereference the pointer after null check

On Thu, Aug 31, 2017 at 04:52:29PM -0700, Nicolin Chen wrote: > The dev pointer is going through a null check after a dereference. > So this patch just reverses that. > > Signed-off-by: Nicolin Chen > --- > drivers/thermal/tegra/soctherm.c | 4 +++- > 1 file changed, 3

Re: [PATCH] thermal: tegra: dereference the pointer after null check

On Thu, Aug 31, 2017 at 04:52:29PM -0700, Nicolin Chen wrote: > The dev pointer is going through a null check after a dereference. > So this patch just reverses that. > > Signed-off-by: Nicolin Chen > --- > drivers/thermal/tegra/soctherm.c | 4 +++- > 1 file changed, 3 insertions(+), 1

Re: [patch 17/29] lockup_detector: Get rid of the thread teardown/setup dance

On Thu, Aug 31, 2017 at 09:16:15AM +0200, Thomas Gleixner wrote: > The lockup detector reconfiguration tears down all watchdog threads when > the watchdog is disabled and sets them up again when its enabled. > > That's a pointless exercise. The watchdog threads are not consuming an > insane

Re: [patch 17/29] lockup_detector: Get rid of the thread teardown/setup dance

On Thu, Aug 31, 2017 at 09:16:15AM +0200, Thomas Gleixner wrote: > The lockup detector reconfiguration tears down all watchdog threads when > the watchdog is disabled and sets them up again when its enabled. > > That's a pointless exercise. The watchdog threads are not consuming an > insane

[GIT] Networking

1) Fix handling of pinned BPF map nodes in hash of maps, from Daniel Borkmann. 2) IPSEC ESP error paths leak memory, from Steffen Klassert. 3) We need an RCU grace period before freeing fib6_node objects, from Wei Wang. 4) Must check skb_put_padto() return value in HSR driver, from

[GIT] Networking

1) Fix handling of pinned BPF map nodes in hash of maps, from Daniel Borkmann. 2) IPSEC ESP error paths leak memory, from Steffen Klassert. 3) We need an RCU grace period before freeing fib6_node objects, from Wei Wang. 4) Must check skb_put_padto() return value in HSR driver, from

Re: [patch 10/29] lockup_detector/perf: Prevent cpu hotplug deadlock

On Thu, Aug 31, 2017 at 09:16:08AM +0200, Thomas Gleixner wrote: > The following deadlock is possible in the watchdog hotplug code: > > cpus_write_lock() > ... > takedown_cpu() > smpboot_park_threads() > smpboot_park_thread() > kthread_park() >

[PATCH 01/16] gpio: Implement tighter IRQ chip integration

From: Thierry Reding Currently GPIO drivers are required to a GPIO chip and the corresponding IRQ chip separately, which can result in a lot of boilerplate. Introduce a new struct gpio_irq_chip, embedded in a struct gpio_chip, that drivers can fill in if they want the GPIO

Re: [patch 10/29] lockup_detector/perf: Prevent cpu hotplug deadlock

On Thu, Aug 31, 2017 at 09:16:08AM +0200, Thomas Gleixner wrote: > The following deadlock is possible in the watchdog hotplug code: > > cpus_write_lock() > ... > takedown_cpu() > smpboot_park_threads() > smpboot_park_thread() > kthread_park() >

[PATCH 01/16] gpio: Implement tighter IRQ chip integration

From: Thierry Reding Currently GPIO drivers are required to a GPIO chip and the corresponding IRQ chip separately, which can result in a lot of boilerplate. Introduce a new struct gpio_irq_chip, embedded in a struct gpio_chip, that drivers can fill in if they want the GPIO core to automatically

[PATCH 02/16] gpio: Move irqchip into struct gpio_irq_chip

From: Thierry Reding In order to consolidate the multiple ways to associate an IRQ chip with a GPIO chip, move more fields into the new struct gpio_irq_chip. Signed-off-by: Thierry Reding --- drivers/gpio/gpiolib.c | 18 +-

[PATCH 03/16] gpio: Move irqdomain into struct gpio_irq_chip

From: Thierry Reding In order to consolidate the multiple ways to associate an IRQ chip with a GPIO chip, move more fields into the new struct gpio_irq_chip. Signed-off-by: Thierry Reding --- Documentation/gpio/driver.txt | 2 +-

[PATCH 02/16] gpio: Move irqchip into struct gpio_irq_chip

From: Thierry Reding In order to consolidate the multiple ways to associate an IRQ chip with a GPIO chip, move more fields into the new struct gpio_irq_chip. Signed-off-by: Thierry Reding --- drivers/gpio/gpiolib.c | 18 +- include/linux/gpio/driver.h | 14 --

[PATCH 03/16] gpio: Move irqdomain into struct gpio_irq_chip

From: Thierry Reding In order to consolidate the multiple ways to associate an IRQ chip with a GPIO chip, move more fields into the new struct gpio_irq_chip. Signed-off-by: Thierry Reding --- Documentation/gpio/driver.txt | 2 +- drivers/bcma/driver_gpio.c | 2

[PATCH 06/16] gpio: Move irq_default_type to struct gpio_irq_chip

From: Thierry Reding In order to consolidate the multiple ways to associate an IRQ chip with a GPIO chip, move more fields into the new struct gpio_irq_chip. Signed-off-by: Thierry Reding --- drivers/gpio/gpiolib.c | 10 +-

[PATCH 06/16] gpio: Move irq_default_type to struct gpio_irq_chip

From: Thierry Reding In order to consolidate the multiple ways to associate an IRQ chip with a GPIO chip, move more fields into the new struct gpio_irq_chip. Signed-off-by: Thierry Reding --- drivers/gpio/gpiolib.c | 10 +- include/linux/gpio/driver.h | 11 --- 2 files

[PATCH 05/16] gpio: Move irq_handler to struct gpio_irq_chip

From: Thierry Reding In order to consolidate the multiple ways to associate an IRQ chip with a GPIO chip, move more fields into the new struct gpio_irq_chip. Signed-off-by: Thierry Reding --- drivers/gpio/gpiolib.c | 4 ++--

[PATCH 07/16] gpio: Move irq_chained_parent to struct gpio_irq_chip

From: Thierry Reding In order to consolidate the multiple ways to associate an IRQ chip with a GPIO chip, move more fields into the new struct gpio_irq_chip. Signed-off-by: Thierry Reding --- drivers/gpio/gpiolib.c | 8 ++--

[PATCH 05/16] gpio: Move irq_handler to struct gpio_irq_chip

From: Thierry Reding In order to consolidate the multiple ways to associate an IRQ chip with a GPIO chip, move more fields into the new struct gpio_irq_chip. Signed-off-by: Thierry Reding --- drivers/gpio/gpiolib.c | 4 ++-- include/linux/gpio/driver.h | 11 --- 2 files changed,

[PATCH 07/16] gpio: Move irq_chained_parent to struct gpio_irq_chip

From: Thierry Reding In order to consolidate the multiple ways to associate an IRQ chip with a GPIO chip, move more fields into the new struct gpio_irq_chip. Signed-off-by: Thierry Reding --- drivers/gpio/gpiolib.c | 8 ++-- include/linux/gpio/driver.h | 4 2 files changed, 2

[PATCH 09/16] gpio: Move irq_valid_mask into struct gpio_irq_chip

From: Thierry Reding In order to consolidate the multiple ways to associate an IRQ chip with a GPIO chip, move more fields into the new struct gpio_irq_chip. Signed-off-by: Thierry Reding --- Documentation/gpio/driver.txt | 4 ++--

[PATCH 09/16] gpio: Move irq_valid_mask into struct gpio_irq_chip

From: Thierry Reding In order to consolidate the multiple ways to associate an IRQ chip with a GPIO chip, move more fields into the new struct gpio_irq_chip. Signed-off-by: Thierry Reding --- Documentation/gpio/driver.txt | 4 ++-- drivers/gpio/gpio-aspeed.c | 4

[PATCH 10/16] gpio: Move lock_key into struct gpio_irq_chip

From: Thierry Reding In order to consolidate the multiple ways to associate an IRQ chip with a GPIO chip, move more fields into the new struct gpio_irq_chip. Signed-off-by: Thierry Reding --- drivers/gpio/gpiolib.c | 4 ++--

[PATCH 10/16] gpio: Move lock_key into struct gpio_irq_chip

From: Thierry Reding In order to consolidate the multiple ways to associate an IRQ chip with a GPIO chip, move more fields into the new struct gpio_irq_chip. Signed-off-by: Thierry Reding --- drivers/gpio/gpiolib.c | 4 ++-- include/linux/gpio/driver.h | 9 +++-- 2 files changed, 9

[PATCH 13/16] gpio: omap: Rename struct gpio_bank to struct omap_gpio_bank

From: Thierry Reding Subsequent patches will want to introduce a struct gpio_bank in core code, so rename this to something driver-specific in order to avoid the names from clashing. Signed-off-by: Thierry Reding --- drivers/gpio/gpio-omap.c | 131

[PATCH 13/16] gpio: omap: Rename struct gpio_bank to struct omap_gpio_bank

From: Thierry Reding Subsequent patches will want to introduce a struct gpio_bank in core code, so rename this to something driver-specific in order to avoid the names from clashing. Signed-off-by: Thierry Reding --- drivers/gpio/gpio-omap.c | 131

[PATCH 14/16] gpio: Add support for banked GPIO controllers

From: Thierry Reding Some GPIO controllers are subdivided into multiple logical blocks called banks (or ports). This is often caused by the design assigning separate resources, such as register regions or interrupts, to each bank, or some set of banks. This commit adds

[PATCH 14/16] gpio: Add support for banked GPIO controllers

From: Thierry Reding Some GPIO controllers are subdivided into multiple logical blocks called banks (or ports). This is often caused by the design assigning separate resources, such as register regions or interrupts, to each bank, or some set of banks. This commit adds support for describing

[PATCH 12/16] gpio: omap: Fix checkpatch warnings

From: Thierry Reding Use unsigned int rather than unsigned, wrap lines longer than 80 characters and other minor coding style cleanups. Signed-off-by: Thierry Reding --- drivers/gpio/gpio-omap.c | 113 ++- 1

[PATCH 12/16] gpio: omap: Fix checkpatch warnings

From: Thierry Reding Use unsigned int rather than unsigned, wrap lines longer than 80 characters and other minor coding style cleanups. Signed-off-by: Thierry Reding --- drivers/gpio/gpio-omap.c | 113 ++- 1 file changed, 63 insertions(+), 50

[PATCH 15/16] gpio: tegra: Use banked GPIO infrastructure

From: Thierry Reding Convert the Tegra GPIO driver to use the banked GPIO infrastructure, which simplifies some parts of the driver. Signed-off-by: Thierry Reding --- drivers/gpio/Kconfig | 1 + drivers/gpio/gpio-tegra.c | 203

[PATCH 15/16] gpio: tegra: Use banked GPIO infrastructure

From: Thierry Reding Convert the Tegra GPIO driver to use the banked GPIO infrastructure, which simplifies some parts of the driver. Signed-off-by: Thierry Reding --- drivers/gpio/Kconfig | 1 + drivers/gpio/gpio-tegra.c | 203 ++ 2 files

Re: tip -ENOBOOT - bisected to locking/refcounts, x86/asm: Implement fast refcount overflow protection

On Fri, Sep 1, 2017 at 10:52 AM, Mike Galbraith wrote: > On Fri, 2017-09-01 at 10:12 -0700, Kees Cook wrote: >> On Fri, Sep 1, 2017 at 6:09 AM, Mike Galbraith wrote: >> > On Fri, 2017-09-01 at 08:57 +0200, Mike Galbraith wrote: >> >> On Thu, 2017-08-31 at 11:45

Re: tip -ENOBOOT - bisected to locking/refcounts, x86/asm: Implement fast refcount overflow protection

On Fri, Sep 1, 2017 at 10:52 AM, Mike Galbraith wrote: > On Fri, 2017-09-01 at 10:12 -0700, Kees Cook wrote: >> On Fri, Sep 1, 2017 at 6:09 AM, Mike Galbraith wrote: >> > On Fri, 2017-09-01 at 08:57 +0200, Mike Galbraith wrote: >> >> On Thu, 2017-08-31 at 11:45 -0700, Kees Cook wrote: >> >> > On

[PATCH 11/16] gpio: Add Tegra186 support

From: Thierry Reding Tegra186 has two GPIO controllers that are largely register compatible between one another but are completely different from the controller found on earlier generations. Signed-off-by: Thierry Reding --- Changes in v4: - use

[PATCH 11/16] gpio: Add Tegra186 support

From: Thierry Reding Tegra186 has two GPIO controllers that are largely register compatible between one another but are completely different from the controller found on earlier generations. Signed-off-by: Thierry Reding --- Changes in v4: - use platform_irq_count() instead of of_irq_count()

[PATCH 16/16] gpio: tegra186: Use banked GPIO infrastructure

From: Thierry Reding Convert the Tegra186 GPIO driver to use the banked GPIO infrastructure, which simplifies some parts of the driver. Signed-off-by: Thierry Reding --- drivers/gpio/gpio-tegra186.c | 211 --- 1

[PATCH 16/16] gpio: tegra186: Use banked GPIO infrastructure

From: Thierry Reding Convert the Tegra186 GPIO driver to use the banked GPIO infrastructure, which simplifies some parts of the driver. Signed-off-by: Thierry Reding --- drivers/gpio/gpio-tegra186.c | 211 --- 1 file changed, 79 insertions(+), 132

[PATCH 08/16] gpio: Move irq_nested into struct gpio_irq_chip

From: Thierry Reding In order to consolidate the multiple ways to associate an IRQ chip with a GPIO chip, move more fields into the new struct gpio_irq_chip. Signed-off-by: Thierry Reding --- drivers/gpio/gpiolib.c | 12 ++--

[PATCH 08/16] gpio: Move irq_nested into struct gpio_irq_chip

From: Thierry Reding In order to consolidate the multiple ways to associate an IRQ chip with a GPIO chip, move more fields into the new struct gpio_irq_chip. Signed-off-by: Thierry Reding --- drivers/gpio/gpiolib.c | 12 ++-- include/linux/gpio/driver.h | 9 +++-- 2 files

[PATCH 04/16] gpio: Move irq_base to struct gpio_irq_chip

From: Thierry Reding In order to consolidate the multiple ways to associate an IRQ chip with a GPIO chip, move more fields into the new struct gpio_irq_chip. Signed-off-by: Thierry Reding --- drivers/gpio/gpiolib.c | 2 +-

[PATCH 04/16] gpio: Move irq_base to struct gpio_irq_chip

From: Thierry Reding In order to consolidate the multiple ways to associate an IRQ chip with a GPIO chip, move more fields into the new struct gpio_irq_chip. Signed-off-by: Thierry Reding --- drivers/gpio/gpiolib.c | 2 +- drivers/pinctrl/mvebu/pinctrl-armada-37xx.c | 2

[PATCH 00/16] gpio: Tight IRQ chip integration and banked infrastructure

From: Thierry Reding Hi Linus, here's the latest series of patches that implement the tighter IRQ chip integration as well as the banked GPIO infrastructure that we had discussed a couple of weeks/months back. The first couple of patches are mostly preparatory work in order

[PATCH 00/16] gpio: Tight IRQ chip integration and banked infrastructure

From: Thierry Reding Hi Linus, here's the latest series of patches that implement the tighter IRQ chip integration as well as the banked GPIO infrastructure that we had discussed a couple of weeks/months back. The first couple of patches are mostly preparatory work in order to consolidate all

Re: [RFC PATCH v3] membarrier: provide core serialization

- On Sep 1, 2017, at 1:10 PM, Will Deacon will.dea...@arm.com wrote: > Hi Mathieu, > > On Fri, Sep 01, 2017 at 05:00:38PM +, Mathieu Desnoyers wrote: >> - On Sep 1, 2017, at 12:25 PM, Will Deacon will.dea...@arm.com wrote: >> >> > On Fri, Sep 01, 2017 at 12:10:07PM -0400, Mathieu

Re: [RFC PATCH v3] membarrier: provide core serialization

- On Sep 1, 2017, at 1:10 PM, Will Deacon will.dea...@arm.com wrote: > Hi Mathieu, > > On Fri, Sep 01, 2017 at 05:00:38PM +, Mathieu Desnoyers wrote: >> - On Sep 1, 2017, at 12:25 PM, Will Deacon will.dea...@arm.com wrote: >> >> > On Fri, Sep 01, 2017 at 12:10:07PM -0400, Mathieu

RE: [PATCH v4 3/3] eeprom: at24: enable runtime pm support

Hi Sakari, Thanks for the review. My comments below. --- ^Divagar >-Original Message- >From: Sakari Ailus [mailto:sakari.ai...@iki.fi] >Sent: Thursday, August 31, 2017 9:07 PM >To: Mohandass, Divagar >Cc: robh...@kernel.org; mark.rutl...@arm.com;

RE: [PATCH v4 3/3] eeprom: at24: enable runtime pm support

Hi Sakari, Thanks for the review. My comments below. --- ^Divagar >-Original Message- >From: Sakari Ailus [mailto:sakari.ai...@iki.fi] >Sent: Thursday, August 31, 2017 9:07 PM >To: Mohandass, Divagar >Cc: robh...@kernel.org; mark.rutl...@arm.com; w...@the-dreams.de;

Re: RFC: Revert move default dialect from CIFS to to SMB3

Linus Torvalds wrote: On Thu, Aug 31, 2017 at 2:36 PM, Thorsten Leemhuis wrote: Lo! To give a bit more background to this (the mail I reply to was the first I sent with git send-email and I missed some details): Maybe I'm over stretching my abilities/position as

Re: RFC: Revert move default dialect from CIFS to to SMB3

Linus Torvalds wrote: On Thu, Aug 31, 2017 at 2:36 PM, Thorsten Leemhuis wrote: Lo! To give a bit more background to this (the mail I reply to was the first I sent with git send-email and I missed some details): Maybe I'm over stretching my abilities/position as regression tracker with this

[PATCH] [media] si2168: Delete an error message for a failed memory allocation in si2168_probe()

From: Markus Elfring Date: Fri, 1 Sep 2017 19:50:45 +0200 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH] [media] si2168: Delete an error message for a failed memory allocation in si2168_probe()

From: Markus Elfring Date: Fri, 1 Sep 2017 19:50:45 +0200 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- drivers/media/dvb-frontends/si2168.c | 1 - 1 file changed, 1

Fast Loans

Apply for a loan at 3% reply to this Email for more Info

Fast Loans

Apply for a loan at 3% reply to this Email for more Info

[PATCH] ARC: Machine Check Exception: enable MMU in single place

Machine check Exception is handled in distinc ways depending on cause - Duplicate TLB Entry (relevent mostly for ARC700) - everything else Currently we re-enable MMU seperately for each of these cases, which can be consolidated by dign this before we fork off the handling in low level handler.

[PATCH] ARC: Machine Check Exception: enable MMU in single place

Machine check Exception is handled in distinc ways depending on cause - Duplicate TLB Entry (relevent mostly for ARC700) - everything else Currently we re-enable MMU seperately for each of these cases, which can be consolidated by dign this before we fork off the handling in low level handler.

Re: [PATCH 13/31] timer: Remove meaningless .data/.function assignments

Kees Cook writes: > Several timer users needlessly reset their .function/.data fields during > their timer callback, but nothing else changes them. Some users do not > use their .data field at all. Each instance is removed here. For *wan/hdlc* Acked-by: Krzysztof Halasa

Re: [PATCH 13/31] timer: Remove meaningless .data/.function assignments

Kees Cook writes: > Several timer users needlessly reset their .function/.data fields during > their timer callback, but nothing else changes them. Some users do not > use their .data field at all. Each instance is removed here. For *wan/hdlc* Acked-by: Krzysztof Halasa > ---

Re: [PATCH 26/31] staging/comedi/das16: Make timer initialization unconditional

On Fri, Sep 1, 2017 at 2:38 AM, Ian Abbott wrote: > On 01/09/17 10:29, Ian Abbott wrote: >> >> On 01/09/17 00:29, Kees Cook wrote: >>> >>> With timer initialization made unconditional, there is no reason to >>> make del_timer_sync() calls conditionally, there by removing the

Re: [PATCH 26/31] staging/comedi/das16: Make timer initialization unconditional

On Fri, Sep 1, 2017 at 2:38 AM, Ian Abbott wrote: > On 01/09/17 10:29, Ian Abbott wrote: >> >> On 01/09/17 00:29, Kees Cook wrote: >>> >>> With timer initialization made unconditional, there is no reason to >>> make del_timer_sync() calls conditionally, there by removing the test >>> of the .data

Re: tip -ENOBOOT - bisected to locking/refcounts, x86/asm: Implement fast refcount overflow protection

On Fri, 2017-09-01 at 10:12 -0700, Kees Cook wrote: > On Fri, Sep 1, 2017 at 6:09 AM, Mike Galbraith wrote: > > On Fri, 2017-09-01 at 08:57 +0200, Mike Galbraith wrote: > >> On Thu, 2017-08-31 at 11:45 -0700, Kees Cook wrote: > >> > On Thu, Aug 31, 2017 at 10:19 AM, Mike Galbraith

Re: tip -ENOBOOT - bisected to locking/refcounts, x86/asm: Implement fast refcount overflow protection

On Fri, 2017-09-01 at 10:12 -0700, Kees Cook wrote: > On Fri, Sep 1, 2017 at 6:09 AM, Mike Galbraith wrote: > > On Fri, 2017-09-01 at 08:57 +0200, Mike Galbraith wrote: > >> On Thu, 2017-08-31 at 11:45 -0700, Kees Cook wrote: > >> > On Thu, Aug 31, 2017 at 10:19 AM, Mike Galbraith wrote: > >> >

Re: Support standalone metrics and metric groups for perf

On Fri, Sep 01, 2017 at 10:42:04AM -0700, Andi Kleen wrote: > > could you please check on that and maybe shift the alignment for the > > longest name? > > To make everything align would require shifting everything. So most > usages which don't have that wide events wouldn't fit into 80 >

Re: Support standalone metrics and metric groups for perf

On Fri, Sep 01, 2017 at 10:42:04AM -0700, Andi Kleen wrote: > > could you please check on that and maybe shift the alignment for the > > longest name? > > To make everything align would require shifting everything. So most > usages which don't have that wide events wouldn't fit into 80 >

[PATCH] perf sched timehist: Add pid and tid options

Add options to only show event for specific pid(s) and tid(s). Signed-off-by: David Ahern --- tools/perf/Documentation/perf-sched.txt | 8 tools/perf/builtin-sched.c | 4 2 files changed, 12 insertions(+) diff --git

[PATCH] perf sched timehist: Add pid and tid options

Add options to only show event for specific pid(s) and tid(s). Signed-off-by: David Ahern --- tools/perf/Documentation/perf-sched.txt | 8 tools/perf/builtin-sched.c | 4 2 files changed, 12 insertions(+) diff --git a/tools/perf/Documentation/perf-sched.txt

Re: [patch v7 1/4] drivers: jtag: Add JTAG core driver

Nit inline ;-) On Fri, Sep 1, 2017 at 9:06 AM, Oleksandr Shamray wrote: > Initial patch for JTAG friver s/friver/driver > JTAG class driver provide infrastructure to support hardware/software > JTAG platform drivers. It provide user layer API interface for flashing >

Re: [patch v7 1/4] drivers: jtag: Add JTAG core driver

Nit inline ;-) On Fri, Sep 1, 2017 at 9:06 AM, Oleksandr Shamray wrote: > Initial patch for JTAG friver s/friver/driver > JTAG class driver provide infrastructure to support hardware/software > JTAG platform drivers. It provide user layer API interface for flashing > and debugging external

Re: [PATCH V2 0/5] support PERF_SAMPLE_PHYS_ADDR (user)

On Fri, Sep 01, 2017 at 02:39:48PM -0300, Arnaldo Carvalho de Melo wrote: > Em Fri, Sep 01, 2017 at 05:45:02PM +0200, Jiri Olsa escreveu: > > On Tue, Aug 29, 2017 at 01:11:07PM -0400, kan.li...@intel.com wrote: > > > From: Kan Liang > > > > > > The patch series is to support

Re: [PATCH V2 0/5] support PERF_SAMPLE_PHYS_ADDR (user)

On Fri, Sep 01, 2017 at 02:39:48PM -0300, Arnaldo Carvalho de Melo wrote: > Em Fri, Sep 01, 2017 at 05:45:02PM +0200, Jiri Olsa escreveu: > > On Tue, Aug 29, 2017 at 01:11:07PM -0400, kan.li...@intel.com wrote: > > > From: Kan Liang > > > > > > The patch series is to support

Re: [PATCH v2] leds: pca955x: Don't invert requested value in pca955x_gpio_set_value()

On 09/01/2017 07:38 AM, Andrew Jeffery wrote: > The PCA9552 lines can be used either for driving LEDs or as GPIOs. The > manual states that for LEDs, the operation is open-drain: > > The LSn LED select registers determine the source of the LED data. > >00 = output is set LOW

Re: [PATCH v2] leds: pca955x: Don't invert requested value in pca955x_gpio_set_value()

On 09/01/2017 07:38 AM, Andrew Jeffery wrote: > The PCA9552 lines can be used either for driving LEDs or as GPIOs. The > manual states that for LEDs, the operation is open-drain: > > The LSn LED select registers determine the source of the LED data. > >00 = output is set LOW

Re: virtio_net: ethtool supported link modes

On Fri, Sep 01, 2017 at 05:19:53PM +0100, Radu Rendec wrote: > On Fri, 2017-09-01 at 18:43 +0300, Michael S. Tsirkin wrote: > > On Thu, Aug 31, 2017 at 06:04:04PM +0100, Radu Rendec wrote: > > > Looking at the code in virtnet_set_link_ksettings, it seems the speed > > > and duplex can be set to

Re: virtio_net: ethtool supported link modes

On Fri, Sep 01, 2017 at 05:19:53PM +0100, Radu Rendec wrote: > On Fri, 2017-09-01 at 18:43 +0300, Michael S. Tsirkin wrote: > > On Thu, Aug 31, 2017 at 06:04:04PM +0100, Radu Rendec wrote: > > > Looking at the code in virtnet_set_link_ksettings, it seems the speed > > > and duplex can be set to

Re: Support standalone metrics and metric groups for perf

> could you please check on that and maybe shift the alignment for the longest > name? To make everything align would require shifting everything. So most usages which don't have that wide events wouldn't fit into 80 character columns anymore. That would be worse. Or do a two pass output that

Re: Support standalone metrics and metric groups for perf

> could you please check on that and maybe shift the alignment for the longest > name? To make everything align would require shifting everything. So most usages which don't have that wide events wouldn't fit into 80 character columns anymore. That would be worse. Or do a two pass output that

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