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

On Thu, May 11, 2017 at 9:24 PM, Anatolij Gustschin wrote: > Add stubs for gpiod_add_lookup_table() and gpiod_remove_lookup_table() > for the !GPIOLIB case to prevent build errors. > Thanks! FWIW: Reviewed-by: Andy Shevchenko It will fix this kbuild

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

On Thu, May 11, 2017 at 9:24 PM, Anatolij Gustschin wrote: > Add stubs for gpiod_add_lookup_table() and gpiod_remove_lookup_table() > for the !GPIOLIB case to prevent build errors. > Thanks! FWIW: Reviewed-by: Andy Shevchenko It will fix this kbuild bot complain:

Re: [PATCH] usb-musb: keep VBUS on when device is disconnected

On Thu, May 11, 2017 at 11:55:28AM -0700, Tony Lindgren wrote: > * Bin Liu [170511 11:53]: > > On Mon, Mar 27, 2017 at 10:55:37AM -0700, Tony Lindgren wrote: > > > * Bin Liu [170327 10:17]: > > > > On Mon, Mar 27, 2017 at 09:59:47AM -0700, Tony Lindgren wrote: > > > >

Re: [PATCH] usb-musb: keep VBUS on when device is disconnected

On Thu, May 11, 2017 at 11:55:28AM -0700, Tony Lindgren wrote: > * Bin Liu [170511 11:53]: > > On Mon, Mar 27, 2017 at 10:55:37AM -0700, Tony Lindgren wrote: > > > * Bin Liu [170327 10:17]: > > > > On Mon, Mar 27, 2017 at 09:59:47AM -0700, Tony Lindgren wrote: > > > > > * Moreno Bartalucci

Re: [RFC PATCH v1 00/30] fs: inode->i_version rework and optimization

On Wed, Apr 05, 2017 at 02:14:09PM -0400, J. Bruce Fields wrote: > On Wed, Apr 05, 2017 at 10:05:51AM +0200, Jan Kara wrote: > > 1) Keep i_version as is, make clients also check for i_ctime. > > That would be a protocol revision, which we'd definitely rather avoid. > > But can't we accomplish

Re: [RFC PATCH v1 00/30] fs: inode->i_version rework and optimization

On Wed, Apr 05, 2017 at 02:14:09PM -0400, J. Bruce Fields wrote: > On Wed, Apr 05, 2017 at 10:05:51AM +0200, Jan Kara wrote: > > 1) Keep i_version as is, make clients also check for i_ctime. > > That would be a protocol revision, which we'd definitely rather avoid. > > But can't we accomplish

Re: [RFC] adding of TGID to ftrace output

On Thu, May 11, 2017 at 7:23 AM, Steven Rostedt wrote: [..] >> To fix the suggestion I made in the very beginning of this email, I >> suggest a combination of trace_find_cmdline type of approach to save >> the tgid of all current threads available, and then using >>

Re: [RFC] adding of TGID to ftrace output

On Thu, May 11, 2017 at 7:23 AM, Steven Rostedt wrote: [..] >> To fix the suggestion I made in the very beginning of this email, I >> suggest a combination of trace_find_cmdline type of approach to save >> the tgid of all current threads available, and then using >> trace_sched_fork to find out

Re: [PATCH] usb-musb: keep VBUS on when device is disconnected

* Bin Liu [170511 11:53]: > On Mon, Mar 27, 2017 at 10:55:37AM -0700, Tony Lindgren wrote: > > * Bin Liu [170327 10:17]: > > > On Mon, Mar 27, 2017 at 09:59:47AM -0700, Tony Lindgren wrote: > > > > * Moreno Bartalucci [170327 09:23]: >

Re: [PATCH] usb-musb: keep VBUS on when device is disconnected

* Bin Liu [170511 11:53]: > On Mon, Mar 27, 2017 at 10:55:37AM -0700, Tony Lindgren wrote: > > * Bin Liu [170327 10:17]: > > > On Mon, Mar 27, 2017 at 09:59:47AM -0700, Tony Lindgren wrote: > > > > * Moreno Bartalucci [170327 09:23]: > > > > > If I understood your patch, however, if the device

Re: [PATCH] smp_call_function: use inline helpers instead of macros

Hi Arnd, [auto build test ERROR on linus/master] [also build test ERROR on v4.11 next-20170511] [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/linux/commits/Arnd-Bergmann/smp_call_function-use-inline-helpers

Re: [PATCH] smp_call_function: use inline helpers instead of macros

Hi Arnd, [auto build test ERROR on linus/master] [also build test ERROR on v4.11 next-20170511] [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/linux/commits/Arnd-Bergmann/smp_call_function-use-inline-helpers

Re: [PATCH] usb-musb: keep VBUS on when device is disconnected

On Mon, Mar 27, 2017 at 10:55:37AM -0700, Tony Lindgren wrote: > * Bin Liu [170327 10:17]: > > On Mon, Mar 27, 2017 at 09:59:47AM -0700, Tony Lindgren wrote: > > > * Moreno Bartalucci [170327 09:23]: > > > > If I understood your patch, however, if

Re: [PATCH] usb-musb: keep VBUS on when device is disconnected

On Mon, Mar 27, 2017 at 10:55:37AM -0700, Tony Lindgren wrote: > * Bin Liu [170327 10:17]: > > On Mon, Mar 27, 2017 at 09:59:47AM -0700, Tony Lindgren wrote: > > > * Moreno Bartalucci [170327 09:23]: > > > > If I understood your patch, however, if the device (anyone, not just my > > > > one)

Re: [PATCH 1/9] mtd: cfi_cmdset_0020: Drop unnecessary static

On Thu, May 04, 2017 at 10:10:46PM +0200, Julia Lawall wrote: > Drop static on a local variable, when the variable is initialized before > any use on every possible execution path through the function. The static > has no benefit, and dropping it reduces the code size. > > The semantic patch

Re: [PATCH 1/9] mtd: cfi_cmdset_0020: Drop unnecessary static

On Thu, May 04, 2017 at 10:10:46PM +0200, Julia Lawall wrote: > Drop static on a local variable, when the variable is initialized before > any use on every possible execution path through the function. The static > has no benefit, and dropping it reduces the code size. > > The semantic patch

Re: [PATCH] x86/efi: Add EFI_PGT_DUMP support for x86_32, kexec and efi=old_map

On Thu, 2017-05-11 at 13:18 +0200, Borislav Petkov wrote: > On Wed, May 10, 2017 at 03:49:05PM -0700, Sai Praneeth Prakhya wrote: > > From: Sai Praneeth > > > > EFI_PGT_DUMP, as the name suggests dumps efi page tables to dmesg during > > kernel boot. This feature

Re: [PATCH] x86/efi: Add EFI_PGT_DUMP support for x86_32, kexec and efi=old_map

On Thu, 2017-05-11 at 13:18 +0200, Borislav Petkov wrote: > On Wed, May 10, 2017 at 03:49:05PM -0700, Sai Praneeth Prakhya wrote: > > From: Sai Praneeth > > > > EFI_PGT_DUMP, as the name suggests dumps efi page tables to dmesg during > > kernel boot. This feature is very useful while debugging

Re: [PATCH 3/3] f2fs: introduce io_list for serialize data/node IOs

Hi Chao, On 05/09, Chao Yu wrote: > From: Chao Yu > > Serialize data/node IOs by using fifo list instead of mutex lock, > it will help to enhance concurrency of f2fs, meanwhile keeping LFS > IO semantics. I'm not against to give it a try, but not sure how much we can get a

Re: [PATCH 3/3] f2fs: introduce io_list for serialize data/node IOs

Hi Chao, On 05/09, Chao Yu wrote: > From: Chao Yu > > Serialize data/node IOs by using fifo list instead of mutex lock, > it will help to enhance concurrency of f2fs, meanwhile keeping LFS > IO semantics. I'm not against to give it a try, but not sure how much we can get a benefit from this

Re: [PATCH 1/3] f2fs: split wio_mutex

On 05/09, Chao Yu wrote: > From: Chao Yu > > Split wio_mutex to adjust different temperature bio cache. This can be rephrased like: Signed-off-by: Chao Yu Signed-off-by: Jaegeuk Kim --- fs/f2fs/f2fs.h| 3 ++- fs/f2fs/segment.c

Re: [PATCH 1/3] f2fs: split wio_mutex

On 05/09, Chao Yu wrote: > From: Chao Yu > > Split wio_mutex to adjust different temperature bio cache. This can be rephrased like: Signed-off-by: Chao Yu Signed-off-by: Jaegeuk Kim --- fs/f2fs/f2fs.h| 3 ++- fs/f2fs/segment.c | 4 ++-- fs/f2fs/super.c | 7 --- 3 files changed, 8

[GIT PULL] target updates for v4.12-rc1

Hi Linus, Here are the target-pending updates for v4.12-rc1. Please go ahead and pull from: git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git for-next Things where alot more calm than previously expected. It's primarily fixes in various areas, with most of the new

[GIT PULL] target updates for v4.12-rc1

Hi Linus, Here are the target-pending updates for v4.12-rc1. Please go ahead and pull from: git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git for-next Things where alot more calm than previously expected. It's primarily fixes in various areas, with most of the new

Re: [PATCH v6 3/5] test: add new driver_data load tester

On Thu, May 11, 2017 at 11:26 AM, Luis R. Rodriguez wrote: > > It would seems to make sense to me to only need to verify files when read > for the first time, once its cache I don't see why we would re-verify them ? To be clear, the fw cache feature reads the files from the fs

Re: [PATCH v6 3/5] test: add new driver_data load tester

On Thu, May 11, 2017 at 11:26 AM, Luis R. Rodriguez wrote: > > It would seems to make sense to me to only need to verify files when read > for the first time, once its cache I don't see why we would re-verify them ? To be clear, the fw cache feature reads the files from the fs prior to suspend,

Re: [PATCH v2 1/3] kvm: x86: Add a hook for arch specific dirty logging emulation

"Huang, Kai" writes: ... > Hi Bandan, > > I was just suggesting. You and Paolo still make the decision :) Sure Kai, I don't mind the name change at all. The maintainer has already picked this up and I don't think the function name change is worth submitting a follow

Re: [PATCH v2 1/3] kvm: x86: Add a hook for arch specific dirty logging emulation

"Huang, Kai" writes: ... > Hi Bandan, > > I was just suggesting. You and Paolo still make the decision :) Sure Kai, I don't mind the name change at all. The maintainer has already picked this up and I don't think the function name change is worth submitting a follow up. Thank you very much for

Re: [PATCH] mtd: nand: make nand_ooblayout_lp_hamming_ops static

On Thu, May 04, 2017 at 04:08:13PM +0200, Boris Brezillon wrote: > On Thu, 4 May 2017 13:11:00 +0100 > Colin King wrote: > > > From: Colin Ian King > > > > nand_ooblayout_lp_hamming_ops can be made static as it does not need to be > > in

Re: [PATCH] mtd: nand: make nand_ooblayout_lp_hamming_ops static

On Thu, May 04, 2017 at 04:08:13PM +0200, Boris Brezillon wrote: > On Thu, 4 May 2017 13:11:00 +0100 > Colin King wrote: > > > From: Colin Ian King > > > > nand_ooblayout_lp_hamming_ops can be made static as it does not need to be > > in global scope. > > > > Signed-off-by: Colin Ian King >

Re: Threads stuck in zap_pid_ns_processes()

On Thu, May 11, 2017 at 12:31:21PM -0500, Eric W. Biederman wrote: > Guenter Roeck writes: > > > Hi all, > > > > the test program attached below almost always results in one of the child > > processes being stuck in zap_pid_ns_processes(). When this happens, I can > > see

Re: Threads stuck in zap_pid_ns_processes()

On Thu, May 11, 2017 at 12:31:21PM -0500, Eric W. Biederman wrote: > Guenter Roeck writes: > > > Hi all, > > > > the test program attached below almost always results in one of the child > > processes being stuck in zap_pid_ns_processes(). When this happens, I can > > see from test logs that

[PATCH v2 5/7] drm/ltdc: Use the panel-bridge helper.

Another 100 lines of boilerplate gone. Bridges aren't supported yet, but will be trivial to add later. Signed-off-by: Eric Anholt --- Also untested. drivers/gpu/drm/stm/ltdc.c | 128 + drivers/gpu/drm/stm/ltdc.h | 2 +- 2 files

[PATCH v2 5/7] drm/ltdc: Use the panel-bridge helper.

Another 100 lines of boilerplate gone. Bridges aren't supported yet, but will be trivial to add later. Signed-off-by: Eric Anholt --- Also untested. drivers/gpu/drm/stm/ltdc.c | 128 + drivers/gpu/drm/stm/ltdc.h | 2 +- 2 files changed, 13

[PATCH v2 6/7] drm/atmel-hlcdc: Drop custom encoder cleanup func.

drm_encoder_cleanup() finishes with memsetting it to 0, already. Signed-off-by: Eric Anholt --- drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_output.c | 8 +--- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_output.c

[PATCH v2 6/7] drm/atmel-hlcdc: Drop custom encoder cleanup func.

drm_encoder_cleanup() finishes with memsetting it to 0, already. Signed-off-by: Eric Anholt --- drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_output.c | 8 +--- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_output.c

[PATCH v2 4/7] drm/mediatek: Use the panel-bridge helper.

Avoids a bunch of connector boilerplate. Note that this causes panel prepare() to be moved before mtk_dsi_poweron() and unprepare() to be after poweroff(). I think this is the expected usage of the panel API (enable should be when you do things that require the link to be brought up), but there

[PATCH v2 2/7] drm/vc4: Switch DSI to the panel-bridge layer, and support bridges.

The newer version of the RPi panel driver is going to be a combination of a bridge and a panel, but we should also support panels without a bridge, so the panel-bridge layer lets us do that cleanly. v2: Drop "dev" argument. Signed-off-by: Eric Anholt Acked-by: Daniel Vetter

[PATCH v2 4/7] drm/mediatek: Use the panel-bridge helper.

Avoids a bunch of connector boilerplate. Note that this causes panel prepare() to be moved before mtk_dsi_poweron() and unprepare() to be after poweroff(). I think this is the expected usage of the panel API (enable should be when you do things that require the link to be brought up), but there

[PATCH v2 2/7] drm/vc4: Switch DSI to the panel-bridge layer, and support bridges.

The newer version of the RPi panel driver is going to be a combination of a bridge and a panel, but we should also support panels without a bridge, so the panel-bridge layer lets us do that cleanly. v2: Drop "dev" argument. Signed-off-by: Eric Anholt Acked-by: Daniel Vetter ---

[PATCH v2 3/7] drm/vc4: Switch DPI to using the panel-bridge helper.

Another 100 lines of boilerplate gone, while allowing for bridges to be connected in the display chain. Signed-off-by: Eric Anholt --- drivers/gpu/drm/vc4/vc4_dpi.c | 164 -- 1 file changed, 30 insertions(+), 134 deletions(-) diff --git

[PATCH v2 7/7] drm/atmel-hlcdc: Replace the panel usage with drm_panel_bridge.

This cuts 135 lines of boilerplate, at the cost of losing the filtering of get_modes() using atmel_hlcdc_dc_mode_valid(). The atomic check will still check that we don't set an invalid mode, though. Signed-off-by: Eric Anholt --- This patch is just a proposal for atmel-hlcdc

[PATCH v2 1/7] drm/bridge: Refactor out the panel wrapper from the lvds-encoder bridge.

Many DRM drivers have common code to make a stub connector implementation that wraps a drm_panel. By wrapping the panel in a DRM bridge, all of the connector code (including calls during encoder enable/disable) goes away. v2: Fix build with CONFIG_DRM=m, drop "dev" argument that should just

[PATCH v2 3/7] drm/vc4: Switch DPI to using the panel-bridge helper.

Another 100 lines of boilerplate gone, while allowing for bridges to be connected in the display chain. Signed-off-by: Eric Anholt --- drivers/gpu/drm/vc4/vc4_dpi.c | 164 -- 1 file changed, 30 insertions(+), 134 deletions(-) diff --git

[PATCH v2 7/7] drm/atmel-hlcdc: Replace the panel usage with drm_panel_bridge.

This cuts 135 lines of boilerplate, at the cost of losing the filtering of get_modes() using atmel_hlcdc_dc_mode_valid(). The atomic check will still check that we don't set an invalid mode, though. Signed-off-by: Eric Anholt --- This patch is just a proposal for atmel-hlcdc if you like it --

[PATCH v2 1/7] drm/bridge: Refactor out the panel wrapper from the lvds-encoder bridge.

Many DRM drivers have common code to make a stub connector implementation that wraps a drm_panel. By wrapping the panel in a DRM bridge, all of the connector code (including calls during encoder enable/disable) goes away. v2: Fix build with CONFIG_DRM=m, drop "dev" argument that should just

[PATCH][V2] ethernet: aquantia: remove redundant checks on error status

From: Colin Ian King The error status err is initialized as zero and then being checked several times to see if it is less than zero even when it has not been updated. It may seem that the err should be assigned to the return code of the call to the various

[PATCH][V2] ethernet: aquantia: remove redundant checks on error status

From: Colin Ian King The error status err is initialized as zero and then being checked several times to see if it is less than zero even when it has not been updated. It may seem that the err should be assigned to the return code of the call to the various *offload_en_set calls and then we

Re: [PATCH v7 1/5] firmware: add extensible driver data params

On Thu, May 11, 2017 at 01:17:39PM -0500, Li, Yi wrote: > On 5/2/2017 3:49 AM, Luis R. Rodriguez wrote: > > As the firmware API evolves we keep extending functions with more arguments. > > Stop this nonsense by proving an extensible data structure which can be used > > to represent both user

Re: [PATCH v7 1/5] firmware: add extensible driver data params

On Thu, May 11, 2017 at 01:17:39PM -0500, Li, Yi wrote: > On 5/2/2017 3:49 AM, Luis R. Rodriguez wrote: > > As the firmware API evolves we keep extending functions with more arguments. > > Stop this nonsense by proving an extensible data structure which can be used > > to represent both user

Re: [PATCH v6 3/5] test: add new driver_data load tester

On Thu, May 11, 2017 at 07:46:27PM +0900, AKASHI Takahiro wrote: > On Fri, Apr 28, 2017 at 03:45:35AM +0200, Luis R. Rodriguez wrote: > > > > diff --git a/tools/testing/selftests/firmware/driver_data.sh > > > > b/tools/testing/selftests/firmware/driver_data.sh > > ... > > > > > >

Re: [PATCH v6 3/5] test: add new driver_data load tester

On Thu, May 11, 2017 at 07:46:27PM +0900, AKASHI Takahiro wrote: > On Fri, Apr 28, 2017 at 03:45:35AM +0200, Luis R. Rodriguez wrote: > > > > diff --git a/tools/testing/selftests/firmware/driver_data.sh > > > > b/tools/testing/selftests/firmware/driver_data.sh > > ... > > > > > >

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

Add stubs for gpiod_add_lookup_table() and gpiod_remove_lookup_table() for the !GPIOLIB case to prevent build errors. Signed-off-by: Anatolij Gustschin --- Changes in v4: - move stubs to gpio/machine.h Changes in v3: - add stubs for !GPIOLIB case. Drop prototypes, these are

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

Add stubs for gpiod_add_lookup_table() and gpiod_remove_lookup_table() for the !GPIOLIB case to prevent build errors. Signed-off-by: Anatolij Gustschin --- Changes in v4: - move stubs to gpio/machine.h Changes in v3: - add stubs for !GPIOLIB case. Drop prototypes, these are already in

[PATCH net] net: phy: Call bus->reset() after releasing PHYs from reset

The API convention makes it that a given MDIO bus reset should be able to access PHY devices in its reset() callback and perform additional MDIO accesses in order to bring the bus and PHYs in a working state. Commit 69226896ad63 ("mdio_bus: Issue GPIO RESET to PHYs.") broke that contract by first

[PATCH net] net: phy: Call bus->reset() after releasing PHYs from reset

The API convention makes it that a given MDIO bus reset should be able to access PHY devices in its reset() callback and perform additional MDIO accesses in order to bring the bus and PHYs in a working state. Commit 69226896ad63 ("mdio_bus: Issue GPIO RESET to PHYs.") broke that contract by first

Re: [PATCH] Bluetooth: hci_nokia: select CONFIG_BT_HCIUART_H4

Hi Arnd, On Thu, May 11, 2017 at 02:11:26PM +0200, Arnd Bergmann wrote: > Like the other H4 variants, this only builds when the base > H4 support is enabled, otherwise we get a build error: > > drivers/bluetooth/hci_nokia.c:624:33: error: array type has incomplete > element type 'struct

Re: [PATCH] Bluetooth: hci_nokia: select CONFIG_BT_HCIUART_H4

Hi Arnd, On Thu, May 11, 2017 at 02:11:26PM +0200, Arnd Bergmann wrote: > Like the other H4 variants, this only builds when the base > H4 support is enabled, otherwise we get a build error: > > drivers/bluetooth/hci_nokia.c:624:33: error: array type has incomplete > element type 'struct

Re: [PATCH] bluetooth: hci_ll: add proper SERDEV dependency

Hi, On Thu, May 11, 2017 at 01:41:54PM +0200, Arnd Bergmann wrote: > When SERDEV is a loadable module, and the HCI code is built-in, we > get a link error: > > drivers/bluetooth/built-in.o: In function `ll_close': > hci_ll.c:(.text+0x278d): undefined reference to `serdev_device_close' >

Re: [PATCH] bluetooth: hci_ll: add proper SERDEV dependency

Hi, On Thu, May 11, 2017 at 01:41:54PM +0200, Arnd Bergmann wrote: > When SERDEV is a loadable module, and the HCI code is built-in, we > get a link error: > > drivers/bluetooth/built-in.o: In function `ll_close': > hci_ll.c:(.text+0x278d): undefined reference to `serdev_device_close' >

Re: [PATCH] ethernet: aquantia: remove redundant checks on error status

On 11/05/17 19:16, David Miller wrote: > From: Colin King > Date: Thu, 11 May 2017 18:29:29 +0100 > >> From: Colin Ian King >> >> The error status err is initialized as zero and then being checked >> several times to see if it is less than

Re: [PATCH] ethernet: aquantia: remove redundant checks on error status

On 11/05/17 19:16, David Miller wrote: > From: Colin King > Date: Thu, 11 May 2017 18:29:29 +0100 > >> From: Colin Ian King >> >> The error status err is initialized as zero and then being checked >> several times to see if it is less than zero even when it has not >> been updated. Since these

Re: [PATCH v7 1/5] firmware: add extensible driver data params

On 5/2/2017 3:49 AM, Luis R. Rodriguez wrote: As the firmware API evolves we keep extending functions with more arguments. Stop this nonsense by proving an extensible data structure which can be used to represent both user parameters and private internal parameters. We introduce 3 data

Re: [PATCH v7 1/5] firmware: add extensible driver data params

On 5/2/2017 3:49 AM, Luis R. Rodriguez wrote: As the firmware API evolves we keep extending functions with more arguments. Stop this nonsense by proving an extensible data structure which can be used to represent both user parameters and private internal parameters. We introduce 3 data

Re: [PATCH] ethernet: aquantia: remove redundant checks on error status

From: Colin King Date: Thu, 11 May 2017 18:29:29 +0100 > From: Colin Ian King > > The error status err is initialized as zero and then being checked > several times to see if it is less than zero even when it has not > been updated. Since

Re: [PATCH v4 2/2] x86/refcount: Implement fast refcount overflow protection

On Wed, May 10, 2017 at 6:24 PM, PaX Team wrote: > On 9 May 2017 at 12:01, Kees Cook wrote: >> Various differences from PaX: >> - uses earlier value reset implementation in assembly >> - uses UD0 and refcount exception handler instead of new int vector >> - uses

Re: [PATCH] ethernet: aquantia: remove redundant checks on error status

From: Colin King Date: Thu, 11 May 2017 18:29:29 +0100 > From: Colin Ian King > > The error status err is initialized as zero and then being checked > several times to see if it is less than zero even when it has not > been updated. Since these checks are redundant we can remove these > as

Re: [PATCH v4 2/2] x86/refcount: Implement fast refcount overflow protection

On Wed, May 10, 2017 at 6:24 PM, PaX Team wrote: > On 9 May 2017 at 12:01, Kees Cook wrote: >> Various differences from PaX: >> - uses earlier value reset implementation in assembly >> - uses UD0 and refcount exception handler instead of new int vector >> - uses .text.unlikely instead of custom

Re: [PATCH v6 3/5] test: add new driver_data load tester

On Thu, May 11, 2017 at 07:46:27PM +0900, AKASHI Takahiro wrote: > On Fri, Apr 28, 2017 at 03:45:35AM +0200, Luis R. Rodriguez wrote: > > > > diff --git a/lib/test_driver_data.c b/lib/test_driver_data.c > > > > new file mode 100644 > > > > index ..11175a3b9f0a > > > > --- /dev/null > >

Re: [PATCH v6 3/5] test: add new driver_data load tester

On Thu, May 11, 2017 at 07:46:27PM +0900, AKASHI Takahiro wrote: > On Fri, Apr 28, 2017 at 03:45:35AM +0200, Luis R. Rodriguez wrote: > > > > diff --git a/lib/test_driver_data.c b/lib/test_driver_data.c > > > > new file mode 100644 > > > > index ..11175a3b9f0a > > > > --- /dev/null > >

Re: [PATCH 4.10 000/129] 4.10.16-stable review

On Thu, May 11, 2017 at 07:45:55PM +0200, Greg Kroah-Hartman wrote: > On Thu, May 11, 2017 at 09:59:55AM -0600, Shuah Khan wrote: > > On 05/11/2017 08:10 AM, Greg Kroah-Hartman wrote: > > > This is the start of the stable review cycle for the 4.10.16 release. > > > There are 129 patches in this

Re: [PATCH 4.10 000/129] 4.10.16-stable review

On Thu, May 11, 2017 at 07:45:55PM +0200, Greg Kroah-Hartman wrote: > On Thu, May 11, 2017 at 09:59:55AM -0600, Shuah Khan wrote: > > On 05/11/2017 08:10 AM, Greg Kroah-Hartman wrote: > > > This is the start of the stable review cycle for the 4.10.16 release. > > > There are 129 patches in this

[PULL] A few small documentation updates

The following changes since commit 4a1e31c68e9f40be32838944931178b0d9ed9162: Merge tag 'arc-4.12-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc (2017-05-09 10:10:15 -0700) are available in the git repository at: git://git.lwn.net/linux.git tags/docs-4.12-2 for you to

[PULL] A few small documentation updates

The following changes since commit 4a1e31c68e9f40be32838944931178b0d9ed9162: Merge tag 'arc-4.12-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc (2017-05-09 10:10:15 -0700) are available in the git repository at: git://git.lwn.net/linux.git tags/docs-4.12-2 for you to

Re: Kernel modules under new copyleft licence : (was Re: [PATCH v2] module.h: add copyleft-next >= 0.3.1 as GPL compatible)

Sorry this is an old topic now but a clarification was requested by AKASHI, so following up. On Tue, Aug 09, 2016 at 07:58:27PM -0700, Linus Torvalds wrote: > On Tue, Aug 9, 2016 at 1:14 PM, Luis R. Rodriguez wrote: > > > > I'm personally fine with MODULE_LICENSE("GPL") being

[PATCH] target: Re-add check to reject control WRITEs with overflow data

From: Nicholas Bellinger During v4.3 when the overflow/underflow check was relaxed by commit c72c525022: commit c72c5250224d475614a00c1d7e54a67f77cd3410 Author: Roland Dreier Date: Wed Jul 22 15:08:18 2015 -0700 target: allow

Re: Kernel modules under new copyleft licence : (was Re: [PATCH v2] module.h: add copyleft-next >= 0.3.1 as GPL compatible)

Sorry this is an old topic now but a clarification was requested by AKASHI, so following up. On Tue, Aug 09, 2016 at 07:58:27PM -0700, Linus Torvalds wrote: > On Tue, Aug 9, 2016 at 1:14 PM, Luis R. Rodriguez wrote: > > > > I'm personally fine with MODULE_LICENSE("GPL") being used with > >

[PATCH] target: Re-add check to reject control WRITEs with overflow data

From: Nicholas Bellinger During v4.3 when the overflow/underflow check was relaxed by commit c72c525022: commit c72c5250224d475614a00c1d7e54a67f77cd3410 Author: Roland Dreier Date: Wed Jul 22 15:08:18 2015 -0700 target: allow underflow/overflow for PR OUT etc. commands to

Re: [PATCHv2] arm64/cpufeature: don't use mutex in bringup path

On Thu, May 11, 2017 at 05:08:19PM +0100, Marc Zyngier wrote: > On 11/05/17 16:54, Suzuki K Poulose wrote: > > On 11/05/17 16:37, Mark Rutland wrote: > >> On Thu, May 11, 2017 at 04:15:38PM +0100, Suzuki K Poulose wrote: > >>> On 11/05/17 16:01, Mark Rutland wrote: > +static inline bool

Re: [PATCHv2] arm64/cpufeature: don't use mutex in bringup path

On Thu, May 11, 2017 at 05:08:19PM +0100, Marc Zyngier wrote: > On 11/05/17 16:54, Suzuki K Poulose wrote: > > On 11/05/17 16:37, Mark Rutland wrote: > >> On Thu, May 11, 2017 at 04:15:38PM +0100, Suzuki K Poulose wrote: > >>> On 11/05/17 16:01, Mark Rutland wrote: > +static inline bool

Re: pinctrl-sx150x.c broken in 4.11

* Nikita Yushchenko [170511 10:01]: > >>> Hmm maybe yeah. I don't quite follow the above the "pinctrl-0 property > >>> of sx150x device tree node, is misinterpreted as hog" part though. > >> > >> sx150x is i2c-gpio device. It has 16 GPIO lines that are

Re: pinctrl-sx150x.c broken in 4.11

* Nikita Yushchenko [170511 10:01]: > >>> Hmm maybe yeah. I don't quite follow the above the "pinctrl-0 property > >>> of sx150x device tree node, is misinterpreted as hog" part though. > >> > >> sx150x is i2c-gpio device. It has 16 GPIO lines that are communicated > >> with via i2c bus, and an

Re: [PATCH 1/4] vmbus: Improve a size determination in vmbus_device_create()

On Thu, May 11, 2017 at 09:30:56AM -0700, Stephen Hemminger wrote: > On Thu, 11 May 2017 18:15:46 +0200 > SF Markus Elfring wrote: > > > From: Markus Elfring > > Date: Thu, 11 May 2017 17:30:10 +0200 > > > > Replace the

Re: [PATCH 1/4] vmbus: Improve a size determination in vmbus_device_create()

On Thu, May 11, 2017 at 09:30:56AM -0700, Stephen Hemminger wrote: > On Thu, 11 May 2017 18:15:46 +0200 > SF Markus Elfring wrote: > > > From: Markus Elfring > > Date: Thu, 11 May 2017 17:30:10 +0200 > > > > Replace the specification of a data structure by a pointer dereference > > as the

Re: [PATCH 4.10 000/129] 4.10.16-stable review

On Thu, May 11, 2017 at 09:59:55AM -0600, Shuah Khan wrote: > On 05/11/2017 08:10 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.10.16 release. > > There are 129 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH 4.10 000/129] 4.10.16-stable review

On Thu, May 11, 2017 at 09:59:55AM -0600, Shuah Khan wrote: > On 05/11/2017 08:10 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.10.16 release. > > There are 129 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [RFC 01/10] x86/mm: Reimplement flush_tlb_page() using flush_tlb_mm_range()

On Sun, May 07, 2017 at 05:38:30AM -0700, Andy Lutomirski wrote: > flush_tlb_page() was very similar to flush_tlb_mm_range() except that > it had a couple of issues: > > - It was missing an smp_mb() in the case where >current->active_mm != mm. (This is a longstanding bug reported by >

Re: [RFC 01/10] x86/mm: Reimplement flush_tlb_page() using flush_tlb_mm_range()

On Sun, May 07, 2017 at 05:38:30AM -0700, Andy Lutomirski wrote: > flush_tlb_page() was very similar to flush_tlb_mm_range() except that > it had a couple of issues: > > - It was missing an smp_mb() in the case where >current->active_mm != mm. (This is a longstanding bug reported by >

Re: [PATCH v9 7/9] coresight: add support for CPU debug module

On 09/05/17 03:50, Leo Yan wrote: Coresight includes debug module and usually the module connects with CPU debug logic. ARMv8 architecture reference manual (ARM DDI 0487A.k) has description for related info in "Part H: External Debug". Chapter H7 "The Sample-based Profiling Extension"

Re: [PATCH v9 7/9] coresight: add support for CPU debug module

On 09/05/17 03:50, Leo Yan wrote: Coresight includes debug module and usually the module connects with CPU debug logic. ARMv8 architecture reference manual (ARM DDI 0487A.k) has description for related info in "Part H: External Debug". Chapter H7 "The Sample-based Profiling Extension"

Re: Threads stuck in zap_pid_ns_processes()

Guenter Roeck writes: > Hi all, > > the test program attached below almost always results in one of the child > processes being stuck in zap_pid_ns_processes(). When this happens, I can > see from test logs that nr_hashed == 2 and init_pids==1, but there is only > a single

Re: Threads stuck in zap_pid_ns_processes()

Guenter Roeck writes: > Hi all, > > the test program attached below almost always results in one of the child > processes being stuck in zap_pid_ns_processes(). When this happens, I can > see from test logs that nr_hashed == 2 and init_pids==1, but there is only > a single thread left in the pid

Re: [RFC][PATCH] sched/deadline: Remove if statement before clearing throttle and yielded

On 05/11/2017 04:01 PM, Juri Lelli wrote: > Looks good to me. > > Peter, any particular reason why you wanted to first check the values? +1 -- Daniel

Re: [RFC][PATCH] sched/deadline: Remove if statement before clearing throttle and yielded

On 05/11/2017 04:01 PM, Juri Lelli wrote: > Looks good to me. > > Peter, any particular reason why you wanted to first check the values? +1 -- Daniel

[PATCH] ethernet: aquantia: remove redundant checks on error status

From: Colin Ian King The error status err is initialized as zero and then being checked several times to see if it is less than zero even when it has not been updated. Since these checks are redundant we can remove these as well as err and the error exit label err_exit.

[PATCH] ethernet: aquantia: remove redundant checks on error status

From: Colin Ian King The error status err is initialized as zero and then being checked several times to see if it is less than zero even when it has not been updated. Since these checks are redundant we can remove these as well as err and the error exit label err_exit. Detected by

Re: [RFC][PATCH 00/14] VFS: Introduce superblock configuration context [ver #2]

Hi David, On 05/11/2017 09:59 AM, David Howells wrote: > > Here are a set of patches to create a superblock configuration context > prior to setting up a new mount, populating it with the parsed > options/binary data, creating the superblock and then effecting the mount. > > This allows

Re: [RFC][PATCH 00/14] VFS: Introduce superblock configuration context [ver #2]

Hi David, On 05/11/2017 09:59 AM, David Howells wrote: > > Here are a set of patches to create a superblock configuration context > prior to setting up a new mount, populating it with the parsed > options/binary data, creating the superblock and then effecting the mount. > > This allows

Re: [PATCH 1/2] kbuild: cleanup signing keys with mrproper

On Wed, 3 May 2017 13:37:08 +0900 Masahiro Yamada wrote: > +CC David Woodhouse > +CC David Howells > > > 2017-04-15 6:54 GMT+09:00 Stephen Hemminger : > > When 'make mrproper' is run it was supposed to remove the signing > > keys in

Re: [PATCH 1/2] kbuild: cleanup signing keys with mrproper

On Wed, 3 May 2017 13:37:08 +0900 Masahiro Yamada wrote: > +CC David Woodhouse > +CC David Howells > > > 2017-04-15 6:54 GMT+09:00 Stephen Hemminger : > > When 'make mrproper' is run it was supposed to remove the signing > > keys in the certs directory, but only the filename is given > >

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