Linux 4.10.1

I'm announcing the release of the 4.10.1 kernel. All users of the 4.10 kernel series must upgrade. The updated 4.10.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.10.y and can be browsed at the normal kernel.org git web browser:

Re: Linux 4.10.1

diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt index be7c0d9506b1..18eefa860f76 100644 --- a/Documentation/admin-guide/kernel-parameters.txt +++ b/Documentation/admin-guide/kernel-parameters.txt @@ -1201,6 +1201,10 @@

Linux 4.10.1

I'm announcing the release of the 4.10.1 kernel. All users of the 4.10 kernel series must upgrade. The updated 4.10.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.10.y and can be browsed at the normal kernel.org git web browser:

Re: Linux 4.10.1

diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt index be7c0d9506b1..18eefa860f76 100644 --- a/Documentation/admin-guide/kernel-parameters.txt +++ b/Documentation/admin-guide/kernel-parameters.txt @@ -1201,6 +1201,10 @@

[PATCH v3] staging: xgifb: correct the multiple line dereference

Error was reported by checkpatch.pl as "Avoid multiple line dereference".And If there is boolean operator then it is fixed by Splitting line at boolean operator to satisfy coding style. Signed-off-by: Arushi Singhal --- changes in v3 - changes done such that

[PATCH v3] staging: xgifb: correct the multiple line dereference

Error was reported by checkpatch.pl as "Avoid multiple line dereference".And If there is boolean operator then it is fixed by Splitting line at boolean operator to satisfy coding style. Signed-off-by: Arushi Singhal --- changes in v3 - changes done such that no other errors can generate.

Re: [PATCH v2] drm/msm/dsi: Fix the releasing of resources in error path in 'dsi_bus_clk_enable()'

On Sun, Feb 26, 2017 at 7:10 AM, Christophe JAILLET wrote: > If a 'clk_prepare_enable()' fails, then we need to disable_unprepare the > clk already handled. > > With the current implemenatation, we try to do that on the clk that has > triggered the error, which is a

Re: [PATCH v2] drm/msm/dsi: Fix the releasing of resources in error path in 'dsi_bus_clk_enable()'

On Sun, Feb 26, 2017 at 7:10 AM, Christophe JAILLET wrote: > If a 'clk_prepare_enable()' fails, then we need to disable_unprepare the > clk already handled. > > With the current implemenatation, we try to do that on the clk that has > triggered the error, which is a no-op and leave

Re: [PATCH] [linux-next] bcache: Remove duplicate inclusion of blkdev.h

On 2017/2/26 下午2:02, Masanari Iida wrote: > This patch remove duplicate inclusion of blkdev.h in util.h. > Confirm compile successfully after remove the line. > > Signed-off-by: Masanari Iida > --- > drivers/md/bcache/util.h | 1 - > 1 file changed, 1 deletion(-) > >

Re: [PATCH] [linux-next] bcache: Remove duplicate inclusion of blkdev.h

On 2017/2/26 下午2:02, Masanari Iida wrote: > This patch remove duplicate inclusion of blkdev.h in util.h. > Confirm compile successfully after remove the line. > > Signed-off-by: Masanari Iida > --- > drivers/md/bcache/util.h | 1 - > 1 file changed, 1 deletion(-) > > diff --git

[PATCH] rtlwifi: rtl8192de: ix spelling mistake: "althougth" -> "although"

From: Colin Ian King trivial fix to spelling mistake in RT_TRACE message Signed-off-by: Colin Ian King --- drivers/net/wireless/realtek/rtlwifi/rtl8192de/phy.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] rtlwifi: rtl8192de: ix spelling mistake: "althougth" -> "although"

From: Colin Ian King trivial fix to spelling mistake in RT_TRACE message Signed-off-by: Colin Ian King --- drivers/net/wireless/realtek/rtlwifi/rtl8192de/phy.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/wireless/realtek/rtlwifi/rtl8192de/phy.c

Re: [PATCH 00/10] fujitsu-laptop: renames and cleanups

On Sun, Feb 26, 2017 at 1:30 PM, Michał Kępień wrote: >> On Fri, Feb 17, 2017 at 6:17 AM, Jonathan Woithe wrote: >> > On Thu, Feb 16, 2017 at 07:53:19PM -0800, Darren Hart wrote: >> >> On Fri, Feb 17, 2017 at 01:38:04PM +1030, Jonathan Woithe wrote: >> >> >

Re: [PATCH 00/10] fujitsu-laptop: renames and cleanups

On Sun, Feb 26, 2017 at 1:30 PM, Michał Kępień wrote: >> On Fri, Feb 17, 2017 at 6:17 AM, Jonathan Woithe wrote: >> > On Thu, Feb 16, 2017 at 07:53:19PM -0800, Darren Hart wrote: >> >> On Fri, Feb 17, 2017 at 01:38:04PM +1030, Jonathan Woithe wrote: >> >> > Do you want me to continue to use

Re: [PATCH v3 2/2] iio: stm32 trigger: Implement parent trigger feature

2017-02-25 18:53 GMT+01:00 Jonathan Cameron : > On 24/02/17 14:48, Benjamin Gaignard wrote: >> Add validate_trigger function in iio_trigger_ops and >> dev_attr_parent_trigger into trigger attribute group to be able >> to accept triggers as parents. >> >> Introduce an IIO device

Re: [PATCH v3 2/2] iio: stm32 trigger: Implement parent trigger feature

2017-02-25 18:53 GMT+01:00 Jonathan Cameron : > On 24/02/17 14:48, Benjamin Gaignard wrote: >> Add validate_trigger function in iio_trigger_ops and >> dev_attr_parent_trigger into trigger attribute group to be able >> to accept triggers as parents. >> >> Introduce an IIO device with one IIO_COUNT

Re: [PATCH v2 04/17] clocksource: Add Owl timer

On Sun, Feb 26, 2017 at 03:40:49PM +0100, Andreas Färber wrote: > Am 25.02.2017 um 22:59 schrieb Daniel Lezcano: > > On Sat, Feb 25, 2017 at 12:25:32AM +0100, Andreas Färber wrote: > >> Am 24.02.2017 um 23:29 schrieb Daniel Lezcano: > >>> On Fri, Feb 24, 2017 at 04:40:42AM +0100, Andreas Färber

Re: [PATCH v2 04/17] clocksource: Add Owl timer

On Sun, Feb 26, 2017 at 03:40:49PM +0100, Andreas Färber wrote: > Am 25.02.2017 um 22:59 schrieb Daniel Lezcano: > > On Sat, Feb 25, 2017 at 12:25:32AM +0100, Andreas Färber wrote: > >> Am 24.02.2017 um 23:29 schrieb Daniel Lezcano: > >>> On Fri, Feb 24, 2017 at 04:40:42AM +0100, Andreas Färber

Re: [PATCH] lib: fix spelling mistake: "actualy" -> "actually"

Sun, Feb 26, 2017 at 01:10:12PM CET, colin.k...@canonical.com wrote: >From: Colin Ian King > >trivial fix to spelling mistake in pr_err message > >Signed-off-by: Colin Ian King Acked-by: Jiri Pirko >--- >

Re: [PATCH] lib: fix spelling mistake: "actualy" -> "actually"

Sun, Feb 26, 2017 at 01:10:12PM CET, colin.k...@canonical.com wrote: >From: Colin Ian King > >trivial fix to spelling mistake in pr_err message > >Signed-off-by: Colin Ian King Acked-by: Jiri Pirko >--- > lib/test_parman.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > >diff --git

RE: FOR YOUR INFORMATION

From: Eddie Concepcion Sent: Sunday, February 26, 2017 9:11 AM To: Eddie Concepcion Subject: FOR YOUR INFORMATION Hi, You have received a donation of 1,000,000USD; reply to merlebutler...@gmail.com, for details.

RE: FOR YOUR INFORMATION

From: Eddie Concepcion Sent: Sunday, February 26, 2017 9:11 AM To: Eddie Concepcion Subject: FOR YOUR INFORMATION Hi, You have received a donation of 1,000,000USD; reply to merlebutler...@gmail.com, for details.

[LSF/MM TOPIC] do we really need PG_error at all?

Proposing this as a LSF/MM TOPIC, but it may turn out to be me just not understanding the semantics here. As I was looking into -ENOSPC handling in cephfs, I noticed that PG_error is only ever tested in one place [1] __filemap_fdatawait_range, which does this: if

[LSF/MM TOPIC] do we really need PG_error at all?

Proposing this as a LSF/MM TOPIC, but it may turn out to be me just not understanding the semantics here. As I was looking into -ENOSPC handling in cephfs, I noticed that PG_error is only ever tested in one place [1] __filemap_fdatawait_range, which does this: if

Re: [PATCH v2 04/17] clocksource: Add Owl timer

Am 25.02.2017 um 22:59 schrieb Daniel Lezcano: > On Sat, Feb 25, 2017 at 12:25:32AM +0100, Andreas Färber wrote: >> Am 24.02.2017 um 23:29 schrieb Daniel Lezcano: >>> On Fri, Feb 24, 2017 at 04:40:42AM +0100, Andreas Färber wrote: +static struct clock_event_device owl_clockevent = { +

Re: [PATCH v2 04/17] clocksource: Add Owl timer

Am 25.02.2017 um 22:59 schrieb Daniel Lezcano: > On Sat, Feb 25, 2017 at 12:25:32AM +0100, Andreas Färber wrote: >> Am 24.02.2017 um 23:29 schrieb Daniel Lezcano: >>> On Fri, Feb 24, 2017 at 04:40:42AM +0100, Andreas Färber wrote: +static struct clock_event_device owl_clockevent = { +

Re: [PATCH v2] drm/msm/dsi: Fix the releasing of resources in error path in 'dsi_bus_clk_enable()'

looks good to me. Reviewed-by: wha...@bfs.de Am 26.02.2017 13:10, schrieb Christophe JAILLET: > If a 'clk_prepare_enable()' fails, then we need to disable_unprepare the > clk already handled. > > With the current implemenatation, we try to do that on the clk that has > triggered the error,

Re: [PATCH v2] drm/msm/dsi: Fix the releasing of resources in error path in 'dsi_bus_clk_enable()'

looks good to me. Reviewed-by: wha...@bfs.de Am 26.02.2017 13:10, schrieb Christophe JAILLET: > If a 'clk_prepare_enable()' fails, then we need to disable_unprepare the > clk already handled. > > With the current implemenatation, we try to do that on the clk that has > triggered the error,

Re: [PATCH 0/8] ARM: sun8i: a33: Mali improvements

Hi Maxime, Thanks for the links. On 24 February 2017 at 00:19, Maxime Ripard wrote: > Hi, > > On Fri, Feb 17, 2017 at 08:39:33PM +, Emil Velikov wrote: >> As I feared things have taken a turn for the bitter end :-] >> >> It seems that this is a heated

Re: [PATCH 0/8] ARM: sun8i: a33: Mali improvements

Hi Maxime, Thanks for the links. On 24 February 2017 at 00:19, Maxime Ripard wrote: > Hi, > > On Fri, Feb 17, 2017 at 08:39:33PM +, Emil Velikov wrote: >> As I feared things have taken a turn for the bitter end :-] >> >> It seems that this is a heated topic, so I'l kindly ask that we try >>

Re: [PATCH v1 2/2] coresight: add support for debug module

On Fri, Feb 24, 2017 at 12:07:11PM -0700, Mathieu Poirier wrote: > On Thu, Feb 23, 2017 at 09:57:47AM +0800, Leo Yan wrote: [...] > > +/* bits definition for EDDEVID1 */ > > +#define EDDEVID1_PCSR_OFFSET_MASK GENMASK(3, 0) > > +#define EDDEVID1_PCSR_OFFSET_INS_SET (0x0) > > +#define

Re: [PATCH v1 2/2] coresight: add support for debug module

On Fri, Feb 24, 2017 at 12:07:11PM -0700, Mathieu Poirier wrote: > On Thu, Feb 23, 2017 at 09:57:47AM +0800, Leo Yan wrote: [...] > > +/* bits definition for EDDEVID1 */ > > +#define EDDEVID1_PCSR_OFFSET_MASK GENMASK(3, 0) > > +#define EDDEVID1_PCSR_OFFSET_INS_SET (0x0) > > +#define

[PATCH v4 4/4] iio: accel: adxl345: Add SPI support

Add SPI driver that initializes SPI regmap for the adxl345 core driver. The driver supports the same functionality as I2C namely the x, y, z and scale readings. Signed-off-by: Eva Rachel Retuya --- Changes from v3: * Revert to explicit and separate I2C and SPI configuration

[PATCH v4 4/4] iio: accel: adxl345: Add SPI support

Add SPI driver that initializes SPI regmap for the adxl345 core driver. The driver supports the same functionality as I2C namely the x, y, z and scale readings. Signed-off-by: Eva Rachel Retuya --- Changes from v3: * Revert to explicit and separate I2C and SPI configuration * Add OF match table,

[PATCH v4 3/4] iio: accel: adxl345: Split driver into core and I2C

Move I2C-specific code into its own file and rely on regmap to access registers. The core code provides access to x, y, z and scale readings. Signed-off-by: Eva Rachel Retuya --- Changes from v3: * Revert to explicit and separate I2C and SPI configuration * Add OF match

[PATCH v4 3/4] iio: accel: adxl345: Split driver into core and I2C

Move I2C-specific code into its own file and rely on regmap to access registers. The core code provides access to x, y, z and scale readings. Signed-off-by: Eva Rachel Retuya --- Changes from v3: * Revert to explicit and separate I2C and SPI configuration * Add OF match table, make it enumerable

[PATCH v4 2/4] iio: accel: adxl345: Use I2C regmap instead of direct I2C access

Convert the driver to use regmap instead of I2C-specific functions. This is done in preparation for splitting this driver into core and I2C-specific code as well as introduction of SPI driver. Signed-off-by: Eva Rachel Retuya --- Changes from v3: * Keep intact I2C client

[PATCH v4 2/4] iio: accel: adxl345: Use I2C regmap instead of direct I2C access

Convert the driver to use regmap instead of I2C-specific functions. This is done in preparation for splitting this driver into core and I2C-specific code as well as introduction of SPI driver. Signed-off-by: Eva Rachel Retuya --- Changes from v3: * Keep intact I2C client structure which was

[PATCH v4 0/4] iio: accel: adxl345: Split driver into core and I2C then add SPI support

This patchset modifies the adxl345 to use regmap. In doing so, we can easily introduce SPI support and let regmap handle the rest. Recap of basic features: read_raw for x, y and z axes, scale. After applying this series, driver now supports the SPI protocol and enumeration of device via device

[PATCH v4 0/4] iio: accel: adxl345: Split driver into core and I2C then add SPI support

This patchset modifies the adxl345 to use regmap. In doing so, we can easily introduce SPI support and let regmap handle the rest. Recap of basic features: read_raw for x, y and z axes, scale. After applying this series, driver now supports the SPI protocol and enumeration of device via device

[PATCH v4 1/4] Documentation: dt-bindings: Document ADXL345 accelerometer binding

Add the device tree binding documentation for the ADXL345 3-axis digital accelerometer. Signed-off-by: Eva Rachel Retuya --- .../devicetree/bindings/iio/accel/adxl345.txt | 38 ++ 1 file changed, 38 insertions(+) create mode 100644

[PATCH v4 1/4] Documentation: dt-bindings: Document ADXL345 accelerometer binding

Add the device tree binding documentation for the ADXL345 3-axis digital accelerometer. Signed-off-by: Eva Rachel Retuya --- .../devicetree/bindings/iio/accel/adxl345.txt | 38 ++ 1 file changed, 38 insertions(+) create mode 100644

I915 dmesg warnings on Mac Mini, solo core edition

Hello. I am not using this computer actively and can't report easily on the state of the screen. Still, I observed the following situation in the system's dmesg: running the stock Archlinux Kernel. This is an Apple MacMini system, booted via an EFI bootloader. Thank you very much, Enrico [

I915 dmesg warnings on Mac Mini, solo core edition

Hello. I am not using this computer actively and can't report easily on the state of the screen. Still, I observed the following situation in the system's dmesg: running the stock Archlinux Kernel. This is an Apple MacMini system, booted via an EFI bootloader. Thank you very much, Enrico [

Re: [PATCH] drm/msm/dsi: Fix the releasing of resources in error path in 'dsi_bus_clk_enable()'

On Sun, Feb 26, 2017 at 2:52 AM, Christophe JAILLET wrote: > If a 'clk_prepare_enable()' fails, then we need to disable_unprepare the > clk already handled. > > With the current implemenatation, we try to do that on the clk that has > triggered the error, which is a

Re: [PATCH] drm/msm/dsi: Fix the releasing of resources in error path in 'dsi_bus_clk_enable()'

On Sun, Feb 26, 2017 at 2:52 AM, Christophe JAILLET wrote: > If a 'clk_prepare_enable()' fails, then we need to disable_unprepare the > clk already handled. > > With the current implemenatation, we try to do that on the clk that has > triggered the error, which is a no-op, and leave

Winning Details

New york.docx Description: MS-Word 2007 document

Winning Details

New york.docx Description: MS-Word 2007 document

[PATCH v2] drm/msm/dsi: Fix the releasing of resources in error path in 'dsi_bus_clk_enable()'

If a 'clk_prepare_enable()' fails, then we need to disable_unprepare the clk already handled. With the current implemenatation, we try to do that on the clk that has triggered the error, which is a no-op and leave msm_host->bus_clks[0] untouched. Count forward in order to fix it and be more

[PATCH v2] drm/msm/dsi: Fix the releasing of resources in error path in 'dsi_bus_clk_enable()'

If a 'clk_prepare_enable()' fails, then we need to disable_unprepare the clk already handled. With the current implemenatation, we try to do that on the clk that has triggered the error, which is a no-op and leave msm_host->bus_clks[0] untouched. Count forward in order to fix it and be more

[PATCH] lib: fix spelling mistake: "actualy" -> "actually"

From: Colin Ian King trivial fix to spelling mistake in pr_err message Signed-off-by: Colin Ian King --- lib/test_parman.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/test_parman.c b/lib/test_parman.c index

[PATCH] lib: fix spelling mistake: "actualy" -> "actually"

From: Colin Ian King trivial fix to spelling mistake in pr_err message Signed-off-by: Colin Ian King --- lib/test_parman.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/test_parman.c b/lib/test_parman.c index fe9f3a7..35e3224 100644 --- a/lib/test_parman.c +++

Re: Linux 4.4.52

diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt index c360f80c3473..ca64ca566099 100644 --- a/Documentation/kernel-parameters.txt +++ b/Documentation/kernel-parameters.txt @@ -1255,6 +1255,10 @@ bytes respectively. Such letter suffixes can also be entirely

Re: Linux 4.4.52

diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt index c360f80c3473..ca64ca566099 100644 --- a/Documentation/kernel-parameters.txt +++ b/Documentation/kernel-parameters.txt @@ -1255,6 +1255,10 @@ bytes respectively. Such letter suffixes can also be entirely

Linux 4.4.52

I'm announcing the release of the 4.4.52 kernel. All users of the 4.4 kernel series must upgrade. The updated 4.4.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.4.y and can be browsed at the normal kernel.org git web browser:

Linux 4.4.52

I'm announcing the release of the 4.4.52 kernel. All users of the 4.4 kernel series must upgrade. The updated 4.4.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.4.y and can be browsed at the normal kernel.org git web browser:

[RFC] ERR_USER_PTR

In an attempt to clean up sparse warnings, I offer this small patch. The two warnings it fixes are: fs/exec.c:424:39: warning: incorrect type in return expression (different address spaces) fs/exec.c:424:39:expected char const [noderef] * fs/exec.c:424:39:got void * fs/exec.c:431:31:

[RFC] ERR_USER_PTR

In an attempt to clean up sparse warnings, I offer this small patch. The two warnings it fixes are: fs/exec.c:424:39: warning: incorrect type in return expression (different address spaces) fs/exec.c:424:39:expected char const [noderef] * fs/exec.c:424:39:got void * fs/exec.c:431:31:

Re: [PATCH v2 6/7] tpm: expose spaces via a device link /dev/tpms

On Fri, Feb 24, 2017 at 08:02:08AM -0500, James Bottomley wrote: > On Thu, 2017-02-23 at 11:09 +0200, Jarkko Sakkinen wrote: > > On Thu, Feb 16, 2017 at 09:25:19PM +0200, Jarkko Sakkinen wrote: > > > From: James Bottomley > > > > > > Currently the tpm

Re: [PATCH v2 6/7] tpm: expose spaces via a device link /dev/tpms

On Fri, Feb 24, 2017 at 08:02:08AM -0500, James Bottomley wrote: > On Thu, 2017-02-23 at 11:09 +0200, Jarkko Sakkinen wrote: > > On Thu, Feb 16, 2017 at 09:25:19PM +0200, Jarkko Sakkinen wrote: > > > From: James Bottomley > > > > > > Currently the tpm spaces are not exposed to userspace. Make

[PATCH] mm, add_memory_resource: hold device_hotplug lock over mem_hotplug_{begin, done}

With 4.10.0-10265-gc4f3f22 the following warning is triggered on s390: WARNING: CPU: 6 PID: 1 at drivers/base/core.c:643 assert_held_device_hotplug+0x4a/0x58 [5.731214] Call Trace: [5.731219] ([<0067b8b0>] assert_held_device_hotplug+0x40/0x58) [5.731225] [<00337914>]

[PATCH] mm, add_memory_resource: hold device_hotplug lock over mem_hotplug_{begin, done}

With 4.10.0-10265-gc4f3f22 the following warning is triggered on s390: WARNING: CPU: 6 PID: 1 at drivers/base/core.c:643 assert_held_device_hotplug+0x4a/0x58 [5.731214] Call Trace: [5.731219] ([<0067b8b0>] assert_held_device_hotplug+0x40/0x58) [5.731225] [<00337914>]

Re: Linux 4.9.13

diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt index 922dec8fa07e..65b05ba6ef98 100644 --- a/Documentation/kernel-parameters.txt +++ b/Documentation/kernel-parameters.txt @@ -1391,6 +1391,10 @@ bytes respectively. Such letter suffixes can also be entirely

Re: Linux 4.9.13

diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt index 922dec8fa07e..65b05ba6ef98 100644 --- a/Documentation/kernel-parameters.txt +++ b/Documentation/kernel-parameters.txt @@ -1391,6 +1391,10 @@ bytes respectively. Such letter suffixes can also be entirely

Linux 4.9.13

I'm announcing the release of the 4.9.13 kernel. All users of the 4.9 kernel series must upgrade. The updated 4.9.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.9.y and can be browsed at the normal kernel.org git web browser:

Linux 4.9.13

I'm announcing the release of the 4.9.13 kernel. All users of the 4.9 kernel series must upgrade. The updated 4.9.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.9.y and can be browsed at the normal kernel.org git web browser:

Re: [PATCH 00/10] fujitsu-laptop: renames and cleanups

> On Fri, Feb 17, 2017 at 6:17 AM, Jonathan Woithe wrote: > > On Thu, Feb 16, 2017 at 07:53:19PM -0800, Darren Hart wrote: > >> On Fri, Feb 17, 2017 at 01:38:04PM +1030, Jonathan Woithe wrote: > >> > Do you want me to continue to use Acked-by, or should I switch to > >> >

Re: [PATCH 00/10] fujitsu-laptop: renames and cleanups

> On Fri, Feb 17, 2017 at 6:17 AM, Jonathan Woithe wrote: > > On Thu, Feb 16, 2017 at 07:53:19PM -0800, Darren Hart wrote: > >> On Fri, Feb 17, 2017 at 01:38:04PM +1030, Jonathan Woithe wrote: > >> > Do you want me to continue to use Acked-by, or should I switch to > >> > Reviewed-by? > >> > >>

Re: [GIT PULL] Kselftest update for 4.11-rc1

On Sat, Feb 25, 2017 at 03:42:55PM -0800, Linus Torvalds wrote: > On Fri, Feb 24, 2017 at 1:09 PM, Shuah Khan wrote: > > > > Stephen saw a conflict during kselftest merge with next > [..] > > There was also a conflict with some of Andrew's new userfaultfd tests. > > I'm

Re: [GIT PULL] Kselftest update for 4.11-rc1

On Sat, Feb 25, 2017 at 03:42:55PM -0800, Linus Torvalds wrote: > On Fri, Feb 24, 2017 at 1:09 PM, Shuah Khan wrote: > > > > Stephen saw a conflict during kselftest merge with next > [..] > > There was also a conflict with some of Andrew's new userfaultfd tests. > > I'm not at all sure I merged

Re: [ieee802154_unregister_hw] bea5b158ff BUG: scheduling while atomic: swapper/1/0x00000002

Hi, On 02/26/2017 10:43 AM, Fengguang Wu wrote: > Greetings, > > FYI, this debug patch discloses an old-but-still-active bug in > ieee802154/fakelb. The attached reproduce-* script may help debug it. > fixed by: bdca1fd9a6df ("fakelb: fix schedule while atomic"). It should be send to stable.

Re: [ieee802154_unregister_hw] bea5b158ff BUG: scheduling while atomic: swapper/1/0x00000002

Hi, On 02/26/2017 10:43 AM, Fengguang Wu wrote: > Greetings, > > FYI, this debug patch discloses an old-but-still-active bug in > ieee802154/fakelb. The attached reproduce-* script may help debug it. > fixed by: bdca1fd9a6df ("fakelb: fix schedule while atomic"). It should be send to stable.

Re: [PATCH RFC] arm64/mm: handle memmap kernel option

On 25 February 2017 at 06:47, Yisheng Xie wrote: > When use device tree mode, user can reserve memory by changes the dts, > however, when boot with ACPI, user cannot reserve memory except by > changing the ACPI table in BIOS, which is not so convenient. > > To make user

Re: [PATCH RFC] arm64/mm: handle memmap kernel option

On 25 February 2017 at 06:47, Yisheng Xie wrote: > When use device tree mode, user can reserve memory by changes the dts, > however, when boot with ACPI, user cannot reserve memory except by > changing the ACPI table in BIOS, which is not so convenient. > > To make user reserve memory for some

[usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

[Sorry, resend to correct Felipe's email address] Greetings, This debug patch possibly discloses some USB/I2C bugs. Since the USB warning shows up earlier in dmesg, it might also be the root cause of the I2C bug. The attached reproduce-* script may help debug them.

[usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

[Sorry, resend to correct Felipe's email address] Greetings, This debug patch possibly discloses some USB/I2C bugs. Since the USB warning shows up earlier in dmesg, it might also be the root cause of the I2C bug. The attached reproduce-* script may help debug them.

[usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

Greetings, This debug patch possibly discloses some USB/I2C bugs. Since the USB warning shows up earlier in dmesg, it might also be the root cause of the I2C bug. The attached reproduce-* script may help debug them. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master

[usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

Greetings, This debug patch possibly discloses some USB/I2C bugs. Since the USB warning shows up earlier in dmesg, it might also be the root cause of the I2C bug. The attached reproduce-* script may help debug them. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master

Re: [PATCH v5 2/7] clk: sunxi-ng: rename sun8i-h3 driver to sunxi-h3-h5

On Sun, Feb 26, 2017 at 09:19:51AM +0800, Icenowy Zheng wrote: > As the CCU in the Allwinner H5 SoC is very similar to the one in H3, > rename the H3 driver to sunxi-h3-h5 so that it can be extended with H5 > support. > > Trasitional header symlinks are created, to ensure current device tree

Re: [PATCH v5 2/7] clk: sunxi-ng: rename sun8i-h3 driver to sunxi-h3-h5

On Sun, Feb 26, 2017 at 09:19:51AM +0800, Icenowy Zheng wrote: > As the CCU in the Allwinner H5 SoC is very similar to the one in H3, > rename the H3 driver to sunxi-h3-h5 so that it can be extended with H5 > support. > > Trasitional header symlinks are created, to ensure current device tree

Re: [PATCH v5 7/7] arm64: dts: sunxi: add support for the Orange Pi PC 2 board

On Sun, Feb 26, 2017 at 09:19:56AM +0800, Icenowy Zheng wrote: > diff --git a/arch/arm64/boot/dts/allwinner/sun50i-h5-orangepi-pc2.dts > b/arch/arm64/boot/dts/allwinner/sun50i-h5-orangepi-pc2.dts > new file mode 100644 > index ..79784cba806c > --- /dev/null > +++

Re: [PATCH v5 7/7] arm64: dts: sunxi: add support for the Orange Pi PC 2 board

On Sun, Feb 26, 2017 at 09:19:56AM +0800, Icenowy Zheng wrote: > diff --git a/arch/arm64/boot/dts/allwinner/sun50i-h5-orangepi-pc2.dts > b/arch/arm64/boot/dts/allwinner/sun50i-h5-orangepi-pc2.dts > new file mode 100644 > index ..79784cba806c > --- /dev/null > +++

Re: [PATCH v5 6/7] arm64: dts: allwinner: add Allwinner H5 .dtsi

On Sun, Feb 26, 2017 at 4:55 PM, Rask Ingemann Lambertsen wrote: > On Sun, Feb 26, 2017 at 09:19:55AM +0800, Icenowy Zheng wrote: >> From: Andre Przywara >> >> The Allwinner H5 SoC is pin-compatible to the H3 SoC, but uses >> Cortex-A53 cores instead.

Re: [PATCH v5 6/7] arm64: dts: allwinner: add Allwinner H5 .dtsi

On Sun, Feb 26, 2017 at 4:55 PM, Rask Ingemann Lambertsen wrote: > On Sun, Feb 26, 2017 at 09:19:55AM +0800, Icenowy Zheng wrote: >> From: Andre Przywara >> >> The Allwinner H5 SoC is pin-compatible to the H3 SoC, but uses >> Cortex-A53 cores instead. >> Based on the now shared base .dtsi

Re: [Intel-wired-lan] [PATCH] e1000e: fix timing for 82579 Gigabit Ethernet controller

On 2/19/2017 14:55, Neftin, Sasha wrote: On 2/16/2017 20:42, Bernd Faust wrote: After an upgrade to Linux kernel v4.x the hardware timestamps of the 82579 Gigabit Ethernet Controller are different than expected. The values that are being read are almost four times as big as before the kernel

Re: [Intel-wired-lan] [PATCH] e1000e: fix timing for 82579 Gigabit Ethernet controller

On 2/19/2017 14:55, Neftin, Sasha wrote: On 2/16/2017 20:42, Bernd Faust wrote: After an upgrade to Linux kernel v4.x the hardware timestamps of the 82579 Gigabit Ethernet Controller are different than expected. The values that are being read are almost four times as big as before the kernel

Re: [PATCH] drm/msm/dsi: Fix the releasing of resources in error path in 'dsi_bus_clk_enable()'

Am 26.02.2017 08:52, schrieb Christophe JAILLET: > If a 'clk_prepare_enable()' fails, then we need to disable_unprepare the > clk already handled. > > With the current implemenatation, we try to do that on the clk that has > triggered the error, which is a no-op, and leave

Re: [PATCH] drm/msm/dsi: Fix the releasing of resources in error path in 'dsi_bus_clk_enable()'

Am 26.02.2017 08:52, schrieb Christophe JAILLET: > If a 'clk_prepare_enable()' fails, then we need to disable_unprepare the > clk already handled. > > With the current implemenatation, we try to do that on the clk that has > triggered the error, which is a no-op, and leave

Re: [PATCH v5 6/7] arm64: dts: allwinner: add Allwinner H5 .dtsi

On Sun, Feb 26, 2017 at 09:19:55AM +0800, Icenowy Zheng wrote: > From: Andre Przywara > > The Allwinner H5 SoC is pin-compatible to the H3 SoC, but uses > Cortex-A53 cores instead. > Based on the now shared base .dtsi describing the common peripherals > describe the H5

Re: [PATCH v5 6/7] arm64: dts: allwinner: add Allwinner H5 .dtsi

On Sun, Feb 26, 2017 at 09:19:55AM +0800, Icenowy Zheng wrote: > From: Andre Przywara > > The Allwinner H5 SoC is pin-compatible to the H3 SoC, but uses > Cortex-A53 cores instead. > Based on the now shared base .dtsi describing the common peripherals > describe the H5 specific nodes on top of

[PATCH] KVM: nVMX: Fix pending events injection

From: Wanpeng Li L2 fails to boot on a non-APICv box dues to 'commit 0ad3bed6c5ec ("kvm: nVMX: move nested events check to kvm_vcpu_running")' KVM internal error. Suberror: 3 extra data[0]: 80ef extra data[1]: 1 RAX= RBX=81f36140

[PATCH] KVM: nVMX: Fix pending events injection

From: Wanpeng Li L2 fails to boot on a non-APICv box dues to 'commit 0ad3bed6c5ec ("kvm: nVMX: move nested events check to kvm_vcpu_running")' KVM internal error. Suberror: 3 extra data[0]: 80ef extra data[1]: 1 RAX= RBX=81f36140 RCX=

Re: Still OOM problems with 4.9er/4.10er kernels

On 04.01.2017 10:11, Michal Hocko wrote: The VM stops working (e.g. not pingable) after around 8h (will be restarted automatically), happened serveral times. Had also further OOMs which I sent to Mincham. Could you post them to the mailing list as well, please? Still OOMs on dnf update

Re: Still OOM problems with 4.9er/4.10er kernels

On 04.01.2017 10:11, Michal Hocko wrote: The VM stops working (e.g. not pingable) after around 8h (will be restarted automatically), happened serveral times. Had also further OOMs which I sent to Mincham. Could you post them to the mailing list as well, please? Still OOMs on dnf update

Re: camera subdevice support was Re: [PATCH 1/4] v4l2: device_register_subdev_nodes: allow calling multiple times

Ahoj! :-) > > > > Ok, I got the camera sensor to work. No subdevices support, so I don't > > > > have focus (etc) working, but that's a start. I also had to remove > > > > video-bus-switch support; but I guess it will be easier to use > > > > video-multiplexer patches... > > > > > > > > I'll

Re: camera subdevice support was Re: [PATCH 1/4] v4l2: device_register_subdev_nodes: allow calling multiple times

Ahoj! :-) > > > > Ok, I got the camera sensor to work. No subdevices support, so I don't > > > > have focus (etc) working, but that's a start. I also had to remove > > > > video-bus-switch support; but I guess it will be easier to use > > > > video-multiplexer patches... > > > > > > > > I'll

Re: [PATCH 1/2] lightnvm: add generic ocssd detection

[adding linux-nvme to Cc as the patch changes the nvme driver, despite the subject line] On Sat, Feb 25, 2017 at 08:16:04PM +0100, Matias Bjørling wrote: > On 02/25/2017 07:21 PM, Christoph Hellwig wrote: > > On Fri, Feb 24, 2017 at 06:16:48PM +0100, Matias Bjørling wrote: > > > More

Re: [PATCH 1/2] lightnvm: add generic ocssd detection

[adding linux-nvme to Cc as the patch changes the nvme driver, despite the subject line] On Sat, Feb 25, 2017 at 08:16:04PM +0100, Matias Bjørling wrote: > On 02/25/2017 07:21 PM, Christoph Hellwig wrote: > > On Fri, Feb 24, 2017 at 06:16:48PM +0100, Matias Bjørling wrote: > > > More

Re: [PATCH] ASoC: spear: Remove redundant message

On Feb 25 2017 19:33, dspmihai wrote: This was reported by checkpatch.pl Signed-off-by: Despotovici Mihai --- sound/soc/spear/spdif_in.c | 4 +--- sound/soc/spear/spdif_out.c | 4 +--- 2 files changed, 2 insertions(+), 6 deletions(-) diff --git

Re: [PATCH] ASoC: spear: Remove redundant message

On Feb 25 2017 19:33, dspmihai wrote: This was reported by checkpatch.pl Signed-off-by: Despotovici Mihai --- sound/soc/spear/spdif_in.c | 4 +--- sound/soc/spear/spdif_out.c | 4 +--- 2 files changed, 2 insertions(+), 6 deletions(-) diff --git a/sound/soc/spear/spdif_in.c

<    1   2   3   4   5   6   >