Re: [PATCH 6/6] wl1251: Set generated MAC address back to NVS data

Pali Rohár writes: > In case there is no valid MAC address kernel generates random one. This > patch propagate this generated MAC address back to NVS data which will be > uploaded to wl1251 chip. So HW would have same MAC address as linux kernel > uses. > > Signed-off-by:

Re: [PATCH 6/6] wl1251: Set generated MAC address back to NVS data

Pali Rohár writes: > In case there is no valid MAC address kernel generates random one. This > patch propagate this generated MAC address back to NVS data which will be > uploaded to wl1251 chip. So HW would have same MAC address as linux kernel > uses. > > Signed-off-by: Pali Rohár Why? What

Re: [GIT PULL] soc: samsung: Drivers for v4.11

On Thu, Jan 26, 2017 at 04:59:45PM +0100, Linus Walleij wrote: > On Fri, Jan 20, 2017 at 7:13 PM, Krzysztof Kozlowski wrote: > > > The following changes since commit 0c744ea4f77d72b3dcebb7a8f2684633ec79be88: > > > > Linux 4.10-rc2 (2017-01-01 14:31:53 -0800) > > > > are

Re: [GIT PULL] soc: samsung: Drivers for v4.11

On Thu, Jan 26, 2017 at 04:59:45PM +0100, Linus Walleij wrote: > On Fri, Jan 20, 2017 at 7:13 PM, Krzysztof Kozlowski wrote: > > > The following changes since commit 0c744ea4f77d72b3dcebb7a8f2684633ec79be88: > > > > Linux 4.10-rc2 (2017-01-01 14:31:53 -0800) > > > > are available in the git

Re: [PATCH 5/6] wl1251: Parse and use MAC address from supplied NVS data

Pali Rohár writes: > This patch implements parsing MAC address from NVS data which are sent to > wl1251 chip. Calibration NVS data could contain valid MAC address and it > will be used instead randomly generated. > > This patch also move code for requesting NVS data from

Re: [PATCH 5/6] wl1251: Parse and use MAC address from supplied NVS data

Pali Rohár writes: > This patch implements parsing MAC address from NVS data which are sent to > wl1251 chip. Calibration NVS data could contain valid MAC address and it > will be used instead randomly generated. > > This patch also move code for requesting NVS data from userspace to driver >

Re: [v3 PATCH 04/10] x86/insn-kernel: Add a function to obtain register offset in ModRM

On Wed, 25 Jan 2017 22:07:16 -0800 Ricardo Neri wrote: > Hi Masami, > > On Thu, 2017-01-26 at 11:11 +0900, Masami Hiramatsu wrote: > > On Wed, 25 Jan 2017 12:23:47 -0800 > > Ricardo Neri wrote: > > > > > The

Re: [Xen-devel] [PATCH v2] xen, input: try to read screen resolution for xen-kbdfront

On 01/27/2017 09:46 AM, Juergen Gross wrote: On 27/01/17 08:21, Oleksandr Andrushchenko wrote: On 01/27/2017 09:12 AM, Juergen Gross wrote: Instead of using the default resolution of 800*600 for the pointing device of xen-kbdfront try to read the resolution of the (virtual) framebuffer device.

Re: [v3 PATCH 04/10] x86/insn-kernel: Add a function to obtain register offset in ModRM

On Wed, 25 Jan 2017 22:07:16 -0800 Ricardo Neri wrote: > Hi Masami, > > On Thu, 2017-01-26 at 11:11 +0900, Masami Hiramatsu wrote: > > On Wed, 25 Jan 2017 12:23:47 -0800 > > Ricardo Neri wrote: > > > > > The function insn_get_reg_offset requires a type to indicate whether > > > the returned

Re: [Xen-devel] [PATCH v2] xen, input: try to read screen resolution for xen-kbdfront

On 01/27/2017 09:46 AM, Juergen Gross wrote: On 27/01/17 08:21, Oleksandr Andrushchenko wrote: On 01/27/2017 09:12 AM, Juergen Gross wrote: Instead of using the default resolution of 800*600 for the pointing device of xen-kbdfront try to read the resolution of the (virtual) framebuffer device.

Re: [PATCH 2/2] base/memory, hotplug: fix a kernel oops in show_valid_zones()

On Thu, Jan 26, 2017 at 10:26:23PM +, Kani, Toshimitsu wrote: > On Thu, 2017-01-26 at 13:52 -0800, Andrew Morton wrote: > > On Thu, 26 Jan 2017 14:44:15 -0700 Toshi Kani > > wrote: > > > > > Reading a sysfs memoryN/valid_zones file leads to the following > > > oops when

Re: [PATCH 2/2] base/memory, hotplug: fix a kernel oops in show_valid_zones()

On Thu, Jan 26, 2017 at 10:26:23PM +, Kani, Toshimitsu wrote: > On Thu, 2017-01-26 at 13:52 -0800, Andrew Morton wrote: > > On Thu, 26 Jan 2017 14:44:15 -0700 Toshi Kani > > wrote: > > > > > Reading a sysfs memoryN/valid_zones file leads to the following > > > oops when the first page of a

Re: [PATCH v4 3/3] p54: convert to sysdata API

On Thu, Jan 26, 2017 at 10:50:05PM +0100, Luis R. Rodriguez wrote: > On Thu, Jan 19, 2017 at 05:27:51PM +0100, Luis R. Rodriguez wrote: > > On Thu, Jan 19, 2017 at 12:38:57PM +0100, Greg KH wrote: > > > On Thu, Jan 12, 2017 at 07:02:44AM -0800, Luis R. Rodriguez wrote: > > > > --- > > > >

Re: [PATCH v4 3/3] p54: convert to sysdata API

On Thu, Jan 26, 2017 at 10:50:05PM +0100, Luis R. Rodriguez wrote: > On Thu, Jan 19, 2017 at 05:27:51PM +0100, Luis R. Rodriguez wrote: > > On Thu, Jan 19, 2017 at 12:38:57PM +0100, Greg KH wrote: > > > On Thu, Jan 12, 2017 at 07:02:44AM -0800, Luis R. Rodriguez wrote: > > > > --- > > > >

Re: [PATCH 2/6] wl1251: Use request_firmware_prefer_user() for loading NVS calibration data

Pali Rohár writes: > NVS calibration data for wl1251 are model specific. Every one device with > wl1251 chip has different and calibrated in factory. > > Not all wl1251 chips have own EEPROM where are calibration data stored. And > in that case there is no "standard" place.

Re: [PATCH 2/6] wl1251: Use request_firmware_prefer_user() for loading NVS calibration data

Pali Rohár writes: > NVS calibration data for wl1251 are model specific. Every one device with > wl1251 chip has different and calibrated in factory. > > Not all wl1251 chips have own EEPROM where are calibration data stored. And > in that case there is no "standard" place. Every device has

Re: [PATCH v2 0/4] USB support for Broadcom NSP SoC

Hi, On Thursday 26 January 2017 10:57 PM, Florian Fainelli wrote: > On 01/26/2017 07:34 AM, Kishon Vijay Abraham I wrote: >> >> >> On Tuesday 17 January 2017 09:44 PM, Yendapally Reddy Dhananjaya Reddy wrote: >>> This patch set contains the usb support for Broadcom NSP SoC. The >>> usb3 phy is

Re: [PATCH v2 0/4] USB support for Broadcom NSP SoC

Hi, On Thursday 26 January 2017 10:57 PM, Florian Fainelli wrote: > On 01/26/2017 07:34 AM, Kishon Vijay Abraham I wrote: >> >> >> On Tuesday 17 January 2017 09:44 PM, Yendapally Reddy Dhananjaya Reddy wrote: >>> This patch set contains the usb support for Broadcom NSP SoC. The >>> usb3 phy is

Re: [PATCH] drm/ttm: Make sure BOs being swapped out are cacheable

On Fri, Jan 27, 2017 at 07:23:58AM +0100, Thomas Hellstrom wrote: > On 01/27/2017 03:29 AM, Michel Dänzer wrote: > > On 26/01/17 09:46 AM, Sinclair Yeh wrote: > >> On Wed, Jan 25, 2017 at 10:49:33AM +0100, Christian König wrote: > >>> Am 25.01.2017 um 10:25 schrieb Thomas Hellstrom: > On

Re: [PATCH] drm/ttm: Make sure BOs being swapped out are cacheable

On Fri, Jan 27, 2017 at 07:23:58AM +0100, Thomas Hellstrom wrote: > On 01/27/2017 03:29 AM, Michel Dänzer wrote: > > On 26/01/17 09:46 AM, Sinclair Yeh wrote: > >> On Wed, Jan 25, 2017 at 10:49:33AM +0100, Christian König wrote: > >>> Am 25.01.2017 um 10:25 schrieb Thomas Hellstrom: > On

Re: mm, vmscan: commit makes PAE kernel crash nightly (bisected)

On Thu 26-01-17 17:18:58, Trevor Cordes wrote: > On 2017-01-24 Michal Hocko wrote: > > On Sun 22-01-17 18:45:59, Trevor Cordes wrote: > > [...] > > > Also, completely separate from your patch I ran mhocko's 4.9 tree > > > with mem=2G to see if lower ram amount would help, but it didn't. > > > Even

Re: mm, vmscan: commit makes PAE kernel crash nightly (bisected)

On Thu 26-01-17 17:18:58, Trevor Cordes wrote: > On 2017-01-24 Michal Hocko wrote: > > On Sun 22-01-17 18:45:59, Trevor Cordes wrote: > > [...] > > > Also, completely separate from your patch I ran mhocko's 4.9 tree > > > with mem=2G to see if lower ram amount would help, but it didn't. > > > Even

Re: [PATCH] ARM: dts: Odroid XU4: fix USB3.0 ports

On 25/01/2017 15:17, Krzysztof Kozlowski wrote: > On Wed, Jan 25, 2017 at 3:48 PM, Marek Szyprowski > wrote: >> Hi Krzysztof, >> >> On 2017-01-25 08:55, Krzysztof Kozlowski wrote: >>> >>> On Wed, Jan 25, 2017 at 7:51 AM, Anand Moon wrote:

Re: [PATCH] ARM: dts: Odroid XU4: fix USB3.0 ports

On 25/01/2017 15:17, Krzysztof Kozlowski wrote: > On Wed, Jan 25, 2017 at 3:48 PM, Marek Szyprowski > wrote: >> Hi Krzysztof, >> >> On 2017-01-25 08:55, Krzysztof Kozlowski wrote: >>> >>> On Wed, Jan 25, 2017 at 7:51 AM, Anand Moon wrote: On 24 January 2017 at 19:18, Richard Genoud

Re: [PATCH] staging: octeon-usb: Fix coding style issues

On Thu, Jan 26, 2017 at 10:46:02PM -0500, William Blough wrote: > Wrap lines that exceed 80 characters. > > Signed-off-by: William Blough > --- > drivers/staging/octeon-usb/octeon-hcd.c | 18 -- > 1 file changed, 12 insertions(+), 6 deletions(-) > > diff --git

Re: [PATCH] staging: octeon-usb: Fix coding style issues

On Thu, Jan 26, 2017 at 10:46:02PM -0500, William Blough wrote: > Wrap lines that exceed 80 characters. > > Signed-off-by: William Blough > --- > drivers/staging/octeon-usb/octeon-hcd.c | 18 -- > 1 file changed, 12 insertions(+), 6 deletions(-) > > diff --git

Re: [Xen-devel] [PATCH v2] xen, input: try to read screen resolution for xen-kbdfront

On 01/27/2017 09:12 AM, Juergen Gross wrote: Instead of using the default resolution of 800*600 for the pointing device of xen-kbdfront try to read the resolution of the (virtual) framebuffer device. Use the default as fallback only. Signed-off-by: Juergen Gross --- V2: get

Re: [Xen-devel] [PATCH v2] xen, input: try to read screen resolution for xen-kbdfront

On 01/27/2017 09:12 AM, Juergen Gross wrote: Instead of using the default resolution of 800*600 for the pointing device of xen-kbdfront try to read the resolution of the (virtual) framebuffer device. Use the default as fallback only. Signed-off-by: Juergen Gross --- V2: get framebuffer

[PATCH v2] xen,input: try to read screen resolution for xen-kbdfront

Instead of using the default resolution of 800*600 for the pointing device of xen-kbdfront try to read the resolution of the (virtual) framebuffer device. Use the default as fallback only. Signed-off-by: Juergen Gross --- V2: get framebuffer resolution only if CONFIG_FB (Dmitry

[PATCH v2] xen,input: try to read screen resolution for xen-kbdfront

Instead of using the default resolution of 800*600 for the pointing device of xen-kbdfront try to read the resolution of the (virtual) framebuffer device. Use the default as fallback only. Signed-off-by: Juergen Gross --- V2: get framebuffer resolution only if CONFIG_FB (Dmitry Torokhov) ---

Re: v4.10-rc4 to v4.10-rc5: battery regression on Nokia N900

On 01/26/2017 07:39 PM, Zhang Rui wrote: On Thu, 2017-01-26 at 18:03 -0800, Guenter Roeck wrote: On 01/26/2017 05:37 PM, Zhang Rui wrote: On Wed, 2017-01-25 at 13:09 +0100, Pali Rohár wrote: On Wednesday 25 January 2017 12:12:33 Pavel Machek wrote: Hi! Right. Before

Re: v4.10-rc4 to v4.10-rc5: battery regression on Nokia N900

On 01/26/2017 07:39 PM, Zhang Rui wrote: On Thu, 2017-01-26 at 18:03 -0800, Guenter Roeck wrote: On 01/26/2017 05:37 PM, Zhang Rui wrote: On Wed, 2017-01-25 at 13:09 +0100, Pali Rohár wrote: On Wednesday 25 January 2017 12:12:33 Pavel Machek wrote: Hi! Right. Before

Re: [PATCH 3/3] powerpc: enable support for GCC plugins

On 09/12/16 21:59, PaX Team wrote: the specific problem addressed here can (and IMHO should) be solved in another way: remove the inclusion of the offending headers in gcc-common.h as neither tm.h nor c-common.h are needed by existing plugins. for background, We can't build without tm.h:

Re: [PATCH 3/3] powerpc: enable support for GCC plugins

On 09/12/16 21:59, PaX Team wrote: the specific problem addressed here can (and IMHO should) be solved in another way: remove the inclusion of the offending headers in gcc-common.h as neither tm.h nor c-common.h are needed by existing plugins. for background, We can't build without tm.h:

Re: [PATCH 2/2] tpm2-space: add handling for global session exhaustion

On Thu, Jan 26, 2017 at 04:45:52PM -0800, James Bottomley wrote: > On Thu, 2017-01-26 at 14:56 +0200, Jarkko Sakkinen wrote: > > On Mon, Jan 23, 2017 at 09:38:33PM -0800, James Bottomley wrote: > > > In a TPM2, sessions can be globally exhausted once there are > > > TPM_PT_ACTIVE_SESSION_MAX of

Re: [PATCH 2/2] tpm2-space: add handling for global session exhaustion

On Thu, Jan 26, 2017 at 04:45:52PM -0800, James Bottomley wrote: > On Thu, 2017-01-26 at 14:56 +0200, Jarkko Sakkinen wrote: > > On Mon, Jan 23, 2017 at 09:38:33PM -0800, James Bottomley wrote: > > > In a TPM2, sessions can be globally exhausted once there are > > > TPM_PT_ACTIVE_SESSION_MAX of

Re: [PATCH v5 1/4] usb: dbc: early driver for xhci debug capability

* Peter Zijlstra wrote: > On Thu, Jan 26, 2017 at 05:01:05PM +0100, Ingo Molnar wrote: > > > > > > > > I.e. if there's any polling component then it would be reasonable to > > > > add an error > > > > component: poll the status and if it goes 'disconnected' then disable

Re: [PATCH v5 1/4] usb: dbc: early driver for xhci debug capability

* Peter Zijlstra wrote: > On Thu, Jan 26, 2017 at 05:01:05PM +0100, Ingo Molnar wrote: > > > > > > > > I.e. if there's any polling component then it would be reasonable to > > > > add an error > > > > component: poll the status and if it goes 'disconnected' then disable > > > > early-printk

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

On Thu, Jan 26, 2017 at 08:26:19AM -0800, James Bottomley wrote: > On Thu, 2017-01-26 at 14:51 +0200, Jarkko Sakkinen wrote: > [...] > > > diff --git a/drivers/char/tpm/tpm.h b/drivers/char/tpm/tpm.h > > > index c48255e..b77fc60 100644 > > > --- a/drivers/char/tpm/tpm.h > > > +++

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

On Thu, Jan 26, 2017 at 08:26:19AM -0800, James Bottomley wrote: > On Thu, 2017-01-26 at 14:51 +0200, Jarkko Sakkinen wrote: > [...] > > > diff --git a/drivers/char/tpm/tpm.h b/drivers/char/tpm/tpm.h > > > index c48255e..b77fc60 100644 > > > --- a/drivers/char/tpm/tpm.h > > > +++

Re: [PATCH] tpm: fix RC value check in tpm2_seal_trusted

On Thu, Jan 26, 2017 at 11:32:52AM -0700, Jason Gunthorpe wrote: > On Thu, Jan 26, 2017 at 01:27:14PM +0200, Jarkko Sakkinen wrote: > > > "The error code handling is bogus as any error code that has the bits > > set that TPM_RC_HASH could pass. Implemented tpm2_rc_value() helper to > > parse the

Re: [PATCH] tpm: fix RC value check in tpm2_seal_trusted

On Thu, Jan 26, 2017 at 11:32:52AM -0700, Jason Gunthorpe wrote: > On Thu, Jan 26, 2017 at 01:27:14PM +0200, Jarkko Sakkinen wrote: > > > "The error code handling is bogus as any error code that has the bits > > set that TPM_RC_HASH could pass. Implemented tpm2_rc_value() helper to > > parse the

Re: [tpmdd-devel] [PATCH RFC v3 5/5] tpm2: expose resource manager via a device link /dev/tpms

On Thu, Jan 26, 2017 at 04:29:02PM -0800, James Bottomley wrote: > On Wed, 2017-01-25 at 15:40 +0200, Jarkko Sakkinen wrote: > > On Mon, Jan 23, 2017 at 02:16:37PM -0800, James Bottomley wrote: > > > On Mon, 2017-01-23 at 23:42 +0200, Jarkko Sakkinen wrote: > > > > On Mon, Jan 23, 2017 at

Re: [tpmdd-devel] [PATCH RFC v3 5/5] tpm2: expose resource manager via a device link /dev/tpms

On Thu, Jan 26, 2017 at 04:29:02PM -0800, James Bottomley wrote: > On Wed, 2017-01-25 at 15:40 +0200, Jarkko Sakkinen wrote: > > On Mon, Jan 23, 2017 at 02:16:37PM -0800, James Bottomley wrote: > > > On Mon, 2017-01-23 at 23:42 +0200, Jarkko Sakkinen wrote: > > > > On Mon, Jan 23, 2017 at

Re: [PATCH RFC] tpm: define a command filter

On Thu, Jan 26, 2017 at 11:05:06AM -0700, Jason Gunthorpe wrote: > On Thu, Jan 26, 2017 at 01:14:03PM +0200, Jarkko Sakkinen wrote: > > On Wed, Jan 25, 2017 at 03:11:36PM -0700, Jason Gunthorpe wrote: > > > On Wed, Jan 25, 2017 at 10:21:37PM +0200, Jarkko Sakkinen wrote: > > > > > > > There

Re: [PATCH RFC] tpm: define a command filter

On Thu, Jan 26, 2017 at 11:05:06AM -0700, Jason Gunthorpe wrote: > On Thu, Jan 26, 2017 at 01:14:03PM +0200, Jarkko Sakkinen wrote: > > On Wed, Jan 25, 2017 at 03:11:36PM -0700, Jason Gunthorpe wrote: > > > On Wed, Jan 25, 2017 at 10:21:37PM +0200, Jarkko Sakkinen wrote: > > > > > > > There

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

On Thu, Jan 26, 2017 at 07:18:49AM -0800, James Bottomley wrote: > On Thu, 2017-01-26 at 14:51 +0200, Jarkko Sakkinen wrote: > > On Mon, Jan 23, 2017 at 09:37:11PM -0800, James Bottomley wrote: > > > sessions are different from transient objects in that their handles > > > may not be virtualized

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

On Thu, Jan 26, 2017 at 07:18:49AM -0800, James Bottomley wrote: > On Thu, 2017-01-26 at 14:51 +0200, Jarkko Sakkinen wrote: > > On Mon, Jan 23, 2017 at 09:37:11PM -0800, James Bottomley wrote: > > > sessions are different from transient objects in that their handles > > > may not be virtualized

Re: fs, net: deadlock between bind/splice on af_unix

On Thu, Jan 26, 2017 at 09:11:07PM -0800, Cong Wang wrote: > On Thu, Jan 26, 2017 at 3:29 PM, Mateusz Guzik wrote: > > On Tue, Jan 17, 2017 at 01:21:48PM -0800, Cong Wang wrote: > >> On Mon, Jan 16, 2017 at 1:32 AM, Dmitry Vyukov wrote: > >> > On Fri, Dec

Re: fs, net: deadlock between bind/splice on af_unix

On Thu, Jan 26, 2017 at 09:11:07PM -0800, Cong Wang wrote: > On Thu, Jan 26, 2017 at 3:29 PM, Mateusz Guzik wrote: > > On Tue, Jan 17, 2017 at 01:21:48PM -0800, Cong Wang wrote: > >> On Mon, Jan 16, 2017 at 1:32 AM, Dmitry Vyukov wrote: > >> > On Fri, Dec 9, 2016 at 7:41 AM, Al Viro wrote: > >>

[PATCH] spi: qup: Fix runtime and system PM callbacks.

The SPI clocks were being turned on every suspend/resume cycle. This was increamenting the prepare/enable count after every resume. Fix the same. Signed-off-by: Pramod Gurav --- Tested on db410c drivers/spi/spi-qup.c | 18 +- 1 file changed, 9

[PATCH] spi: qup: Fix runtime and system PM callbacks.

The SPI clocks were being turned on every suspend/resume cycle. This was increamenting the prepare/enable count after every resume. Fix the same. Signed-off-by: Pramod Gurav --- Tested on db410c drivers/spi/spi-qup.c | 18 +- 1 file changed, 9 insertions(+), 9 deletions(-)

Re: [tpmdd-devel] [PATCH v6 1/2] tpm: implement TPM 2.0 capability to get active PCR banks

On Thu, Jan 26, 2017 at 07:23:15AM -0500, Stefan Berger wrote: > On 01/20/2017 12:05 PM, Nayna Jain wrote: > > This patch implements the TPM 2.0 capability TPM_CAP_PCRS to > > retrieve the active PCR banks from the TPM. This is needed > > to enable extending all active banks as recommended by TPM

Re: [tpmdd-devel] [PATCH v6 1/2] tpm: implement TPM 2.0 capability to get active PCR banks

On Thu, Jan 26, 2017 at 07:23:15AM -0500, Stefan Berger wrote: > On 01/20/2017 12:05 PM, Nayna Jain wrote: > > This patch implements the TPM 2.0 capability TPM_CAP_PCRS to > > retrieve the active PCR banks from the TPM. This is needed > > to enable extending all active banks as recommended by TPM

Re: [PATCH v4 2/4] phy: qcom-qusb2: New driver for QUSB2 PHY on Qcom chips

On 01/26/2017 11:45 PM, Bjorn Andersson wrote: On Tue 24 Jan 01:19 PST 2017, Kishon Vijay Abraham I wrote: On Monday 23 January 2017 03:43 PM, Vivek Gautam wrote: On Wed, Jan 18, 2017 at 11:33 PM, Bjorn Andersson [..] Yes, that's correct. The QMP and QUSB2 phy init sequences are a bunch of

Re: [PATCH v4 2/4] phy: qcom-qusb2: New driver for QUSB2 PHY on Qcom chips

On 01/26/2017 11:45 PM, Bjorn Andersson wrote: On Tue 24 Jan 01:19 PST 2017, Kishon Vijay Abraham I wrote: On Monday 23 January 2017 03:43 PM, Vivek Gautam wrote: On Wed, Jan 18, 2017 at 11:33 PM, Bjorn Andersson [..] Yes, that's correct. The QMP and QUSB2 phy init sequences are a bunch of

Re: [PATCH] drm/ttm: Make sure BOs being swapped out are cacheable

On 01/27/2017 03:29 AM, Michel Dänzer wrote: > On 26/01/17 09:46 AM, Sinclair Yeh wrote: >> On Wed, Jan 25, 2017 at 10:49:33AM +0100, Christian König wrote: >>> Am 25.01.2017 um 10:25 schrieb Thomas Hellstrom: On 01/25/2017 09:21 AM, Michel Dänzer wrote: > From: Michel Dänzer

Re: [PATCH] drm/ttm: Make sure BOs being swapped out are cacheable

On 01/27/2017 03:29 AM, Michel Dänzer wrote: > On 26/01/17 09:46 AM, Sinclair Yeh wrote: >> On Wed, Jan 25, 2017 at 10:49:33AM +0100, Christian König wrote: >>> Am 25.01.2017 um 10:25 schrieb Thomas Hellstrom: On 01/25/2017 09:21 AM, Michel Dänzer wrote: > From: Michel Dänzer > >

Re: [PATCH 8/8] Revert "ext4: fix wrong gfp type under transaction"

On Thu, Jan 26, 2017 at 08:44:55AM +0100, Michal Hocko wrote: > > > I'm convinced the current series is OK, only real life will tell us > > > whether > > > we missed something or not ;) > > > > I would like to extend the changelog of "jbd2: mark the transaction > > context with the scope

Re: [PATCH 8/8] Revert "ext4: fix wrong gfp type under transaction"

On Thu, Jan 26, 2017 at 08:44:55AM +0100, Michal Hocko wrote: > > > I'm convinced the current series is OK, only real life will tell us > > > whether > > > we missed something or not ;) > > > > I would like to extend the changelog of "jbd2: mark the transaction > > context with the scope

Re: [PATCH] xen,input: try to read screen resolution for xen-kbdfront

On 24/01/17 19:47, Dmitry Torokhov wrote: > On Tue, Jan 24, 2017 at 01:09:55PM +0100, Juergen Gross wrote: >> Instead of using the default resolution of 800*600 for the pointing >> device of xen-kbdfront try to read the resolution of the (virtual) >> framebuffer device. Use the default as fallback

Re: [PATCH] xen,input: try to read screen resolution for xen-kbdfront

On 24/01/17 19:47, Dmitry Torokhov wrote: > On Tue, Jan 24, 2017 at 01:09:55PM +0100, Juergen Gross wrote: >> Instead of using the default resolution of 800*600 for the pointing >> device of xen-kbdfront try to read the resolution of the (virtual) >> framebuffer device. Use the default as fallback

Re: [PATCH v3] gpio: aspeed: Add banks Y, Z, AA, AB and AC

On Fri, Jan 27, 2017 at 3:24 PM, Andrew Jeffery wrote: > This is less straight-forward than one would hope, as some banks only > have 4 pins rather than 8, others are output only, yet more (W and > X, already supported) are input-only, and in the case of the g4 SoC bank > AC

Re: [PATCH v3] gpio: aspeed: Add banks Y, Z, AA, AB and AC

On Fri, Jan 27, 2017 at 3:24 PM, Andrew Jeffery wrote: > This is less straight-forward than one would hope, as some banks only > have 4 pins rather than 8, others are output only, yet more (W and > X, already supported) are input-only, and in the case of the g4 SoC bank > AC doesn't exist. > >

Re: [PATCH 3/3] powerpc: enable support for GCC plugins

On 27/01/17 16:52, Andrew Donnellan wrote: basic-block.h includes tm.h, and I don't believe we can remove that. I'm not convinced there's a way around this. Includes via function.h, I should say. -- Andrew Donnellan OzLabs, ADL Canberra andrew.donnel...@au1.ibm.com IBM Australia

Re: [PATCH 3/3] powerpc: enable support for GCC plugins

On 27/01/17 16:52, Andrew Donnellan wrote: basic-block.h includes tm.h, and I don't believe we can remove that. I'm not convinced there's a way around this. Includes via function.h, I should say. -- Andrew Donnellan OzLabs, ADL Canberra andrew.donnel...@au1.ibm.com IBM Australia

Re: [PATCH net-next v2] macb: Common code to enable ptp support for MACB/GEM

Hi Rafal, On Thu, Jan 26, 2017 at 8:45 PM, Rafal Ozieblo wrote: >> -Original Message- >> From: Andrei Pistirica [mailto:andrei.pistir...@microchip.com] >> Sent: 19 stycznia 2017 16:56 >> Subject: [PATCH net-next v2] macb: Common code to enable ptp support for >>

Re: [PATCH net-next v2] macb: Common code to enable ptp support for MACB/GEM

Hi Rafal, On Thu, Jan 26, 2017 at 8:45 PM, Rafal Ozieblo wrote: >> -Original Message- >> From: Andrei Pistirica [mailto:andrei.pistir...@microchip.com] >> Sent: 19 stycznia 2017 16:56 >> Subject: [PATCH net-next v2] macb: Common code to enable ptp support for >> MACB/GEM >> >> >>

hi

hi http://www.mobilam.net/education.php?death=2afxa279semd4a cputrdoc

hi

hi http://www.mobilam.net/education.php?death=2afxa279semd4a cputrdoc

Re: [PATCH v4 3/4] dt-bindings: phy: Add support for QMP phy

On 01/27/2017 05:13 AM, Stephen Boyd wrote: On 01/24, Vivek Gautam wrote: Below is one binding that works for me. phy@34000 { compatible = "qcom,msm8996-qmp-pcie-phy"; reg = <0x034000 0x488>;

Re: [PATCH v4 3/4] dt-bindings: phy: Add support for QMP phy

On 01/27/2017 05:13 AM, Stephen Boyd wrote: On 01/24, Vivek Gautam wrote: Below is one binding that works for me. phy@34000 { compatible = "qcom,msm8996-qmp-pcie-phy"; reg = <0x034000 0x488>;

Re: fs, net: deadlock between bind/splice on af_unix

On Thu, Jan 26, 2017 at 3:29 PM, Mateusz Guzik wrote: > On Tue, Jan 17, 2017 at 01:21:48PM -0800, Cong Wang wrote: >> On Mon, Jan 16, 2017 at 1:32 AM, Dmitry Vyukov wrote: >> > On Fri, Dec 9, 2016 at 7:41 AM, Al Viro wrote: >> >>

Re: fs, net: deadlock between bind/splice on af_unix

On Thu, Jan 26, 2017 at 3:29 PM, Mateusz Guzik wrote: > On Tue, Jan 17, 2017 at 01:21:48PM -0800, Cong Wang wrote: >> On Mon, Jan 16, 2017 at 1:32 AM, Dmitry Vyukov wrote: >> > On Fri, Dec 9, 2016 at 7:41 AM, Al Viro wrote: >> >> On Thu, Dec 08, 2016 at 10:32:00PM -0800, Cong Wang wrote: >> >>

Re: [PATCH 1/5] DT: mfd: axp20x: Add AXP806 to list of current AXP20x family members

On Fri, Jan 27, 2017 at 5:23 AM, Rask Ingemann Lambertsen wrote: > An entry for the AXP806 was forgotten, so add one. > > Signed-off-by: Rask Ingemann Lambertsen > Fixes: 204ae2963e10 ("mfd: axp20x: Add bindings for AXP806 PMIC") Acked-by: Chen-Yu Tsai

Re: [PATCH 1/5] DT: mfd: axp20x: Add AXP806 to list of current AXP20x family members

On Fri, Jan 27, 2017 at 5:23 AM, Rask Ingemann Lambertsen wrote: > An entry for the AXP806 was forgotten, so add one. > > Signed-off-by: Rask Ingemann Lambertsen > Fixes: 204ae2963e10 ("mfd: axp20x: Add bindings for AXP806 PMIC") Acked-by: Chen-Yu Tsai

Re: [PATCH 0/3] ata: add m68k/Atari Falcon PATA support

Hi Finn, Am 26.01.2017 um 21:47 schrieb Finn Thain: >> I hadn't considered that. Can PDMA for Falcon SCSI coexist with >> interrupt-using DMA for TT SCSI in the same driver (i.e. as runtime >> options)? > > Sure, why not? > >> How much overhead and latency would polling for DMA completion

Re: [PATCH 0/3] ata: add m68k/Atari Falcon PATA support

Hi Finn, Am 26.01.2017 um 21:47 schrieb Finn Thain: >> I hadn't considered that. Can PDMA for Falcon SCSI coexist with >> interrupt-using DMA for TT SCSI in the same driver (i.e. as runtime >> options)? > > Sure, why not? > >> How much overhead and latency would polling for DMA completion

[PATCH] staging: octeon-usb: Fix coding style issues

Wrap lines that exceed 80 characters. Signed-off-by: William Blough --- drivers/staging/octeon-usb/octeon-hcd.c | 18 -- 1 file changed, 12 insertions(+), 6 deletions(-) diff --git a/drivers/staging/octeon-usb/octeon-hcd.c

[PATCH] staging: octeon-usb: Fix coding style issues

Wrap lines that exceed 80 characters. Signed-off-by: William Blough --- drivers/staging/octeon-usb/octeon-hcd.c | 18 -- 1 file changed, 12 insertions(+), 6 deletions(-) diff --git a/drivers/staging/octeon-usb/octeon-hcd.c b/drivers/staging/octeon-usb/octeon-hcd.c index

[PATCH v3] gpio: aspeed: Add banks Y, Z, AA, AB and AC

This is less straight-forward than one would hope, as some banks only have 4 pins rather than 8, others are output only, yet more (W and X, already supported) are input-only, and in the case of the g4 SoC bank AC doesn't exist. Add some structs to describe the varying properties of different

[PATCH v3] gpio: aspeed: Add banks Y, Z, AA, AB and AC

This is less straight-forward than one would hope, as some banks only have 4 pins rather than 8, others are output only, yet more (W and X, already supported) are input-only, and in the case of the g4 SoC bank AC doesn't exist. Add some structs to describe the varying properties of different

Re: [PATCH 2/3] perf ftrace: Add ftrace.tracer config option

On 01/27/2017 03:58 AM, Arnaldo Carvalho de Melo wrote: Em Thu, Jan 26, 2017 at 06:35:38PM +0900, Taeung Song escreveu: Currently perf ftrace command will select 'function_graph' or 'function'. So add ftrace.tracer config option to select tracer # cat ~/.perfconfig [ftrace]

Re: [PATCH 2/3] perf ftrace: Add ftrace.tracer config option

On 01/27/2017 03:58 AM, Arnaldo Carvalho de Melo wrote: Em Thu, Jan 26, 2017 at 06:35:38PM +0900, Taeung Song escreveu: Currently perf ftrace command will select 'function_graph' or 'function'. So add ftrace.tracer config option to select tracer # cat ~/.perfconfig [ftrace]

[PATCH] perf ftrace: Add ftrace.tracer config option

Currently perf ftrace command will select 'function_graph' or 'function'. So add ftrace.tracer config option to select tracer # cat ~/.perfconfig [ftrace] tracer = function # perf ftrace usleep 123456 | head -10 <...>-14450 [002] d... 10089.284231: finish_task_switch

[PATCH] perf ftrace: Add ftrace.tracer config option

Currently perf ftrace command will select 'function_graph' or 'function'. So add ftrace.tracer config option to select tracer # cat ~/.perfconfig [ftrace] tracer = function # perf ftrace usleep 123456 | head -10 <...>-14450 [002] d... 10089.284231: finish_task_switch

GIT PULL] Thermal management updates for v4.10-rc6

Hi, Linus, Please pull from   git://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux.git for-rc to receive the latest Thermal Management updates for v4.10-rc6 with top-most commit 3feb479cea37fc623cf4e705631b2e679cbfbd7a:   Revert "thermal: thermal_hwmon: Convert to

GIT PULL] Thermal management updates for v4.10-rc6

Hi, Linus, Please pull from   git://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux.git for-rc to receive the latest Thermal Management updates for v4.10-rc6 with top-most commit 3feb479cea37fc623cf4e705631b2e679cbfbd7a:   Revert "thermal: thermal_hwmon: Convert to

Re: [v3 PATCH 05/10] x86/insn-kernel: Add support to resolve 16-bit addressing encodings

On Thu, 2017-01-26 at 09:05 -0800, Andy Lutomirski wrote: > On Wed, Jan 25, 2017 at 9:50 PM, Ricardo Neri > wrote: > > On Wed, 2017-01-25 at 13:58 -0800, Andy Lutomirski wrote: > >> On Wed, Jan 25, 2017 at 12:23 PM, Ricardo Neri > >>

Re: [v3 PATCH 05/10] x86/insn-kernel: Add support to resolve 16-bit addressing encodings

On Thu, 2017-01-26 at 09:05 -0800, Andy Lutomirski wrote: > On Wed, Jan 25, 2017 at 9:50 PM, Ricardo Neri > wrote: > > On Wed, 2017-01-25 at 13:58 -0800, Andy Lutomirski wrote: > >> On Wed, Jan 25, 2017 at 12:23 PM, Ricardo Neri > >> wrote: > >> > Tasks running in virtual-8086 mode will use

Re: v4.10-rc4 to v4.10-rc5: battery regression on Nokia N900

On Thu, 2017-01-26 at 18:03 -0800, Guenter Roeck wrote: > On 01/26/2017 05:37 PM, Zhang Rui wrote: > > > > On Wed, 2017-01-25 at 13:09 +0100, Pali Rohár wrote: > > > > > > On Wednesday 25 January 2017 12:12:33 Pavel Machek wrote: > > > > > > > > > > > > Hi! > > > > > > > > > > > > > > > > >

Re: v4.10-rc4 to v4.10-rc5: battery regression on Nokia N900

On Thu, 2017-01-26 at 18:03 -0800, Guenter Roeck wrote: > On 01/26/2017 05:37 PM, Zhang Rui wrote: > > > > On Wed, 2017-01-25 at 13:09 +0100, Pali Rohár wrote: > > > > > > On Wednesday 25 January 2017 12:12:33 Pavel Machek wrote: > > > > > > > > > > > > Hi! > > > > > > > > > > > > > > > > >

Re: [v3 PATCH 05/10] x86/insn-kernel: Add support to resolve 16-bit addressing encodings (fwd)

rove the system] > > url: > https://github.com/0day-ci/linux/commits/Ricardo-Neri/x86-Enable-User-Mode-Instruction-Prevention/20170126-043345 > :: branch date: 51 minutes ago > :: commit date: 51 minutes ago > > >> arch/x86/lib/insn-kernel.c:267:6-9: WARNING: Un

Re: [v3 PATCH 05/10] x86/insn-kernel: Add support to resolve 16-bit addressing encodings (fwd)

0day-ci/linux/commits/Ricardo-Neri/x86-Enable-User-Mode-Instruction-Prevention/20170126-043345 > :: branch date: 51 minutes ago > :: commit date: 51 minutes ago > > >> arch/x86/lib/insn-kernel.c:267:6-9: WARNING: Unsigned expression compared > >> with zero: s

[PATCHv5 4/5] arm: mvebu: Add device tree for 98DX3236 SoCs

The Marvell 98DX3236, 98DX3336, 98DX4521 and variants are switch ASICs with integrated CPUs. They are similar to the Armada XP SoCs but have different I/O interfaces. Signed-off-by: Chris Packham Acked-by: Rob Herring --- Notes: Changes

[PATCHv5 0/5] Support for Marvell switches with integrated CPUs

The 98DX3236, 98DX3336 and 98DX4251 are a set of switch ASICs with integrated CPUs. They CPU block is common within these product lines and (as far as I can tell/have been told) is based on the Armada XP. There are a few differences due to the fact they have to squeeze the CPU into the same

[PATCHv5 4/5] arm: mvebu: Add device tree for 98DX3236 SoCs

The Marvell 98DX3236, 98DX3336, 98DX4521 and variants are switch ASICs with integrated CPUs. They are similar to the Armada XP SoCs but have different I/O interfaces. Signed-off-by: Chris Packham Acked-by: Rob Herring --- Notes: Changes in v2: - Update devicetree binding documentation

[PATCHv5 0/5] Support for Marvell switches with integrated CPUs

The 98DX3236, 98DX3336 and 98DX4251 are a set of switch ASICs with integrated CPUs. They CPU block is common within these product lines and (as far as I can tell/have been told) is based on the Armada XP. There are a few differences due to the fact they have to squeeze the CPU into the same

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

From: Kalyan Kinthada This pinctrl driver supports the 98DX3236, 98DX3336 and 98DX4251 SoCs from Marvell. Signed-off-by: Kalyan Kinthada Signed-off-by: Chris Packham Acked-by: Rob

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

From: Kalyan Kinthada This pinctrl driver supports the 98DX3236, 98DX3336 and 98DX4251 SoCs from Marvell. Signed-off-by: Kalyan Kinthada Signed-off-by: Chris Packham Acked-by: Rob Herring Acked-by: Sebastian Hesselbarth --- Notes: Changes in v2: - include sdio support for the

  1   2   3   4   5   6   7   8   9   10   >