[QUEUED v20160408 07/18] stm class: Fix stm device initialization order

Currently, stm_register_device() makes the device visible and then proceeds to initializing spinlocks and other properties, which leaves a window when the device can already be opened but is not yet fully operational. Fix this by reversing the initialization order. Reported-by: Alan Cox

[QUEUED v20160408 03/18] stm class: dummy_stm: Make nr_dummies parameter read-only

Changing nr_dummies after the module has been loaded doesn't actually change anything, so just make it read-only. Reported-by: Alan Cox Signed-off-by: Alexander Shishkin --- drivers/hwtracing/stm/dummy_stm.c | 14 +- 1 file changed, 5 insertions(+), 9 deletions(-) diff --git

[QUEUED v20160408 07/18] stm class: Fix stm device initialization order

Currently, stm_register_device() makes the device visible and then proceeds to initializing spinlocks and other properties, which leaves a window when the device can already be opened but is not yet fully operational. Fix this by reversing the initialization order. Reported-by: Alan Cox

[QUEUED v20160408 04/18] stm class: stm_heartbeat: Make nr_devs parameter read-only

Changing nr_devs after the module has been loaded doesn't actually change anything, so just make it read-only. Reported-by: Alan Cox Signed-off-by: Alexander Shishkin --- drivers/hwtracing/stm/heartbeat.c | 14 +- 1 file changed, 5 insertions(+), 9 deletions(-) diff --git

[QUEUED v20160408 10/18] intel_th: msu: Handle kstrndup() failure

Currently, the nr_pages attribute store does not check if kstrndup() succeeded. Fix this. Reported-by: Alan Cox Signed-off-by: Alexander Shishkin --- drivers/hwtracing/intel_th/msu.c | 5 + 1 file changed, 5 insertions(+) diff --git

[QUEUED v20160408 16/18] intel_th: Hold output driver module reference while capture is active

Right now it's possible to unload the output subdevice's driver while the capture to this output is active. Prevent this by holding the output driver's module reference. Signed-off-by: Alexander Shishkin --- drivers/hwtracing/intel_th/core.c | 5 + 1 file

[QUEUED v20160408 10/18] intel_th: msu: Handle kstrndup() failure

Currently, the nr_pages attribute store does not check if kstrndup() succeeded. Fix this. Reported-by: Alan Cox Signed-off-by: Alexander Shishkin --- drivers/hwtracing/intel_th/msu.c | 5 + 1 file changed, 5 insertions(+) diff --git a/drivers/hwtracing/intel_th/msu.c

[QUEUED v20160408 16/18] intel_th: Hold output driver module reference while capture is active

Right now it's possible to unload the output subdevice's driver while the capture to this output is active. Prevent this by holding the output driver's module reference. Signed-off-by: Alexander Shishkin --- drivers/hwtracing/intel_th/core.c | 5 + 1 file changed, 5 insertions(+) diff

Re: [PATCH 2/2] localmodconfig: Reset certificate paths

On Sat, Apr 02, 2016 at 10:55:22AM -0700, Benjamin Poirier wrote: > When using `make localmodconfig` and friends, if the input config comes > from a kernel that was built in a different environment (for example, the > canonical case of using localmodconfig to trim a distribution kernel > config)

[QUEUED v20160408 15/18] intel_th: msu: Serialize enabling/disabling

In order to guarantee that readers don't race with trace enabling, both should happen under the same mutex. Having two mutexes seems like an overkill, considering that because of the above, they'll have to be acquired together, around trace enabling and char device opening. This patch makes both

Re: [PATCH 2/2] localmodconfig: Reset certificate paths

On Sat, Apr 02, 2016 at 10:55:22AM -0700, Benjamin Poirier wrote: > When using `make localmodconfig` and friends, if the input config comes > from a kernel that was built in a different environment (for example, the > canonical case of using localmodconfig to trim a distribution kernel > config)

[QUEUED v20160408 15/18] intel_th: msu: Serialize enabling/disabling

In order to guarantee that readers don't race with trace enabling, both should happen under the same mutex. Having two mutexes seems like an overkill, considering that because of the above, they'll have to be acquired together, around trace enabling and char device opening. This patch makes both

Re: [PATCH] scripts: Fallback to KBUILD_OUTPUT if O is not specified

Em Fri, Apr 08, 2016 at 11:14:09AM +0200, Thierry Reding escreveu: > From: Thierry Reding > > The KBUILD_OUTPUT environment can be used to set the build directory as > an alternative to passing the O variable on the command-line. This works > with regular kernel builds, so

Re: [PATCH 1/2] localmodconfig: Fix parsing of Kconfig "source" statements

On Sat, Apr 02, 2016 at 10:55:21AM -0700, Benjamin Poirier wrote: > The parameter of Kconfig "source" statements does not need to be quoted. > The current regex causes many kconfig files to be skipped and hence, > dependencies to be missed. > > Also fix the whitespace repeat count. > >

Re: [PATCH] scripts: Fallback to KBUILD_OUTPUT if O is not specified

Em Fri, Apr 08, 2016 at 11:14:09AM +0200, Thierry Reding escreveu: > From: Thierry Reding > > The KBUILD_OUTPUT environment can be used to set the build directory as > an alternative to passing the O variable on the command-line. This works > with regular kernel builds, so it's surprising if it

Re: [PATCH 1/2] localmodconfig: Fix parsing of Kconfig "source" statements

On Sat, Apr 02, 2016 at 10:55:21AM -0700, Benjamin Poirier wrote: > The parameter of Kconfig "source" statements does not need to be quoted. > The current regex causes many kconfig files to be skipped and hence, > dependencies to be missed. > > Also fix the whitespace repeat count. > >

[QUEUED v20160408 17/18] intel_th: msu: Set fops::owner to prevent module from unloading

Right now it's possible to unload the msu driver while its character device is open. Prevent it by setting fops::owner, which will result in the module reference being held while the device node is open. Signed-off-by: Alexander Shishkin ---

[QUEUED v20160408 18/18] intel_th: msu: Release resources on removal

Do release the resources when msu subdevice gets removed: stop the capture if it is active (which is still possible even though the module in pinned) and free the capture buffers. Signed-off-by: Alexander Shishkin --- drivers/hwtracing/intel_th/msu.c | 12

[QUEUED v20160408 13/18] intel_th: pti: Create sysfs attributes using core driver's facility

The core intel_th driver allows subdevices to bring in their sysfs attributes. Use this instead of taking care of them in probe and remove. Signed-off-by: Alexander Shishkin --- drivers/hwtracing/intel_th/pti.c | 7 +-- 1 file changed, 1 insertion(+), 6

[QUEUED v20160408 17/18] intel_th: msu: Set fops::owner to prevent module from unloading

Right now it's possible to unload the msu driver while its character device is open. Prevent it by setting fops::owner, which will result in the module reference being held while the device node is open. Signed-off-by: Alexander Shishkin --- drivers/hwtracing/intel_th/msu.c | 1 + 1 file

[QUEUED v20160408 18/18] intel_th: msu: Release resources on removal

Do release the resources when msu subdevice gets removed: stop the capture if it is active (which is still possible even though the module in pinned) and free the capture buffers. Signed-off-by: Alexander Shishkin --- drivers/hwtracing/intel_th/msu.c | 12 1 file changed, 12

[QUEUED v20160408 13/18] intel_th: pti: Create sysfs attributes using core driver's facility

The core intel_th driver allows subdevices to bring in their sysfs attributes. Use this instead of taking care of them in probe and remove. Signed-off-by: Alexander Shishkin --- drivers/hwtracing/intel_th/pti.c | 7 +-- 1 file changed, 1 insertion(+), 6 deletions(-) diff --git

[QUEUED v20160408 00/18] stm class/intel_th: Patches in my queue

Hi everybody, These are the patches that I have in my queue for the next merge window at the moment. They can also be found in a git tree [1] or via cgit [2], branch stm-dev. Let me know what you think. [1] git://git.kernel.org/pub/scm/linux/kernel/git/ash/stm.git [2]

[QUEUED v20160408 02/18] stm class: Fix integer boundary checks for master range

From: Chunyan Zhang Master IDs are of unsigned int type, yet in the configfs policy code we're validating user's input against INT_MAX. This is both pointless and misleading as the real limits are imposed by the stm device's [sw_start..sw_end] (which are also limited by

[QUEUED v20160408 02/18] stm class: Fix integer boundary checks for master range

From: Chunyan Zhang Master IDs are of unsigned int type, yet in the configfs policy code we're validating user's input against INT_MAX. This is both pointless and misleading as the real limits are imposed by the stm device's [sw_start..sw_end] (which are also limited by the spec to be no larger

[QUEUED v20160408 00/18] stm class/intel_th: Patches in my queue

Hi everybody, These are the patches that I have in my queue for the next merge window at the moment. They can also be found in a git tree [1] or via cgit [2], branch stm-dev. Let me know what you think. [1] git://git.kernel.org/pub/scm/linux/kernel/git/ash/stm.git [2]

[QUEUED v20160408 06/18] stm class: Do not leak the chrdev in error path

Currently, the error path of stm_register_device() forgets to unregister the chrdev. Fix this. Reported-by: Alan Cox Signed-off-by: Alexander Shishkin --- drivers/hwtracing/stm/core.c | 2 ++ 1 file changed, 2 insertions(+) diff --git

[QUEUED v20160408 05/18] stm class: Remove a pointless line

No point in explicitly setting something to zero right after we explicitly checked that it is zero. Fix this. Reported-by: Alan Cox Signed-off-by: Alexander Shishkin --- drivers/hwtracing/stm/core.c | 2 -- 1 file changed, 2 deletions(-)

[QUEUED v20160408 09/18] intel_th: pti: Do remove sysfs group on device removal

Right now, the PTI output driver forgets to clean up its sysfs group when it gets removed. Fix this. Reported-by: Alan Cox Signed-off-by: Alexander Shishkin --- drivers/hwtracing/intel_th/pti.c | 1 + 1 file changed, 1 insertion(+) diff

[QUEUED v20160408 14/18] intel_th: Fix activating a subdevice without a driver

If output subdevice driver is not loaded, activating it will try to call its ->activate method and crash. Fix this by explicitly checking for the driver. Signed-off-by: Alexander Shishkin --- drivers/hwtracing/intel_th/core.c | 12 ++--

[QUEUED v20160408 11/18] intel_th: Allow subdevice drivers to bring in own attribute groups

Some subdevices (MSU, PTI) need to register their own driver-specific attribute groups. Provide a way for those to pass their attribute groups to the core driver in their driver structure so that the core can take care of creating and removing them. Signed-off-by: Alexander Shishkin

[QUEUED v20160408 01/18] MAINTAINERS: Add a git tree for the stm class

So that people know where their patches go. Signed-off-by: Alexander Shishkin --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS b/MAINTAINERS index 03e00c7c88..4b511b25d1 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -9742,6

[QUEUED v20160408 06/18] stm class: Do not leak the chrdev in error path

Currently, the error path of stm_register_device() forgets to unregister the chrdev. Fix this. Reported-by: Alan Cox Signed-off-by: Alexander Shishkin --- drivers/hwtracing/stm/core.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/hwtracing/stm/core.c

[QUEUED v20160408 05/18] stm class: Remove a pointless line

No point in explicitly setting something to zero right after we explicitly checked that it is zero. Fix this. Reported-by: Alan Cox Signed-off-by: Alexander Shishkin --- drivers/hwtracing/stm/core.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/hwtracing/stm/core.c

[QUEUED v20160408 09/18] intel_th: pti: Do remove sysfs group on device removal

Right now, the PTI output driver forgets to clean up its sysfs group when it gets removed. Fix this. Reported-by: Alan Cox Signed-off-by: Alexander Shishkin --- drivers/hwtracing/intel_th/pti.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/hwtracing/intel_th/pti.c

[QUEUED v20160408 14/18] intel_th: Fix activating a subdevice without a driver

If output subdevice driver is not loaded, activating it will try to call its ->activate method and crash. Fix this by explicitly checking for the driver. Signed-off-by: Alexander Shishkin --- drivers/hwtracing/intel_th/core.c | 12 ++-- drivers/hwtracing/intel_th/intel_th.h | 3 +++

[QUEUED v20160408 11/18] intel_th: Allow subdevice drivers to bring in own attribute groups

Some subdevices (MSU, PTI) need to register their own driver-specific attribute groups. Provide a way for those to pass their attribute groups to the core driver in their driver structure so that the core can take care of creating and removing them. Signed-off-by: Alexander Shishkin ---

[QUEUED v20160408 01/18] MAINTAINERS: Add a git tree for the stm class

So that people know where their patches go. Signed-off-by: Alexander Shishkin --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS b/MAINTAINERS index 03e00c7c88..4b511b25d1 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -9742,6 +9742,7 @@ F:

[QUEUED v20160408 12/18] intel_th: msu: Create sysfs attributes using core driver's facility

The core intel_th driver allows subdevices to bring in their sysfs attributes. Use this instead of taking care of them in probe and remove. Signed-off-by: Alexander Shishkin --- drivers/hwtracing/intel_th/msu.c | 6 +- 1 file changed, 1 insertion(+), 5

[QUEUED v20160408 12/18] intel_th: msu: Create sysfs attributes using core driver's facility

The core intel_th driver allows subdevices to bring in their sysfs attributes. Use this instead of taking care of them in probe and remove. Signed-off-by: Alexander Shishkin --- drivers/hwtracing/intel_th/msu.c | 6 +- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git

Re: Odroid XU4 deadlock

Hello Anand, On 04/08/2016 09:51 AM, Anand Moon wrote: > Hi All, > > I am observing this deadlock or warning on my Odroid XU4. > I thinks the is related to clk from exynos5_i2c_xfer clk_prepare_enable > but I am not able to figure out which clk. > By reading your logs, it seems the problem

Re: Odroid XU4 deadlock

Hello Anand, On 04/08/2016 09:51 AM, Anand Moon wrote: > Hi All, > > I am observing this deadlock or warning on my Odroid XU4. > I thinks the is related to clk from exynos5_i2c_xfer clk_prepare_enable > but I am not able to figure out which clk. > By reading your logs, it seems the problem

Re: [BUG] lib: zram lz4 compression/decompression still broken on big endian

2016-04-07 15:07 GMT+01:00 Sergey Senozhatsky : > On (04/07/16 13:33), Rui Salvaterra wrote: > [..] >> Hi again, Sergey > > Hello, > >> Thanks for the patch, I'll test it as soon as possible. I agree with >> your second option, usually one selects lz4 when (especially

Re: [BUG] lib: zram lz4 compression/decompression still broken on big endian

2016-04-07 15:07 GMT+01:00 Sergey Senozhatsky : > On (04/07/16 13:33), Rui Salvaterra wrote: > [..] >> Hi again, Sergey > > Hello, > >> Thanks for the patch, I'll test it as soon as possible. I agree with >> your second option, usually one selects lz4 when (especially >> decompression) speed is

Re: [PATCH RT 4/6] rt/locking: Reenable migration accross schedule

On 04/08/2016 04:16 PM, Mike Galbraith wrote: >> okay. and how did you trigger this? Just Steven's script or was there >> more to it? > > I run stockfish, futextest, hackbench and tbench with it, terminating > and restarting them at random intervals just to make sure nobody gets > into a

Re: [PATCH RT 4/6] rt/locking: Reenable migration accross schedule

On 04/08/2016 04:16 PM, Mike Galbraith wrote: >> okay. and how did you trigger this? Just Steven's script or was there >> more to it? > > I run stockfish, futextest, hackbench and tbench with it, terminating > and restarting them at random intervals just to make sure nobody gets > into a

[ANNOUNCE] v4.4.6-rt14

[ANNOUNCE] 4.4.6-rt14 Dear RT folks! I'm pleased to announce the v4.4.6-rt14 patch set. Changes since v4.4.6-rt13: - Dan Murphy reported that zram does not compile on !RT. Now it does. - The TWD timer is now enabled on IMX6Q configs even with !SMP. People with i.MX6SOLO should now see better

[ANNOUNCE] v4.4.6-rt14

[ANNOUNCE] 4.4.6-rt14 Dear RT folks! I'm pleased to announce the v4.4.6-rt14 patch set. Changes since v4.4.6-rt13: - Dan Murphy reported that zram does not compile on !RT. Now it does. - The TWD timer is now enabled on IMX6Q configs even with !SMP. People with i.MX6SOLO should now see better

Re: [PATCH] MAINTAINERS: Update email address

Andrew, If no one else grabs this, can you pull this change in through your tree. Thanks! -- Steve On Thu, 31 Mar 2016 22:33:23 +0900 mhira...@kernel.org wrote: > From: Masami Hiramatsu > > Since Masami Hiramatsu moves to Linaro, this old address doesn't > work

Re: [PATCH] MAINTAINERS: Update email address

Andrew, If no one else grabs this, can you pull this change in through your tree. Thanks! -- Steve On Thu, 31 Mar 2016 22:33:23 +0900 mhira...@kernel.org wrote: > From: Masami Hiramatsu > > Since Masami Hiramatsu moves to Linaro, this old address doesn't > work anymore. I'll use

[PATCH] [linux-next] clk:st: Fix typo in st,clkgen.txt

This patch fix typos in st,clkgen.txt Signed-off-by: Masanari Iida --- Documentation/devicetree/bindings/clock/st/st,clkgen.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/devicetree/bindings/clock/st/st,clkgen.txt

[PATCH] [linux-next] clk:st: Fix typo in st,clkgen.txt

This patch fix typos in st,clkgen.txt Signed-off-by: Masanari Iida --- Documentation/devicetree/bindings/clock/st/st,clkgen.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/devicetree/bindings/clock/st/st,clkgen.txt

Re: [PATCH 07/17] kvm-arm: arm32: Introduce stage2 page table helpers

On 08/04/16 13:43, Christoffer Dall wrote: On Mon, Apr 04, 2016 at 05:26:07PM +0100, Suzuki K Poulose wrote: Define the page table helpers for walking the stage2 pagetable for arm. Since both hyp and stage2 have the same number of levels, as that of the host we reuse the host helpers. The

Re: [PATCH 07/17] kvm-arm: arm32: Introduce stage2 page table helpers

On 08/04/16 13:43, Christoffer Dall wrote: On Mon, Apr 04, 2016 at 05:26:07PM +0100, Suzuki K Poulose wrote: Define the page table helpers for walking the stage2 pagetable for arm. Since both hyp and stage2 have the same number of levels, as that of the host we reuse the host helpers. The

Re: [RFC PATCH v1.9 05/14] sched: horrible way to detect whether a task has been preempted

On Fri, Apr 08, 2016 at 10:07:10AM +0200, Petr Mladek wrote: > On Thu 2016-04-07 09:34:03, Josh Poimboeuf wrote: > > On Thu, Apr 07, 2016 at 11:47:00AM +0200, Petr Mladek wrote: > > > On Wed 2016-04-06 11:33:56, Josh Poimboeuf wrote: > > > > On Wed, Apr 06, 2016 at 03:06:19PM +0200, Petr Mladek

Re: [RFC PATCH v1.9 05/14] sched: horrible way to detect whether a task has been preempted

On Fri, Apr 08, 2016 at 10:07:10AM +0200, Petr Mladek wrote: > On Thu 2016-04-07 09:34:03, Josh Poimboeuf wrote: > > On Thu, Apr 07, 2016 at 11:47:00AM +0200, Petr Mladek wrote: > > > On Wed 2016-04-06 11:33:56, Josh Poimboeuf wrote: > > > > On Wed, Apr 06, 2016 at 03:06:19PM +0200, Petr Mladek

Re: sched: horrible way to detect whether a task has been preempted

On Fri, Apr 08, 2016 at 10:03:04AM +0200, Petr Mladek wrote: > On Fri 2016-04-08 09:05:28, Jiri Kosina wrote: > > On Thu, 7 Apr 2016, Jessica Yu wrote: > > > > > > Alternatively, without eating up a TIF_ space, it'd be possible to push > > > > a > > > > magic contents on top of the stack in

Re: sched: horrible way to detect whether a task has been preempted

On Fri, Apr 08, 2016 at 10:03:04AM +0200, Petr Mladek wrote: > On Fri 2016-04-08 09:05:28, Jiri Kosina wrote: > > On Thu, 7 Apr 2016, Jessica Yu wrote: > > > > > > Alternatively, without eating up a TIF_ space, it'd be possible to push > > > > a > > > > magic contents on top of the stack in

Re: [PATCH v3] ARM64: ACPI: Update documentation for latest specification version

On 04/08/2016 07:12 AM, Will Deacon wrote: > On Thu, Apr 07, 2016 at 03:50:55PM -0600, Al Stone wrote: >> On 03/28/2016 06:06 PM, Al Stone wrote: >>> The ACPI 6.1 specification was recently released at the end of January >>> 2016, but the arm64 kernel documentation for the use of ACPI was written

Re: [PATCH v3] ARM64: ACPI: Update documentation for latest specification version

On 04/08/2016 07:12 AM, Will Deacon wrote: > On Thu, Apr 07, 2016 at 03:50:55PM -0600, Al Stone wrote: >> On 03/28/2016 06:06 PM, Al Stone wrote: >>> The ACPI 6.1 specification was recently released at the end of January >>> 2016, but the arm64 kernel documentation for the use of ACPI was written

[git pull] IOMMU Fixes for Linux v4.6-rc2

Hi Linus, The following changes since commit 9735a22799b9214d17d3c231fe377fc852f042e9: Linux 4.6-rc2 (2016-04-03 09:09:40 -0500) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v4.6-rc2 for you to fetch changes up to

[git pull] IOMMU Fixes for Linux v4.6-rc2

Hi Linus, The following changes since commit 9735a22799b9214d17d3c231fe377fc852f042e9: Linux 4.6-rc2 (2016-04-03 09:09:40 -0500) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git tags/iommu-fixes-v4.6-rc2 for you to fetch changes up to

RE: [PATCH] ARM: dts: r8a7791: Don't disable referenced optional clocks

Hi, On 07 April 2016 20:14, Sergei Shtylyov wrote: > On 04/07/2016 10:00 AM, Sjoerd Simons wrote: > > > Hey Sergei, > > > > Thanks for your review. > > You're welcome. :-) > > > On Thu, 2016-04-07 at 02:15 +0300, Sergei Shtylyov wrote: > >> On 04/06/2016 03:52 PM, Sjoerd Simons wrote: > >>

RE: [PATCH] ARM: dts: r8a7791: Don't disable referenced optional clocks

Hi, On 07 April 2016 20:14, Sergei Shtylyov wrote: > On 04/07/2016 10:00 AM, Sjoerd Simons wrote: > > > Hey Sergei, > > > > Thanks for your review. > > You're welcome. :-) > > > On Thu, 2016-04-07 at 02:15 +0300, Sergei Shtylyov wrote: > >> On 04/06/2016 03:52 PM, Sjoerd Simons wrote: > >>

Re: [Xen-devel] HVMLite / PVHv2 - using x86 EFI boot entry

On 07/04/16 19:51, Luis R. Rodriguez wrote: > While Andrew's position is right in that perhaps only Xen tools have to deal > with the HVMLite specific entry, it would also still mean diverging from ARM's > own EFI entry only position, which I'd like to clarify that ARM has no custom > Xen entry,

Re: [Xen-devel] HVMLite / PVHv2 - using x86 EFI boot entry

On 07/04/16 19:51, Luis R. Rodriguez wrote: > While Andrew's position is right in that perhaps only Xen tools have to deal > with the HVMLite specific entry, it would also still mean diverging from ARM's > own EFI entry only position, which I'd like to clarify that ARM has no custom > Xen entry,

Re: [PATCH RT 4/6] rt/locking: Reenable migration accross schedule

On Fri, 2016-04-08 at 15:58 +0200, Sebastian Andrzej Siewior wrote: > On 04/08/2016 03:44 PM, Mike Galbraith wrote: > > On Thu, 2016-04-07 at 18:47 +0200, Sebastian Andrzej Siewior wrote: > > > > > just to be clear: The patch I attached did _not_ work for you. > > > > Did you perchance mean with

Re: [PATCH RT 4/6] rt/locking: Reenable migration accross schedule

On Fri, 2016-04-08 at 15:58 +0200, Sebastian Andrzej Siewior wrote: > On 04/08/2016 03:44 PM, Mike Galbraith wrote: > > On Thu, 2016-04-07 at 18:47 +0200, Sebastian Andrzej Siewior wrote: > > > > > just to be clear: The patch I attached did _not_ work for you. > > > > Did you perchance mean with

Re: [PATCH] i2c: designware: do not disable adapter after transfer

On 2016-04-07 19:28, De Marchi, Lucas wrote: > Hi Christian, > > On Thu, 2016-04-07 at 15:37 +0200, Christian Ruppert wrote: >> Dear Lucas, >> >> Sorry for the late reply but I had to put our test environment back >> together to check this patch. I'll keep it around for a while in case >> you

Re: [PATCH] i2c: designware: do not disable adapter after transfer

On 2016-04-07 19:28, De Marchi, Lucas wrote: > Hi Christian, > > On Thu, 2016-04-07 at 15:37 +0200, Christian Ruppert wrote: >> Dear Lucas, >> >> Sorry for the late reply but I had to put our test environment back >> together to check this patch. I'll keep it around for a while in case >> you

Re: [PATCH] usb: core: buffer: avoid NULL pointer dereferrence

On Fri, Apr 08, 2016 at 05:08:03PM +0800, Chunfeng Yun wrote: > NULL pointer dereferrence will happen when class driver > wants to allocate zero length buffer and pool_max[0] > can't be used, so skip reserved pool in this case. Why would a driver want to allocate a 0 length buffer? What driver

Re: [PATCH] usb: core: buffer: avoid NULL pointer dereferrence

On Fri, Apr 08, 2016 at 05:08:03PM +0800, Chunfeng Yun wrote: > NULL pointer dereferrence will happen when class driver > wants to allocate zero length buffer and pool_max[0] > can't be used, so skip reserved pool in this case. Why would a driver want to allocate a 0 length buffer? What driver

Re: [PATCH v9 04/13] task_isolation: add initial support

On Wed, Mar 09, 2016 at 02:39:28PM -0500, Chris Metcalf wrote: > Frederic, > > Thanks for the detailed feedback on the task isolation stuff. > > This reply kind of turned into an essay, so I've added a little "TL;DR" > sentence before each section. I think I'm going to cut my reply into several

Re: [PATCH v9 04/13] task_isolation: add initial support

On Wed, Mar 09, 2016 at 02:39:28PM -0500, Chris Metcalf wrote: > Frederic, > > Thanks for the detailed feedback on the task isolation stuff. > > This reply kind of turned into an essay, so I've added a little "TL;DR" > sentence before each section. I think I'm going to cut my reply into several

Re: [PATCH RT 4/6] rt/locking: Reenable migration accross schedule

On 04/08/2016 03:44 PM, Mike Galbraith wrote: > On Thu, 2016-04-07 at 18:47 +0200, Sebastian Andrzej Siewior wrote: > >> just to be clear: The patch I attached did _not_ work for you. > > Did you perchance mean with "Reenable migration across schedule" > reverted? Figured it would still explode

Re: [PATCH RT 4/6] rt/locking: Reenable migration accross schedule

On 04/08/2016 03:44 PM, Mike Galbraith wrote: > On Thu, 2016-04-07 at 18:47 +0200, Sebastian Andrzej Siewior wrote: > >> just to be clear: The patch I attached did _not_ work for you. > > Did you perchance mean with "Reenable migration across schedule" > reverted? Figured it would still explode

Re: [PATCH] phy: phy-mt65xx-usb3: add support for mt2701 platform

On 08/04/16 11:13, Chunfeng Yun wrote: A new compatible string, "mediatek,mt2701-u3phy", is added. Some register settings to avoid RX sensitivity level degradation which may arise on mt8173 platform are separated from other platforms. Signed-off-by: Chunfeng Yun

Re: [PATCH] phy: phy-mt65xx-usb3: add support for mt2701 platform

On 08/04/16 11:13, Chunfeng Yun wrote: A new compatible string, "mediatek,mt2701-u3phy", is added. Some register settings to avoid RX sensitivity level degradation which may arise on mt8173 platform are separated from other platforms. Signed-off-by: Chunfeng Yun ---

Odroid XU4 deadlock

Hi All, I am observing this deadlock or warning on my Odroid XU4. I thinks the is related to clk from exynos5_i2c_xfer clk_prepare_enable but I am not able to figure out which clk. [ 11.640221] == [ 11.646343] [ INFO: possible circular

Odroid XU4 deadlock

Hi All, I am observing this deadlock or warning on my Odroid XU4. I thinks the is related to clk from exynos5_i2c_xfer clk_prepare_enable but I am not able to figure out which clk. [ 11.640221] == [ 11.646343] [ INFO: possible circular

Re: [PATCH 1/2] x86/arch_prctl: add ARCH_SET_{COMPAT,NATIVE} to change compatible mode

On 04/07/2016 05:39 PM, Andy Lutomirski wrote: For 32-bit, the vdso *must* exist in memory at the address that the kernel thinks it's at. Even if you had a pure 32-bit restore stub, you would still need vdso remap, because there's a chance the vdso could land at an unusable address, say one

Re: [PATCH 1/2] x86/arch_prctl: add ARCH_SET_{COMPAT,NATIVE} to change compatible mode

On 04/07/2016 05:39 PM, Andy Lutomirski wrote: For 32-bit, the vdso *must* exist in memory at the address that the kernel thinks it's at. Even if you had a pure 32-bit restore stub, you would still need vdso remap, because there's a chance the vdso could land at an unusable address, say one

Re: [PATCH RT 4/6] rt/locking: Reenable migration accross schedule

On Thu, 2016-04-07 at 18:47 +0200, Sebastian Andrzej Siewior wrote: > just to be clear: The patch I attached did _not_ work for you. Did you perchance mean with "Reenable migration across schedule" reverted? Figured it would still explode in seconds.. it did. [ 172.996232] kernel BUG at

Re: [PATCH RT 4/6] rt/locking: Reenable migration accross schedule

On Thu, 2016-04-07 at 18:47 +0200, Sebastian Andrzej Siewior wrote: > just to be clear: The patch I attached did _not_ work for you. Did you perchance mean with "Reenable migration across schedule" reverted? Figured it would still explode in seconds.. it did. [ 172.996232] kernel BUG at

Re: [PATCH 13/17] kvm-arm: Add stage2 page table modifiers

On Mon, Apr 04, 2016 at 05:26:13PM +0100, Suzuki K Poulose wrote: > Now that the hyp page table is handled by different set of > routines, rename the original shared routines to stage2 handlers. > Also make explicit use of the stage2 page table helpers. > > unmap_range has been merged to existing

Re: [PATCH 13/17] kvm-arm: Add stage2 page table modifiers

On Mon, Apr 04, 2016 at 05:26:13PM +0100, Suzuki K Poulose wrote: > Now that the hyp page table is handled by different set of > routines, rename the original shared routines to stage2 handlers. > Also make explicit use of the stage2 page table helpers. > > unmap_range has been merged to existing

[PATCH] memory failure: replace 'MCE' with 'Memory failure'

HWPoison was specific to some particular x86 platforms. And it is often seen as high level machine check handler. And therefore, 'MCE' is used for the format prefix of printk(). However, 'PowerNV' has also used HWPoison for handling memory errors[1], so 'MCE' is no longer suitable to

[PATCH] memory failure: replace 'MCE' with 'Memory failure'

HWPoison was specific to some particular x86 platforms. And it is often seen as high level machine check handler. And therefore, 'MCE' is used for the format prefix of printk(). However, 'PowerNV' has also used HWPoison for handling memory errors[1], so 'MCE' is no longer suitable to

RE: [PATCH v2] PCI: designware: move remaining rc setup code to dw_pcie_setup_rc()

Hi Bjorn Many thanks for your reply > -Original Message- > From: Bjorn Helgaas [mailto:helg...@kernel.org] > Sent: 07 April 2016 15:06 > To: Gabriele Paoloni > Cc: Jisheng Zhang; jingooh...@gmail.com; pratyush.an...@gmail.com; > bhelg...@google.com; linux-...@vger.kernel.org; linux- >

RE: [PATCH v2] PCI: designware: move remaining rc setup code to dw_pcie_setup_rc()

Hi Bjorn Many thanks for your reply > -Original Message- > From: Bjorn Helgaas [mailto:helg...@kernel.org] > Sent: 07 April 2016 15:06 > To: Gabriele Paoloni > Cc: Jisheng Zhang; jingooh...@gmail.com; pratyush.an...@gmail.com; > bhelg...@google.com; linux-...@vger.kernel.org; linux- >

Re: [PATCH v6 0/7] KVM PCIe/MSI passthrough on ARM/ARM64: kernel part 1/3: iommu changes

Hi Alex, On 04/07/2016 07:50 PM, Alex Williamson wrote: > On Thu, 7 Apr 2016 14:28:59 +0200 > Eric Auger wrote: > >> Hi Alex, >> On 04/07/2016 01:15 AM, Alex Williamson wrote: >>> On Mon, 4 Apr 2016 08:06:55 + >>> Eric Auger wrote: >>>

Re: [PATCH v6 0/7] KVM PCIe/MSI passthrough on ARM/ARM64: kernel part 1/3: iommu changes

Hi Alex, On 04/07/2016 07:50 PM, Alex Williamson wrote: > On Thu, 7 Apr 2016 14:28:59 +0200 > Eric Auger wrote: > >> Hi Alex, >> On 04/07/2016 01:15 AM, Alex Williamson wrote: >>> On Mon, 4 Apr 2016 08:06:55 + >>> Eric Auger wrote: >>> This series introduces the dma-reserved-iommu

[PATCH v3.5 1/1] dmaengine: dw: fix master selection

The commit 895005202987 ("dmaengine: dw: apply both HS interfaces and remove slave_id usage") cleaned up the code to avoid usage of depricated slave_id member of generic slave configuration. Meanwhile it broke the master selection by removing important call to dwc_set_masters() in

[PATCH v3.5 1/1] dmaengine: dw: fix master selection

The commit 895005202987 ("dmaengine: dw: apply both HS interfaces and remove slave_id usage") cleaned up the code to avoid usage of depricated slave_id member of generic slave configuration. Meanwhile it broke the master selection by removing important call to dwc_set_masters() in

Re: [PATCH v2] gpio: pca953x: add PCAL9535 interrupt support for Galileo Gen2

n Thu, Apr 7, 2016 at 6:56 AM, Yong Li wrote: > Galileo Gen2 board uses the PCAL9535 as the GPIO expansion, > it is different from PCA9535 and includes interrupt mask/status registers, > The current driver does not support the interrupt registers configuration, > it causes

Re: [PATCH v2] gpio: pca953x: add PCAL9535 interrupt support for Galileo Gen2

n Thu, Apr 7, 2016 at 6:56 AM, Yong Li wrote: > Galileo Gen2 board uses the PCAL9535 as the GPIO expansion, > it is different from PCA9535 and includes interrupt mask/status registers, > The current driver does not support the interrupt registers configuration, > it causes some gpio pins cannot

Re: [PATCH 04/10] iio: stx104: Change STX104 dependency to ISA_BUS

On 04/08/2016 05:31 AM, William Breathitt Gray wrote: On Thu, Apr 07, 2016 at 05:45:03PM -0700, Guenter Roeck wrote: This means for this and other similar drivers that the driver is no longer supported on architectures which support ISA but not the newly introduced ISA_BUS. Affected

Re: [PATCH 11/17] kvm-arm: Use explicit stage2 helper routines

On Mon, Apr 04, 2016 at 05:26:11PM +0100, Suzuki K Poulose wrote: > We have stage2 page table helpers for both arm and arm64. Switch to > the stage2 helpers for routines that only deal with stage2 page table. > > Cc: Marc Zyngier > Cc: Christoffer Dall

Re: [PATCH 04/10] iio: stx104: Change STX104 dependency to ISA_BUS

On 04/08/2016 05:31 AM, William Breathitt Gray wrote: On Thu, Apr 07, 2016 at 05:45:03PM -0700, Guenter Roeck wrote: This means for this and other similar drivers that the driver is no longer supported on architectures which support ISA but not the newly introduced ISA_BUS. Affected

Re: [PATCH 11/17] kvm-arm: Use explicit stage2 helper routines

On Mon, Apr 04, 2016 at 05:26:11PM +0100, Suzuki K Poulose wrote: > We have stage2 page table helpers for both arm and arm64. Switch to > the stage2 helpers for routines that only deal with stage2 page table. > > Cc: Marc Zyngier > Cc: Christoffer Dall > Signed-off-by: Suzuki K Poulose > ---

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