Re: [PATCH] libnvdimm, nfit: treat volatile virtual CD region as read-only pmem

On Fri, Jun 3, 2016 at 12:13 AM, Lee, Chun-Yi wrote: > This patch adds codes to treat a volatile virtual CD region as a > read-only pmem region, then read-only /dev/pmem* device can be mounted > with iso9660. > > It's useful to work with the httpboot in EFI firmware to

Re: [PATCH] libnvdimm, nfit: treat volatile virtual CD region as read-only pmem

On Fri, Jun 3, 2016 at 12:13 AM, Lee, Chun-Yi wrote: > This patch adds codes to treat a volatile virtual CD region as a > read-only pmem region, then read-only /dev/pmem* device can be mounted > with iso9660. > > It's useful to work with the httpboot in EFI firmware to pull a remote > ISO file to

Re: [v2, 1/2] Documentation: bindings: add DT documentation for Rockchip USB2PHY

On Thu, Jun 02, 2016 at 02:48:09PM +0800, Frank Wang wrote: > Signed-off-by: Frank Wang > --- > > Changes in v2: > - Changed vbus_host optional property from gpio to regulator. > - Specified vbus_otg-supply optional property. > - Specified otg_id and otg_bvalid

Re: [v2, 1/2] Documentation: bindings: add DT documentation for Rockchip USB2PHY

On Thu, Jun 02, 2016 at 02:48:09PM +0800, Frank Wang wrote: > Signed-off-by: Frank Wang > --- > > Changes in v2: > - Changed vbus_host optional property from gpio to regulator. > - Specified vbus_otg-supply optional property. > - Specified otg_id and otg_bvalid property. > >

Re: [PATCH] Documentation: Fix some grammar mistakes in sync_file.txt

On Sat, 14 May 2016 02:28:36 -0400 Javier Martinez Canillas wrote: > There are two sentences in the Sync File documentation where the > english is a little off. This patch is an attempt to fix these. Applied to the docs tree, thanks. jon

Re: [PATCH] Documentation: Fix some grammar mistakes in sync_file.txt

On Sat, 14 May 2016 02:28:36 -0400 Javier Martinez Canillas wrote: > There are two sentences in the Sync File documentation where the > english is a little off. This patch is an attempt to fix these. Applied to the docs tree, thanks. jon

Re: [PATCH] net: ethernet: ti: cpsw: remove rx_descs property

On 06/03/2016 09:25 PM, Ivan Khoronzhuk wrote: > > > On 03.06.16 19:50, Grygorii Strashko wrote: >> On 06/03/2016 01:43 AM, Ivan Khoronzhuk wrote: >>> There is no reason to hold s/w dependent parameter in device tree. >>> Even more, there is no reason in this parameter because davinici_cpdma >>>

Re: [PATCH] net: ethernet: ti: cpsw: remove rx_descs property

On 06/03/2016 09:25 PM, Ivan Khoronzhuk wrote: > > > On 03.06.16 19:50, Grygorii Strashko wrote: >> On 06/03/2016 01:43 AM, Ivan Khoronzhuk wrote: >>> There is no reason to hold s/w dependent parameter in device tree. >>> Even more, there is no reason in this parameter because davinici_cpdma >>>

Re: [PATCH -v4 5/7] locking, arch: Update spin_unlock_wait()

On Fri, Jun 03, 2016 at 06:35:37PM +0100, Will Deacon wrote: > On Fri, Jun 03, 2016 at 03:42:49PM +0200, Peter Zijlstra wrote: > > On Fri, Jun 03, 2016 at 01:47:34PM +0100, Will Deacon wrote: > > > Even on x86, I think you need a fence here: > > > > > > X86 lock > > > { > > > } > > > P0

Re: [PATCH -v4 5/7] locking, arch: Update spin_unlock_wait()

On Fri, Jun 03, 2016 at 06:35:37PM +0100, Will Deacon wrote: > On Fri, Jun 03, 2016 at 03:42:49PM +0200, Peter Zijlstra wrote: > > On Fri, Jun 03, 2016 at 01:47:34PM +0100, Will Deacon wrote: > > > Even on x86, I think you need a fence here: > > > > > > X86 lock > > > { > > > } > > > P0

Re: [PATCH 01/20] drm/atomic: Fix remaining places where !funcs->best_encoder is valid

On Fri, Jun 03, 2016 at 09:37:43AM +0200, Boris Brezillon wrote: > On Thu, 2 Jun 2016 23:57:02 +0200 > Daniel Vetter wrote: > > > On Thu, Jun 2, 2016 at 11:05 PM, Laurent Pinchart > > wrote: > > > Hi Boris, > > > > > > Thank you for the patch.

Re: [PATCH 01/20] drm/atomic: Fix remaining places where !funcs->best_encoder is valid

On Fri, Jun 03, 2016 at 09:37:43AM +0200, Boris Brezillon wrote: > On Thu, 2 Jun 2016 23:57:02 +0200 > Daniel Vetter wrote: > > > On Thu, Jun 2, 2016 at 11:05 PM, Laurent Pinchart > > wrote: > > > Hi Boris, > > > > > > Thank you for the patch. > > > > > > On Thursday 02 Jun 2016 16:31:28 Boris

Re: [PATCH v8 0/9] ARM: dts: DRA7: Add dt nodes for PWMSS

Gentle ping on this series On 05/03/2016 10:56 AM, Franklin S Cooper Jr wrote: This patch series adds support for PWM for DRA7. The IP is the same as the one present in AM33XX and AM437XX. However, before doing so remove unnecessary hwmod entries for eCAP, ePWM and eQEP. The following are the

Re: [PATCH v8 0/9] ARM: dts: DRA7: Add dt nodes for PWMSS

Gentle ping on this series On 05/03/2016 10:56 AM, Franklin S Cooper Jr wrote: This patch series adds support for PWM for DRA7. The IP is the same as the one present in AM33XX and AM437XX. However, before doing so remove unnecessary hwmod entries for eCAP, ePWM and eQEP. The following are the

Re: [PATCH 3/7] Input: synaptics-rmi4: Add dribble and palm gesture parameters to devicetree

On Fri, Jun 03, 2016 at 11:40:28AM -0700, Andrew Duggan wrote: > Signed-off-by: Andrew Duggan > --- > .../devicetree/bindings/input/rmi4/rmi_2d_sensor.txt | 5 + > drivers/input/rmi4/rmi_2d_sensor.c | 14 > ++ > 2 files

Re: [PATCH 3/7] Input: synaptics-rmi4: Add dribble and palm gesture parameters to devicetree

On Fri, Jun 03, 2016 at 11:40:28AM -0700, Andrew Duggan wrote: > Signed-off-by: Andrew Duggan > --- > .../devicetree/bindings/input/rmi4/rmi_2d_sensor.txt | 5 + > drivers/input/rmi4/rmi_2d_sensor.c | 14 > ++ > 2 files changed, 19 insertions(+) >

[PATCH] iio: generic_buffer: Fix --trigger-num option

Initialize trig_num to -1 and handle trig_num=0 as a valid id. Fixes: 7c7e9dad (iio: iio_generic_buffer: Add --trigger-num option) Signed-off-by: Crestez Dan Leonard --- tools/iio/iio_generic_buffer.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff

[PATCH] iio: generic_buffer: Fix --trigger-num option

Initialize trig_num to -1 and handle trig_num=0 as a valid id. Fixes: 7c7e9dad (iio: iio_generic_buffer: Add --trigger-num option) Signed-off-by: Crestez Dan Leonard --- tools/iio/iio_generic_buffer.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

Re: [PATCH 0/5] ARM:Keystone: Add pinmuxing support

Franklin, On 6/3/2016 11:42 AM, Franklin Cooper Jr. wrote: Gentle ping on this series On 04/27/2016 09:11 AM, Franklin S Cooper Jr wrote: Unlike most Keystone 2 devices, K2G supports pinmuxing of its pins. This patch series enables pinmuxing for Keystone 2 devices. Franklin S Cooper Jr (1):

Re: [PATCH 0/5] ARM:Keystone: Add pinmuxing support

Franklin, On 6/3/2016 11:42 AM, Franklin Cooper Jr. wrote: Gentle ping on this series On 04/27/2016 09:11 AM, Franklin S Cooper Jr wrote: Unlike most Keystone 2 devices, K2G supports pinmuxing of its pins. This patch series enables pinmuxing for Keystone 2 devices. Franklin S Cooper Jr (1):

Re: [PATCH v4 0/3] iio: generic_buffer: Select device/trigger by number

On 05/30/2016 06:19 PM, Crestez Dan Leonard wrote: > This patch series adds support for selecting iio devices/triggers by numeric > id > rather than just name. This is useful because the names are not actually > guaranteed to be unique. > > Changes since v3: > * Rebase on top of latest

Re: [PATCH v4 0/3] iio: generic_buffer: Select device/trigger by number

On 05/30/2016 06:19 PM, Crestez Dan Leonard wrote: > This patch series adds support for selecting iio devices/triggers by numeric > id > rather than just name. This is useful because the names are not actually > guaranteed to be unique. > > Changes since v3: > * Rebase on top of latest

Re: [kernel-hardening] [PATCH 2/2] arm: apply more __ro_after_init

On Fri, Jun 03, 2016 at 11:40:24AM -0700, Kees Cook wrote: > Guided by grsecurity's analogous __read_only markings in arch/arm, > this applies several uses of __ro_after_init to structures that are > only updated during __init. > > Signed-off-by: Kees Cook > --- >

Re: [kernel-hardening] [PATCH 2/2] arm: apply more __ro_after_init

On Fri, Jun 03, 2016 at 11:40:24AM -0700, Kees Cook wrote: > Guided by grsecurity's analogous __read_only markings in arch/arm, > this applies several uses of __ro_after_init to structures that are > only updated during __init. > > Signed-off-by: Kees Cook > --- > arch/arm/kernel/cpuidle.c | 2

Re: [RFC][PATCH 0/7] locking/rwsem: Convert rwsem count to atomic_long_t

On Fri, Jun 03, 2016 at 11:09:54AM -0700, Jason Low wrote: > arch/alpha/include/asm/rwsem.h | 26 +- > arch/ia64/include/asm/rwsem.h | 20 ++-- So I was looking at rm arch/*/include/asm/rwsem.h :-) Because at the end of the day you're reimplementing

Re: [RFC][PATCH 0/7] locking/rwsem: Convert rwsem count to atomic_long_t

On Fri, Jun 03, 2016 at 11:09:54AM -0700, Jason Low wrote: > arch/alpha/include/asm/rwsem.h | 26 +- > arch/ia64/include/asm/rwsem.h | 20 ++-- So I was looking at rm arch/*/include/asm/rwsem.h :-) Because at the end of the day you're reimplementing

Adding module support for __ro_after_init

Hi Rusty, I'd love to get your thoughts on the best way to support __ro_after_init markings for modules. Are the r/o markings done after module __init runs? If so, this should make things easy, and then we just need to move .data..ro_after_init into .rodata at link time. If not, then we'd need to

Adding module support for __ro_after_init

Hi Rusty, I'd love to get your thoughts on the best way to support __ro_after_init markings for modules. Are the r/o markings done after module __init runs? If so, this should make things easy, and then we just need to move .data..ro_after_init into .rodata at link time. If not, then we'd need to

[PATCH 5/7] Input: synaptics-rmi4: Remove pointer to rmi_function in f12_data

The pointer to struct rmi_function in f12_data is never set and was never used. The fn pointer is also stored in rmi_2d_sensor which is a member of f12_data. Signed-off-by: Andrew Duggan --- drivers/input/rmi4/rmi_f12.c | 1 - 1 file changed, 1 deletion(-) diff --git

[PATCH 5/7] Input: synaptics-rmi4: Remove pointer to rmi_function in f12_data

The pointer to struct rmi_function in f12_data is never set and was never used. The fn pointer is also stored in rmi_2d_sensor which is a member of f12_data. Signed-off-by: Andrew Duggan --- drivers/input/rmi4/rmi_f12.c | 1 - 1 file changed, 1 deletion(-) diff --git

[PATCH 3/7] Input: synaptics-rmi4: Add dribble and palm gesture parameters to devicetree

Signed-off-by: Andrew Duggan --- .../devicetree/bindings/input/rmi4/rmi_2d_sensor.txt | 5 + drivers/input/rmi4/rmi_2d_sensor.c | 14 ++ 2 files changed, 19 insertions(+) diff --git

[PATCH 3/7] Input: synaptics-rmi4: Add dribble and palm gesture parameters to devicetree

Signed-off-by: Andrew Duggan --- .../devicetree/bindings/input/rmi4/rmi_2d_sensor.txt | 5 + drivers/input/rmi4/rmi_2d_sensor.c | 14 ++ 2 files changed, 19 insertions(+) diff --git a/Documentation/devicetree/bindings/input/rmi4/rmi_2d_sensor.txt

[PATCH 7/7] Input: synaptics-rmi4: Handle incomplete input data

Commit 5b65c2a02966 ("HID: rmi: check sanity of the incoming report") added support for handling incomplete HID reports do to the input data being corrupted in transit. This patch reimplements this functionality in the function drivers so they can handle getting less valid data then they expect.

[PATCH 7/7] Input: synaptics-rmi4: Handle incomplete input data

Commit 5b65c2a02966 ("HID: rmi: check sanity of the incoming report") added support for handling incomplete HID reports do to the input data being corrupted in transit. This patch reimplements this functionality in the function drivers so they can handle getting less valid data then they expect.

[PATCH v2] HID: rmi: Make hid-rmi a transport driver for synaptics-rmi4

The Synaptics RMI4 driver provides support for RMI4 devices. Instead of duplicating the RMI4 processing code, make hid-rmi a transport driver and register it with the Synaptics RMI4 core. Signed-off-by: Andrew Duggan --- Here is the updated version of the hid-rmi patch.

[PATCH 6/7] Input: synaptics-rmi4: Remove unneeded variable

Remove the data_base_addr_offset variable in rmi_f11_attention(). The f11 data is read as a single block so there is no need to store an offset to the data address. Signed-off-by: Andrew Duggan --- drivers/input/rmi4/rmi_f11.c | 5 + 1 file changed, 1 insertion(+), 4

[PATCH 2/7] Input: synaptics-rmi4: Add parameters for dribble packets and palm detect gesture

The rmi_f11 driver currently disables dribble packets and the palm detect gesture for all devices. This patch creates a parameter in the 2d sensor platform data for controlling this functionality on a per device basis. For more information on dribble packets: Commit 05ba999fcabb ("HID: rmi:

[PATCH v2] HID: rmi: Make hid-rmi a transport driver for synaptics-rmi4

The Synaptics RMI4 driver provides support for RMI4 devices. Instead of duplicating the RMI4 processing code, make hid-rmi a transport driver and register it with the Synaptics RMI4 core. Signed-off-by: Andrew Duggan --- Here is the updated version of the hid-rmi patch. This patch along with the

[PATCH 6/7] Input: synaptics-rmi4: Remove unneeded variable

Remove the data_base_addr_offset variable in rmi_f11_attention(). The f11 data is read as a single block so there is no need to store an offset to the data address. Signed-off-by: Andrew Duggan --- drivers/input/rmi4/rmi_f11.c | 5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff

[PATCH 2/7] Input: synaptics-rmi4: Add parameters for dribble packets and palm detect gesture

The rmi_f11 driver currently disables dribble packets and the palm detect gesture for all devices. This patch creates a parameter in the 2d sensor platform data for controlling this functionality on a per device basis. For more information on dribble packets: Commit 05ba999fcabb ("HID: rmi:

[PATCH 4/7] Input: synaptics-rmi4: Add support for controlling dribble packets in F12

Implements reading and setting the dribble bit in F12's control registers. Signed-off-by: Andrew Duggan --- drivers/input/rmi4/rmi_f12.c | 74 +++- 1 file changed, 73 insertions(+), 1 deletion(-) diff --git

[PATCH 4/7] Input: synaptics-rmi4: Add support for controlling dribble packets in F12

Implements reading and setting the dribble bit in F12's control registers. Signed-off-by: Andrew Duggan --- drivers/input/rmi4/rmi_f12.c | 74 +++- 1 file changed, 73 insertions(+), 1 deletion(-) diff --git a/drivers/input/rmi4/rmi_f12.c

Re: [PATCH 0/5] ARM:Keystone: Add pinmuxing support

Gentle ping on this series On 04/27/2016 09:11 AM, Franklin S Cooper Jr wrote: Unlike most Keystone 2 devices, K2G supports pinmuxing of its pins. This patch series enables pinmuxing for Keystone 2 devices. Franklin S Cooper Jr (1): ARM: keystone: defconfig: Enable PINCTRL SINGLE for

Re: [PATCH 0/5] ARM:Keystone: Add pinmuxing support

Gentle ping on this series On 04/27/2016 09:11 AM, Franklin S Cooper Jr wrote: Unlike most Keystone 2 devices, K2G supports pinmuxing of its pins. This patch series enables pinmuxing for Keystone 2 devices. Franklin S Cooper Jr (1): ARM: keystone: defconfig: Enable PINCTRL SINGLE for

Re: [PATCH RFC v7 0/5] skb_array: array based FIFO for skbs

I applied this V7 to my github tree: https://github.com/netoptimizer/prototype-kernel/commits/master And adjusted my benchmark and unit-tests of this skb_array API. Added an unit test of re-sizing to small queue size.

Re: [PATCH RFC v7 0/5] skb_array: array based FIFO for skbs

I applied this V7 to my github tree: https://github.com/netoptimizer/prototype-kernel/commits/master And adjusted my benchmark and unit-tests of this skb_array API. Added an unit test of re-sizing to small queue size.

[PATCH 1/2] x86: apply more __ro_after_init and const

Guided by grsecurity's analogous __read_only markings in arch/x86, this applies several uses of __ro_after_init to structures that are only updated during __init, and const for some structures that are never updated. Additionally extends __init markings to some functions that are only used during

[PATCH 1/2] x86: apply more __ro_after_init and const

Guided by grsecurity's analogous __read_only markings in arch/x86, this applies several uses of __ro_after_init to structures that are only updated during __init, and const for some structures that are never updated. Additionally extends __init markings to some functions that are only used during

[PATCH 2/2] arm: apply more __ro_after_init

Guided by grsecurity's analogous __read_only markings in arch/arm, this applies several uses of __ro_after_init to structures that are only updated during __init. Signed-off-by: Kees Cook --- arch/arm/kernel/cpuidle.c | 2 +- arch/arm/kernel/setup.c | 10 +-

[PATCH 0/2] expand use of __ro_after_init

After v4.6 released, a number of people complained that Linux's use of __ro_after_init was extremely limited, but they did not send patches. In the interest of showing how to make progress in this area, this is a set of two patches for x86 and arm, extracted from the grsecurity/PaX patchset in

[PATCH 0/2] expand use of __ro_after_init

After v4.6 released, a number of people complained that Linux's use of __ro_after_init was extremely limited, but they did not send patches. In the interest of showing how to make progress in this area, this is a set of two patches for x86 and arm, extracted from the grsecurity/PaX patchset in

[PATCH 2/2] arm: apply more __ro_after_init

Guided by grsecurity's analogous __read_only markings in arch/arm, this applies several uses of __ro_after_init to structures that are only updated during __init. Signed-off-by: Kees Cook --- arch/arm/kernel/cpuidle.c | 2 +- arch/arm/kernel/setup.c | 10 +- arch/arm/kernel/smp.c

Re: [RFC PATCHv2] usb: USB Type-C Connector Class

On Fri, Jun 03, 2016 at 06:17:46PM +0300, Heikki Krogerus wrote: [ ... ] > > > > > > > > In my test case, this gives me > > > > /sys/class/type-c/usbc0/ > > > > usbc0.svid:18d1 > > > > usbc0.svid:18d1/mode0 > > > > usbc0.svid:18d1/mode0/vdo > > > >

Re: [RFC PATCHv2] usb: USB Type-C Connector Class

On Fri, Jun 03, 2016 at 06:17:46PM +0300, Heikki Krogerus wrote: [ ... ] > > > > > > > > In my test case, this gives me > > > > /sys/class/type-c/usbc0/ > > > > usbc0.svid:18d1 > > > > usbc0.svid:18d1/mode0 > > > > usbc0.svid:18d1/mode0/vdo > > > >

[PATCH 0/7] Input: synaptics-rmi4: Reimplement functionality from hid-rmi

The majority of this patch is reimplementing some of the functionality which was initially implemented in hid-rmi and reimplements it in the core. When hid-rmi is converted into a transport for rmi_core the functionality of existing touchpads should not change. Several of these patches address

[PATCH 1/7] Input: synaptics-rmi4: Increment the refcount of the transport dev's of_node

Increment the refcount for the transport device's of_node before calling of_find_node_by_name(). Since of_find_node_by_name() assumes the refcount was incremented by the caller and calls of_node_put() when it is done. Signed-off-by: Andrew Duggan ---

[PATCH 0/7] Input: synaptics-rmi4: Reimplement functionality from hid-rmi

The majority of this patch is reimplementing some of the functionality which was initially implemented in hid-rmi and reimplements it in the core. When hid-rmi is converted into a transport for rmi_core the functionality of existing touchpads should not change. Several of these patches address

[PATCH 1/7] Input: synaptics-rmi4: Increment the refcount of the transport dev's of_node

Increment the refcount for the transport device's of_node before calling of_find_node_by_name(). Since of_find_node_by_name() assumes the refcount was incremented by the caller and calls of_node_put() when it is done. Signed-off-by: Andrew Duggan --- drivers/input/rmi4/rmi_bus.c | 5 +++-- 1

Re: Dcache oops

On Jun 3, 2016, at 2:22 PM, Al Viro wrote: > On Fri, Jun 03, 2016 at 12:38:40PM -0400, Oleg Drokin wrote: >> I am dropping NFS people since it seems to be converting into a generic >> VFS/dcache bug even though you need NFS or the like to trigger it - the >> lookup_open path. > > NFS bug is

Re: Dcache oops

On Jun 3, 2016, at 2:22 PM, Al Viro wrote: > On Fri, Jun 03, 2016 at 12:38:40PM -0400, Oleg Drokin wrote: >> I am dropping NFS people since it seems to be converting into a generic >> VFS/dcache bug even though you need NFS or the like to trigger it - the >> lookup_open path. > > NFS bug is

[PATCH] iio: inv_mpu6050: Fix use-after-free in ACPI code

In some cases this can result in incorrectly returning a negative value from asus_acpi_get_sensor_info and the AK8963 magnetometer failing to show up. Cc: Srinivas Pandruvada Signed-off-by: Crestez Dan Leonard ---

[PATCH] iio: inv_mpu6050: Fix use-after-free in ACPI code

In some cases this can result in incorrectly returning a negative value from asus_acpi_get_sensor_info and the AK8963 magnetometer failing to show up. Cc: Srinivas Pandruvada Signed-off-by: Crestez Dan Leonard --- drivers/iio/imu/inv_mpu6050/inv_mpu_acpi.c | 5 +++-- 1 file changed, 3

Re: [PATCH] hwmon: (fam15h_power) Disable preemption when reading registers

On Fri, Jun 03, 2016 at 11:18:36AM -0700, Guenter Roeck wrote: > I like this version. Applied, though it would be nice to get a > Tested-by: or Acked-by: from someone at AMD. I'll hold back until > early next week before sending it to Linus. If it makes you feel any better: I have the affected

Re: [PATCH] hwmon: (fam15h_power) Disable preemption when reading registers

On Fri, Jun 03, 2016 at 11:18:36AM -0700, Guenter Roeck wrote: > I like this version. Applied, though it would be nice to get a > Tested-by: or Acked-by: from someone at AMD. I'll hold back until > early next week before sending it to Linus. If it makes you feel any better: I have the affected

Re: [PATCH] net: ethernet: ti: cpsw: remove rx_descs property

On 03.06.16 19:50, Grygorii Strashko wrote: On 06/03/2016 01:43 AM, Ivan Khoronzhuk wrote: There is no reason to hold s/w dependent parameter in device tree. Even more, there is no reason in this parameter because davinici_cpdma driver splits pool of descriptors equally between tx and rx

Re: [PATCH] net: ethernet: ti: cpsw: remove rx_descs property

On 03.06.16 19:50, Grygorii Strashko wrote: On 06/03/2016 01:43 AM, Ivan Khoronzhuk wrote: There is no reason to hold s/w dependent parameter in device tree. Even more, there is no reason in this parameter because davinici_cpdma driver splits pool of descriptors equally between tx and rx

Re: Dcache oops

On Fri, Jun 03, 2016 at 12:38:40PM -0400, Oleg Drokin wrote: > I am dropping NFS people since it seems to be converting into a generic > VFS/dcache bug even though you need NFS or the like to trigger it - the > lookup_open path. NFS bug is real; there might very well be something else, but that

Re: Dcache oops

On Fri, Jun 03, 2016 at 12:38:40PM -0400, Oleg Drokin wrote: > I am dropping NFS people since it seems to be converting into a generic > VFS/dcache bug even though you need NFS or the like to trigger it - the > lookup_open path. NFS bug is real; there might very well be something else, but that

Re: [RFC][PATCH 0/7] locking/rwsem: Convert rwsem count to atomic_long_t

On Fri, 2016-06-03 at 10:04 +0200, Ingo Molnar wrote: > * Peter Zijlstra wrote: > > > On Mon, May 16, 2016 at 06:12:25PM -0700, Linus Torvalds wrote: > > > On Mon, May 16, 2016 at 5:37 PM, Jason Low wrote: > > > > > > > > This rest of the series

Re: [RFC][PATCH 0/7] locking/rwsem: Convert rwsem count to atomic_long_t

On Fri, 2016-06-03 at 10:04 +0200, Ingo Molnar wrote: > * Peter Zijlstra wrote: > > > On Mon, May 16, 2016 at 06:12:25PM -0700, Linus Torvalds wrote: > > > On Mon, May 16, 2016 at 5:37 PM, Jason Low wrote: > > > > > > > > This rest of the series converts the rwsem count variable to an > > > >

Re: [PATCH] hwmon: (fam15h_power) Disable preemption when reading registers

On Thu, Jun 02, 2016 at 10:14:39AM +0200, Borislav Petkov wrote: > On Thu, Jun 02, 2016 at 09:58:30AM +0200, Borislav Petkov wrote: > > Ha, very nice! Let me try it. > > Yap, much better than opencoding on_each_cpu_mask() :-) > > --- > From: Borislav Petkov > Date: Wed, 1 Jun 2016

Re: [PATCH] hwmon: (fam15h_power) Disable preemption when reading registers

On Thu, Jun 02, 2016 at 10:14:39AM +0200, Borislav Petkov wrote: > On Thu, Jun 02, 2016 at 09:58:30AM +0200, Borislav Petkov wrote: > > Ha, very nice! Let me try it. > > Yap, much better than opencoding on_each_cpu_mask() :-) > > --- > From: Borislav Petkov > Date: Wed, 1 Jun 2016 11:36:13

[PATCH] msr tracing: Fix copy paste

From: "Dr. David Alan Gilbert" The msr tracing for writes is incorrectly conditional on the read trace. Fixes: 7f47d8cc Signed-off-by: Dr. David Alan Gilbert --- arch/x86/include/asm/msr.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)

[PATCH] msr tracing: Fix copy paste

From: "Dr. David Alan Gilbert" The msr tracing for writes is incorrectly conditional on the read trace. Fixes: 7f47d8cc Signed-off-by: Dr. David Alan Gilbert --- arch/x86/include/asm/msr.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/x86/include/asm/msr.h

Re: [PATCH 4/5] ARM: dts: Arria10 ECC Manager IRQ controller changes

On Wed, 25 May 2016, ttha...@opensource.altera.com wrote: > From: Thor Thayer > > Changes to support IRQ controller implementation including adding > new property irq-controller to eccmgr and adding IRQ property > to children. > > Signed-off-by: Thor Thayer

Re: [PATCH 4/5] ARM: dts: Arria10 ECC Manager IRQ controller changes

On Wed, 25 May 2016, ttha...@opensource.altera.com wrote: > From: Thor Thayer > > Changes to support IRQ controller implementation including adding > new property irq-controller to eccmgr and adding IRQ property > to children. > > Signed-off-by: Thor Thayer > --- >

Re: [PATCH RFC v7 1/5] ptr_ring: array based FIFO for pointers

On Thu, 2 Jun 2016 19:08:18 +0300 "Michael S. Tsirkin" wrote: > A simple array based FIFO of pointers. Intended for net stack which > commonly has a single consumer/producer. > > Signed-off-by: Michael S. Tsirkin > --- > include/linux/ptr_ring.h | 264 >

Re: [PATCH RFC v7 1/5] ptr_ring: array based FIFO for pointers

On Thu, 2 Jun 2016 19:08:18 +0300 "Michael S. Tsirkin" wrote: > A simple array based FIFO of pointers. Intended for net stack which > commonly has a single consumer/producer. > > Signed-off-by: Michael S. Tsirkin > --- > include/linux/ptr_ring.h | 264 >

[PATCH v2] iio: stx104: Add GPIO support for the Apex Embedded Systems STX104

The Apex Embedded Systems STX104 device features eight lines of digital I/O (four digital inputs and four digital outputs). This patch adds GPIO support for these eight lines of digital I/O via GPIOLIB. Signed-off-by: William Breathitt Gray --- Changes in v2: - Change

[PATCH v2] iio: stx104: Add GPIO support for the Apex Embedded Systems STX104

The Apex Embedded Systems STX104 device features eight lines of digital I/O (four digital inputs and four digital outputs). This patch adds GPIO support for these eight lines of digital I/O via GPIOLIB. Signed-off-by: William Breathitt Gray --- Changes in v2: - Change GPIOLIB Kconfig selection

Re: [RFC 05/13] x86/mm: Add barriers and document switch_mm-vs-flush synchronization

Following this patch, if (current->active_mm != mm), flush_tlb_page() still doesn’t call smp_mb() before checking mm_cpumask(mm). In contrast, flush_tlb_mm_range() does call smp_mb(). Is there a reason for this discrepancy? Thanks, Nadav Andy Lutomirski wrote: > When

Re: [RFC 05/13] x86/mm: Add barriers and document switch_mm-vs-flush synchronization

Following this patch, if (current->active_mm != mm), flush_tlb_page() still doesn’t call smp_mb() before checking mm_cpumask(mm). In contrast, flush_tlb_mm_range() does call smp_mb(). Is there a reason for this discrepancy? Thanks, Nadav Andy Lutomirski wrote: > When switch_mm activates a

Re: [PATCH v2 1/3] Add the latent_entropy gcc plugin

On Wed, 1 Jun 2016 12:42:27 -0700 Andrew Morton wrote: > On Tue, 31 May 2016 01:31:45 +0200 Emese Revfy wrote: > > > This plugin mitigates the problem of the kernel having too little entropy > > during > > and after boot for generating crypto

Re: [PATCH v2 1/3] Add the latent_entropy gcc plugin

On Wed, 1 Jun 2016 12:42:27 -0700 Andrew Morton wrote: > On Tue, 31 May 2016 01:31:45 +0200 Emese Revfy wrote: > > > This plugin mitigates the problem of the kernel having too little entropy > > during > > and after boot for generating crypto keys. > > > > It creates a local variable in

Re: [PATCH] f2fs: fix to redirty page if fail to gc data page

On Fri, Jun 03, 2016 at 01:59:15PM +0800, Chao Yu wrote: ... > >>> Do we have another expectation? > >> > >> ENOMEM or EIO? > > > > EIO will stop everything. > > ENOMEM would be better to wait for a while from page reclaim? > > Agree, but for ioctl path, IMO, we don't need to let user waiting

Re: [PATCH] f2fs: fix to redirty page if fail to gc data page

On Fri, Jun 03, 2016 at 01:59:15PM +0800, Chao Yu wrote: ... > >>> Do we have another expectation? > >> > >> ENOMEM or EIO? > > > > EIO will stop everything. > > ENOMEM would be better to wait for a while from page reclaim? > > Agree, but for ioctl path, IMO, we don't need to let user waiting

Re: [PATCH -v4 5/7] locking, arch: Update spin_unlock_wait()

On Fri, Jun 03, 2016 at 03:42:49PM +0200, Peter Zijlstra wrote: > On Fri, Jun 03, 2016 at 01:47:34PM +0100, Will Deacon wrote: > > Even on x86, I think you need a fence here: > > > > X86 lock > > { > > } > > P0| P1; > > MOV EAX,$1| MOV EAX,$1; > >

Re: [PATCH -v4 5/7] locking, arch: Update spin_unlock_wait()

On Fri, Jun 03, 2016 at 03:42:49PM +0200, Peter Zijlstra wrote: > On Fri, Jun 03, 2016 at 01:47:34PM +0100, Will Deacon wrote: > > Even on x86, I think you need a fence here: > > > > X86 lock > > { > > } > > P0| P1; > > MOV EAX,$1| MOV EAX,$1; > >

Re: [PATCH 2/2] aer: add support aer interrupt with none MSI/MSI-X/INTx mode

Po, Sorry to hijack your discussion, but the problem seems to be same for Keystone PCI controller which is also designware (old version) based. On 06/03/2016 12:09 AM, Bjorn Helgaas wrote: > On Thu, Jun 02, 2016 at 11:37:28AM -0400, Murali Karicheri wrote: >> On 06/02/2016 09:55 AM, Bjorn

Re: [PATCH 2/2] aer: add support aer interrupt with none MSI/MSI-X/INTx mode

Po, Sorry to hijack your discussion, but the problem seems to be same for Keystone PCI controller which is also designware (old version) based. On 06/03/2016 12:09 AM, Bjorn Helgaas wrote: > On Thu, Jun 02, 2016 at 11:37:28AM -0400, Murali Karicheri wrote: >> On 06/02/2016 09:55 AM, Bjorn

Re: [PATCH] drm: sun4i: fix LPAE warnings

On Fri, Jun 03, 2016 at 05:57:31PM +0100, Andre Przywara wrote: > When the sun4i DRM driver is compiled with LPAE enabled, dma_addr_t turns > into a 64-bit type, which causes warnings with some debug printks: > = > In file included from > drivers/gpu/drm/sun4i/sun4i_backend.c:13::

Re: [PATCH] drm: sun4i: fix LPAE warnings

On Fri, Jun 03, 2016 at 05:57:31PM +0100, Andre Przywara wrote: > When the sun4i DRM driver is compiled with LPAE enabled, dma_addr_t turns > into a 64-bit type, which causes warnings with some debug printks: > = > In file included from > drivers/gpu/drm/sun4i/sun4i_backend.c:13::

[PATCH] net: stmmac: dwmac-rk: keep PHY up for WoL

Do not shutdown the PHY if Wake-on-Lan is enabled, else it cannot wake us up. Signed-off-by: Vincent Palatin --- drivers/net/ethernet/stmicro/stmmac/dwmac-rk.c | 8 1 file changed, 8 insertions(+) diff --git a/drivers/net/ethernet/stmicro/stmmac/dwmac-rk.c

[PATCH] net: stmmac: dwmac-rk: keep PHY up for WoL

Do not shutdown the PHY if Wake-on-Lan is enabled, else it cannot wake us up. Signed-off-by: Vincent Palatin --- drivers/net/ethernet/stmicro/stmmac/dwmac-rk.c | 8 1 file changed, 8 insertions(+) diff --git a/drivers/net/ethernet/stmicro/stmmac/dwmac-rk.c

Re: [PATCH 5/8] x86, pkeys: allocation/free syscalls

On 06/02/2016 05:26 PM, Michael Kerrisk (man-pages) wrote: > On 06/01/2016 07:17 PM, Dave Hansen wrote: >> On 06/01/2016 05:11 PM, Michael Kerrisk (man-pages) wrote: >>> >>> If I read this right, it doesn't actually remove any pkey restrictions >>> that may have been applied while the

Re: [PATCH 5/8] x86, pkeys: allocation/free syscalls

On 06/02/2016 05:26 PM, Michael Kerrisk (man-pages) wrote: > On 06/01/2016 07:17 PM, Dave Hansen wrote: >> On 06/01/2016 05:11 PM, Michael Kerrisk (man-pages) wrote: >>> >>> If I read this right, it doesn't actually remove any pkey restrictions >>> that may have been applied while the

[PATCH 1/2] gpiolib: Fix NULL pointer deference

Under some circumstances, a gpiochip might be half cleaned from the gpio_device list. This patch makes sure that the chip pointer is still valid, before calling the match function. [ 104.088296] BUG: unable to handle kernel NULL pointer dereference at 0090 [ 104.089772] IP: []

[PATCH 1/2] gpiolib: Fix NULL pointer deference

Under some circumstances, a gpiochip might be half cleaned from the gpio_device list. This patch makes sure that the chip pointer is still valid, before calling the match function. [ 104.088296] BUG: unable to handle kernel NULL pointer dereference at 0090 [ 104.089772] IP: []

Re: Anyone have a clone of wireless-legacy.git?

On Fri, Jun 03, 2016 at 10:34:08AM -0400, John W. Linville wrote: > On Fri, Jun 03, 2016 at 09:06:23AM +0200, Johannes Berg wrote: > > > > > http://www.filewatcher.com/_/?q=wireless-legacy.git, maybe ? > > > > > > > Seems to work - both have the same branches: > > > >   adm8211 

Re: Anyone have a clone of wireless-legacy.git?

On Fri, Jun 03, 2016 at 10:34:08AM -0400, John W. Linville wrote: > On Fri, Jun 03, 2016 at 09:06:23AM +0200, Johannes Berg wrote: > > > > > http://www.filewatcher.com/_/?q=wireless-legacy.git, maybe ? > > > > > > > Seems to work - both have the same branches: > > > >   adm8211 

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