[PATCH 1/4] bcache: bch_writeback_thread() is not freezable

From: Jiri Kosina bch_writeback_thread() is calling try_to_freeze(), but that's just an expensive no-op given the fact that the thread is not marked freezable. I/O helper kthreads, exactly such as the bcache writeback thread, actually shouldn't be freezable, because they are

[RFC][PATCH 0/3] spin_unlock_wait and assorted borkage

As per recent discussions spin_unlock_wait() has an unintuitive 'feature'. lkml.kernel.org/r/20160520053926.gc31...@linux-uzut.site These patches pull the existing solution into generic code; annotate all spin_unlock_wait() users and fix nf_conntrack more. The alternative -- putting

Re: [RFC PATCH 2/2] lightnvm: Append device name to target name

It's fine to allow the user to define a device name as long as hold the global lock and link the targets into a global list but that may against the idea to move the target management into media mgr. 2016-05-24 22:17 GMT+08:00 Matias Bjørling : > On 05/23/2016 03:31 PM, Wenwei

[RFC][PATCH 3/3] locking,netfilter: Fix nf_conntrack_lock()

nf_conntrack_lock{,_all}() is borken as it misses a bunch of memory barriers to order the whole global vs local locks scheme. Even x86 (and other TSO archs) are affected. Signed-off-by: Peter Zijlstra (Intel) --- net/netfilter/nf_conntrack_core.c | 30

Re: [RFC PATCH] usb: gadget: Introduce Cadence USB2 UDC Driver

Hi, (please break lines at 80-columns and don't top-post ;) Neil Armstrong writes: > [ Unknown signature status ] > Hi Felipe, Laurent, > > I submitted this driver for a Cadence IP library from a now abandoned > project. > > The driver was working on a SoC platform

[PATCH 4/4] MAINTAINERS: mark bcache as orphan

The submitted patches are not being reacted upon, and Jens is only picking up stable fixes on an rather ad-hoc basis. Link: lkml.kernel.org/r/574462c5.40...@kernel.dk Signed-off-by: Jiri Kosina --- MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 1/4] bcache: bch_writeback_thread() is not freezable

From: Jiri Kosina bch_writeback_thread() is calling try_to_freeze(), but that's just an expensive no-op given the fact that the thread is not marked freezable. I/O helper kthreads, exactly such as the bcache writeback thread, actually shouldn't be freezable, because they are potentially

[RFC][PATCH 0/3] spin_unlock_wait and assorted borkage

As per recent discussions spin_unlock_wait() has an unintuitive 'feature'. lkml.kernel.org/r/20160520053926.gc31...@linux-uzut.site These patches pull the existing solution into generic code; annotate all spin_unlock_wait() users and fix nf_conntrack more. The alternative -- putting

Re: [RFC PATCH 2/2] lightnvm: Append device name to target name

It's fine to allow the user to define a device name as long as hold the global lock and link the targets into a global list but that may against the idea to move the target management into media mgr. 2016-05-24 22:17 GMT+08:00 Matias Bjørling : > On 05/23/2016 03:31 PM, Wenwei Tao wrote: >> >>

[RFC][PATCH 3/3] locking,netfilter: Fix nf_conntrack_lock()

nf_conntrack_lock{,_all}() is borken as it misses a bunch of memory barriers to order the whole global vs local locks scheme. Even x86 (and other TSO archs) are affected. Signed-off-by: Peter Zijlstra (Intel) --- net/netfilter/nf_conntrack_core.c | 30 +- 1 file

Re: [RFC PATCH] usb: gadget: Introduce Cadence USB2 UDC Driver

Hi, (please break lines at 80-columns and don't top-post ;) Neil Armstrong writes: > [ Unknown signature status ] > Hi Felipe, Laurent, > > I submitted this driver for a Cadence IP library from a now abandoned > project. > > The driver was working on a SoC platform ported on a FPGA, but I do >

[PATCH 4/4] MAINTAINERS: mark bcache as orphan

The submitted patches are not being reacted upon, and Jens is only picking up stable fixes on an rather ad-hoc basis. Link: lkml.kernel.org/r/574462c5.40...@kernel.dk Signed-off-by: Jiri Kosina --- MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MAINTAINERS

Re: [PATCH V7 00/11] Support for generic ACPI based PCI host controller

Hi Gabriele, all, On 05/24/2016 03:23 AM, Gabriele Paoloni wrote: >> Sorry Gab, I guess I was really responding to earlier messages :) >> >> I don't really have much to say here, except that it doesn't seem >> right to have an MCFG that describes a non-standard ECAM mapping. > > The ACPI table

[RFC][PATCH 2/3] locking: Annotate spin_unlock_wait() users

spin_unlock_wait() has an unintuitive 'feature' in that it doesn't fully serialize against the spin_unlock() we've waited on. In particular, spin_unlock_wait() only provides a control dependency, which is a LOAD->STORE order. This means subsequent loads can creep up and observe state prior to the

Re: [PATCH V7 00/11] Support for generic ACPI based PCI host controller

Hi Gabriele, all, On 05/24/2016 03:23 AM, Gabriele Paoloni wrote: >> Sorry Gab, I guess I was really responding to earlier messages :) >> >> I don't really have much to say here, except that it doesn't seem >> right to have an MCFG that describes a non-standard ECAM mapping. > > The ACPI table

[RFC][PATCH 2/3] locking: Annotate spin_unlock_wait() users

spin_unlock_wait() has an unintuitive 'feature' in that it doesn't fully serialize against the spin_unlock() we've waited on. In particular, spin_unlock_wait() only provides a control dependency, which is a LOAD->STORE order. This means subsequent loads can creep up and observe state prior to the

RE: [PATCH V7 00/11] Support for generic ACPI based PCI host controller

Hi Jon > -Original Message- > From: Jon Masters [mailto:j...@redhat.com] > Sent: 24 May 2016 02:11 > To: Bjorn Helgaas > Cc: Gabriele Paoloni; Lorenzo Pieralisi; Ard Biesheuvel; Tomasz > Nowicki; a...@arndb.de; will.dea...@arm.com; catalin.mari...@arm.com; > raf...@kernel.org;

RE: [PATCH V7 00/11] Support for generic ACPI based PCI host controller

Hi Jon > -Original Message- > From: Jon Masters [mailto:j...@redhat.com] > Sent: 24 May 2016 02:11 > To: Bjorn Helgaas > Cc: Gabriele Paoloni; Lorenzo Pieralisi; Ard Biesheuvel; Tomasz > Nowicki; a...@arndb.de; will.dea...@arm.com; catalin.mari...@arm.com; > raf...@kernel.org;

RE: [PATCH RFC kernel] balloon: speed up inflating/deflating process

> > > > > This can be pre-initialized, correct? > > > > > > > > pre-initialized? I am not quite understand your mean. > > > > > > I think you can maintain sg as part of device state and init sg with the > bitmap. > > > > > > > I got it. > > > > > > > This is grossly inefficient if you only

RE: [PATCH RFC kernel] balloon: speed up inflating/deflating process

> > > > > This can be pre-initialized, correct? > > > > > > > > pre-initialized? I am not quite understand your mean. > > > > > > I think you can maintain sg as part of device state and init sg with the > bitmap. > > > > > > > I got it. > > > > > > > This is grossly inefficient if you only

Re: [PATCH] ibmvscsis: Initial commit of IBM VSCSI Tgt Driver

On Tue, May 24, 2016 at 08:52:58AM -0500, Bryant G. Ly wrote: > From: bgly Really? Please go get a proper review from the other internal IBM developers to fix this, and the other obvious problems with your patch, before you send it publically and force us to tell you these

Re: [PATCH] ibmvscsis: Initial commit of IBM VSCSI Tgt Driver

On Tue, May 24, 2016 at 08:52:58AM -0500, Bryant G. Ly wrote: > From: bgly Really? Please go get a proper review from the other internal IBM developers to fix this, and the other obvious problems with your patch, before you send it publically and force us to tell you these things... thanks,

[PATCH v3] drm/i915/ilk: Don't disable SSC source if it's in use

Thanks to Ville Syrjälä for pointing me towards the cause of this issue. Unfortunately one of the sideaffects of having the refclk for a DPLL set to SSC is that as long as it's set to SSC, the GPU will prevent us from powering down any of the pipes or transcoders using it. A couple of BIOSes

[PATCH v3] drm/i915/ilk: Don't disable SSC source if it's in use

Thanks to Ville Syrjälä for pointing me towards the cause of this issue. Unfortunately one of the sideaffects of having the refclk for a DPLL set to SSC is that as long as it's set to SSC, the GPU will prevent us from powering down any of the pipes or transcoders using it. A couple of BIOSes

[PATCH v5] platform:x86: Add PMC Driver for Intel Core SoC

This patch adds the Power Management Controller driver as a pci driver for Intel Core SoC architecture. This driver can utilize debugging capabilities and supported features as exposed by the Power Management Controller. Please refer to the below specification for more details on PMC features.

[PATCH v5] platform:x86: Add PMC Driver for Intel Core SoC

This patch adds the Power Management Controller driver as a pci driver for Intel Core SoC architecture. This driver can utilize debugging capabilities and supported features as exposed by the Power Management Controller. Please refer to the below specification for more details on PMC features.

Re: [PATCH] NVMe: Only release requested regions

On Tue, May 24, 2016 at 02:19:17AM -0700, Christoph Hellwig wrote: > On Tue, May 24, 2016 at 11:15:52AM +0200, Johannes Thumshirn wrote: > > As I've probably missed v4.7, is it possible to get it for v4.8? > > Or should I take on the PCI helper functions Christoph suggested first? > > Let's get

Re: [PATCH] NVMe: Only release requested regions

On Tue, May 24, 2016 at 02:19:17AM -0700, Christoph Hellwig wrote: > On Tue, May 24, 2016 at 11:15:52AM +0200, Johannes Thumshirn wrote: > > As I've probably missed v4.7, is it possible to get it for v4.8? > > Or should I take on the PCI helper functions Christoph suggested first? > > Let's get

Re: [PATCH] usb: core: add debugobjects support for urb object

On Tue, 24 May 2016 changbin...@intel.com wrote: > From: "Du, Changbin" > > Add debugobject support to track the life time of struct urb. > This feature help us detect violation of urb operations by > generating a warning message from debugobject core. I'm pretty sure

Re: [PATCH] usb: core: add debugobjects support for urb object

On Tue, 24 May 2016 changbin...@intel.com wrote: > From: "Du, Changbin" > > Add debugobject support to track the life time of struct urb. > This feature help us detect violation of urb operations by > generating a warning message from debugobject core. I'm pretty sure the USB core already does

Re: [PATCH] bcache: bch_writeback_thread() is not freezable

On Tue, 24 May 2016, Jens Axboe wrote: > > Ok, I call it officially ridiculous now. I guess I'll be resending through > > akpm. > > You can just send it to me, I've funneled bcache stable fixes before. > > > Is it a time to claim (by MAINTAINERS entry) the in-tree bcache orphaned? > > I think

Re: [PATCH] bcache: bch_writeback_thread() is not freezable

On Tue, 24 May 2016, Jens Axboe wrote: > > Ok, I call it officially ridiculous now. I guess I'll be resending through > > akpm. > > You can just send it to me, I've funneled bcache stable fixes before. > > > Is it a time to claim (by MAINTAINERS entry) the in-tree bcache orphaned? > > I think

Re: [PATCH] bcache: bch_writeback_thread() is not freezable

On 05/23/2016 05:05 PM, Jiri Kosina wrote: On Wed, 18 May 2016, Jiri Kosina wrote: bch_writeback_thread() is calling try_to_freeze(), but that's just an expensive no-op given the fact that the thread is not marked freezable. I/O helper kthreads, exactly such as the bcache writeback thread,

Re: [PATCH] bcache: bch_writeback_thread() is not freezable

On 05/23/2016 05:05 PM, Jiri Kosina wrote: On Wed, 18 May 2016, Jiri Kosina wrote: bch_writeback_thread() is calling try_to_freeze(), but that's just an expensive no-op given the fact that the thread is not marked freezable. I/O helper kthreads, exactly such as the bcache writeback thread,

Re: [PATCHv2 2/3] drm/imx: convey the pixelclk-active and de-active flags from DT to the ipu-di driver

Hi Lothar, thank you for rebasing. I have applied the other two patches. With this one, I'd like to avoid the duplicated code. See below: Am Dienstag, den 24.05.2016, 08:31 +0200 schrieb Lothar Waßmann: > Currently these flags are lost in the call > drm_display_mode_from_videomode() > >

Re: [PATCHv2 2/3] drm/imx: convey the pixelclk-active and de-active flags from DT to the ipu-di driver

Hi Lothar, thank you for rebasing. I have applied the other two patches. With this one, I'd like to avoid the duplicated code. See below: Am Dienstag, den 24.05.2016, 08:31 +0200 schrieb Lothar Waßmann: > Currently these flags are lost in the call > drm_display_mode_from_videomode() > >

Re: [RFC PATCH 2/2] lightnvm: Append device name to target name

On 05/23/2016 03:31 PM, Wenwei Tao wrote: Eh.. my lock patch can only prevent concurrent creation of the same name target on the same backend device, not the concurrent creation of same name target on different backend devices, since target management is protect by per device's gn->lock not the

Re: [RFC PATCH 2/2] lightnvm: Append device name to target name

On 05/23/2016 03:31 PM, Wenwei Tao wrote: Eh.. my lock patch can only prevent concurrent creation of the same name target on the same backend device, not the concurrent creation of same name target on different backend devices, since target management is protect by per device's gn->lock not the

Re: [RFC PATCH] usb: gadget: Introduce Cadence USB2 UDC Driver

Hi Felipe, Laurent, I submitted this driver for a Cadence IP library from a now abandoned project. The driver was working on a SoC platform ported on a FPGA, but I do not have access to this HW anymore. But I have a fixed version... Now, I am looking for SoCs, vendors and even Cadence people

Re: [RFC PATCH] usb: gadget: Introduce Cadence USB2 UDC Driver

Hi Felipe, Laurent, I submitted this driver for a Cadence IP library from a now abandoned project. The driver was working on a SoC platform ported on a FPGA, but I do not have access to this HW anymore. But I have a fixed version... Now, I am looking for SoCs, vendors and even Cadence people

Re: [PATCH] ibmvscsis: Initial commit of IBM VSCSI Tgt Driver

On Tue, 2016-05-24 at 08:52 -0500, Bryant G. Ly wrote: > From: bgly > > This initial commit contains WIP of the IBM VSCSI Target Fabric > Module. It currently supports read/writes, and I have tested > the ability to create a file backstore with the driver and install > RHEL VIA

Re: [PATCH] ibmvscsis: Initial commit of IBM VSCSI Tgt Driver

On Tue, 2016-05-24 at 08:52 -0500, Bryant G. Ly wrote: > From: bgly > > This initial commit contains WIP of the IBM VSCSI Target Fabric > Module. It currently supports read/writes, and I have tested > the ability to create a file backstore with the driver and install > RHEL VIA NIM and then boot

can't boot with reiserfs on linux-4.6.0+

Seems to break after index 348619f..d55dc5a 100644 Boot up with ext4 works, but try anything to access anything on the reiser partition such as "/mnt/bin/passwd" resulted in the following ... [ 93.380353] BUG: unable to handle kernel NULL pointer dereference at (null) [ 93.380924]

can't boot with reiserfs on linux-4.6.0+

Seems to break after index 348619f..d55dc5a 100644 Boot up with ext4 works, but try anything to access anything on the reiser partition such as "/mnt/bin/passwd" resulted in the following ... [ 93.380353] BUG: unable to handle kernel NULL pointer dereference at (null) [ 93.380924]

Re: [PATCH] arm64: defconfig: Enable cros-ec and battery driver

Hi Rhyland, On 03/05/16 16:45, Rhyland Klein wrote: > Enable the ChromeOS Embedded Controller, its I2C tunnel driver, and > the BA27XXX battery driver. These are all used on the Tegra210 Smaug > platform. > > Signed-off-by: Rhyland Klein I tried booting with this patch with

Re: [PATCH] arm64: defconfig: Enable cros-ec and battery driver

Hi Rhyland, On 03/05/16 16:45, Rhyland Klein wrote: > Enable the ChromeOS Embedded Controller, its I2C tunnel driver, and > the BA27XXX battery driver. These are all used on the Tegra210 Smaug > platform. > > Signed-off-by: Rhyland Klein I tried booting with this patch with next-20160523 on

Re: v4.6 kernel BUG at mm/rmap.c:1101!

On Tue, May 24, 2016 at 11:12:23AM +0300, Mika Westerberg wrote: > Hmm, the kernel shipped with Fedora 23 has that enabled: > > lahna % grep CONFIG_DEBUG_VM /boot/config-4.4.9-300.fc23.x86_64 > CONFIG_DEBUG_VM=y > # CONFIG_DEBUG_VM_VMACACHE is not set > # CONFIG_DEBUG_VM_RB is not set Yes, it

Re: v4.6 kernel BUG at mm/rmap.c:1101!

On Tue, May 24, 2016 at 11:12:23AM +0300, Mika Westerberg wrote: > Hmm, the kernel shipped with Fedora 23 has that enabled: > > lahna % grep CONFIG_DEBUG_VM /boot/config-4.4.9-300.fc23.x86_64 > CONFIG_DEBUG_VM=y > # CONFIG_DEBUG_VM_VMACACHE is not set > # CONFIG_DEBUG_VM_RB is not set Yes, it

Re: [PATCH 1/2] drm/exynos: g2d: Add support for old S5Pv210 type

Hello Krzysztof, are you sure that these are the only differences. Because AFAIK there are quite a few more: - DMA submission of commands - blend mode / rounding - solid fill - YCrCb support - and probably more One would need to add least split the command list parser into a v3 and v41 version

Re: [PATCH 1/2] drm/exynos: g2d: Add support for old S5Pv210 type

Hello Krzysztof, are you sure that these are the only differences. Because AFAIK there are quite a few more: - DMA submission of commands - blend mode / rounding - solid fill - YCrCb support - and probably more One would need to add least split the command list parser into a v3 and v41 version

Re: [PATCH 1/2] drm/exynos: g2d: Add support for old S5Pv210 type

On 05/24/2016 03:49 PM, Tobias Jakobi wrote: > Hello Krzysztof, > > are you sure that these are the only differences. Because AFAIK there > are quite a few more: > - DMA submission of commands > - blend mode / rounding > - solid fill > - YCrCb support > - and probably more > > One would need to

Re: [PATCH 1/2] drm/exynos: g2d: Add support for old S5Pv210 type

On 05/24/2016 03:49 PM, Tobias Jakobi wrote: > Hello Krzysztof, > > are you sure that these are the only differences. Because AFAIK there > are quite a few more: > - DMA submission of commands > - blend mode / rounding > - solid fill > - YCrCb support > - and probably more > > One would need to

Re: [PATCH] mm: oom_kill_process: do not abort if the victim is exiting

On Tue 24-05-16 15:24:02, Vladimir Davydov wrote: > After selecting an oom victim, we first check if it's already exiting > and if it is, we don't bother killing tasks sharing its mm. We do try to > reap its mm though, but we abort if any of the processes sharing it is > still alive. This might

Re: [PATCH] mm: oom_kill_process: do not abort if the victim is exiting

On Tue 24-05-16 15:24:02, Vladimir Davydov wrote: > After selecting an oom victim, we first check if it's already exiting > and if it is, we don't bother killing tasks sharing its mm. We do try to > reap its mm though, but we abort if any of the processes sharing it is > still alive. This might

Re: [PATCH 3.12 00/76] 3.12.60-stable review

On 05/24/2016, 02:58 PM, Shuah Khan wrote: > On 05/19/2016 03:08 AM, Jiri Slaby wrote: >> This is the start of the stable review cycle for the 3.12.60 release. >> There are 76 patches in this series, all will be posted as a response >> to this one. If anyone has any issues with these being

Re: [PATCH 3.12 00/76] 3.12.60-stable review

On 05/24/2016, 02:58 PM, Shuah Khan wrote: > On 05/19/2016 03:08 AM, Jiri Slaby wrote: >> This is the start of the stable review cycle for the 3.12.60 release. >> There are 76 patches in this series, all will be posted as a response >> to this one. If anyone has any issues with these being

[PATCH] ibmvscsis: Initial commit of IBM VSCSI Tgt Driver

From: bgly This initial commit contains WIP of the IBM VSCSI Target Fabric Module. It currently supports read/writes, and I have tested the ability to create a file backstore with the driver and install RHEL VIA NIM and then boot up the partition via filio backstore through the

[PATCH] ibmvscsis: Initial commit of IBM VSCSI Tgt Driver

From: bgly This initial commit contains WIP of the IBM VSCSI Target Fabric Module. It currently supports read/writes, and I have tested the ability to create a file backstore with the driver and install RHEL VIA NIM and then boot up the partition via filio backstore through the driver.

Re: [PATCH 06/16] sched: Disable WAKE_AFFINE for asymmetric configurations

On 24 May 2016 at 15:36, Morten Rasmussen wrote: > On Tue, May 24, 2016 at 03:27:05PM +0200, Vincent Guittot wrote: >> On 24 May 2016 at 15:16, Morten Rasmussen wrote: >> > On Tue, May 24, 2016 at 02:12:38PM +0200, Vincent Guittot wrote: >> >>

Re: [PATCH 06/16] sched: Disable WAKE_AFFINE for asymmetric configurations

On 24 May 2016 at 15:36, Morten Rasmussen wrote: > On Tue, May 24, 2016 at 03:27:05PM +0200, Vincent Guittot wrote: >> On 24 May 2016 at 15:16, Morten Rasmussen wrote: >> > On Tue, May 24, 2016 at 02:12:38PM +0200, Vincent Guittot wrote: >> >> On 24 May 2016 at 12:29, Morten Rasmussen >> >>

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

On 05/19/2016 05:44 AM, Heikki Krogerus wrote: The purpose of this class is to provide unified interface for user space to get the status and basic information about USB Type-C Connectors in the system, control data role swapping, and when USB PD is available, also power role swapping and

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

On 05/19/2016 05:44 AM, Heikki Krogerus wrote: The purpose of this class is to provide unified interface for user space to get the status and basic information about USB Type-C Connectors in the system, control data role swapping, and when USB PD is available, also power role swapping and

[tip:irq/urgent] genirq: Fix missing return value in irq_destroy_ipi()

Commit-ID: 59fa5860204ffc95128d60cba9f54f9740a42c7d Gitweb: http://git.kernel.org/tip/59fa5860204ffc95128d60cba9f54f9740a42c7d Author: Matt Redfearn AuthorDate: Tue, 24 May 2016 11:42:30 +0100 Committer: Thomas Gleixner CommitDate: Tue, 24

[tip:irq/urgent] genirq: Fix missing return value in irq_destroy_ipi()

Commit-ID: 59fa5860204ffc95128d60cba9f54f9740a42c7d Gitweb: http://git.kernel.org/tip/59fa5860204ffc95128d60cba9f54f9740a42c7d Author: Matt Redfearn AuthorDate: Tue, 24 May 2016 11:42:30 +0100 Committer: Thomas Gleixner CommitDate: Tue, 24 May 2016 15:40:14 +0200 genirq: Fix missing

Re: modify_irte NULL pointer

On Sun, 22 May 2016, Wanpeng Li wrote: > [ 39.98] BUG: unable to handle kernel NULL pointer dereference > at (null) > [ 39.988494] IP: [] modify_irte+0x58/0x140 > [ 39.996939] PGD cede3067 PUD 2d790067 PMD 0 > [ 40.004087] Oops: [#1] SMP > > This can be reproduced by

Re: modify_irte NULL pointer

On Sun, 22 May 2016, Wanpeng Li wrote: > [ 39.98] BUG: unable to handle kernel NULL pointer dereference > at (null) > [ 39.988494] IP: [] modify_irte+0x58/0x140 > [ 39.996939] PGD cede3067 PUD 2d790067 PMD 0 > [ 40.004087] Oops: [#1] SMP > > This can be reproduced by

[PATCH 0/3] ARM: OMAP: DRA7: Update to latest TRM and cleanup

Hi, Here are the final(hopefully) pending patches for DRA7 based on recent TRM updates. Updates include removing retention support on L3init and L4per as per latest SoC updates. Test Log: X15 (no modules): http://pastebin.ubuntu.com/16655027/ Latest TRM (rev F):

[PATCH 0/3] ARM: OMAP: DRA7: Update to latest TRM and cleanup

Hi, Here are the final(hopefully) pending patches for DRA7 based on recent TRM updates. Updates include removing retention support on L3init and L4per as per latest SoC updates. Test Log: X15 (no modules): http://pastebin.ubuntu.com/16655027/ Latest TRM (rev F):

[PATCH] MAINTAINERS: ASoC: samsung: Add Sylwester Nawrocki and Krzysztof Kozlowski

Extend maintainer entry for Samsung SoC sound drivers with Krzysztof Kozlowski and Sylwester Nawrocki. The file pattern is duplicated in main Exynos ARM section so remove it from there. Cc: Kukjin Kim Cc: Sangbeom Kim Cc: Sylwester Nawrocki

[PATCH] MAINTAINERS: ASoC: samsung: Add Sylwester Nawrocki and Krzysztof Kozlowski

Extend maintainer entry for Samsung SoC sound drivers with Krzysztof Kozlowski and Sylwester Nawrocki. The file pattern is duplicated in main Exynos ARM section so remove it from there. Cc: Kukjin Kim Cc: Sangbeom Kim Cc: Sylwester Nawrocki Cc: Liam Girdwood Cc: Mark Brown Cc:

Re: [PATCH 06/16] sched: Disable WAKE_AFFINE for asymmetric configurations

On Tue, May 24, 2016 at 03:27:05PM +0200, Vincent Guittot wrote: > On 24 May 2016 at 15:16, Morten Rasmussen wrote: > > On Tue, May 24, 2016 at 02:12:38PM +0200, Vincent Guittot wrote: > >> On 24 May 2016 at 12:29, Morten Rasmussen wrote: > >>

Re: [PATCH 06/16] sched: Disable WAKE_AFFINE for asymmetric configurations

On Tue, May 24, 2016 at 03:27:05PM +0200, Vincent Guittot wrote: > On 24 May 2016 at 15:16, Morten Rasmussen wrote: > > On Tue, May 24, 2016 at 02:12:38PM +0200, Vincent Guittot wrote: > >> On 24 May 2016 at 12:29, Morten Rasmussen wrote: > >> > On Tue, May 24, 2016 at 11:10:28AM +0200, Vincent

[GIT PULL] arch/nios2 update for 4.7

Hi Linus Here is nios2 update for v4.7. Please consider pulling. Regards Ley Foon The following changes since commit 2dcd0af568b0cf583645c8a317dd12e344b1c72a: Linux 4.6 (2016-05-15 15:43:13 -0700) are available in the git repository at:

[GIT PULL] arch/nios2 update for 4.7

Hi Linus Here is nios2 update for v4.7. Please consider pulling. Regards Ley Foon The following changes since commit 2dcd0af568b0cf583645c8a317dd12e344b1c72a: Linux 4.6 (2016-05-15 15:43:13 -0700) are available in the git repository at:

[PATCH v5 2/6] clocksource/drivers/arm_arch_timer: Add a new enum for spi type

From: Fu Wei This patch add a new enum "spi_nr" and use it in the driver. Just for code's readability, no functional change. Signed-off-by: Fu Wei --- drivers/clocksource/arm_arch_timer.c | 4 ++-- include/clocksource/arm_arch_timer.h | 6 ++ 2 files

[PATCH v5 2/6] clocksource/drivers/arm_arch_timer: Add a new enum for spi type

From: Fu Wei This patch add a new enum "spi_nr" and use it in the driver. Just for code's readability, no functional change. Signed-off-by: Fu Wei --- drivers/clocksource/arm_arch_timer.c | 4 ++-- include/clocksource/arm_arch_timer.h | 6 ++ 2 files changed, 8 insertions(+), 2

[PATCH v5 3/6] clocksource/drivers/arm_arch_timer: Improve printk relevant code

From: Fu Wei This patch defines pr_fmt(fmt) for all pr_* functions, then the pr_* don't need to add "arch_timer:" everytime. Also delete some Blank Spaces in arch_timer_banner, according to the suggestion from checkpatch.pl. No functional change. Signed-off-by: Fu Wei

[PATCH v5 6/6] clocksource/drivers/arm_arch_timer: Add GTDT support for memory-mapped timer

From: Fu Wei The patch add memory-mapped timer register support by using the information provided by the new GTDT driver of ACPI. Signed-off-by: Fu Wei --- drivers/clocksource/arm_arch_timer.c | 147 +-- 1 file changed, 142

[PATCH v5 5/6] clocksource/drivers/arm_arch_timer: Simplify ACPI support code.

From: Fu Wei The patch update arm_arch_timer driver to use the function provided by the new GTDT driver of ACPI. By this way, arm_arch_timer.c can be simplified, and separate all the ACPI GTDT knowledge from this timer driver. Signed-off-by: Fu Wei

[PATCH v5 5/6] clocksource/drivers/arm_arch_timer: Simplify ACPI support code.

From: Fu Wei The patch update arm_arch_timer driver to use the function provided by the new GTDT driver of ACPI. By this way, arm_arch_timer.c can be simplified, and separate all the ACPI GTDT knowledge from this timer driver. Signed-off-by: Fu Wei Signed-off-by: Hanjun Guo ---

[PATCH v5 3/6] clocksource/drivers/arm_arch_timer: Improve printk relevant code

From: Fu Wei This patch defines pr_fmt(fmt) for all pr_* functions, then the pr_* don't need to add "arch_timer:" everytime. Also delete some Blank Spaces in arch_timer_banner, according to the suggestion from checkpatch.pl. No functional change. Signed-off-by: Fu Wei ---

[PATCH v5 6/6] clocksource/drivers/arm_arch_timer: Add GTDT support for memory-mapped timer

From: Fu Wei The patch add memory-mapped timer register support by using the information provided by the new GTDT driver of ACPI. Signed-off-by: Fu Wei --- drivers/clocksource/arm_arch_timer.c | 147 +-- 1 file changed, 142 insertions(+), 5 deletions(-) diff

[PATCH v5 4/6] acpi: Add GTDT table parse driver into ACPI driver

From: Fu Wei This driver adds support for parsing all kinds of timer in GTDT: (1)arch timer: provide a kernel API to parse all the PPIs and always-on info in GTDT and export them by filling the structs which provided by parameters(pointer of them). (2)memory-mapped timer:

Re: [PATCH] drm: rcar-du: EPROBE_DEFER case doesn't need error message

Hi Morimoto-san, Thank you for the patch. On Tuesday 24 May 2016 14:24:09 Kuninori Morimoto wrote: > From: Kuninori Morimoto > > EPROBE_DEFER is not error, thus, error message on kernel log on this > case is confusable for user. Prints it only error cases. >

[PATCH v5 4/6] acpi: Add GTDT table parse driver into ACPI driver

From: Fu Wei This driver adds support for parsing all kinds of timer in GTDT: (1)arch timer: provide a kernel API to parse all the PPIs and always-on info in GTDT and export them by filling the structs which provided by parameters(pointer of them). (2)memory-mapped timer: provide a kernel APIs

Re: [PATCH] drm: rcar-du: EPROBE_DEFER case doesn't need error message

Hi Morimoto-san, Thank you for the patch. On Tuesday 24 May 2016 14:24:09 Kuninori Morimoto wrote: > From: Kuninori Morimoto > > EPROBE_DEFER is not error, thus, error message on kernel log on this > case is confusable for user. Prints it only error cases. > > Signed-off-by: Kuninori Morimoto

[PATCH 3/3] ARM: OMAP: DRA7: powerdomain data: Remove unused pwrsts_mem_ret

As per the latest revision F of public TRM for DRA7/AM57xx SoCs SPRUHZ6F[1] (April 2016), with the exception of MPU power domain, all other power domains do not have memories capable of retention since they all operate in either "ON" or "OFF" mode. For these power states, the retention state for

[PATCH 2/3] ARM: OMAP: DRA7: powerdomain data: Remove unused pwrsts_logic_ret

As per the latest revision F of public TRM for DRA7/AM57xx SoCs SPRUHZ6F[1] (April 2016), with the exception of MPU power domain (and CPUx sub power domains), all other power domains can either operate in "ON" mode OR in some cases, "OFF" mode. For these power states, the logic retention state is

[PATCH 3/3] ARM: OMAP: DRA7: powerdomain data: Remove unused pwrsts_mem_ret

As per the latest revision F of public TRM for DRA7/AM57xx SoCs SPRUHZ6F[1] (April 2016), with the exception of MPU power domain, all other power domains do not have memories capable of retention since they all operate in either "ON" or "OFF" mode. For these power states, the retention state for

[PATCH 2/3] ARM: OMAP: DRA7: powerdomain data: Remove unused pwrsts_logic_ret

As per the latest revision F of public TRM for DRA7/AM57xx SoCs SPRUHZ6F[1] (April 2016), with the exception of MPU power domain (and CPUx sub power domains), all other power domains can either operate in "ON" mode OR in some cases, "OFF" mode. For these power states, the logic retention state is

[PATCH 1/3] ARM: OMAP: DRA7: powerdomain data: Set L3init and L4per to ON

As per the latest revision F of public TRM for DRA7/AM57xx SoCs SPRUHZ6F[1] (April 2016), L4Per and L3init power domains now operate in always "ON" mode due to asymmetric aging limitations. Update the same [1] http://www.ti.com/lit/pdf/spruhz6 Signed-off-by: Nishanth Menon ---

[PATCH 1/3] ARM: OMAP: DRA7: powerdomain data: Set L3init and L4per to ON

As per the latest revision F of public TRM for DRA7/AM57xx SoCs SPRUHZ6F[1] (April 2016), L4Per and L3init power domains now operate in always "ON" mode due to asymmetric aging limitations. Update the same [1] http://www.ti.com/lit/pdf/spruhz6 Signed-off-by: Nishanth Menon ---

[PATCH v5 0/6] acpi, clocksource: add GTDT driver and GTDT support in arm_arch_timer

From: Fu Wei This patchset: (1)Preparation for adding GTDT support in arm_arch_timer 1. Move some enums and marcos to header file 2. Add a new enum for spi type. 3. Improve printk relevant code (2)Introduce ACPI GTDT parser: drivers/acpi/gtdt.c

[PATCH v5 0/6] acpi, clocksource: add GTDT driver and GTDT support in arm_arch_timer

From: Fu Wei This patchset: (1)Preparation for adding GTDT support in arm_arch_timer 1. Move some enums and marcos to header file 2. Add a new enum for spi type. 3. Improve printk relevant code (2)Introduce ACPI GTDT parser: drivers/acpi/gtdt.c Parse all

[PATCH v5 1/6] clocksource/drivers/arm_arch_timer: Move enums and defines to header file

From: Fu Wei To support the arm_arch_timer via ACPI we need to share defines and enums between the driver and the ACPI parser code. Split out the relevant defines and enums into arm_arch_timer.h. No functional change. Signed-off-by: Fu Wei ---

[PATCH v5 1/6] clocksource/drivers/arm_arch_timer: Move enums and defines to header file

From: Fu Wei To support the arm_arch_timer via ACPI we need to share defines and enums between the driver and the ACPI parser code. Split out the relevant defines and enums into arm_arch_timer.h. No functional change. Signed-off-by: Fu Wei --- drivers/clocksource/arm_arch_timer.c | 11

[PATCH] gpio: core: Do not call get_direction in atomic context for sleeping gpio

When adding the gpiochip, the GPIO HW drivers' callback get_direction() get called in atomic context. Some of the GPIO HW drivers can sleep when accessing the register and hence it can create the sleeping call in atomic context. Call get_direction() in non-atomic context from gpiochip_add() if

[PATCH] gpio: core: Do not call get_direction in atomic context for sleeping gpio

When adding the gpiochip, the GPIO HW drivers' callback get_direction() get called in atomic context. Some of the GPIO HW drivers can sleep when accessing the register and hence it can create the sleeping call in atomic context. Call get_direction() in non-atomic context from gpiochip_add() if

[PATCH 1/2] drm/exynos: g2d: Add support for old S5Pv210 type

The non-DRM s5p-g2d driver supports two versions of G2D: v3.0 on S5Pv210 and v4.x on Exynos 4x12 (or newer). The driver for 3.0 device version is doing two things differently: 1. Before starting the render process, it invalidates caches (pattern, source buffer and mask buffer). Cache control is

[PATCH 1/2] drm/exynos: g2d: Add support for old S5Pv210 type

The non-DRM s5p-g2d driver supports two versions of G2D: v3.0 on S5Pv210 and v4.x on Exynos 4x12 (or newer). The driver for 3.0 device version is doing two things differently: 1. Before starting the render process, it invalidates caches (pattern, source buffer and mask buffer). Cache control is

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