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

On Monday 30 January 2017 18:53:09 Tony Lindgren wrote: > * Pavel Machek [170127 11:41]: > > On Fri 2017-01-27 17:23:07, Kalle Valo wrote: > > > Pali Rohár writes: > > > > On Friday 27 January 2017 14:26:22 Kalle Valo wrote: > > > >> Pali Rohár

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

On Monday 30 January 2017 18:53:09 Tony Lindgren wrote: > * Pavel Machek [170127 11:41]: > > On Fri 2017-01-27 17:23:07, Kalle Valo wrote: > > > Pali Rohár writes: > > > > On Friday 27 January 2017 14:26:22 Kalle Valo wrote: > > > >> Pali Rohár writes: > > > >> > 2) It was already tested that

Re: [PATCH v3 07/24] drm/rockchip: dw-mipi-dsi: include bad value in error message

On Sun, Jan 29, 2017 at 01:24:27PM +, John Keeping wrote: > As an aid to debugging. Reviewed-by: Sean Paul > > Signed-off-by: John Keeping > Reviewed-by: Chris Zhong > --- > v3: > - Add Chris' Reviewed-by > Unchanged in v2 >

Re: [PATCH v3 07/24] drm/rockchip: dw-mipi-dsi: include bad value in error message

On Sun, Jan 29, 2017 at 01:24:27PM +, John Keeping wrote: > As an aid to debugging. Reviewed-by: Sean Paul > > Signed-off-by: John Keeping > Reviewed-by: Chris Zhong > --- > v3: > - Add Chris' Reviewed-by > Unchanged in v2 > > drivers/gpu/drm/rockchip/dw-mipi-dsi.c | 3 ++- > 1 file

Re: [PATCH v3 06/24] drm/rockchip: dw-mipi-dsi: avoid out-of-bounds read on tx_buf

On Sun, Jan 29, 2017 at 01:24:26PM +, John Keeping wrote: > As a side-effect of this, encode the endianness explicitly rather than > casting a u16. > > Signed-off-by: John Keeping > Reviewed-by: Chris Zhong > --- > v3: > - Add Chris' Reviewed-by >

Re: [PATCH v3 06/24] drm/rockchip: dw-mipi-dsi: avoid out-of-bounds read on tx_buf

On Sun, Jan 29, 2017 at 01:24:26PM +, John Keeping wrote: > As a side-effect of this, encode the endianness explicitly rather than > casting a u16. > > Signed-off-by: John Keeping > Reviewed-by: Chris Zhong > --- > v3: > - Add Chris' Reviewed-by > Unchanged in v2 > >

Re: [PATCH 5/5] gpio: ws16c48: Add support for GPIO names

Hi William, [auto build test ERROR on gpio/for-next] [also build test ERROR on next-20170130] [cannot apply to v4.10-rc6] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/William-Breathitt-Gray

Re: [PATCH 5/5] gpio: ws16c48: Add support for GPIO names

Hi William, [auto build test ERROR on gpio/for-next] [also build test ERROR on next-20170130] [cannot apply to v4.10-rc6] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/William-Breathitt-Gray

Re: [RFC V2 11/12] mm: Tag VMA with VM_CDM flag during page fault

Here's the flag definition: > +#ifdef CONFIG_COHERENT_DEVICE > +#define VM_CDM 0x0080 /* Contains coherent device > memory */ > +#endif But it doesn't match the implementation: > +#ifdef CONFIG_COHERENT_DEVICE > +static void mark_vma_cdm(nodemask_t *nmask, > +

Re: [RFC V2 11/12] mm: Tag VMA with VM_CDM flag during page fault

Here's the flag definition: > +#ifdef CONFIG_COHERENT_DEVICE > +#define VM_CDM 0x0080 /* Contains coherent device > memory */ > +#endif But it doesn't match the implementation: > +#ifdef CONFIG_COHERENT_DEVICE > +static void mark_vma_cdm(nodemask_t *nmask, > +

[PATCH] tick/broadcast: Reduce lock cacheline contention

It was observed that on an Intel x86 system without the ARAT (Always running APIC timer) feature and with fairly large number of CPUs as well as CPUs coming in and out of intel_idle frequently, the lock contention on the tick_broadcast_lock can become significant. To reduce contention, the lock

[PATCH] tick/broadcast: Reduce lock cacheline contention

It was observed that on an Intel x86 system without the ARAT (Always running APIC timer) feature and with fairly large number of CPUs as well as CPUs coming in and out of intel_idle frequently, the lock contention on the tick_broadcast_lock can become significant. To reduce contention, the lock

Re: [GIT PULL 4/4] arm64: dts: exynos: for v4.11, 2nd round

On Sun, Jan 29, 2017 at 09:23:29PM -0800, Olof Johansson wrote: > Hi Krzysztof, > > On Sun, Jan 29, 2017 at 10:06:29PM +0200, Krzysztof Kozlowski wrote: > > Hi, > > > > On top of previous pull request. > > > > This adds proper clocks to LPASS node on Exynos5433 which is needed > > by Marek's

Re: [GIT PULL 4/4] arm64: dts: exynos: for v4.11, 2nd round

On Sun, Jan 29, 2017 at 09:23:29PM -0800, Olof Johansson wrote: > Hi Krzysztof, > > On Sun, Jan 29, 2017 at 10:06:29PM +0200, Krzysztof Kozlowski wrote: > > Hi, > > > > On top of previous pull request. > > > > This adds proper clocks to LPASS node on Exynos5433 which is needed > > by Marek's

Re: [PATCH v20 08/17] clocksource/drivers/arm_arch_timer: Rework counter frequency detection.

On Thu, Jan 26, 2017 at 01:49:03PM +0800, Fu Wei wrote: > On 26 January 2017 at 01:25, Mark Rutland wrote: > > On Wed, Jan 25, 2017 at 02:46:12PM +0800, Fu Wei wrote: > >> On 25 January 2017 at 01:24, Mark Rutland wrote: > >> > On Wed, Jan 18, 2017 at

[PATCH] powerpc: sort Kconfig selects under CONFIG_PPC

--- On top of linux-next 20170130 --- arch/powerpc/Kconfig | 128 +-- 1 file changed, 64 insertions(+), 64 deletions(-) diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig index 689cf9218b21..570195c8a86a 100644 --- a/arch/powerpc/Kconfi

Re: [PATCH v20 08/17] clocksource/drivers/arm_arch_timer: Rework counter frequency detection.

On Thu, Jan 26, 2017 at 01:49:03PM +0800, Fu Wei wrote: > On 26 January 2017 at 01:25, Mark Rutland wrote: > > On Wed, Jan 25, 2017 at 02:46:12PM +0800, Fu Wei wrote: > >> On 25 January 2017 at 01:24, Mark Rutland wrote: > >> > On Wed, Jan 18, 2017 at 09:25:32PM +0800, fu@linaro.org wrote: >

[PATCH] powerpc: sort Kconfig selects under CONFIG_PPC

config PPC has a lot of selects under it. They're not sorted in any particular order, leading to merge conflicts when adding items at the end. Sort them alphabetically. Suggested-by: Michael Ellerman Signed-off-by: Andrew Donnellan --- On top of linux-next 20170130 --- arch/powerpc/Kconfig

[PATCH] xen-netfront: Delete rx_refill_timer in xennet_disconnect_backend()

rx_refill_timer should be deleted as soon as we disconnect from the backend since otherwise it is possible for the timer to go off before we get to xennet_destroy_queues(). If this happens we may dereference queue->rx.sring which is set to NULL in xennet_disconnect_backend(). Signed-off-by: Boris

Re: [RFC v2 06/10] KVM: arm/arm64: Update the physical timer interrupt level

On 30/01/17 15:02, Christoffer Dall wrote: > On Sun, Jan 29, 2017 at 03:21:06PM +, Marc Zyngier wrote: >> On Fri, Jan 27 2017 at 01:04:56 AM, Jintack Lim >> wrote: >>> Now that we maintain the EL1 physical timer register states of VMs, >>> update the physical timer

[PATCH] xen-netfront: Delete rx_refill_timer in xennet_disconnect_backend()

rx_refill_timer should be deleted as soon as we disconnect from the backend since otherwise it is possible for the timer to go off before we get to xennet_destroy_queues(). If this happens we may dereference queue->rx.sring which is set to NULL in xennet_disconnect_backend(). Signed-off-by: Boris

Re: [RFC v2 06/10] KVM: arm/arm64: Update the physical timer interrupt level

On 30/01/17 15:02, Christoffer Dall wrote: > On Sun, Jan 29, 2017 at 03:21:06PM +, Marc Zyngier wrote: >> On Fri, Jan 27 2017 at 01:04:56 AM, Jintack Lim >> wrote: >>> Now that we maintain the EL1 physical timer register states of VMs, >>> update the physical timer interrupt level along with

Re: [PATCH 0/7] Fix issues and factorize arm/arm64 capacity information code

On Mon, Jan 30, 2017 at 12:29:01PM +, Juri Lelli wrote: > I'd need more advice on this set, especially on how and if patch 6 could fly. Since you got some comments and said that you are going to fix them in the next version, I guess people are waiting for you to post a new series. --

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

From: Thierry Reding This adds a very simple framework that allows drivers to register system power and restart controllers. The goal of this framework is to replace the current notifier based mechanism for restart handlers and the power off equivalent that is the global

Re: [PATCH 0/7] Fix issues and factorize arm/arm64 capacity information code

On Mon, Jan 30, 2017 at 12:29:01PM +, Juri Lelli wrote: > I'd need more advice on this set, especially on how and if patch 6 could fly. Since you got some comments and said that you are going to fix them in the next version, I guess people are waiting for you to post a new series. --

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

From: Thierry Reding This adds a very simple framework that allows drivers to register system power and restart controllers. The goal of this framework is to replace the current notifier based mechanism for restart handlers and the power off equivalent that is the global pm_power_off() function.

Re: irq domain hierarchy vs. chaining w/ PCI MSI-X...

On 01/30/2017 05:32 AM, Thomas Gleixner wrote: On Fri, 13 Jan 2017, David Daney wrote: At the point where the handle_*_irq() functions call handle_irq_event(), we need to 9optionally) do something both immediately before and after the call to handle_irq_event(). In irq_chip add a function:

Re: irq domain hierarchy vs. chaining w/ PCI MSI-X...

On 01/30/2017 05:32 AM, Thomas Gleixner wrote: On Fri, 13 Jan 2017, David Daney wrote: At the point where the handle_*_irq() functions call handle_irq_event(), we need to 9optionally) do something both immediately before and after the call to handle_irq_event(). In irq_chip add a function:

Re: [RFC V2 12/12] mm: Tag VMA with VM_CDM flag explicitly during mbind(MPOL_BIND)

On 01/29/2017 07:35 PM, Anshuman Khandual wrote: > + if ((new_pol->mode == MPOL_BIND) > + && nodemask_has_cdm(new_pol->v.nodes)) > + set_vm_cdm(vma); So, if you did: mbind(addr, PAGE_SIZE, MPOL_BIND, all_nodes, ...); mbind(addr,

Re: [RFC V2 12/12] mm: Tag VMA with VM_CDM flag explicitly during mbind(MPOL_BIND)

On 01/29/2017 07:35 PM, Anshuman Khandual wrote: > + if ((new_pol->mode == MPOL_BIND) > + && nodemask_has_cdm(new_pol->v.nodes)) > + set_vm_cdm(vma); So, if you did: mbind(addr, PAGE_SIZE, MPOL_BIND, all_nodes, ...); mbind(addr,

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

On Mon, Jan 30, 2017 at 06:31:38PM +0100, Rabin Vincent wrote: > Would it be possible for you to please submit it as a patch yourself so > that this gets fixed in the way you like? Thank you. Sure. I'll add your Reported-by when we're done. -- Regards/Gruss, Boris. SUSE Linux GmbH, GF:

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

On Mon, Jan 30, 2017 at 06:31:38PM +0100, Rabin Vincent wrote: > Would it be possible for you to please submit it as a patch yourself so > that this gets fixed in the way you like? Thank you. Sure. I'll add your Reported-by when we're done. -- Regards/Gruss, Boris. SUSE Linux GmbH, GF:

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

* Pavel Machek [170127 11:41]: > On Fri 2017-01-27 17:23:07, Kalle Valo wrote: > > Pali Rohár writes: > > > > > On Friday 27 January 2017 14:26:22 Kalle Valo wrote: > > >> Pali Rohár writes: > > >> > > >> > 2) It was already tested

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

* Pavel Machek [170127 11:41]: > On Fri 2017-01-27 17:23:07, Kalle Valo wrote: > > Pali Rohár writes: > > > > > On Friday 27 January 2017 14:26:22 Kalle Valo wrote: > > >> Pali Rohár writes: > > >> > > >> > 2) It was already tested that example NVS data can be used for N900 > > >> > e.g. > >

Re: [PATCH v6 5/5] Documentation:powerpc: Add device-tree bindings for power-mgt

On Wed, Jan 25, 2017 at 02:06:29PM +0530, Gautham R. Shenoy wrote: > From: "Gautham R. Shenoy" > > Document the device-tree bindings defining the the properties under > the @power-mgt node in the device tree that describe the idle states > for Linux running on baremetal

Re: [PATCH v6 5/5] Documentation:powerpc: Add device-tree bindings for power-mgt

On Wed, Jan 25, 2017 at 02:06:29PM +0530, Gautham R. Shenoy wrote: > From: "Gautham R. Shenoy" > > Document the device-tree bindings defining the the properties under > the @power-mgt node in the device tree that describe the idle states > for Linux running on baremetal POWER servers. > > These

Re: [PATCH RESEND 2/5] dmaengine: Provide a wrapper for memcpy operations

Hi Vinod, On Mon, 30 Jan 2017 22:24:17 +0530 Vinod Koul wrote: > On Fri, Jan 27, 2017 at 05:42:01PM +0100, Boris Brezillon wrote: > > Almost all ->device_prep_dma_xx() methods have a wrapper defined in > > dmaengine.h. Add one for ->device_prep_dma_memcpy(). > > Looks

Re: [PATCH RESEND 2/5] dmaengine: Provide a wrapper for memcpy operations

Hi Vinod, On Mon, 30 Jan 2017 22:24:17 +0530 Vinod Koul wrote: > On Fri, Jan 27, 2017 at 05:42:01PM +0100, Boris Brezillon wrote: > > Almost all ->device_prep_dma_xx() methods have a wrapper defined in > > dmaengine.h. Add one for ->device_prep_dma_memcpy(). > > Looks good to me. > >

Re: [PATCH] Staging: omap4iss: fix coding style issues

Hello Avraham, Thank you for the patch. On Saturday 28 Jan 2017 20:00:08 Avraham Shukron wrote: > This is a patch that fixes checkpatch.pl issues in omap4iss/iss_video.c > Specifically, it fixes "line over 80 characters" issues > > Signed-off-by: Avraham Shukron

Re: [PATCH] Staging: omap4iss: fix coding style issues

Hello Avraham, Thank you for the patch. On Saturday 28 Jan 2017 20:00:08 Avraham Shukron wrote: > This is a patch that fixes checkpatch.pl issues in omap4iss/iss_video.c > Specifically, it fixes "line over 80 characters" issues > > Signed-off-by: Avraham Shukron This looks OK to me. I've

Re: [PATCH] perf/x86/intel/rapl: Rename rapl_cpu_prepare() to rapl_cpu_starting()

On 01/30/2017 11:56 AM, Thomas Gleixner wrote: On Mon, 30 Jan 2017, Yasuaki Ishimatsu wrote: Hi Thomas, Do you have any idea to fix the issue? If you have the idea, please send me the patch. Yes, I have a patch, but need to do some tests and get changelogs written. Will keep you updated.

Re: [PATCH] perf/x86/intel/rapl: Rename rapl_cpu_prepare() to rapl_cpu_starting()

On 01/30/2017 11:56 AM, Thomas Gleixner wrote: On Mon, 30 Jan 2017, Yasuaki Ishimatsu wrote: Hi Thomas, Do you have any idea to fix the issue? If you have the idea, please send me the patch. Yes, I have a patch, but need to do some tests and get changelogs written. Will keep you updated.

Re: [RFC v2 05/10] KVM: arm/arm64: Initialize the emulated EL1 physical timer

On 30/01/17 14:58, Christoffer Dall wrote: > On Sun, Jan 29, 2017 at 12:07:48PM +, Marc Zyngier wrote: >> On Fri, Jan 27 2017 at 01:04:55 AM, Jintack Lim >> wrote: >>> Initialize the emulated EL1 physical timer with the default irq number. >>> >>> Signed-off-by:

Re: [RFC v2 05/10] KVM: arm/arm64: Initialize the emulated EL1 physical timer

On 30/01/17 14:58, Christoffer Dall wrote: > On Sun, Jan 29, 2017 at 12:07:48PM +, Marc Zyngier wrote: >> On Fri, Jan 27 2017 at 01:04:55 AM, Jintack Lim >> wrote: >>> Initialize the emulated EL1 physical timer with the default irq number. >>> >>> Signed-off-by: Jintack Lim >>> --- >>>

Re: [PATCH] i2c: at91: ensure state is restored after suspending

> + at91_init_twi_bus(twi_dev); Can't this function reinit the registers to the needed values? I am not convinced that a cache will always reflect the proper state after resume. signature.asc Description: PGP signature

Re: [PATCH] i2c: at91: ensure state is restored after suspending

> + at91_init_twi_bus(twi_dev); Can't this function reinit the registers to the needed values? I am not convinced that a cache will always reflect the proper state after resume. signature.asc Description: PGP signature

Re: [RFC v2 10/10] KVM: arm/arm64: Emulate the EL1 phys timer register access

On 30/01/17 17:26, Peter Maydell wrote: > On 30 January 2017 at 17:08, Jintack Lim wrote: >> On Sun, Jan 29, 2017 at 10:44 AM, Marc Zyngier wrote: >>> Shouldn't we take the ENABLE bit into account? The ARMv8 ARM version I >>> have at hand (version

Re: [RFC v2 10/10] KVM: arm/arm64: Emulate the EL1 phys timer register access

On 30/01/17 17:26, Peter Maydell wrote: > On 30 January 2017 at 17:08, Jintack Lim wrote: >> On Sun, Jan 29, 2017 at 10:44 AM, Marc Zyngier wrote: >>> Shouldn't we take the ENABLE bit into account? The ARMv8 ARM version I >>> have at hand (version h) seems to indicate that we should, but we

[RFC 0/3] Add system power and restart framework

From: Thierry Reding Hi everyone, This series of patches proposes a small framework targetted at system power and restart drivers. Restart drivers currently use a notifier chain and there was an attempt by Guenter Roeck a while ago to move power off drivers to similar

[RFC 0/3] Add system power and restart framework

From: Thierry Reding Hi everyone, This series of patches proposes a small framework targetted at system power and restart drivers. Restart drivers currently use a notifier chain and there was an attempt by Guenter Roeck a while ago to move power off drivers to similar infrastructure[0]. That

[PATCH 1/2] iommu/vt-d: Fix some macros that are incorrectly specified in intel-iommu

From: CQ Tang Some of the macros are incorrect with wrong bit-shifts resulting in picking the incorrect invalidation granularity. Incorrect Source-ID in extended devtlb invalidation caused device side errors. To: Joerg Roedel To: David Woodhouse

[PATCH 1/2] iommu/vt-d: Fix some macros that are incorrectly specified in intel-iommu

From: CQ Tang Some of the macros are incorrect with wrong bit-shifts resulting in picking the incorrect invalidation granularity. Incorrect Source-ID in extended devtlb invalidation caused device side errors. To: Joerg Roedel To: David Woodhouse Cc: io...@lists.linux-foundation.org Cc:

[PATCH 2/2] iommu/vt-d: tylersburg isoch identity map check is done too late.

The check to set identity map for tylersburg is done too late. It needs to be done before the check for identity_map domain is done. To: Joerg Roedel To: David Woodhouse Cc: io...@lists.linux-foundation.org Cc: linux-kernel@vger.kernel.org Cc:

[PATCH 2/2] iommu/vt-d: tylersburg isoch identity map check is done too late.

The check to set identity map for tylersburg is done too late. It needs to be done before the check for identity_map domain is done. To: Joerg Roedel To: David Woodhouse Cc: io...@lists.linux-foundation.org Cc: linux-kernel@vger.kernel.org Cc: sta...@vger.kernel.org Cc: Ashok Raj Fixes:

Re: [RFC v2 02/10] KVM: arm/arm64: Move cntvoff to each timer context

On Mon, Jan 30, 2017 at 9:51 AM, Marc Zyngier wrote: > On 30/01/17 14:45, Christoffer Dall wrote: >> On Sun, Jan 29, 2017 at 11:54:05AM +, Marc Zyngier wrote: >>> On Fri, Jan 27 2017 at 01:04:52 AM, Jintack Lim >>> wrote: Make cntvoff per

Re: [RFC v2 02/10] KVM: arm/arm64: Move cntvoff to each timer context

On Mon, Jan 30, 2017 at 9:51 AM, Marc Zyngier wrote: > On 30/01/17 14:45, Christoffer Dall wrote: >> On Sun, Jan 29, 2017 at 11:54:05AM +, Marc Zyngier wrote: >>> On Fri, Jan 27 2017 at 01:04:52 AM, Jintack Lim >>> wrote: Make cntvoff per each timer context. This is helpful to abstract

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

On Fri, Jan 27, 2017 at 07:19:30PM +0100, Borislav Petkov wrote: > On Fri, Jan 27, 2017 at 04:42:30PM +0100, Rabin Vincent wrote: > > proc_dostring() eats the '\n' and stops > > Not a problem, see diff below. Would it be possible for you to please submit it as a patch yourself so that this gets

Re: [PATCH v16 3/3] usb: typec: add driver for Intel Whiskey Cove PMIC USB Type-C PHY

Hi Heikki, [auto build test WARNING on usb/usb-testing] [also build test WARNING on v4.10-rc6 next-20170130] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Heikki-Krogerus/lib-string-add

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

On Fri, Jan 27, 2017 at 07:19:30PM +0100, Borislav Petkov wrote: > On Fri, Jan 27, 2017 at 04:42:30PM +0100, Rabin Vincent wrote: > > proc_dostring() eats the '\n' and stops > > Not a problem, see diff below. Would it be possible for you to please submit it as a patch yourself so that this gets

Re: [PATCH v16 3/3] usb: typec: add driver for Intel Whiskey Cove PMIC USB Type-C PHY

Hi Heikki, [auto build test WARNING on usb/usb-testing] [also build test WARNING on v4.10-rc6 next-20170130] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Heikki-Krogerus/lib-string-add

[PATCH] usb: typec: fix ptr_ret.cocci warnings

drivers/usb/typec/typec.c:1249:1-3: WARNING: PTR_ERR_OR_ZERO can be used Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR Generated by: scripts/coccinelle/api/ptr_ret.cocci CC: Heikki Krogerus Signed-off-by: Fengguang Wu ---

[PATCH] usb: typec: fix ptr_ret.cocci warnings

drivers/usb/typec/typec.c:1249:1-3: WARNING: PTR_ERR_OR_ZERO can be used Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR Generated by: scripts/coccinelle/api/ptr_ret.cocci CC: Heikki Krogerus Signed-off-by: Fengguang Wu --- typec.c |4 +--- 1 file changed, 1 insertion(+), 3

Re: [PATCH V2] ARM: dts: BCM5301X: Add missing Netgear R8000 LEDs and Keys

On 01/30/2017 01:08 AM, Aditya Xavier wrote: > Would you require me to send the revised Patch ? > > Or would this do ? Will take care of it this time. > > And thanks for guiding me through this process :) > > >> On 29-Jan-2017, at 2:45 AM, Rafał Miłecki wrote: >> >> On 28

Re: [PATCH V2] ARM: dts: BCM5301X: Add missing Netgear R8000 LEDs and Keys

On 01/30/2017 01:08 AM, Aditya Xavier wrote: > Would you require me to send the revised Patch ? > > Or would this do ? Will take care of it this time. > > And thanks for guiding me through this process :) > > >> On 29-Jan-2017, at 2:45 AM, Rafał Miłecki wrote: >> >> On 28 January 2017 at

Re: [RFC v2 10/10] KVM: arm/arm64: Emulate the EL1 phys timer register access

Hi Peter, On Mon, Jan 30, 2017 at 12:26 PM, Peter Maydell wrote: > On 30 January 2017 at 17:08, Jintack Lim wrote: >> On Sun, Jan 29, 2017 at 10:44 AM, Marc Zyngier wrote: >>> Shouldn't we take the ENABLE bit into

Re: [PATCH 2/2] x86/fpu: copy MXCSR & MXCSR_FLAGS with SSE/YMM state

On Wed, Jan 25, 2017 at 08:57:59PM -0500, r...@redhat.com wrote: > From: Rik van Riel > > On Skylake CPUs I noticed that XRSTOR is unable to deal with states > created by copyout_from_xsaves if the xstate has only SSE/YMM state, and > no FP state. That is, xfeatures had

Re: [RFC v2 10/10] KVM: arm/arm64: Emulate the EL1 phys timer register access

Hi Peter, On Mon, Jan 30, 2017 at 12:26 PM, Peter Maydell wrote: > On 30 January 2017 at 17:08, Jintack Lim wrote: >> On Sun, Jan 29, 2017 at 10:44 AM, Marc Zyngier wrote: >>> Shouldn't we take the ENABLE bit into account? The ARMv8 ARM version I >>> have at hand (version h) seems to indicate

Re: [PATCH 2/2] x86/fpu: copy MXCSR & MXCSR_FLAGS with SSE/YMM state

On Wed, Jan 25, 2017 at 08:57:59PM -0500, r...@redhat.com wrote: > From: Rik van Riel > > On Skylake CPUs I noticed that XRSTOR is unable to deal with states > created by copyout_from_xsaves if the xstate has only SSE/YMM state, and > no FP state. That is, xfeatures had XFEATURE_MASK_SSE set,

Re: [RFC V2 03/12] mm: Change generic FALLBACK zonelist creation process

On 01/29/2017 07:35 PM, Anshuman Khandual wrote: > * CDM node's zones are not part of any other node's FALLBACK zonelist > * CDM node's FALLBACK list contains it's own memory zones followed by > all system RAM zones in regular order as before > * CDM node's zones are part of it's own NOFALLBACK

Re: [PATCH RT] Align rt_mutex inlining with upstream behavior

On Thu, Jan 26, 2017 at 06:01:09PM +0100, Sebastian Andrzej Siewior wrote: > On 2017-01-24 18:45:50 [-0800], Alex Goins wrote: > > mutex_destroy is no-op inline when DEBUG_MUTEX is not enabled. The RT Linux > > patches replace mutex_destroy() with rt_mutex_destroy(). This patch aligns > >

Re: [RFC V2 03/12] mm: Change generic FALLBACK zonelist creation process

On 01/29/2017 07:35 PM, Anshuman Khandual wrote: > * CDM node's zones are not part of any other node's FALLBACK zonelist > * CDM node's FALLBACK list contains it's own memory zones followed by > all system RAM zones in regular order as before > * CDM node's zones are part of it's own NOFALLBACK

Re: [PATCH RT] Align rt_mutex inlining with upstream behavior

On Thu, Jan 26, 2017 at 06:01:09PM +0100, Sebastian Andrzej Siewior wrote: > On 2017-01-24 18:45:50 [-0800], Alex Goins wrote: > > mutex_destroy is no-op inline when DEBUG_MUTEX is not enabled. The RT Linux > > patches replace mutex_destroy() with rt_mutex_destroy(). This patch aligns > >

Re: [PATCH RESEND] staging: media: lirc: use new parport device model

On Sat, Jan 21, 2017 at 12:55:54AM +, Sudip Mukherjee wrote: > From: Sudip Mukherjee > > Modify lirc_parallel driver to use the new parallel port device model. > > Signed-off-by: Sudip Mukherjee > --- > > Resending after

Re: [PATCH RESEND] staging: media: lirc: use new parport device model

On Sat, Jan 21, 2017 at 12:55:54AM +, Sudip Mukherjee wrote: > From: Sudip Mukherjee > > Modify lirc_parallel driver to use the new parallel port device model. > > Signed-off-by: Sudip Mukherjee > --- > > Resending after more than one year. > Prevoius patch is at

Re: [PATCH 11/22] ARM: dts: add top-level DT bindings for Cortina Gemini

On Sat, Jan 28, 2017 at 3:56 PM, Linus Walleij wrote: > On Mon, Jan 23, 2017 at 9:21 PM, Rob Herring wrote: >> On Sun, Jan 22, 2017 at 01:22:19PM +0100, Linus Walleij wrote: >>> This adds the top level SoC bindings for Cortina systems Gemini >>>

Re: [PATCH 11/22] ARM: dts: add top-level DT bindings for Cortina Gemini

On Sat, Jan 28, 2017 at 3:56 PM, Linus Walleij wrote: > On Mon, Jan 23, 2017 at 9:21 PM, Rob Herring wrote: >> On Sun, Jan 22, 2017 at 01:22:19PM +0100, Linus Walleij wrote: >>> This adds the top level SoC bindings for Cortina systems Gemini >>> platforms. > (...) >>> +- intcon: the root node

Re: linux-next: manual merge of the gpio tree with the staging tree

On Mon, Jan 30, 2017 at 5:28 AM, Stephen Rothwell wrote: > I fixed it up (see below) and can carry the fix as necessary. This > is now fixed as far as linux-next is concerned, but any non trivial > conflicts should be mentioned to your upstream maintainer when your tree >

Re: linux-next: manual merge of the gpio tree with the staging tree

On Mon, Jan 30, 2017 at 5:28 AM, Stephen Rothwell wrote: > I fixed it up (see below) and can carry the fix as necessary. This > is now fixed as far as linux-next is concerned, but any non trivial > conflicts should be mentioned to your upstream maintainer when your tree > is submitted for

[GIT PULL rcu/next] RCU commits for 4.11

Hello, Ingo, This pull request contains the following changes: 1. Documentation updates. http://lkml.kernel.org/r/20170114085032.ga18...@linux.vnet.ibm.com 2. Dyntick updates, consolidating open-coded counter accesses into a well-defined API.

[GIT PULL rcu/next] RCU commits for 4.11

Hello, Ingo, This pull request contains the following changes: 1. Documentation updates. http://lkml.kernel.org/r/20170114085032.ga18...@linux.vnet.ibm.com 2. Dyntick updates, consolidating open-coded counter accesses into a well-defined API.

Re: [PATCH 8/9] bcache: use kvmalloc

On Mon 30-01-17 17:47:31, Vlastimil Babka wrote: > On 01/30/2017 10:49 AM, Michal Hocko wrote: > > From: Michal Hocko > > > > bcache_device_init uses kmalloc for small requests and vmalloc for those > > which are larger than 64 pages. This alone is a strange criterion. > >

Re: [PATCH 8/9] bcache: use kvmalloc

On Mon 30-01-17 17:47:31, Vlastimil Babka wrote: > On 01/30/2017 10:49 AM, Michal Hocko wrote: > > From: Michal Hocko > > > > bcache_device_init uses kmalloc for small requests and vmalloc for those > > which are larger than 64 pages. This alone is a strange criterion. > > Moreover kmalloc can

Re: [PATCH 04/14] x86/fpu: Remove 'kbuf' parameter from the copy_xstate_to_user() APIs

On Mon, Jan 30, 2017 at 04:45:21PM +0100, Borislav Petkov wrote: > On Mon, Jan 30, 2017 at 10:57:28AM +0100, Ingo Molnar wrote: > > Would anyone object to using u32 in these prototypes? > > Well, would there be any disadvantage to forcing them to u32? > Potentially by something else wanting to

Re: [PATCH 04/14] x86/fpu: Remove 'kbuf' parameter from the copy_xstate_to_user() APIs

On Mon, Jan 30, 2017 at 04:45:21PM +0100, Borislav Petkov wrote: > On Mon, Jan 30, 2017 at 10:57:28AM +0100, Ingo Molnar wrote: > > Would anyone object to using u32 in these prototypes? > > Well, would there be any disadvantage to forcing them to u32? > Potentially by something else wanting to

[PATCH] i2c: at91: ensure state is restored after suspending

When going to suspend, the I2C registers may be lost because the power to VDDcore is cut. Save them and restore them when resuming. Signed-off-by: Alexandre Belloni --- drivers/i2c/busses/i2c-at91.c | 24 1 file changed, 24

[PATCH] i2c: at91: ensure state is restored after suspending

When going to suspend, the I2C registers may be lost because the power to VDDcore is cut. Save them and restore them when resuming. Signed-off-by: Alexandre Belloni --- drivers/i2c/busses/i2c-at91.c | 24 1 file changed, 24 insertions(+) diff --git

Re: [RFC v2 10/10] KVM: arm/arm64: Emulate the EL1 phys timer register access

On 30 January 2017 at 17:08, Jintack Lim wrote: > On Sun, Jan 29, 2017 at 10:44 AM, Marc Zyngier wrote: >> Shouldn't we take the ENABLE bit into account? The ARMv8 ARM version I >> have at hand (version h) seems to indicate that we should, but we

Re: [RFC v2 10/10] KVM: arm/arm64: Emulate the EL1 phys timer register access

On 30 January 2017 at 17:08, Jintack Lim wrote: > On Sun, Jan 29, 2017 at 10:44 AM, Marc Zyngier wrote: >> Shouldn't we take the ENABLE bit into account? The ARMv8 ARM version I >> have at hand (version h) seems to indicate that we should, but we should >> check with the latest and greatest... >

[RFC 3/3] PM / hibernate: Wire up system-power framework

From: Thierry Reding Use the system-power framework's equivalent to test for power off capability instead of relying on the globally defined pm_power_off() function pointer. The system-power framework implements a fallback that relies on this global function in case no

[RFC 3/3] PM / hibernate: Wire up system-power framework

From: Thierry Reding Use the system-power framework's equivalent to test for power off capability instead of relying on the globally defined pm_power_off() function pointer. The system-power framework implements a fallback that relies on this global function in case no system power chips have

[PATCH 2/2] watchdog: sama5d4: Implement resume hook

When resuming for the deepest state on sama5d2, it is necessary to restore MR as the registers are lost. Signed-off-by: Alexandre Belloni --- drivers/watchdog/sama5d4_wdt.c | 17 + 1 file changed, 17 insertions(+) diff --git

Re: [PATCH v8 07/12] dt-bindings: i2c: i2c-mux-simple: document i2c-mux-simple bindings

On Sat, Jan 28, 2017 at 4:42 PM, Peter Rosin wrote: > On 2017-01-27 20:39, Rob Herring wrote: >> On Wed, Jan 18, 2017 at 04:57:10PM +0100, Peter Rosin wrote: >>> Describe how a generic multiplexer controller is used to mux an i2c bus. >>> >>> Acked-by: Jonathan Cameron

[PATCH 2/2] watchdog: sama5d4: Implement resume hook

When resuming for the deepest state on sama5d2, it is necessary to restore MR as the registers are lost. Signed-off-by: Alexandre Belloni --- drivers/watchdog/sama5d4_wdt.c | 17 + 1 file changed, 17 insertions(+) diff --git a/drivers/watchdog/sama5d4_wdt.c

Re: [PATCH v8 07/12] dt-bindings: i2c: i2c-mux-simple: document i2c-mux-simple bindings

On Sat, Jan 28, 2017 at 4:42 PM, Peter Rosin wrote: > On 2017-01-27 20:39, Rob Herring wrote: >> On Wed, Jan 18, 2017 at 04:57:10PM +0100, Peter Rosin wrote: >>> Describe how a generic multiplexer controller is used to mux an i2c bus. >>> >>> Acked-by: Jonathan Cameron >>> Signed-off-by: Peter

[PATCH 1/2] watchdog: sama5d4: Cache MR instead of a partial config

.config is used to cache a part of WDT_MR at probe time and is not used afterwards. Instead of doing that, actually cache MR and avoid reading it every time it is modified. Signed-off-by: Alexandre Belloni --- drivers/watchdog/sama5d4_wdt.c | 45

[PATCH 1/2] watchdog: sama5d4: Cache MR instead of a partial config

.config is used to cache a part of WDT_MR at probe time and is not used afterwards. Instead of doing that, actually cache MR and avoid reading it every time it is modified. Signed-off-by: Alexandre Belloni --- drivers/watchdog/sama5d4_wdt.c | 45 ++ 1

Re: [PATCH 09/14] x86/fpu: Change 'size_total' parameter to unsigned and standardize the size checks in copy_xstate_to_*()

On Thu, Jan 26, 2017 at 11:22:54AM +0100, Ingo Molnar wrote: > 'size_total' is derived from an unsigned input parameter - and then converted > to 'int' and checked for negative ranges: > > if (size_total < 0 || offset < size_total) { > > This conversion and the checks are unnecessary

Re: [PATCH 09/14] x86/fpu: Change 'size_total' parameter to unsigned and standardize the size checks in copy_xstate_to_*()

On Thu, Jan 26, 2017 at 11:22:54AM +0100, Ingo Molnar wrote: > 'size_total' is derived from an unsigned input parameter - and then converted > to 'int' and checked for negative ranges: > > if (size_total < 0 || offset < size_total) { > > This conversion and the checks are unnecessary

Re: [PATCH 9/9] net, bpf: use kvzalloc helper

Andrew, please ignore this one. On Mon 30-01-17 10:49:40, Michal Hocko wrote: > From: Michal Hocko > > both bpf_map_area_alloc and xt_alloc_table_info try really hard to > play nicely with large memory requests which can be triggered from > the userspace (by an admin). See

Re: [RFC V2 02/12] mm: Isolate HugeTLB allocations away from CDM nodes

On 01/29/2017 07:35 PM, Anshuman Khandual wrote: > HugeTLB allocation/release/accounting currently spans across all the nodes > under N_MEMORY node mask. Coherent memory nodes should not be part of these > allocations. So use system_ram() call to fetch system RAM only nodes on the > platform which

<    6   7   8   9   10   11   12   13   14   15   >