Re: [RFC for GIT] pull-request: add praise to people doing QA

On Thu, 2017-01-19 at 15:42 -0800, Jacob Keller wrote: > On Thu, Jan 19, 2017 at 1:20 PM, Jeff King wrote: > > On Thu, Jan 19, 2017 at 09:43:45PM +0100, Wolfram Sang wrote: > > > > > > As to the implementation, I am wondering if we can make this somehow > > > > work well with the

Re: [RFC for GIT] pull-request: add praise to people doing QA

On Thu, 2017-01-19 at 15:42 -0800, Jacob Keller wrote: > On Thu, Jan 19, 2017 at 1:20 PM, Jeff King wrote: > > On Thu, Jan 19, 2017 at 09:43:45PM +0100, Wolfram Sang wrote: > > > > > > As to the implementation, I am wondering if we can make this somehow > > > > work well with the "trailers" code

btrfs_alloc_tree_block: Faulting instruction address: 0xc02d4584

Hi, after upgrading this powerpc32 box from 4.10-rc2 to -rc4, the message below occured a few hours after boot. Full dmesg and .config: http://nerdbynature.de/bits/4.10-rc4/ Any ideas? Thanks, Christian. Faulting instruction address: 0xc02d4584 Oops: Kernel access of bad area, sig: 11

btrfs_alloc_tree_block: Faulting instruction address: 0xc02d4584

Hi, after upgrading this powerpc32 box from 4.10-rc2 to -rc4, the message below occured a few hours after boot. Full dmesg and .config: http://nerdbynature.de/bits/4.10-rc4/ Any ideas? Thanks, Christian. Faulting instruction address: 0xc02d4584 Oops: Kernel access of bad area, sig: 11

Re: [PATCH perf/core 6/6] tools lib bpf: Add bpf_object__pin()

On 19 January 2017 at 02:22, Wangnan (F) wrote: > > > On 2017/1/19 7:57, Joe Stringer wrote: >> >> Add a new API to pin a BPF object to the filesystem. The user can >> specify a subdirectory under the BPF filesystem to pin these programs. >> >> For example, with the

Re: [PATCH perf/core 6/6] tools lib bpf: Add bpf_object__pin()

On 19 January 2017 at 02:22, Wangnan (F) wrote: > > > On 2017/1/19 7:57, Joe Stringer wrote: >> >> Add a new API to pin a BPF object to the filesystem. The user can >> specify a subdirectory under the BPF filesystem to pin these programs. >> >> For example, with the subdirectory 'foo', programs

Re: [PATCHv4 3/5] pinctrl: mvebu: pinctrl driver for 98DX3236 SoC

On 20/01/17 12:19, Sebastian Hesselbarth wrote: > On 19.01.2017 22:12, Chris Packham wrote: >> On 14/01/17 20:50, Chris Packham wrote: >>> On 13/01/17 22:54, Sebastian Hesselbarth wrote: On 13.01.2017 10:12, Chris Packham wrote: > From: Kalyan Kinthada

Re: [PATCHv4 3/5] pinctrl: mvebu: pinctrl driver for 98DX3236 SoC

On 20/01/17 12:19, Sebastian Hesselbarth wrote: > On 19.01.2017 22:12, Chris Packham wrote: >> On 14/01/17 20:50, Chris Packham wrote: >>> On 13/01/17 22:54, Sebastian Hesselbarth wrote: On 13.01.2017 10:12, Chris Packham wrote: > From: Kalyan Kinthada > > This pinctrl driver

Re: [PATCH v3 1/3] NFC: trf7970a: add device tree option for 27MHz clock

On Wed, Dec 21, 2016 at 11:18:32PM -0500, Geoff Lansberry wrote: > The TRF7970A has configuration options to support hardware designs > which use a 27.12MHz clock. This commit adds a device tree option > 'clock-frequency' to support configuring the this chip for default > 13.56MHz clock or the

Re: [PATCH v3 1/3] NFC: trf7970a: add device tree option for 27MHz clock

On Wed, Dec 21, 2016 at 11:18:32PM -0500, Geoff Lansberry wrote: > The TRF7970A has configuration options to support hardware designs > which use a 27.12MHz clock. This commit adds a device tree option > 'clock-frequency' to support configuring the this chip for default > 13.56MHz clock or the

Re: [RFC][PATCH] x86: Verify access_ok() context

Frank. On Thu, 19 Jan 2017, Frank Ch. Eigler wrote: > > Well, if you are not in thread context then the check is pointless: > > __range_not_ok(addr, size, user_addr_max()) > > and: > > #define user_addr_max() (current->thread.addr_limit.seg) > > > > So what guarantees when you are not in

Re: [RFC][PATCH] x86: Verify access_ok() context

Frank. On Thu, 19 Jan 2017, Frank Ch. Eigler wrote: > > Well, if you are not in thread context then the check is pointless: > > __range_not_ok(addr, size, user_addr_max()) > > and: > > #define user_addr_max() (current->thread.addr_limit.seg) > > > > So what guarantees when you are not in

Re: [PATCH v10 3/4] console: Add persistent scrollback buffers for all VGA consoles

On Thu, Jan 19, 2017 at 05:33:14PM +0100, Greg KH wrote: > On Thu, Jan 19, 2017 at 05:12:15PM +0100, Manuel Schölling wrote: > > On Thu, 2017-01-19 at 14:23 +0100, Greg KH wrote: > > > On Fri, Jan 13, 2017 at 09:07:57PM +0100, Manuel Schölling wrote: > > > > +   This feature might break your

Re: [PATCH 2/7] iio: adc: stm32: Enable use of stm32 timer triggers

Hi Fabrice, [auto build test ERROR on next-20170119] [also build test ERROR on v4.10-rc4] [cannot apply to iio/togreg robh/for-next v4.9-rc8 v4.9-rc7 v4.9-rc6] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci

Re: [PATCH v10 3/4] console: Add persistent scrollback buffers for all VGA consoles

On Thu, Jan 19, 2017 at 05:33:14PM +0100, Greg KH wrote: > On Thu, Jan 19, 2017 at 05:12:15PM +0100, Manuel Schölling wrote: > > On Thu, 2017-01-19 at 14:23 +0100, Greg KH wrote: > > > On Fri, Jan 13, 2017 at 09:07:57PM +0100, Manuel Schölling wrote: > > > > +   This feature might break your

Re: [PATCH 2/7] iio: adc: stm32: Enable use of stm32 timer triggers

Hi Fabrice, [auto build test ERROR on next-20170119] [also build test ERROR on v4.10-rc4] [cannot apply to iio/togreg robh/for-next v4.9-rc8 v4.9-rc7 v4.9-rc6] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci

Re: [RFC for GIT] pull-request: add praise to people doing QA

On Thu, Jan 19, 2017 at 1:20 PM, Jeff King wrote: > On Thu, Jan 19, 2017 at 09:43:45PM +0100, Wolfram Sang wrote: > >> > As to the implementation, I am wondering if we can make this somehow >> > work well with the "trailers" code we already have, instead of >> > inventing yet

Re: [RFC for GIT] pull-request: add praise to people doing QA

On Thu, Jan 19, 2017 at 1:20 PM, Jeff King wrote: > On Thu, Jan 19, 2017 at 09:43:45PM +0100, Wolfram Sang wrote: > >> > As to the implementation, I am wondering if we can make this somehow >> > work well with the "trailers" code we already have, instead of >> > inventing yet another parser of

Re: [PATCH v2 1/1] mm/ksm: improve deduplication of zero pages with colouring

On Thu, 19 Jan 2017 19:35:53 +0100 Claudio Imbrenda wrote: > Some architectures have a set of zero pages (coloured zero pages) > instead of only one zero page, in order to improve the cache > performance. In those cases, the kernel samepage merger (KSM) would >

Re: [PATCH v2 1/1] mm/ksm: improve deduplication of zero pages with colouring

On Thu, 19 Jan 2017 19:35:53 +0100 Claudio Imbrenda wrote: > Some architectures have a set of zero pages (coloured zero pages) > instead of only one zero page, in order to improve the cache > performance. In those cases, the kernel samepage merger (KSM) would > merge all the allocated pages

RE: [EXT] Re: [PATCH v5 0/2] Add support for the ethernet switch on the ESPRESSObin

+ Bob + Christine Jon Pannell -Original Message- From: Andrew Lunn [mailto:and...@lunn.ch] Sent: Thursday, January 19, 2017 2:06 PM To: Gregory CLEMENT Cc: Vivien Didelot ; Florian Fainelli

RE: [EXT] Re: [PATCH v5 0/2] Add support for the ethernet switch on the ESPRESSObin

+ Bob + Christine Jon Pannell -Original Message- From: Andrew Lunn [mailto:and...@lunn.ch] Sent: Thursday, January 19, 2017 2:06 PM To: Gregory CLEMENT Cc: Vivien Didelot ; Florian Fainelli ; net...@vger.kernel.org; linux-kernel@vger.kernel.org; David S. Miller ; Jason Cooper ;

[GIT PULL] xfs: updates for 4.10-rc5

Hi Linus, I have a few more patches this week -- one to make the behavior of a quota id ioctl consistent with the other filesystems, and the rest improve validation of i_mode & i_size values coming into xfs so that we don't read off the ends of arrays or crash when handed garbage disk data.

[GIT PULL] xfs: updates for 4.10-rc5

Hi Linus, I have a few more patches this week -- one to make the behavior of a quota id ioctl consistent with the other filesystems, and the rest improve validation of i_mode & i_size values coming into xfs so that we don't read off the ends of arrays or crash when handed garbage disk data.

RE: [PATCHv2 3/7] TAP: Tap character device creation/destroy API

> -Original Message- > From: David Miller [mailto:da...@davemloft.net] > Sent: Wednesday, January 18, 2017 1:27 PM > To: Grandhi, Sainath > Cc: net...@vger.kernel.org; mah...@bandewar.net; linux- > ker...@vger.kernel.org > Subject: Re: [PATCHv2 3/7] TAP: Tap

RE: [PATCHv2 3/7] TAP: Tap character device creation/destroy API

> -Original Message- > From: David Miller [mailto:da...@davemloft.net] > Sent: Wednesday, January 18, 2017 1:27 PM > To: Grandhi, Sainath > Cc: net...@vger.kernel.org; mah...@bandewar.net; linux- > ker...@vger.kernel.org > Subject: Re: [PATCHv2 3/7] TAP: Tap character device

RE: [PATCHv2 7/7] IPVTAP: IP-VLAN based tap driver

> -Original Message- > From: David Miller [mailto:da...@davemloft.net] > Sent: Wednesday, January 18, 2017 1:29 PM > To: Grandhi, Sainath > Cc: net...@vger.kernel.org; mah...@bandewar.net; linux- > ker...@vger.kernel.org > Subject: Re: [PATCHv2 7/7] IPVTAP:

RE: [PATCHv2 7/7] IPVTAP: IP-VLAN based tap driver

> -Original Message- > From: David Miller [mailto:da...@davemloft.net] > Sent: Wednesday, January 18, 2017 1:29 PM > To: Grandhi, Sainath > Cc: net...@vger.kernel.org; mah...@bandewar.net; linux- > ker...@vger.kernel.org > Subject: Re: [PATCHv2 7/7] IPVTAP: IP-VLAN based tap driver > >

Re: [PATCH] power: reset: Add MAX77620 support

On Fri, Jan 20, 2017 at 12:00:36AM +0100, Sebastian Reichel wrote: > Hi Thierry, > > > > > [...] > > > > > > Please use register_restart_handler() instead. It has support for > > > priorities, is not arm specific and properly supports unregistering > > > (some handler with lower priority will

Re: [PATCH] power: reset: Add MAX77620 support

On Fri, Jan 20, 2017 at 12:00:36AM +0100, Sebastian Reichel wrote: > Hi Thierry, > > > > > [...] > > > > > > Please use register_restart_handler() instead. It has support for > > > priorities, is not arm specific and properly supports unregistering > > > (some handler with lower priority will

Re: [PATCHv4 3/5] pinctrl: mvebu: pinctrl driver for 98DX3236 SoC

On 19.01.2017 22:12, Chris Packham wrote: > On 14/01/17 20:50, Chris Packham wrote: >> On 13/01/17 22:54, Sebastian Hesselbarth wrote: >>> On 13.01.2017 10:12, Chris Packham wrote: From: Kalyan Kinthada This pinctrl driver supports the 98DX3236,

Re: [PATCHv4 3/5] pinctrl: mvebu: pinctrl driver for 98DX3236 SoC

On 19.01.2017 22:12, Chris Packham wrote: > On 14/01/17 20:50, Chris Packham wrote: >> On 13/01/17 22:54, Sebastian Hesselbarth wrote: >>> On 13.01.2017 10:12, Chris Packham wrote: From: Kalyan Kinthada This pinctrl driver supports the 98DX3236, 98DX3336 and 98DX4251 SoCs from

Re: [PATCH] drivers: power: supply: Compress return logic into one line.

Hey hello, Quoting Sebastian Reichel : Hi, On Wed, Jan 11, 2017 at 08:29:35PM -0600, Gustavo A. R. Silva wrote: Simplify return logic to avoid unnecessary variable assignments. These issues were detected using Coccinelle and the following semantic patch: @@ local

Re: [PATCH] drivers: power: supply: Compress return logic into one line.

Hey hello, Quoting Sebastian Reichel : Hi, On Wed, Jan 11, 2017 at 08:29:35PM -0600, Gustavo A. R. Silva wrote: Simplify return logic to avoid unnecessary variable assignments. These issues were detected using Coccinelle and the following semantic patch: @@ local idexpression ret;

[char-misc-next 2/2] mei: make mei_cl_set_disconnected static

From: Alexander Usyskin mei_cl_set_disconnected is used only in client.c, so make it local to the file and mark static. Signed-off-by: Alexander Usyskin Signed-off-by: Tomas Winkler ---

[char-misc-next 1/2] mei: make mei_io_list_flush static

From: Alexander Usyskin mei_io_list_flush is used only in client.c so make it local to the file and mark static. Signed-off-by: Alexander Usyskin Signed-off-by: Tomas Winkler --- drivers/misc/mei/client.c | 2

[char-misc-next 2/2] mei: make mei_cl_set_disconnected static

From: Alexander Usyskin mei_cl_set_disconnected is used only in client.c, so make it local to the file and mark static. Signed-off-by: Alexander Usyskin Signed-off-by: Tomas Winkler --- drivers/misc/mei/client.c | 2 +- drivers/misc/mei/client.h | 1 - 2 files changed, 1 insertion(+), 2

[char-misc-next 1/2] mei: make mei_io_list_flush static

From: Alexander Usyskin mei_io_list_flush is used only in client.c so make it local to the file and mark static. Signed-off-by: Alexander Usyskin Signed-off-by: Tomas Winkler --- drivers/misc/mei/client.c | 2 +- drivers/misc/mei/client.h | 1 - 2 files changed, 1 insertion(+), 2

[PATCH v2 1/1] mm/ksm: improve deduplication of zero pages with colouring

Some architectures have a set of zero pages (coloured zero pages) instead of only one zero page, in order to improve the cache performance. In those cases, the kernel samepage merger (KSM) would merge all the allocated pages that happen to be filled with zeroes to the same deduplicated page, thus

[PATCH v2 1/1] mm/ksm: improve deduplication of zero pages with colouring

Some architectures have a set of zero pages (coloured zero pages) instead of only one zero page, in order to improve the cache performance. In those cases, the kernel samepage merger (KSM) would merge all the allocated pages that happen to be filled with zeroes to the same deduplicated page, thus

Re: [PATCH] x86/crypto: make constants readonly, allow linker to merge them

On Thu, 19 Jan 2017, Denys Vlasenko wrote: > A lot of asm-optimized routines in arch/x86/crypto/ keep its > constants in .data. This is wrong, they should be on .rodata. > > Mnay of these constants are the same in different modules. > For example, 128-bit shuffle mask

Re: [PATCH v3 0/4] ARM: K2G: Add support for TI-SCI Generic PM Domains

On 1/19/2017 10:59 AM, Dave Gerlach wrote: Santosh, On 01/19/2017 11:51 AM, santosh.shilim...@oracle.com wrote: On 1/4/17 2:06 PM, Dave Gerlach wrote: [...] Am going to send pull request over weekend, so if you would like me take the series via arm-soc tree, please get Rafaels, ack and let

Re: [PATCH] x86/crypto: make constants readonly, allow linker to merge them

On Thu, 19 Jan 2017, Denys Vlasenko wrote: > A lot of asm-optimized routines in arch/x86/crypto/ keep its > constants in .data. This is wrong, they should be on .rodata. > > Mnay of these constants are the same in different modules. > For example, 128-bit shuffle mask

Re: [PATCH v3 0/4] ARM: K2G: Add support for TI-SCI Generic PM Domains

On 1/19/2017 10:59 AM, Dave Gerlach wrote: Santosh, On 01/19/2017 11:51 AM, santosh.shilim...@oracle.com wrote: On 1/4/17 2:06 PM, Dave Gerlach wrote: [...] Am going to send pull request over weekend, so if you would like me take the series via arm-soc tree, please get Rafaels, ack and let

[PATCH v2 1/3] ARM: dts: imx6qdl: Fix "ERROR: code indent should use tabs where possible"

From: Jagan Teki Fixed code indent tabs in respetcive imx6qdl dtsi files and also add space on imx6qdl-icore-rqs.dtsi on usdhc bus-width nodes. Cc: Shawn Guo Signed-off-by: Jagan Teki --- Changes for v2: - none

[PATCH v2 1/3] ARM: dts: imx6qdl: Fix "ERROR: code indent should use tabs where possible"

From: Jagan Teki Fixed code indent tabs in respetcive imx6qdl dtsi files and also add space on imx6qdl-icore-rqs.dtsi on usdhc bus-width nodes. Cc: Shawn Guo Signed-off-by: Jagan Teki --- Changes for v2: - none arch/arm/boot/dts/imx6qdl-gw52xx.dtsi| 2 +-

[PATCH v2 3/3] ARM: dts: imx6ul: Add Engicam Is.IoT MX6UL NAND initial support

From: Jagan Teki Engicam Is.IoT MX6UL has separate module for NAND, so add nand dts file for imx6ul-isiot.dtsi. dmesg: - nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda nand: Micron MT29F2G08ABAEAH4 nand: 256 MiB, SLC, erase size: 128 KiB, page size:

[PATCH v2 3/3] ARM: dts: imx6ul: Add Engicam Is.IoT MX6UL NAND initial support

From: Jagan Teki Engicam Is.IoT MX6UL has separate module for NAND, so add nand dts file for imx6ul-isiot.dtsi. dmesg: - nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda nand: Micron MT29F2G08ABAEAH4 nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64 gpmi-nand

[PATCH v2 2/3] ARM: dts: imx6ul: Add Engicam Is.IoT MX6UL eMMC initial support

From: Jagan Teki Engicam Is.IoT MX6UL has separate module for eMMC, so add emmc dts file for imx6ul-isiot.dtsi, usdhc2 node represent eMMC. dmesg: - mmc1: SDHCI controller on 2194000.usdhc [2194000.usdhc] using ADMA mmc1: new DDR MMC card at address 0001 mmcblk1:

[PATCH v2 2/3] ARM: dts: imx6ul: Add Engicam Is.IoT MX6UL eMMC initial support

From: Jagan Teki Engicam Is.IoT MX6UL has separate module for eMMC, so add emmc dts file for imx6ul-isiot.dtsi, usdhc2 node represent eMMC. dmesg: - mmc1: SDHCI controller on 2194000.usdhc [2194000.usdhc] using ADMA mmc1: new DDR MMC card at address 0001 mmcblk1: mmc1:0001 M62704 3.53 GiB

Re: [PATCH] power: reset: Add MAX77620 support

Hi Thierry, > > > [...] > > > > Please use register_restart_handler() instead. It has support for > > priorities, is not arm specific and properly supports unregistering > > (some handler with lower priority will take over). You can check > > gpio-restart as an example for the API. > > > > If

Re: [PATCH] power: reset: Add MAX77620 support

Hi Thierry, > > > [...] > > > > Please use register_restart_handler() instead. It has support for > > priorities, is not arm specific and properly supports unregistering > > (some handler with lower priority will take over). You can check > > gpio-restart as an example for the API. > > > > If

[Update][PATCH 4/4] cpufreq: intel_pstate: Calculate guaranteed performance for HWP

When HWP is active, turbo activation ratio is not used to calculate max non turbo ratio. But on these systems the max non turbo ratio is decided by config TDP settings. This change removes usage of MSR_TURBO_ACTIVATION_RATIO for HWP systems, instead directly use TDP ratios, when more than one

[Update][PATCH 4/4] cpufreq: intel_pstate: Calculate guaranteed performance for HWP

When HWP is active, turbo activation ratio is not used to calculate max non turbo ratio. But on these systems the max non turbo ratio is decided by config TDP settings. This change removes usage of MSR_TURBO_ACTIVATION_RATIO for HWP systems, instead directly use TDP ratios, when more than one

[patch] mm, oom: header nodemask is NULL when cpusets are disabled

Commit 82e7d3abec86 ("oom: print nodemask in the oom report") implicitly sets the allocation nodemask to cpuset_current_mems_allowed when there is no effective mempolicy. cpuset_current_mems_allowed is only effective when cpusets are enabled, which is also printed by dump_header(), so setting

[patch] mm, oom: header nodemask is NULL when cpusets are disabled

Commit 82e7d3abec86 ("oom: print nodemask in the oom report") implicitly sets the allocation nodemask to cpuset_current_mems_allowed when there is no effective mempolicy. cpuset_current_mems_allowed is only effective when cpusets are enabled, which is also printed by dump_header(), so setting

Re: [PATCH RFC] vfio error recovery: kernel support

On Fri, 20 Jan 2017 00:21:02 +0200 "Michael S. Tsirkin" wrote: > On Thu, Jan 19, 2017 at 03:10:56PM -0700, Alex Williamson wrote: > > On Thu, 19 Jan 2017 22:16:03 +0200 > > "Michael S. Tsirkin" wrote: > > > > > This is a design and an initial patch for

Re: [PATCH RFC] vfio error recovery: kernel support

On Fri, 20 Jan 2017 00:21:02 +0200 "Michael S. Tsirkin" wrote: > On Thu, Jan 19, 2017 at 03:10:56PM -0700, Alex Williamson wrote: > > On Thu, 19 Jan 2017 22:16:03 +0200 > > "Michael S. Tsirkin" wrote: > > > > > This is a design and an initial patch for kernel side for AER > > > support in

Re: [RFC v2 4/5] DT bindings documentation for Synopsys UDC platform driver

On 01/19/2017 02:36 PM, Scott Branden wrote: The driver stands alone from the SoC and does not need compatibility strings per SoC. New SoCs will use the exact same block. >>> >>> Even if you take the exact same block and put it in a different SoC, >>> that's still an integration work

Re: [RFC v2 4/5] DT bindings documentation for Synopsys UDC platform driver

On 01/19/2017 02:36 PM, Scott Branden wrote: The driver stands alone from the SoC and does not need compatibility strings per SoC. New SoCs will use the exact same block. >>> >>> Even if you take the exact same block and put it in a different SoC, >>> that's still an integration work

[PATCH 2/2] Input: tca8418 - switch to using generic device properties

Let's drop legacy platform data support (there are no users in mainline) and switch to using generic device properties, which will make the driver simpler (non-OF boards can use property sets to describe hardware). Signed-off-by: Dmitry Torokhov ---

[PATCH 2/2] Input: tca8418 - switch to using generic device properties

Let's drop legacy platform data support (there are no users in mainline) and switch to using generic device properties, which will make the driver simpler (non-OF boards can use property sets to describe hardware). Signed-off-by: Dmitry Torokhov --- drivers/input/keyboard/tca8418_keypad.c | 90

[PATCH 1/2] Input: matrix-keypad - switch to using generic device properties

Instead of being OF-specific, let's switch to using generic device properties, which will make this code usable on ACPI, device tree and legacy boards that use property sets. As part of the change let's rename matrix_keypad_parse_of_params() to matrix_keypad_parse_properties(). Signed-off-by:

[PATCH 1/2] Input: matrix-keypad - switch to using generic device properties

Instead of being OF-specific, let's switch to using generic device properties, which will make this code usable on ACPI, device tree and legacy boards that use property sets. As part of the change let's rename matrix_keypad_parse_of_params() to matrix_keypad_parse_properties(). Signed-off-by:

Re: [PATCH] drivers: power: supply: Compress return logic into one line.

Hey hello, Quoting Sebastian Reichel : Hi, On Wed, Jan 11, 2017 at 08:45:57PM -0600, Gustavo A. R. Silva wrote: Simplify return logic to avoid unnecessary variable assignments. These issues were detected using Coccinelle and the following semantic patch: @@ local

Re: [PATCH] drivers: power: supply: Compress return logic into one line.

Hey hello, Quoting Sebastian Reichel : Hi, On Wed, Jan 11, 2017 at 08:45:57PM -0600, Gustavo A. R. Silva wrote: Simplify return logic to avoid unnecessary variable assignments. These issues were detected using Coccinelle and the following semantic patch: @@ local idexpression ret;

Re: [PATCH v2 0/6] Selftests fixes for futex and intel_pstate

On Thu, Jan 19, 2017 at 10:35:21AM -0700, Shuah Khan wrote: > On 01/11/2017 08:11 AM, Stafford Horne wrote: > > This is followup to my previous patch [1] which was a very simple makefile > > change. After a comment from Darren Hart I updated intel_pstate as well, > > but noticed a few issues with

Re: [PATCH v2 0/6] Selftests fixes for futex and intel_pstate

On Thu, Jan 19, 2017 at 10:35:21AM -0700, Shuah Khan wrote: > On 01/11/2017 08:11 AM, Stafford Horne wrote: > > This is followup to my previous patch [1] which was a very simple makefile > > change. After a comment from Darren Hart I updated intel_pstate as well, > > but noticed a few issues with

Re: [PATCH v3 0/8] ARM: dts: Switch to new DSA binding

Hi Florian, On jeu., janv. 19 2017, Florian Fainelli wrote: > On 01/17/2017 10:22 AM, Florian Fainelli wrote: >> Hi all, >> >> This patch series converts the in-tree users to utilize the new (relatively) >> DSA binding that was introduced with commit 8c5ad1d6179d ("net:

Re: [PATCH v3 0/8] ARM: dts: Switch to new DSA binding

Hi Florian, On jeu., janv. 19 2017, Florian Fainelli wrote: > On 01/17/2017 10:22 AM, Florian Fainelli wrote: >> Hi all, >> >> This patch series converts the in-tree users to utilize the new (relatively) >> DSA binding that was introduced with commit 8c5ad1d6179d ("net: dsa: Document >> new

Re: [PATCH v3 0/8] ARM: dts: Switch to new DSA binding

On 01/19/2017 02:48 PM, Gregory CLEMENT wrote: > Hi Florian, > > On jeu., janv. 19 2017, Florian Fainelli wrote: > >> On 01/17/2017 10:22 AM, Florian Fainelli wrote: >>> Hi all, >>> >>> This patch series converts the in-tree users to utilize the new (relatively) >>> DSA

Re: [PATCH v3 0/8] ARM: dts: Switch to new DSA binding

On 01/19/2017 02:48 PM, Gregory CLEMENT wrote: > Hi Florian, > > On jeu., janv. 19 2017, Florian Fainelli wrote: > >> On 01/17/2017 10:22 AM, Florian Fainelli wrote: >>> Hi all, >>> >>> This patch series converts the in-tree users to utilize the new (relatively) >>> DSA binding that was

[PATCH v2 3/7] Input: pwm-beeper - use input_set_capability()

Instead of manipulating capability bits directly, let's use input_set_capability() API. Signed-off-by: Dmitry Torokhov --- drivers/input/misc/pwm-beeper.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/input/misc/pwm-beeper.c

[PATCH v2 3/7] Input: pwm-beeper - use input_set_capability()

Instead of manipulating capability bits directly, let's use input_set_capability() API. Signed-off-by: Dmitry Torokhov --- drivers/input/misc/pwm-beeper.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/input/misc/pwm-beeper.c b/drivers/input/misc/pwm-beeper.c

[PATCH v2 2/7] Input: pwm-beeper - switch to using managed resources

Use of managed resources (devm) simplifies error handling and tear down of the driver. Signed-off-by: Dmitry Torokhov --- drivers/input/misc/pwm-beeper.c | 44 ++--- 1 file changed, 10 insertions(+), 34 deletions(-) diff --git

[PATCH 2/2] ARM: dts: exynos: Use correct mfc_pd async-bridge clock for Exynos5420

Commit 94aed538e032 ("ARM: dts: exynos: Add async-bridge clock to MFC power domain for Exynos5420") fixed an imprecise external abort error when the MFC registers were tried to be accessed and the needed clock for the asynchronous bridges were gated. But according to the Exynos5420 manual the

[PATCH v2 2/7] Input: pwm-beeper - switch to using managed resources

Use of managed resources (devm) simplifies error handling and tear down of the driver. Signed-off-by: Dmitry Torokhov --- drivers/input/misc/pwm-beeper.c | 44 ++--- 1 file changed, 10 insertions(+), 34 deletions(-) diff --git

[PATCH 2/2] ARM: dts: exynos: Use correct mfc_pd async-bridge clock for Exynos5420

Commit 94aed538e032 ("ARM: dts: exynos: Add async-bridge clock to MFC power domain for Exynos5420") fixed an imprecise external abort error when the MFC registers were tried to be accessed and the needed clock for the asynchronous bridges were gated. But according to the Exynos5420 manual the

[PATCH 1/2] ARM: dts: exynos: Add CLK_ACLK432_SCALER clock to gsc_pd for Exynos5800

On Exynos5800 SoC the SCALER block uses 2 input clocks: CLK_ACLK_300_GSCL and CLK_ACLK432_SCALER, so both needs to be ungated in order to access it. The SoC manual say the CLK_ACLK432_SCALER is needed to access the internal buses, so add this clock as another asynchronous bridges (ASB) clock.

[PATCH 1/2] ARM: dts: exynos: Add CLK_ACLK432_SCALER clock to gsc_pd for Exynos5800

On Exynos5800 SoC the SCALER block uses 2 input clocks: CLK_ACLK_300_GSCL and CLK_ACLK432_SCALER, so both needs to be ungated in order to access it. The SoC manual say the CLK_ACLK432_SCALER is needed to access the internal buses, so add this clock as another asynchronous bridges (ASB) clock.

[PATCH v2 1/7] Input: pwm-beeper - remove calls to legacy pwm_request API

There are no more users of pwm-beeper driver in mainline relying on this legacy API, so let's remove it and simplify the driver code. Signed-off-by: Dmitry Torokhov --- drivers/input/misc/pwm-beeper.c | 6 -- 1 file changed, 6 deletions(-) diff --git

[PATCH v2 6/7] Input: pwm-beeper - add optional amplifier regulator

From: David Lechner This adds an optional regulator to the pwm-beeper device. This regulator acts as an amplifier. The amplifier is only enabled while beeping in order to reduce power consumption. Tested on LEGO MINDSTORMS EV3, which has a speaker connected to PWM through

[PATCH v2 6/7] Input: pwm-beeper - add optional amplifier regulator

From: David Lechner This adds an optional regulator to the pwm-beeper device. This regulator acts as an amplifier. The amplifier is only enabled while beeping in order to reduce power consumption. Tested on LEGO MINDSTORMS EV3, which has a speaker connected to PWM through an amplifier.

[PATCH v2 1/7] Input: pwm-beeper - remove calls to legacy pwm_request API

There are no more users of pwm-beeper driver in mainline relying on this legacy API, so let's remove it and simplify the driver code. Signed-off-by: Dmitry Torokhov --- drivers/input/misc/pwm-beeper.c | 6 -- 1 file changed, 6 deletions(-) diff --git a/drivers/input/misc/pwm-beeper.c

[PATCH v2 5/7] Input: pwm-beeper - suppress error message on probe defer

From: David Lechner This suppress printing an error message when pwm_get returns -EPROBE_DEFER. Otherwise you get a bunch of noise in the kernel log. Signed-off-by: David Lechner Patchwork-Id: 9499915 Signed-off-by: Dmitry Torokhov

[PATCH v2 5/7] Input: pwm-beeper - suppress error message on probe defer

From: David Lechner This suppress printing an error message when pwm_get returns -EPROBE_DEFER. Otherwise you get a bunch of noise in the kernel log. Signed-off-by: David Lechner Patchwork-Id: 9499915 Signed-off-by: Dmitry Torokhov --- drivers/input/misc/pwm-beeper.c | 3 ++- 1 file changed,

[PATCH v2 4/7] Input: pwm-beeper - fix race when suspending

Usually userspace sends SND_BELL and SND_TONE events, and by the time pwm_beeper_suspend() runs userpsace is already frozen, but theoretically in-kernel users may send these events too, and that may cause pwm_beeper_event() scheduling another work after we canceled it. Let's introduce a

[PATCH v2 4/7] Input: pwm-beeper - fix race when suspending

Usually userspace sends SND_BELL and SND_TONE events, and by the time pwm_beeper_suspend() runs userpsace is already frozen, but theoretically in-kernel users may send these events too, and that may cause pwm_beeper_event() scheduling another work after we canceled it. Let's introduce a

[PATCH v2 7/7] Input: pwm-beeper - switch to using "atomic" PWM API

The "atomic" API allows us to configure PWM period and duty cycle and enable it in one call. Signed-off-by: Dmitry Torokhov --- drivers/input/misc/pwm-beeper.c | 25 - 1 file changed, 16 insertions(+), 9 deletions(-) diff --git

[PATCH v2 7/7] Input: pwm-beeper - switch to using "atomic" PWM API

The "atomic" API allows us to configure PWM period and duty cycle and enable it in one call. Signed-off-by: Dmitry Torokhov --- drivers/input/misc/pwm-beeper.c | 25 - 1 file changed, 16 insertions(+), 9 deletions(-) diff --git a/drivers/input/misc/pwm-beeper.c

Re: [RFC v2 4/5] DT bindings documentation for Synopsys UDC platform driver

On 17-01-19 01:55 PM, Ray Jui wrote: On 1/19/2017 12:17 PM, Florian Fainelli wrote: On 01/19/2017 12:07 PM, Scott Branden wrote: Hi Florian, On 17-01-19 11:40 AM, Florian Fainelli wrote: On 01/19/2017 11:30 AM, Scott Branden wrote: Hi Rob, On 17-01-19 09:36 AM, Rob Herring wrote: On

Re: [RFC v2 4/5] DT bindings documentation for Synopsys UDC platform driver

On 17-01-19 01:55 PM, Ray Jui wrote: On 1/19/2017 12:17 PM, Florian Fainelli wrote: On 01/19/2017 12:07 PM, Scott Branden wrote: Hi Florian, On 17-01-19 11:40 AM, Florian Fainelli wrote: On 01/19/2017 11:30 AM, Scott Branden wrote: Hi Rob, On 17-01-19 09:36 AM, Rob Herring wrote: On

Re: [PATCH v5 2/2] net: dsa: mv88e6xxx: Add support for ethernet switch 88E6341

Gregory CLEMENT writes: > +static bool mv88e6xxx_6341_family(struct mv88e6xxx_chip *chip) > +{ > + return chip->info->family == MV88E6XXX_FAMILY_6341; > +} I don't want to see these erronous family checks anymore, but I cannot blame you for adding it

Re: [PATCH v5 2/2] net: dsa: mv88e6xxx: Add support for ethernet switch 88E6341

Gregory CLEMENT writes: > +static bool mv88e6xxx_6341_family(struct mv88e6xxx_chip *chip) > +{ > + return chip->info->family == MV88E6XXX_FAMILY_6341; > +} I don't want to see these erronous family checks anymore, but I cannot blame you for adding it since not all the code is moved to ops

[PATCH v2 1/2] [media] exynos-gsc: Fix unbalanced pm_runtime_enable() error

Commit a006c04e6218 ("[media] exynos-gsc: Fixup clock management at ->remove()") changed the driver's .remove function logic to fist do a pm_runtime_get_sync() to make sure the device is powered before attempting to gate the gsc clock. But the commit also removed a pm_runtime_disable() call that

[PATCH v2 2/2] [media] exynos-gsc: Only reset the GSC HW on probe() if !CONFIG_PM

Commit 15f90ab57acc ("[media] exynos-gsc: Make driver functional when CONFIG_PM is unset") removed the implicit dependency that the driver had with CONFIG_PM, since it relied on the config option to be enabled. In order to work with !CONFIG_PM, the GSC reset logic that happens in the runtime

[PATCH v2 1/2] [media] exynos-gsc: Fix unbalanced pm_runtime_enable() error

Commit a006c04e6218 ("[media] exynos-gsc: Fixup clock management at ->remove()") changed the driver's .remove function logic to fist do a pm_runtime_get_sync() to make sure the device is powered before attempting to gate the gsc clock. But the commit also removed a pm_runtime_disable() call that

[PATCH v2 2/2] [media] exynos-gsc: Only reset the GSC HW on probe() if !CONFIG_PM

Commit 15f90ab57acc ("[media] exynos-gsc: Make driver functional when CONFIG_PM is unset") removed the implicit dependency that the driver had with CONFIG_PM, since it relied on the config option to be enabled. In order to work with !CONFIG_PM, the GSC reset logic that happens in the runtime

Re: [PATCH v2 3/3] Input: pwm-beeper: add optional amplifier regulator

On Sun, Jan 15, 2017 at 07:04:09PM -0600, David Lechner wrote: > On 01/15/2017 06:34 PM, Dmitry Torokhov wrote: > >On Sun, Jan 15, 2017 at 06:12:29PM -0600, David Lechner wrote: > >>On 01/14/2017 01:19 PM, Dmitry Torokhov wrote: > >>>On Wed, Jan 11, 2017 at 02:02:01PM -0600, David Lechner wrote: >

Re: [PATCH v2 3/3] Input: pwm-beeper: add optional amplifier regulator

On Sun, Jan 15, 2017 at 07:04:09PM -0600, David Lechner wrote: > On 01/15/2017 06:34 PM, Dmitry Torokhov wrote: > >On Sun, Jan 15, 2017 at 06:12:29PM -0600, David Lechner wrote: > >>On 01/14/2017 01:19 PM, Dmitry Torokhov wrote: > >>>On Wed, Jan 11, 2017 at 02:02:01PM -0600, David Lechner wrote: >

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