Re: "isert: isert_setup_id: rdma_bind_addr() failed: -19" spam, followed by Recursive Fault on reboot

On Sun, 29 Jan 2017 09:39:39 +0200 Sagi Grimberg wrote: Hello, thank you very much for your help. I'm very sorry but I think I've made too many changes to my system to recreate the problem. I tried recreating my targtetcli config and downgrading linux+userspace+firmware to the

Re: "isert: isert_setup_id: rdma_bind_addr() failed: -19" spam, followed by Recursive Fault on reboot

On Sun, 29 Jan 2017 09:39:39 +0200 Sagi Grimberg wrote: Hello, thank you very much for your help. I'm very sorry but I think I've made too many changes to my system to recreate the problem. I tried recreating my targtetcli config and downgrading linux+userspace+firmware to the versions I used

Re: [PATCH v3 06/24] ARM: dts: imx6-sabrelite: add OV5642 and OV5640 camera sensors

On Fri, Jan 06, 2017 at 06:11:24PM -0800, Steve Longerbeam wrote: > + ov5640: camera@40 { > + compatible = "ovti,ov5640"; > + pinctrl-names = "default"; > + pinctrl-0 = <_ov5640>; > + clocks = <_xclk>; > + clock-names = "xclk"; > +

Re: [PATCH v3 06/24] ARM: dts: imx6-sabrelite: add OV5642 and OV5640 camera sensors

On Fri, Jan 06, 2017 at 06:11:24PM -0800, Steve Longerbeam wrote: > + ov5640: camera@40 { > + compatible = "ovti,ov5640"; > + pinctrl-names = "default"; > + pinctrl-0 = <_ov5640>; > + clocks = <_xclk>; > + clock-names = "xclk"; > +

Re: [PATCH v2] clk: add more managed APIs

On Mon, Jan 30, 2017 at 09:42:28PM +, Russell King - ARM Linux wrote: > On Mon, Jan 30, 2017 at 11:22:14AM -0800, Guenter Roeck wrote: > > Maybe the additional calls make sense; I can imagine they would. > > However, I personally would be a bit wary of changing the initialization > > order of

Re: [PATCH v2] clk: add more managed APIs

On Mon, Jan 30, 2017 at 09:42:28PM +, Russell King - ARM Linux wrote: > On Mon, Jan 30, 2017 at 11:22:14AM -0800, Guenter Roeck wrote: > > Maybe the additional calls make sense; I can imagine they would. > > However, I personally would be a bit wary of changing the initialization > > order of

Re: [PATCH 1/2] device property: export code duplicating array of property entries

On 1/23/2017 11:46 PM, Dmitry Torokhov wrote: On Mon, Jan 23, 2017 at 05:00:38PM +0200, Andy Shevchenko wrote: On Sun, 2017-01-22 at 23:38 -0800, Dmitry Torokhov wrote: When augmenting ACPI-enumerated devices with additional property data based on DMI info, a module has often several potential

Re: [PATCH 1/2] device property: export code duplicating array of property entries

On 1/23/2017 11:46 PM, Dmitry Torokhov wrote: On Mon, Jan 23, 2017 at 05:00:38PM +0200, Andy Shevchenko wrote: On Sun, 2017-01-22 at 23:38 -0800, Dmitry Torokhov wrote: When augmenting ACPI-enumerated devices with additional property data based on DMI info, a module has often several potential

Re: [Linux v4.10.0-rc1+] Still call-traces after suspend-resume (pm? i915? cpu/hotplug?)

On 1/24/2017 2:33 AM, Sedat Dilek wrote: On Fri, Dec 30, 2016 at 3:02 PM, Rafael J. Wysocki wrote: On Fri, Dec 30, 2016 at 12:40 PM, Sedat Dilek wrote: Hi, I have already reported this issue in [1]. One of the issue was solved. Unfortunately, it

Re: [Linux v4.10.0-rc1+] Still call-traces after suspend-resume (pm? i915? cpu/hotplug?)

On 1/24/2017 2:33 AM, Sedat Dilek wrote: On Fri, Dec 30, 2016 at 3:02 PM, Rafael J. Wysocki wrote: On Fri, Dec 30, 2016 at 12:40 PM, Sedat Dilek wrote: Hi, I have already reported this issue in [1]. One of the issue was solved. Unfortunately, it looks like there is still a different problem

Re: [PATCH net-next v3 06/10] net: dsa: Migrate to device_find_class()

On 01/25/2017 01:25 PM, Greg KH wrote: > On Tue, Jan 24, 2017 at 10:59:15AM -0800, Florian Fainelli wrote: >> On 01/19/2017 10:12 AM, Florian Fainelli wrote: >>> >>> Back to the actual code that triggered this discussion, the whole >>> purpose is just a safeguard. Given a device reference, we can

Re: [PATCH net-next v3 06/10] net: dsa: Migrate to device_find_class()

On 01/25/2017 01:25 PM, Greg KH wrote: > On Tue, Jan 24, 2017 at 10:59:15AM -0800, Florian Fainelli wrote: >> On 01/19/2017 10:12 AM, Florian Fainelli wrote: >>> >>> Back to the actual code that triggered this discussion, the whole >>> purpose is just a safeguard. Given a device reference, we can

Re: [PATCH] printk: fix printk.devkmsg sysctl

On Mon, Jan 30, 2017 at 06:03:18PM +0100, Borislav Petkov wrote: > IOW, I'd like the user to know what she does and mean it. No sloppy > inputs. Ok, here's what I wanna do. I decided to do my own parsing on the write path since proc_dostring() does not really allow me to look at the input string.

Re: [PATCH] printk: fix printk.devkmsg sysctl

On Mon, Jan 30, 2017 at 06:03:18PM +0100, Borislav Petkov wrote: > IOW, I'd like the user to know what she does and mean it. No sloppy > inputs. Ok, here's what I wanna do. I decided to do my own parsing on the write path since proc_dostring() does not really allow me to look at the input string.

Re: [PATCH v3 21/24] media: imx: Add MIPI CSI-2 Receiver subdev driver

On Fri, Jan 06, 2017 at 06:11:39PM -0800, Steve Longerbeam wrote: > Adds MIPI CSI-2 Receiver subdev driver. This subdev is required > for sensors with a MIPI CSI2 interface. > > Signed-off-by: Steve Longerbeam Applying: media: imx: Add MIPI CSI-2 Receiver subdev

Re: [PATCH v3 21/24] media: imx: Add MIPI CSI-2 Receiver subdev driver

On Fri, Jan 06, 2017 at 06:11:39PM -0800, Steve Longerbeam wrote: > Adds MIPI CSI-2 Receiver subdev driver. This subdev is required > for sensors with a MIPI CSI2 interface. > > Signed-off-by: Steve Longerbeam Applying: media: imx: Add MIPI CSI-2 Receiver subdev driver

[GIT] Sparc

Several small bug fixes and tidies, along with a fix for non-resumable memory errors triggered by userspace. Please pull, thanks a lot! The following changes since commit ba6d973f78eb62ffebb32f6ef3334fc9a3b33d22: Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2016-12-20

[GIT] Sparc

Several small bug fixes and tidies, along with a fix for non-resumable memory errors triggered by userspace. Please pull, thanks a lot! The following changes since commit ba6d973f78eb62ffebb32f6ef3334fc9a3b33d22: Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2016-12-20

[PATCH v13 1/2] serial: exar: split out the exar code from 8250_pci

From: Sudip Mukherjee Add the serial driver for the Exar chips. And also register the platform device for the GPIO provided by the Exar chips. Reviewed-by: Andy Shevchenko Signed-off-by: Sudip Mukherjee

[PATCH v13 1/2] serial: exar: split out the exar code from 8250_pci

From: Sudip Mukherjee Add the serial driver for the Exar chips. And also register the platform device for the GPIO provided by the Exar chips. Reviewed-by: Andy Shevchenko Signed-off-by: Sudip Mukherjee --- Andy, I have added the if (!board) check, but I am not sure how board can be NULL

Re: [STLinux Kernel] [PATCH 3/8] serial: st-asc: Read in all Pinctrl states

Hi Lee, On Mon, 30 Jan 2017, Lee Jones wrote: > On Mon, 30 Jan 2017, Peter Griffin wrote: > > On Mon, 30 Jan 2017, Lee Jones wrote: > > > On Mon, 30 Jan 2017, Peter Griffin wrote: > > > > On Fri, 27 Jan 2017, Lee Jones wrote: > > > > > On Wed, 25 Jan 2017, Peter Griffin wrote: > > > > > > On

Re: [STLinux Kernel] [PATCH 3/8] serial: st-asc: Read in all Pinctrl states

Hi Lee, On Mon, 30 Jan 2017, Lee Jones wrote: > On Mon, 30 Jan 2017, Peter Griffin wrote: > > On Mon, 30 Jan 2017, Lee Jones wrote: > > > On Mon, 30 Jan 2017, Peter Griffin wrote: > > > > On Fri, 27 Jan 2017, Lee Jones wrote: > > > > > On Wed, 25 Jan 2017, Peter Griffin wrote: > > > > > > On

Re: [PATCH v3 19/24] media: imx: Add IC subdev drivers

On Fri, Jan 06, 2017 at 06:11:37PM -0800, Steve Longerbeam wrote: > This is a set of three media entity subdevice drivers for the i.MX > Image Converter. The i.MX IC module contains three independent > "tasks": > > - Pre-processing Encode task: video frames are routed directly from > the CSI

Re: [PATCH v3 19/24] media: imx: Add IC subdev drivers

On Fri, Jan 06, 2017 at 06:11:37PM -0800, Steve Longerbeam wrote: > This is a set of three media entity subdevice drivers for the i.MX > Image Converter. The i.MX IC module contains three independent > "tasks": > > - Pre-processing Encode task: video frames are routed directly from > the CSI

[PATCH v13 2/2] serial: 8250_pci: remove exar code

From: Sudip Mukherjee Remove the Exar specific codes from 8250_pci and blacklist those chips so that the new Exar serial driver binds to the devices. Reviewed-by: Andy Shevchenko Signed-off-by: Sudip Mukherjee

[PATCH v13 2/2] serial: 8250_pci: remove exar code

From: Sudip Mukherjee Remove the Exar specific codes from 8250_pci and blacklist those chips so that the new Exar serial driver binds to the devices. Reviewed-by: Andy Shevchenko Signed-off-by: Sudip Mukherjee --- drivers/tty/serial/8250/8250_pci.c | 336 +

Re: [PATCH] sparc32: mm: srmmu: add __ro_after_init to sparc32_cachetlb_ops structures

From: Bhumika Goyal Date: Sat, 14 Jan 2017 18:01:54 +0530 > The objects viking_ops, viking_sun4d_smp_ops and smp_cachetlb_ops of > type sparc32_cachetlb_ops are not modified anywhere after getting modified > in the init functions. Inside init their reference is also stored

Re: [PATCH] sparc32: mm: srmmu: add __ro_after_init to sparc32_cachetlb_ops structures

From: Bhumika Goyal Date: Sat, 14 Jan 2017 18:01:54 +0530 > The objects viking_ops, viking_sun4d_smp_ops and smp_cachetlb_ops of > type sparc32_cachetlb_ops are not modified anywhere after getting modified > in the init functions. Inside init their reference is also stored in a > pointer of

Re: [PATCH v3 17/24] media: imx: Add CSI subdev driver

On Fri, Jan 06, 2017 at 06:11:35PM -0800, Steve Longerbeam wrote: > This is a media entity subdevice for the i.MX Camera > Serial Interface module. > > Signed-off-by: Steve Longerbeam warning: 3 lines add whitespace errors. Applying: media: imx: Add CSI subdev

Re: [PATCH v3 17/24] media: imx: Add CSI subdev driver

On Fri, Jan 06, 2017 at 06:11:35PM -0800, Steve Longerbeam wrote: > This is a media entity subdevice for the i.MX Camera > Serial Interface module. > > Signed-off-by: Steve Longerbeam warning: 3 lines add whitespace errors. Applying: media: imx: Add CSI subdev driver .git/rebase-apply/patch:38:

Re: [PATCH v3 16/24] media: Add i.MX media core driver

On Fri, Jan 06, 2017 at 06:11:34PM -0800, Steve Longerbeam wrote: > Add the core media driver for i.MX SOC. > > Signed-off-by: Steve Longerbeam Applying: media: Add i.MX media core driver .git/rebase-apply/patch:516: new blank line at EOF. +

Re: [PATCH v3 16/24] media: Add i.MX media core driver

On Fri, Jan 06, 2017 at 06:11:34PM -0800, Steve Longerbeam wrote: > Add the core media driver for i.MX SOC. > > Signed-off-by: Steve Longerbeam Applying: media: Add i.MX media core driver .git/rebase-apply/patch:516: new blank line at EOF. + .git/rebase-apply/patch:528: new blank line at EOF. +

Re: [PATCH v3 06/24] ARM: dts: imx6-sabrelite: add OV5642 and OV5640 camera sensors

On Fri, Jan 06, 2017 at 06:11:24PM -0800, Steve Longerbeam wrote: > diff --git a/arch/arm/boot/dts/imx6q-sabrelite.dts > b/arch/arm/boot/dts/imx6q-sabrelite.dts > index 66d10d8..9e2d26d 100644 > --- a/arch/arm/boot/dts/imx6q-sabrelite.dts > +++ b/arch/arm/boot/dts/imx6q-sabrelite.dts > @@ -52,3

Re: [PATCH v3 06/24] ARM: dts: imx6-sabrelite: add OV5642 and OV5640 camera sensors

On Fri, Jan 06, 2017 at 06:11:24PM -0800, Steve Longerbeam wrote: > diff --git a/arch/arm/boot/dts/imx6q-sabrelite.dts > b/arch/arm/boot/dts/imx6q-sabrelite.dts > index 66d10d8..9e2d26d 100644 > --- a/arch/arm/boot/dts/imx6q-sabrelite.dts > +++ b/arch/arm/boot/dts/imx6q-sabrelite.dts > @@ -52,3

Re: [PATCH v2] clk: add more managed APIs

On Mon, Jan 30, 2017 at 01:58:05PM -0800, Dmitry Torokhov wrote: > FWIW I do not think that kitchen sink calls, like > "devm_clk_get_prepare_set_rate_enable" are helpful. Resource > acquisition and use of said resource are logically separate. That alone is an argument against

Re: [PATCH v2] clk: add more managed APIs

On Mon, Jan 30, 2017 at 01:58:05PM -0800, Dmitry Torokhov wrote: > FWIW I do not think that kitchen sink calls, like > "devm_clk_get_prepare_set_rate_enable" are helpful. Resource > acquisition and use of said resource are logically separate. That alone is an argument against

Re: [RFC v1 00/14] Bus1 Kernel Message Bus

Hi! I'm a bit late to the party... > Example: > Imagine a receiver with a limit of 1024 handles. A sender transmits a > message to that receiver. It gets access to half the limit not used by > anyone else, hence 512 handles. It does not matter how many senders > there are, nor how many messages

Re: [RFC v1 00/14] Bus1 Kernel Message Bus

Hi! I'm a bit late to the party... > Example: > Imagine a receiver with a limit of 1024 handles. A sender transmits a > message to that receiver. It gets access to half the limit not used by > anyone else, hence 512 handles. It does not matter how many senders > there are, nor how many messages

Re: [PATCH] phy: qcom-ufs: Fix misplaced jump label

On Friday 27 January 2017 01:40 PM, Vivek Gautam wrote: > We want to skip only tx/rx_iface clocks and not ref_clk_src > as well. Fix the jump label accordingly. > > Fixes: 300f96771d78 ("phy: qcom-ufs: Skip obtaining rx/tx_iface_clk for > msm8996 based phy") merged, thanks. -Kishon > > Cc:

Re: [PATCH] phy: qcom-ufs: Fix misplaced jump label

On Friday 27 January 2017 01:40 PM, Vivek Gautam wrote: > We want to skip only tx/rx_iface clocks and not ref_clk_src > as well. Fix the jump label accordingly. > > Fixes: 300f96771d78 ("phy: qcom-ufs: Skip obtaining rx/tx_iface_clk for > msm8996 based phy") merged, thanks. -Kishon > > Cc:

Re: [PATCH v2 2/3] iommu/ipmmu-vmsa: Increase maximum micro-TLBS to 48

Hi Joerg, On Fri, Jan 27, 2017 at 8:47 PM, Joerg Roedel wrote: > On Mon, Jan 23, 2017 at 08:40:29PM +0900, Magnus Damm wrote: >> From: Magnus Damm >> >> Bump up the maximum numbers of micro-TLBS to 48. >> >> Each IPMMU device instance get micro-TLB

Re: [PATCH v2 2/3] iommu/ipmmu-vmsa: Increase maximum micro-TLBS to 48

Hi Joerg, On Fri, Jan 27, 2017 at 8:47 PM, Joerg Roedel wrote: > On Mon, Jan 23, 2017 at 08:40:29PM +0900, Magnus Damm wrote: >> From: Magnus Damm >> >> Bump up the maximum numbers of micro-TLBS to 48. >> >> Each IPMMU device instance get micro-TLB assignment via >> the "iommus" property in DT.

Re: [PATCH v2] drm: remove unnecessary fault wrappers

On Mon, Jan 30, 2017 at 03:09:39PM -0700, Ross Zwisler wrote: > This patch applies cleanly to mmots/master, which is currently at > v4.10-rc5-mmots-2017-01-26-15-49. Which may not be what you want... The reason I was looking at this code was because it was recently changed by Dave Jiang to

Re: [PATCH v2] drm: remove unnecessary fault wrappers

On Mon, Jan 30, 2017 at 03:09:39PM -0700, Ross Zwisler wrote: > This patch applies cleanly to mmots/master, which is currently at > v4.10-rc5-mmots-2017-01-26-15-49. Which may not be what you want... The reason I was looking at this code was because it was recently changed by Dave Jiang to

Re: [tpmdd-devel] [PATCH v2 1/2] tpm2: add session handle context saving and restoring to the space code

On Mon, 2017-01-30 at 23:45 +0200, Jarkko Sakkinen wrote: > On Sun, Jan 29, 2017 at 02:36:58PM -0800, James Bottomley wrote: [...] > > > 2. Can it really return both TPM_RC_HANDLE and > > > TPM_RC_REFERENCE_H0? > > > > Yes, it seems that a session that doesn't exist (because it's been > >

Re: [tpmdd-devel] [PATCH v2 1/2] tpm2: add session handle context saving and restoring to the space code

On Mon, 2017-01-30 at 23:45 +0200, Jarkko Sakkinen wrote: > On Sun, Jan 29, 2017 at 02:36:58PM -0800, James Bottomley wrote: [...] > > > 2. Can it really return both TPM_RC_HANDLE and > > > TPM_RC_REFERENCE_H0? > > > > Yes, it seems that a session that doesn't exist (because it's been > >

Re: [PATCH v5 4/4] sparc64: Add support for ADI (Application Data Integrity)

From: Khalid Aziz Date: Wed, 25 Jan 2017 12:57:16 -0700 > +static inline void enable_adi(void) > +{ ... > + __asm__ __volatile__( > + "rdpr %%pstate, %%g1\n\t" > + "or %%g1, %0, %%g1\n\t" > + "wrpr %%g1, %%g0, %%pstate\n\t" > +

Re: [PATCH v5 4/4] sparc64: Add support for ADI (Application Data Integrity)

From: Khalid Aziz Date: Wed, 25 Jan 2017 12:57:16 -0700 > +static inline void enable_adi(void) > +{ ... > + __asm__ __volatile__( > + "rdpr %%pstate, %%g1\n\t" > + "or %%g1, %0, %%g1\n\t" > + "wrpr %%g1, %%g0, %%pstate\n\t" > + ".word

Re: [tpmdd-devel] [RFC] tpm2-space: add handling for global session exhaustion

On Mon, 2017-01-30 at 23:58 +0200, Jarkko Sakkinen wrote: > On Mon, Jan 30, 2017 at 08:04:55AM -0800, James Bottomley wrote: > > On Sun, 2017-01-29 at 19:52 -0500, Ken Goldman wrote: > > > On 1/27/2017 5:04 PM, James Bottomley wrote: > > > > > > > > Beware the nasty corner case: > > > > > > > >

Re: [tpmdd-devel] [RFC] tpm2-space: add handling for global session exhaustion

On Mon, 2017-01-30 at 23:58 +0200, Jarkko Sakkinen wrote: > On Mon, Jan 30, 2017 at 08:04:55AM -0800, James Bottomley wrote: > > On Sun, 2017-01-29 at 19:52 -0500, Ken Goldman wrote: > > > On 1/27/2017 5:04 PM, James Bottomley wrote: > > > > > > > > Beware the nasty corner case: > > > > > > > >

[PATCH v2] drm: remove unnecessary fault wrappers

The fault wrappers drm_vm_fault(), drm_vm_shm_fault(), drm_vm_dma_fault() and drm_vm_sg_fault() used to provide extra logic beyond what was in the "drm_do_*" versions of these functions, but as of this commit: commit ca0b07d9a969 ("drm: convert drm from nopage to fault.") They are just

[PATCH v2] drm: remove unnecessary fault wrappers

The fault wrappers drm_vm_fault(), drm_vm_shm_fault(), drm_vm_dma_fault() and drm_vm_sg_fault() used to provide extra logic beyond what was in the "drm_do_*" versions of these functions, but as of this commit: commit ca0b07d9a969 ("drm: convert drm from nopage to fault.") They are just

Re: [PATCH v4 2/4] arm64: Work around Falkor erratum 1003

Hi Mark, On 01/30/2017 05:56 AM, Mark Rutland wrote: > Hi, > > On Fri, Jan 27, 2017 at 04:52:23PM -0500, Christopher Covington wrote: >> On 01/27/2017 09:38 AM, Mark Rutland wrote: >>> On Wed, Jan 25, 2017 at 10:52:30AM -0500, Christopher Covington wrote: > Replacing the above sequence

Re: [PATCH v4 2/4] arm64: Work around Falkor erratum 1003

Hi Mark, On 01/30/2017 05:56 AM, Mark Rutland wrote: > Hi, > > On Fri, Jan 27, 2017 at 04:52:23PM -0500, Christopher Covington wrote: >> On 01/27/2017 09:38 AM, Mark Rutland wrote: >>> On Wed, Jan 25, 2017 at 10:52:30AM -0500, Christopher Covington wrote: > Replacing the above sequence

Re: [PATCH cgroup/for-4.11] cgroup: misc cleanups

On Fri, Jan 20, 2017 at 12:06:08PM -0500, Tejun Heo wrote: > * cgrp_dfl_implicit_ss_mask is ulong instead of u16 unlike other > ss_masks. Make it a u16. > > * Move have_canfork_callback together with other callback ss_masks. > > Signed-off-by: Tejun Heo Applied to

Re: [PATCH cgroup/for-4.11] cgroup: misc cleanups

On Fri, Jan 20, 2017 at 12:06:08PM -0500, Tejun Heo wrote: > * cgrp_dfl_implicit_ss_mask is ulong instead of u16 unlike other > ss_masks. Make it a u16. > > * Move have_canfork_callback together with other callback ss_masks. > > Signed-off-by: Tejun Heo Applied to cgroup/for-4.11. Thanks.

Re: Issue with i2c-designware-platdrv's suspend/runtime-suspend handling

On Tue, Jan 24, 2017 at 2:03 PM, John Stultz wrote: > I noticed that with my hikey board, on resume from suspend I'm getting > the following WARNING: > > [ 54.334054] [ cut here ] > [ 54.334077] WARNING: CPU: 0 PID: 2217 at drivers/clk/clk.c:594

Re: Cherryview wake up events

On Mon, Jan 30, 2017 at 10:57 PM, Johannes Stezenbach wrote: > On Fri, Jan 27, 2017 at 02:30:58PM +0100, Johannes Stezenbach wrote: >> On Fri, Jan 27, 2017 at 03:21:22PM +0200, Andy Shevchenko wrote: >> > On Fri, Jan 27, 2017 at 1:38 PM, Johannes Stezenbach >> >

Re: Issue with i2c-designware-platdrv's suspend/runtime-suspend handling

On Tue, Jan 24, 2017 at 2:03 PM, John Stultz wrote: > I noticed that with my hikey board, on resume from suspend I'm getting > the following WARNING: > > [ 54.334054] [ cut here ] > [ 54.334077] WARNING: CPU: 0 PID: 2217 at drivers/clk/clk.c:594 >

Re: Cherryview wake up events

On Mon, Jan 30, 2017 at 10:57 PM, Johannes Stezenbach wrote: > On Fri, Jan 27, 2017 at 02:30:58PM +0100, Johannes Stezenbach wrote: >> On Fri, Jan 27, 2017 at 03:21:22PM +0200, Andy Shevchenko wrote: >> > On Fri, Jan 27, 2017 at 1:38 PM, Johannes Stezenbach >> > wrote: >> > > On Fri, Jan 27,

[PATCH v2] net: aquantia: atlantic: use new api ethtool_{get|set}_link_ksettings

The ethtool api {get|set}_settings is deprecated. We move this driver to new api {get|set}_link_ksettings. As I don't have the hardware, I'd be very pleased if someone may test this patch. Signed-off-by: Philippe Reynes --- Changelog: v2: - add support and advertise for TP

[PATCH v2] net: aquantia: atlantic: use new api ethtool_{get|set}_link_ksettings

The ethtool api {get|set}_settings is deprecated. We move this driver to new api {get|set}_link_ksettings. As I don't have the hardware, I'd be very pleased if someone may test this patch. Signed-off-by: Philippe Reynes --- Changelog: v2: - add support and advertise for TP

Re: [PATCH v4] mm: add arch-independent testcases for RODATA

On Sun, Jan 29, 2017 at 2:54 AM, Jinbum Park wrote: > This patch makes arch-independent testcases for RODATA. > Both x86 and x86_64 already have testcases for RODATA, > But they are arch-specific because using inline assembly directly. > > and cacheflush.h is not suitable

Re: [PATCH v4] mm: add arch-independent testcases for RODATA

On Sun, Jan 29, 2017 at 2:54 AM, Jinbum Park wrote: > This patch makes arch-independent testcases for RODATA. > Both x86 and x86_64 already have testcases for RODATA, > But they are arch-specific because using inline assembly directly. > > and cacheflush.h is not suitable location for rodata-test

Re: [PATCH v6 5/5] arm: mvebu: Add device tree for db-dxbc2 and db-xc3-24g4xg boards

Hi Gregory, On 31/01/17 03:29, Gregory CLEMENT wrote: > Hi Chris, > > On lun., janv. 30 2017, Chris Packham > wrote: > >> These boards are Marvell's evaluation boards for the 98DX4251 and >> 98DX3336 SoCs. >> >> Signed-off-by: Chris Packham

Re: [PATCH v6 5/5] arm: mvebu: Add device tree for db-dxbc2 and db-xc3-24g4xg boards

Hi Gregory, On 31/01/17 03:29, Gregory CLEMENT wrote: > Hi Chris, > > On lun., janv. 30 2017, Chris Packham > wrote: > >> These boards are Marvell's evaluation boards for the 98DX4251 and >> 98DX3336 SoCs. >> >> Signed-off-by: Chris Packham > > Applied on mvebu/dt > I just noticed that I

Re: Q: lockdep_assert_held_read() after downgrade_write()

On 01/30/2017 02:25 PM, J. R. Okajima wrote: > Peter Zijlstra, > > May I ask you a question? > v4.10-rc1 got a commit > f831948 2016-11-30 locking/lockdep: Provide a type check for > lock_is_held > I've tested a little and lockdep splat a stack trace. > > { > DECLARE_RWSEM(rw); >

Re: Q: lockdep_assert_held_read() after downgrade_write()

On 01/30/2017 02:25 PM, J. R. Okajima wrote: > Peter Zijlstra, > > May I ask you a question? > v4.10-rc1 got a commit > f831948 2016-11-30 locking/lockdep: Provide a type check for > lock_is_held > I've tested a little and lockdep splat a stack trace. > > { > DECLARE_RWSEM(rw); >

Re: [RFC PATCH] scsi, block: fix duplicate bdi name registration crashes

On Mon, Jan 30, 2017 at 4:24 AM, Christoph Hellwig wrote: > Hi Dan, > > this looks mostly fine to me. A few code comments below, but except > for this there is another issue with it: We still have drivers > that share a single request_queue for multiple gendisks, so I wonder scsi

Re: [PATCH net-next v7 0/3] Add support for the ethernet switch on the ESPRESSObin

From: Gregory CLEMENT Date: Mon, 30 Jan 2017 20:29:32 +0100 > This set of patches adds support for the Marvell Ethernet Topaz switch > family (88E6141/88E6341) which is found on the ESPRESSObin. With this > series the network is usable on this board. > > As

Re: [RFC PATCH] scsi, block: fix duplicate bdi name registration crashes

On Mon, Jan 30, 2017 at 4:24 AM, Christoph Hellwig wrote: > Hi Dan, > > this looks mostly fine to me. A few code comments below, but except > for this there is another issue with it: We still have drivers > that share a single request_queue for multiple gendisks, so I wonder scsi drivers or

Re: [PATCH net-next v7 0/3] Add support for the ethernet switch on the ESPRESSObin

From: Gregory CLEMENT Date: Mon, 30 Jan 2017 20:29:32 +0100 > This set of patches adds support for the Marvell Ethernet Topaz switch > family (88E6141/88E6341) which is found on the ESPRESSObin. With this > series the network is usable on this board. > > As usual, I rebased the series on the

Re: [tpmdd-devel] [RFC] tpm2-space: add handling for global session exhaustion

On Mon, Jan 30, 2017 at 08:04:55AM -0800, James Bottomley wrote: > On Sun, 2017-01-29 at 19:52 -0500, Ken Goldman wrote: > > On 1/27/2017 5:04 PM, James Bottomley wrote: > > > > > > Beware the nasty corner case: > > > > > > > > - Application asks for a session and gets 0200 > > > > > > > >

Re: [PATCH v2] clk: add more managed APIs

On Mon, Jan 30, 2017 at 1:42 PM, Russell King - ARM Linux wrote: > On Mon, Jan 30, 2017 at 11:22:14AM -0800, Guenter Roeck wrote: >> Maybe the additional calls make sense; I can imagine they would. >> However, I personally would be a bit wary of changing the initialization

Re: [tpmdd-devel] [RFC] tpm2-space: add handling for global session exhaustion

On Mon, Jan 30, 2017 at 08:04:55AM -0800, James Bottomley wrote: > On Sun, 2017-01-29 at 19:52 -0500, Ken Goldman wrote: > > On 1/27/2017 5:04 PM, James Bottomley wrote: > > > > > > Beware the nasty corner case: > > > > > > > > - Application asks for a session and gets 0200 > > > > > > > >

Re: [PATCH v2] clk: add more managed APIs

On Mon, Jan 30, 2017 at 1:42 PM, Russell King - ARM Linux wrote: > On Mon, Jan 30, 2017 at 11:22:14AM -0800, Guenter Roeck wrote: >> Maybe the additional calls make sense; I can imagine they would. >> However, I personally would be a bit wary of changing the initialization >> order of multi-clock

Re: [PATCH v3 16/24] drm/rockchip: dw-mipi-dsi: properly configure PHY timing

On Sun, Jan 29, 2017 at 01:24:36PM +, John Keeping wrote: > These values are specified as constant time periods but the PHY > configuration is in terms of the current lane byte clock so using > constant values guarantees that the timings will be outside the > specification with some display

Re: [PATCH v3 16/24] drm/rockchip: dw-mipi-dsi: properly configure PHY timing

On Sun, Jan 29, 2017 at 01:24:36PM +, John Keeping wrote: > These values are specified as constant time periods but the PHY > configuration is in terms of the current lane byte clock so using > constant values guarantees that the timings will be outside the > specification with some display

Re: [RFC 1/3] system-power: Add system power and restart framework

Hi! > +struct system_power_chip; > + > +struct system_power_ops { > + int (*restart)(struct system_power_chip *chip, enum reboot_mode mode, > +char *cmd); > + int (*power_off_prepare)(struct system_power_chip *chip); > + int (*power_off)(struct system_power_chip

Re: [RFC 1/3] system-power: Add system power and restart framework

Hi! > +struct system_power_chip; > + > +struct system_power_ops { > + int (*restart)(struct system_power_chip *chip, enum reboot_mode mode, > +char *cmd); > + int (*power_off_prepare)(struct system_power_chip *chip); > + int (*power_off)(struct system_power_chip

Re: [PATCH 0/6] ncr5380: Miscellaneous minor patches

On Sunday 29 January 2017 02:05:02 Finn Thain wrote: > On Sat, 28 Jan 2017, Ondrej Zary wrote: > > On Monday 16 January 2017 00:50:57 Finn Thain wrote: > > > This series removes some unused code and related comments, addresses > > > the warnings generated by 'make W=1' and 'make C=1' and fixes a >

Re: [PATCH 0/6] ncr5380: Miscellaneous minor patches

On Sunday 29 January 2017 02:05:02 Finn Thain wrote: > On Sat, 28 Jan 2017, Ondrej Zary wrote: > > On Monday 16 January 2017 00:50:57 Finn Thain wrote: > > > This series removes some unused code and related comments, addresses > > > the warnings generated by 'make W=1' and 'make C=1' and fixes a >

Re: Fwd: Re: [tpmdd-devel] [PATCH v9 2/2] tpm: add securityfs support,for TPM 2.0 firmware event log

On Mon, Jan 30, 2017 at 03:08:42PM +0530, Nayna wrote: > > > From: "Ken Goldman" > > > > Date: 26-Jan-2017 2:53 AM > > Subject: Re: [tpmdd-devel] [PATCH v9 2/2] tpm: add securityfs > > support,for TPM 2.0 firmware event log > > To:

Re: Fwd: Re: [tpmdd-devel] [PATCH v9 2/2] tpm: add securityfs support,for TPM 2.0 firmware event log

On Mon, Jan 30, 2017 at 03:08:42PM +0530, Nayna wrote: > > > From: "Ken Goldman" > > > > Date: 26-Jan-2017 2:53 AM > > Subject: Re: [tpmdd-devel] [PATCH v9 2/2] tpm: add securityfs > > support,for TPM 2.0 firmware event log > > To: >

Re: [PATCH] tpm: add buffer access validation in tpm2_get_pcr_allocation()

On Mon, Jan 30, 2017 at 08:28:30AM +0530, Nayna wrote: > > > On 01/30/2017 02:50 AM, Jarkko Sakkinen wrote: > > On Sun, Jan 29, 2017 at 10:48:39PM +0530, Nayna wrote: > > > > > > > > > On 01/29/2017 08:10 PM, Jarkko Sakkinen wrote: > > > > On Fri, Jan 27, 2017 at 10:25:49AM -0500, Nayna Jain

Re: [PATCH] tpm: add buffer access validation in tpm2_get_pcr_allocation()

On Mon, Jan 30, 2017 at 08:28:30AM +0530, Nayna wrote: > > > On 01/30/2017 02:50 AM, Jarkko Sakkinen wrote: > > On Sun, Jan 29, 2017 at 10:48:39PM +0530, Nayna wrote: > > > > > > > > > On 01/29/2017 08:10 PM, Jarkko Sakkinen wrote: > > > > On Fri, Jan 27, 2017 at 10:25:49AM -0500, Nayna Jain

Re: [PATCH v2 3/4] ARM: nommu: display vectors base

Hi, On Mon, Jan 30, 2017 at 02:03:26PM +, Russell King - ARM Linux wrote: > On Sun, Jan 22, 2017 at 08:52:12AM +0530, afzal mohammed wrote: > > The exception base address is now dynamically estimated for no-MMU, > > display it. As it is the case, now limit VECTORS_BASE usage to MMU > >

Re: [PATCH v2 3/4] ARM: nommu: display vectors base

Hi, On Mon, Jan 30, 2017 at 02:03:26PM +, Russell King - ARM Linux wrote: > On Sun, Jan 22, 2017 at 08:52:12AM +0530, afzal mohammed wrote: > > The exception base address is now dynamically estimated for no-MMU, > > display it. As it is the case, now limit VECTORS_BASE usage to MMU > >

Re: [tpmdd-devel] [PATCH v2 1/2] tpm2: add session handle context saving and restoring to the space code

On Sun, Jan 29, 2017 at 07:35:32PM -0500, Ken Goldman wrote: > On 1/27/2017 7:32 PM, James Bottomley wrote: > > > > Sessions are also isolated during each instance of a tpm space. This > > means that spaces shouldn't be able to see each other's sessions and > > is enforced by ensuring that a

Re: [tpmdd-devel] [PATCH v2 1/2] tpm2: add session handle context saving and restoring to the space code

On Sun, Jan 29, 2017 at 07:35:32PM -0500, Ken Goldman wrote: > On 1/27/2017 7:32 PM, James Bottomley wrote: > > > > Sessions are also isolated during each instance of a tpm space. This > > means that spaces shouldn't be able to see each other's sessions and > > is enforced by ensuring that a

Re: [tpmdd-devel] [PATCH v2 1/2] tpm2: add session handle context saving and restoring to the space code

On Sun, Jan 29, 2017 at 02:36:58PM -0800, James Bottomley wrote: > On Sun, 2017-01-29 at 23:39 +0200, Jarkko Sakkinen wrote: > > On Fri, Jan 27, 2017 at 04:32:38PM -0800, James Bottomley wrote: > > > sessions are different from transient objects in that their handles > > > may not be virtualized

Re: [tpmdd-devel] [PATCH v2 1/2] tpm2: add session handle context saving and restoring to the space code

On Sun, Jan 29, 2017 at 02:36:58PM -0800, James Bottomley wrote: > On Sun, 2017-01-29 at 23:39 +0200, Jarkko Sakkinen wrote: > > On Fri, Jan 27, 2017 at 04:32:38PM -0800, James Bottomley wrote: > > > sessions are different from transient objects in that their handles > > > may not be virtualized

Re: [PATCH v2] clk: add more managed APIs

On Mon, Jan 30, 2017 at 11:22:14AM -0800, Guenter Roeck wrote: > Maybe the additional calls make sense; I can imagine they would. > However, I personally would be a bit wary of changing the initialization > order of multi-clock initializations, and I am not sure how a single call > could address

Re: [PATCH v2] clk: add more managed APIs

On Mon, Jan 30, 2017 at 11:22:14AM -0800, Guenter Roeck wrote: > Maybe the additional calls make sense; I can imagine they would. > However, I personally would be a bit wary of changing the initialization > order of multi-clock initializations, and I am not sure how a single call > could address

Re: [tip:sched/core] sched/core: Add debugging code to catch missing update_rq_clock() calls

On Tue, 31 Jan, at 08:24:53AM, Michael Ellerman wrote: > > I'm hitting this on multiple powerpc systems: > > [ 38.339126] rq->clock_update_flags < RQCF_ACT_SKIP > [ 38.339134] [ cut here ] > [ 38.339142] WARNING: CPU: 2 PID: 1 at kernel/sched/sched.h:804 >

Re: [tip:sched/core] sched/core: Add debugging code to catch missing update_rq_clock() calls

On Tue, 31 Jan, at 08:24:53AM, Michael Ellerman wrote: > > I'm hitting this on multiple powerpc systems: > > [ 38.339126] rq->clock_update_flags < RQCF_ACT_SKIP > [ 38.339134] [ cut here ] > [ 38.339142] WARNING: CPU: 2 PID: 1 at kernel/sched/sched.h:804 >

Re: [PATCH 1/4] dt-bindings: Add binding for brcm,bcm2835-sdhost.

> Gerd Hoffmann hat am 27. Januar 2017 um 12:36 geschrieben: > > > From: Eric Anholt > > This is the other SD controller on the platform, which can be swapped > to the role of SD card host using pin muxing. AFAIK the SDHOST controller isn't able to handle

Re: [PATCH 1/4] dt-bindings: Add binding for brcm,bcm2835-sdhost.

> Gerd Hoffmann hat am 27. Januar 2017 um 12:36 geschrieben: > > > From: Eric Anholt > > This is the other SD controller on the platform, which can be swapped > to the role of SD card host using pin muxing. AFAIK the SDHOST controller isn't able to handle SDIO. Maybe we should mention this

Re: [PATCH 4/4] ARM: dts: bcm283x: switch from to

> Gerd Hoffmann hat am 27. Januar 2017 um 12:36 geschrieben: > > > This flips the switch from (iproc-driven) sdhci controller to the custom > sdhost controller. As long as the SDHOST driver isn't enabled in bcm2835_defconfig we shouldn't do that. Btw please write down the

Re: [PATCH 4/4] ARM: dts: bcm283x: switch from to

> Gerd Hoffmann hat am 27. Januar 2017 um 12:36 geschrieben: > > > This flips the switch from (iproc-driven) sdhci controller to the custom > sdhost controller. As long as the SDHOST driver isn't enabled in bcm2835_defconfig we shouldn't do that. Btw please write down the reason why this

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