Re: [RFC 19/19] s390/facilities: enable AP facilities needed by guest

On 12/02/2017 02:30 AM, Tony Krowiak wrote: > On 11/03/2017 04:47 AM, Christian Borntraeger wrote: >> >> On 11/02/2017 07:49 PM, Tony Krowiak wrote: >>> On 11/02/2017 11:53 AM, Christian Borntraeger wrote: On 11/02/2017 04:36 PM, Tony Krowiak wrote: > On 11/02/2017 08:08 AM, Christian

[f2fs-dev] [PATCH] f2fs: release reserved blocks for quota

Quota has been modified during inc_valid_block_count(), but not in truncate process. This patch adds it. Signed-off-by: Fan li --- fs/f2fs/f2fs.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h index 82f1dc3..71fbba96 100644 ---

Re: [RFC 19/19] s390/facilities: enable AP facilities needed by guest

On 12/02/2017 02:30 AM, Tony Krowiak wrote: > On 11/03/2017 04:47 AM, Christian Borntraeger wrote: >> >> On 11/02/2017 07:49 PM, Tony Krowiak wrote: >>> On 11/02/2017 11:53 AM, Christian Borntraeger wrote: On 11/02/2017 04:36 PM, Tony Krowiak wrote: > On 11/02/2017 08:08 AM, Christian

[f2fs-dev] [PATCH] f2fs: release reserved blocks for quota

Quota has been modified during inc_valid_block_count(), but not in truncate process. This patch adds it. Signed-off-by: Fan li --- fs/f2fs/f2fs.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h index 82f1dc3..71fbba96 100644 --- a/fs/f2fs/f2fs.h +++

[PATCH] SCSI: run queue if SCSI device queue isn't ready and queue is idle

Before commit 0df21c86bdbf ("scsi: implement .get_budget and .put_budget for blk-mq"), we run queue after 3ms if queue is idle and SCSI device queue isn't ready, which is done in handling BLK_STS_RESOURCE. After commit 0df21c86bdbf is introduced, queue won't be run any more under this situation.

[PATCH] SCSI: run queue if SCSI device queue isn't ready and queue is idle

Before commit 0df21c86bdbf ("scsi: implement .get_budget and .put_budget for blk-mq"), we run queue after 3ms if queue is idle and SCSI device queue isn't ready, which is done in handling BLK_STS_RESOURCE. After commit 0df21c86bdbf is introduced, queue won't be run any more under this situation.

Re: [PATCH 4.14 00/95] 4.14.4-stable review

On Tue, Dec 05, 2017 at 12:31:40PM +0530, Naresh Kamboju wrote: > On 4 December 2017 at 21:29, Greg Kroah-Hartman > wrote: > > This is the start of the stable review cycle for the 4.14.4 release. > > There are 95 patches in this series, all will be posted as a response

Re: [PATCH 4.14 00/95] 4.14.4-stable review

On Tue, Dec 05, 2017 at 12:31:40PM +0530, Naresh Kamboju wrote: > On 4 December 2017 at 21:29, Greg Kroah-Hartman > wrote: > > This is the start of the stable review cycle for the 4.14.4 release. > > There are 95 patches in this series, all will be posted as a response > > to this one. If anyone

Re: Writing "+pids" to cgroup.subtree_control flie yields EINVAL

[dropping Lennart into CC] Hello Tejun, On 12/04/2017 10:47 PM, Tejun Heo wrote: > Hello, Michael. > > On Mon, Dec 04, 2017 at 10:35:13PM +0100, Michael Kerrisk (man-pages) wrote: >> I was trying to do some simple testing ot the CPU controller >> that is merged into 4.15, and ran immediately

Re: Writing "+pids" to cgroup.subtree_control flie yields EINVAL

[dropping Lennart into CC] Hello Tejun, On 12/04/2017 10:47 PM, Tejun Heo wrote: > Hello, Michael. > > On Mon, Dec 04, 2017 at 10:35:13PM +0100, Michael Kerrisk (man-pages) wrote: >> I was trying to do some simple testing ot the CPU controller >> that is merged into 4.15, and ran immediately

Re: [PATCH v2 0/4] lockdep/crossrelease: Apply crossrelease to page locks

On Tue, Dec 05, 2017 at 03:19:46PM +0900, Byungchul Park wrote: > On 12/5/2017 2:46 PM, Byungchul Park wrote: > > On 12/5/2017 2:30 PM, Matthew Wilcox wrote: > > > On Mon, Dec 04, 2017 at 02:16:19PM +0900, Byungchul Park wrote: > > > > For now, wait_for_completion() / complete() works with

Re: [PATCH v2 0/4] lockdep/crossrelease: Apply crossrelease to page locks

On Tue, Dec 05, 2017 at 03:19:46PM +0900, Byungchul Park wrote: > On 12/5/2017 2:46 PM, Byungchul Park wrote: > > On 12/5/2017 2:30 PM, Matthew Wilcox wrote: > > > On Mon, Dec 04, 2017 at 02:16:19PM +0900, Byungchul Park wrote: > > > > For now, wait_for_completion() / complete() works with

Re: [PATCH v3 1/1] at24: support eeproms that do not auto-rollover reads.

On Mon, Dec 04, 2017 at 05:24:33PM -0500, Sven Van Asbroeck wrote: > > If this is truly specific to at24, then vendor prefix would be appropriate, > > plus it'd go to an at24 specific binding file. However if it isn't I'd just > > remove the above sentence. I guess the latter? > > Yes,

Re: [PATCH v3 1/1] at24: support eeproms that do not auto-rollover reads.

On Mon, Dec 04, 2017 at 05:24:33PM -0500, Sven Van Asbroeck wrote: > > If this is truly specific to at24, then vendor prefix would be appropriate, > > plus it'd go to an at24 specific binding file. However if it isn't I'd just > > remove the above sentence. I guess the latter? > > Yes,

Re: [PATCH v2] mmap.2: MAP_FIXED updated documentation

On 12/04/2017 11:08 PM, Michal Hocko wrote: > On Mon 04-12-17 18:52:27, John Hubbard wrote: >> On 12/04/2017 03:31 AM, Mike Rapoport wrote: >>> On Sun, Dec 03, 2017 at 06:14:11PM -0800, john.hubb...@gmail.com wrote: From: John Hubbard >> [...] +.IP +Given

Re: [PATCH v2] mmap.2: MAP_FIXED updated documentation

On 12/04/2017 11:08 PM, Michal Hocko wrote: > On Mon 04-12-17 18:52:27, John Hubbard wrote: >> On 12/04/2017 03:31 AM, Mike Rapoport wrote: >>> On Sun, Dec 03, 2017 at 06:14:11PM -0800, john.hubb...@gmail.com wrote: From: John Hubbard >> [...] +.IP +Given the above

Re: [PATCH v2] mmap.2: MAP_FIXED updated documentation

On 12/04/2017 11:05 PM, Michal Hocko wrote: > On Mon 04-12-17 18:14:18, John Hubbard wrote: >> On 12/04/2017 02:55 AM, Cyril Hrubis wrote: >>> Hi! >>> I know that we are not touching the rest of the existing description for >>> MAP_FIXED however the second sentence in the manual page says that

Re: [PATCH v2] mmap.2: MAP_FIXED updated documentation

On 12/04/2017 11:05 PM, Michal Hocko wrote: > On Mon 04-12-17 18:14:18, John Hubbard wrote: >> On 12/04/2017 02:55 AM, Cyril Hrubis wrote: >>> Hi! >>> I know that we are not touching the rest of the existing description for >>> MAP_FIXED however the second sentence in the manual page says that

Re: [PATCH v3 13/16] iommu/intel-svm: notify page request to guest

Hi, On 11/18/2017 02:55 AM, Jacob Pan wrote: > If the source device of a page request has its PASID table pointer > bond to a guest, the first level page tables are owned by the guest. > In this case, we shall let guest OS to manage page fault. > > This patch uses the IOMMU fault notification API

Re: [PATCH v3 13/16] iommu/intel-svm: notify page request to guest

Hi, On 11/18/2017 02:55 AM, Jacob Pan wrote: > If the source device of a page request has its PASID table pointer > bond to a guest, the first level page tables are owned by the guest. > In this case, we shall let guest OS to manage page fault. > > This patch uses the IOMMU fault notification API

Re: [patch V4 02/11] LICENSES: Add the GPL 2.0 license

On Mon, Dec 04, 2017 at 10:19:29PM +0100, Thomas Gleixner wrote: > Add the full text of the GPL 2.0 license to the LICENSES directory. It was > copied directly from the COPYING file in the kernel source tree as it > differs from the public available version of the license in various places >

Re: [patch V4 02/11] LICENSES: Add the GPL 2.0 license

On Mon, Dec 04, 2017 at 10:19:29PM +0100, Thomas Gleixner wrote: > Add the full text of the GPL 2.0 license to the LICENSES directory. It was > copied directly from the COPYING file in the kernel source tree as it > differs from the public available version of the license in various places >

RE: [PATCH] refcount_t: documentation for memory ordering differences

On 11/29/2017 04:36 AM, Elena Reshetova wrote: > > Some functions from refcount_t API provide different > > memory ordering guarantees that their atomic counterparts. > > This adds a document outlining these differences. > > > > Signed-off-by: Elena Reshetova > > --- >

RE: [PATCH] refcount_t: documentation for memory ordering differences

On 11/29/2017 04:36 AM, Elena Reshetova wrote: > > Some functions from refcount_t API provide different > > memory ordering guarantees that their atomic counterparts. > > This adds a document outlining these differences. > > > > Signed-off-by: Elena Reshetova > > --- > >

Re: [PATCH 21/45] usb: typec: remove duplicate includes

On Tue, Dec 05, 2017 at 07:34:55AM +0530, Pravin Shedge wrote: > These duplicate includes have been found with scripts/checkincludes.pl but > they have been removed manually to avoid removing false positives. > > Signed-off-by: Pravin Shedge Acked-by: Heikki

Re: [PATCH 21/45] usb: typec: remove duplicate includes

On Tue, Dec 05, 2017 at 07:34:55AM +0530, Pravin Shedge wrote: > These duplicate includes have been found with scripts/checkincludes.pl but > they have been removed manually to avoid removing false positives. > > Signed-off-by: Pravin Shedge Acked-by: Heikki Krogerus > --- >

Re: [PATCH net-next V3] tun: add eBPF based queue selection method

On 2017年12月05日 08:16, Willem de Bruijn wrote: On Mon, Dec 4, 2017 at 4:31 AM, Jason Wang wrote: This patch introduces an eBPF based queue selection method. With this, the policy could be offloaded to userspace completely through a new ioctl TUNSETSTEERINGEBPF.

Re: [PATCH net-next V3] tun: add eBPF based queue selection method

On 2017年12月05日 08:16, Willem de Bruijn wrote: On Mon, Dec 4, 2017 at 4:31 AM, Jason Wang wrote: This patch introduces an eBPF based queue selection method. With this, the policy could be offloaded to userspace completely through a new ioctl TUNSETSTEERINGEBPF. Signed-off-by: Jason Wang ---

Re: [PATCH v2] sunxi-rsb: Include OF based modalias in device uevent

Hi, On Tue, Nov 28, 2017 at 11:47 PM, Maxime Ripard wrote: > On Mon, Nov 27, 2017 at 08:05:34PM +0100, Stefan Brüns wrote: >> Include the OF-based modalias in the uevent sent when registering devices >> on the sunxi RSB bus, so that user space has a chance to

Re: [PATCH v2] sunxi-rsb: Include OF based modalias in device uevent

Hi, On Tue, Nov 28, 2017 at 11:47 PM, Maxime Ripard wrote: > On Mon, Nov 27, 2017 at 08:05:34PM +0100, Stefan Brüns wrote: >> Include the OF-based modalias in the uevent sent when registering devices >> on the sunxi RSB bus, so that user space has a chance to autoload the >> kernel module for

Re: [PATCH] checkpatch: warn for use of %px

On Tue, 2017-12-05 at 08:17 +1100, Tobin C. Harding wrote: > Usage of the new %px specifier potentially leaks sensitive > inforamtion. Printing kernel addresses exposes the kernel layout in information > memory, this is potentially exploitable. We have tools in the kernel to > help us do the

Re: [PATCH] checkpatch: warn for use of %px

On Tue, 2017-12-05 at 08:17 +1100, Tobin C. Harding wrote: > Usage of the new %px specifier potentially leaks sensitive > inforamtion. Printing kernel addresses exposes the kernel layout in information > memory, this is potentially exploitable. We have tools in the kernel to > help us do the

Re: [PATCH v9 3/5] perf utils: use pmu->is_uncore to detect PMU UNCORE devices

Hi, I applied the diff but it's failed. jinyao@skl:~/skl-ws/perf-dev/lck-4594/src$ patch -p1 < 1.pat patching file tools/perf/util/pmu.c patch: malformed patch at line 41: *head, struct perf_pmu *pmu) Could you send the patch as attachment to me in another mail thread? to

Re: [PATCH v9 3/5] perf utils: use pmu->is_uncore to detect PMU UNCORE devices

Hi, I applied the diff but it's failed. jinyao@skl:~/skl-ws/perf-dev/lck-4594/src$ patch -p1 < 1.pat patching file tools/perf/util/pmu.c patch: malformed patch at line 41: *head, struct perf_pmu *pmu) Could you send the patch as attachment to me in another mail thread? to

Re: [PATCH 4.4 00/27] 4.4.104-stable review

- kernel: 4.4.104-rc1 git repo: https://git.linaro.org/lkft/arm64-stable-rc.git git tag: 4.4.104-rc1-hikey-20171204-67 git commit: fc49d1746dc96bedfe5bf072eecbe84410972db0 git describe: 4.4.104-rc1-hikey-20171204-67 Test details: https://qa-reports.linaro.org/lkft/li

Re: [PATCH 4.4 00/27] 4.4.104-stable review

kernel: 4.4.104-rc1 git repo: https://git.linaro.org/lkft/arm64-stable-rc.git git tag: 4.4.104-rc1-hikey-20171204-67 git commit: fc49d1746dc96bedfe5bf072eecbe84410972db0 git describe: 4.4.104-rc1-hikey-20171204-67 Test details: https://qa-reports.linaro.org/lkft/linaro-hikey-stable-rc-4.4-oe/build

Re: [PATCH v2 net-next] net/tcp: trace all TCP/IP state transition with tcp_set_state tracepoint

2017-12-05 3:28 GMT+08:00 Marcelo Ricardo Leitner : > On Sat, Dec 02, 2017 at 09:36:41AM +, Yafang Shao wrote: >> The TCP/IP transition from TCP_LISTEN to TCP_SYN_RECV and some other >> transitions are not traced with tcp_set_state tracepoint. >> >> In order to trace

Re: [PATCH v2 net-next] net/tcp: trace all TCP/IP state transition with tcp_set_state tracepoint

2017-12-05 3:28 GMT+08:00 Marcelo Ricardo Leitner : > On Sat, Dec 02, 2017 at 09:36:41AM +, Yafang Shao wrote: >> The TCP/IP transition from TCP_LISTEN to TCP_SYN_RECV and some other >> transitions are not traced with tcp_set_state tracepoint. >> >> In order to trace the whole tcp lifespans,

Re: [PATCH v9 3/5] perf utils: use pmu->is_uncore to detect PMU UNCORE devices

thanks Jin Yao for point this out. looks like logic of leveraging uncore device type(which i have changed in v9) does not go well with some json events of x86. can you please try below diff(logic used till v8), which keeps the original logic of identifying core/cpu PMUs. diff --git

Re: [PATCH v9 3/5] perf utils: use pmu->is_uncore to detect PMU UNCORE devices

thanks Jin Yao for point this out. looks like logic of leveraging uncore device type(which i have changed in v9) does not go well with some json events of x86. can you please try below diff(logic used till v8), which keeps the original logic of identifying core/cpu PMUs. diff --git

[PATCH RESEND] arm64: fault: avoid send SIGBUS two times

If APEI handling the memory error is failed, the do_mem_abort() and do_sea() will all deliver SIGBUS. In fact, sending one time can be enough, so correct it. Signed-off-by: Dongjiu Geng --- arch/arm64/mm/fault.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)

[PATCH RESEND] arm64: fault: avoid send SIGBUS two times

If APEI handling the memory error is failed, the do_mem_abort() and do_sea() will all deliver SIGBUS. In fact, sending one time can be enough, so correct it. Signed-off-by: Dongjiu Geng --- arch/arm64/mm/fault.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git

Re: [PATCH 4.9 00/38] 4.9.67-stable review

On 4 December 2017 at 21:29, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.67 release. > There are 38 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied,

Re: [PATCH 4.9 00/38] 4.9.67-stable review

On 4 December 2017 at 21:29, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.67 release. > There are 38 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > >

Re: [PATCH v2] mmap.2: MAP_FIXED updated documentation

On Mon 04-12-17 18:52:27, John Hubbard wrote: > On 12/04/2017 03:31 AM, Mike Rapoport wrote: > > On Sun, Dec 03, 2017 at 06:14:11PM -0800, john.hubb...@gmail.com wrote: > >> From: John Hubbard > >> > [...] > >> +.IP > >> +Given the above limitations, one of the very few ways

Re: [PATCH v2] mmap.2: MAP_FIXED updated documentation

On Mon 04-12-17 18:52:27, John Hubbard wrote: > On 12/04/2017 03:31 AM, Mike Rapoport wrote: > > On Sun, Dec 03, 2017 at 06:14:11PM -0800, john.hubb...@gmail.com wrote: > >> From: John Hubbard > >> > [...] > >> +.IP > >> +Given the above limitations, one of the very few ways to use this option >

Re: [PATCH] skb_array: fix NULL-pointer exception

On 2017年12月05日 12:40, Michael S. Tsirkin wrote: On Tue, Dec 05, 2017 at 11:11:14AM +0800, Jason Wang wrote: On 2017年12月04日 22:24, George Cherian wrote: While running a multiple VM testscase with each VM running iperf traffic between others the following kernel NULL pointer exception was

Re: [PATCH] skb_array: fix NULL-pointer exception

On 2017年12月05日 12:40, Michael S. Tsirkin wrote: On Tue, Dec 05, 2017 at 11:11:14AM +0800, Jason Wang wrote: On 2017年12月04日 22:24, George Cherian wrote: While running a multiple VM testscase with each VM running iperf traffic between others the following kernel NULL pointer exception was

Re: [PATCH v2] mmap.2: MAP_FIXED updated documentation

On Mon 04-12-17 18:14:18, John Hubbard wrote: > On 12/04/2017 02:55 AM, Cyril Hrubis wrote: > > Hi! > > I know that we are not touching the rest of the existing description for > > MAP_FIXED however the second sentence in the manual page says that "addr > > must be a multiple of the page size."

Re: [PATCH v2] mmap.2: MAP_FIXED updated documentation

On Mon 04-12-17 18:14:18, John Hubbard wrote: > On 12/04/2017 02:55 AM, Cyril Hrubis wrote: > > Hi! > > I know that we are not touching the rest of the existing description for > > MAP_FIXED however the second sentence in the manual page says that "addr > > must be a multiple of the page size."

Re: [PATCH 4.14 00/95] 4.14.4-stable review

On 4 December 2017 at 21:29, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.4 release. > There are 95 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied,

Re: [PATCH 4.14 00/95] 4.14.4-stable review

On 4 December 2017 at 21:29, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.4 release. > There are 95 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > >

[PATCH] arm64: avoid send SIGBUS two times

If APEI handling the memory error is failed, the SIGBUS will be sent twice. In fact, send one time can be enough, so correct it. Signed-off-by: Dongjiu Geng --- arch/arm64/mm/fault.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git

[PATCH] arm64: avoid send SIGBUS two times

If APEI handling the memory error is failed, the SIGBUS will be sent twice. In fact, send one time can be enough, so correct it. Signed-off-by: Dongjiu Geng --- arch/arm64/mm/fault.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/arch/arm64/mm/fault.c

Re: [PATCH] thermal/drivers/hisi: disable multi alarm support for hi3660 SoC

On 05/12/2017 03:02, Eduardo Valentin wrote: > Hello, > > On Thu, Oct 19, 2017 at 09:31:24AM +0800, Wangtao (Kevin, Kirin) wrote: >> >> >> 在 2017/10/18 23:54, Daniel Lezcano 写道: >>> On 18/10/2017 11:15, Tao Wang wrote: From: Kevin Wangtao multi alarm

Re: [PATCH] thermal/drivers/hisi: disable multi alarm support for hi3660 SoC

On 05/12/2017 03:02, Eduardo Valentin wrote: > Hello, > > On Thu, Oct 19, 2017 at 09:31:24AM +0800, Wangtao (Kevin, Kirin) wrote: >> >> >> 在 2017/10/18 23:54, Daniel Lezcano 写道: >>> On 18/10/2017 11:15, Tao Wang wrote: From: Kevin Wangtao multi alarm interrupt forced a re-trigger

Re: [PATCH] SCSI: delay run queue if device is blocked in scsi_dev_queue_ready()

On Tue, Dec 05, 2017 at 01:16:24PM +0800, Ming Lei wrote: > On Mon, Dec 04, 2017 at 11:48:07PM +, Holger Hoffstätte wrote: > > On Tue, 05 Dec 2017 06:45:08 +0800, Ming Lei wrote: > > > > > On Mon, Dec 04, 2017 at 03:09:20PM +, Bart Van Assche wrote: > > >> On Sun, 2017-12-03 at 00:31

Re: [PATCH] SCSI: delay run queue if device is blocked in scsi_dev_queue_ready()

On Tue, Dec 05, 2017 at 01:16:24PM +0800, Ming Lei wrote: > On Mon, Dec 04, 2017 at 11:48:07PM +, Holger Hoffstätte wrote: > > On Tue, 05 Dec 2017 06:45:08 +0800, Ming Lei wrote: > > > > > On Mon, Dec 04, 2017 at 03:09:20PM +, Bart Van Assche wrote: > > >> On Sun, 2017-12-03 at 00:31

Re: [patch V4 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

On Mon, Dec 04, 2017 at 10:19:28PM +0100, Thomas Gleixner wrote: > +3. Syntax: > + > + A is either an SPDX short form license > + identifier found on the SPDX License List, or when multiple licenses > + apply, an expression consisting of keywords "AND", "OR", and "WITH" > + separating

Re: [patch V4 01/11] Documentation: Add license-rules.rst to describe how to properly identify file licenses

On Mon, Dec 04, 2017 at 10:19:28PM +0100, Thomas Gleixner wrote: > +3. Syntax: > + > + A is either an SPDX short form license > + identifier found on the SPDX License List, or when multiple licenses > + apply, an expression consisting of keywords "AND", "OR", and "WITH" > + separating

Re: [PATCH V2] thermal/drivers/hisi: Switch to interrupt mode

On 05/12/2017 03:00, Eduardo Valentin wrote: > Hello, > > On Thu, Sep 28, 2017 at 09:32:20AM +0200, Daniel Lezcano wrote: >> On Thu, Sep 28, 2017 at 02:57:52PM +0800, Leo Yan wrote: >>> Hi Daniel, >>> >>> On Thu, Sep 28, 2017 at 07:13:44AM +0200, Daniel Lezcano wrote: At this moment, we have

Re: [PATCH V2] thermal/drivers/hisi: Switch to interrupt mode

On 05/12/2017 03:00, Eduardo Valentin wrote: > Hello, > > On Thu, Sep 28, 2017 at 09:32:20AM +0200, Daniel Lezcano wrote: >> On Thu, Sep 28, 2017 at 02:57:52PM +0800, Leo Yan wrote: >>> Hi Daniel, >>> >>> On Thu, Sep 28, 2017 at 07:13:44AM +0200, Daniel Lezcano wrote: At this moment, we have

[PATCH 1/2] ARM: dts: keystone-k2g: Add UART 1 and 2 instances

From: Franklin S Cooper Jr Add DT nodes for two other UART instances of 66AK2G SoC. Also add power domain and clock domain nodes to UART 0 Signed-off-by: Franklin S Cooper Jr Signed-off-by: Vignesh R --- arch/arm/boot/dts/keystone-k2g.dtsi |

[PATCH 1/2] ARM: dts: keystone-k2g: Add UART 1 and 2 instances

From: Franklin S Cooper Jr Add DT nodes for two other UART instances of 66AK2G SoC. Also add power domain and clock domain nodes to UART 0 Signed-off-by: Franklin S Cooper Jr Signed-off-by: Vignesh R --- arch/arm/boot/dts/keystone-k2g.dtsi | 29 - 1 file changed,

Re: [PATCH] thermal/drivers/hisi: Remove confusing error message

On 05/12/2017 02:52, Eduardo Valentin wrote: > Hello, > > Catching up on old patches. > On Fri, Jul 07, 2017 at 05:03:52PM +0200, Daniel Lezcano wrote: >> The sensor id is unknown at init time and we use all id in the authorized >> MAX_SENSORS interval to register the sensor. On this SoC there is

[PATCH 0/2] 66AK2G: Add DT entry for UART1 and UART2

This series adds DT entry for the remaining two UART instances on 66AK2G SoC. Based on linux-next. Franklin S Cooper Jr (2): ARM: dts: keystone-k2g: Add UART 1 and 2 instances ARM: dts: keystone-k2g-evm: Enable UART 2 arch/arm/boot/dts/keystone-k2g-evm.dts | 13 +

[PATCH 2/2] ARM: dts: keystone-k2g-evm: Enable UART 2

From: Franklin S Cooper Jr 66AK2G GP EVM has a Baseboard Management Controller (BMC) on board. This controller handles things like setting the SoCs boot mode along with controlling the on board character LCD display module. Enable UART2 which communicates with the BMC. This

Re: [PATCH] thermal/drivers/hisi: Remove confusing error message

On 05/12/2017 02:52, Eduardo Valentin wrote: > Hello, > > Catching up on old patches. > On Fri, Jul 07, 2017 at 05:03:52PM +0200, Daniel Lezcano wrote: >> The sensor id is unknown at init time and we use all id in the authorized >> MAX_SENSORS interval to register the sensor. On this SoC there is

[PATCH 0/2] 66AK2G: Add DT entry for UART1 and UART2

This series adds DT entry for the remaining two UART instances on 66AK2G SoC. Based on linux-next. Franklin S Cooper Jr (2): ARM: dts: keystone-k2g: Add UART 1 and 2 instances ARM: dts: keystone-k2g-evm: Enable UART 2 arch/arm/boot/dts/keystone-k2g-evm.dts | 13 +

[PATCH 2/2] ARM: dts: keystone-k2g-evm: Enable UART 2

From: Franklin S Cooper Jr 66AK2G GP EVM has a Baseboard Management Controller (BMC) on board. This controller handles things like setting the SoCs boot mode along with controlling the on board character LCD display module. Enable UART2 which communicates with the BMC. This enables userspace

Re: [PATCH v4 3/5] remoteproc: Pass type of shutdown to subdev remove

On Fri 01 Dec 06:50 PST 2017, Arnaud Pouliquen wrote: > hello Bjorn, > > Sorry for these late remarks/questions > No worries, I'm happy to see you reading the patch! > > On 11/30/2017 02:16 AM, Bjorn Andersson wrote: [..] > > diff --git a/drivers/remoteproc/qcom_common.c > >

Re: [PATCH v4 3/5] remoteproc: Pass type of shutdown to subdev remove

On Fri 01 Dec 06:50 PST 2017, Arnaud Pouliquen wrote: > hello Bjorn, > > Sorry for these late remarks/questions > No worries, I'm happy to see you reading the patch! > > On 11/30/2017 02:16 AM, Bjorn Andersson wrote: [..] > > diff --git a/drivers/remoteproc/qcom_common.c > >

[PATCH v2 2/2] regulator: sc2731: Add regulator driver to support Spreadtrum SC2731 PMIC

Add regulator driver for Spreadtrum SC2731 device. It has 17 general purpose LDOs, BUCKs generator and digital output to control regulators. Signed-off-by: Erick Chen Reviewed-by: Baolin Wang --- Changes since v1: - Remove of_device_id

[PATCH v2 2/2] regulator: sc2731: Add regulator driver to support Spreadtrum SC2731 PMIC

Add regulator driver for Spreadtrum SC2731 device. It has 17 general purpose LDOs, BUCKs generator and digital output to control regulators. Signed-off-by: Erick Chen Reviewed-by: Baolin Wang --- Changes since v1: - Remove of_device_id table. - Change subsys_init() to module_init(). - Change

[PATCH v2 1/2] dt-bindings: regulator: Add Spreadtrum SC2731 regulator documentation

This patch adds support for the Spreadtrum SC2731 voltage regulator device. Signed-off-by: Erick Chen --- Changes since v1: - Remove reg property. - Remove regulators sub-node. --- .../bindings/regulator/sprd,sc2731-regulator.txt | 43 1 file

[PATCH v2 1/2] dt-bindings: regulator: Add Spreadtrum SC2731 regulator documentation

This patch adds support for the Spreadtrum SC2731 voltage regulator device. Signed-off-by: Erick Chen --- Changes since v1: - Remove reg property. - Remove regulators sub-node. --- .../bindings/regulator/sprd,sc2731-regulator.txt | 43 1 file changed, 43 insertions(+)

RE: [Bug fix] octeon-i2c driver updates

Hi Jan, Thanks for your comments, I get your point for the second point (retry of START after recovery). Hi David, For the issue as the first one, would you give your further comments? Thanks in advance. I have an environment with CN6780 (TWSI core has property: compatible =

RE: [Bug fix] octeon-i2c driver updates

Hi Jan, Thanks for your comments, I get your point for the second point (retry of START after recovery). Hi David, For the issue as the first one, would you give your further comments? Thanks in advance. I have an environment with CN6780 (TWSI core has property: compatible =

[PATCH] writeback: fix comment in __mark_inode_dirty

Signed-off-by: Wang Long --- fs/fs-writeback.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c index cea4836..8d477cf 100644 --- a/fs/fs-writeback.c +++ b/fs/fs-writeback.c @@ -2209,7 +2209,7 @@ void

[PATCH] writeback: fix comment in __mark_inode_dirty

Signed-off-by: Wang Long --- fs/fs-writeback.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c index cea4836..8d477cf 100644 --- a/fs/fs-writeback.c +++ b/fs/fs-writeback.c @@ -2209,7 +2209,7 @@ void __mark_inode_dirty(struct inode

Re: [PATCH v3 12/16] iommu/vt-d: report unrecoverable device faults

Hi, On 11/18/2017 02:55 AM, Jacob Pan wrote: > Currently, when device DMA faults are detected by IOMMU the fault > reasons are printed but the driver of the offending device is "... but the driver of the offending device is not involved in ..." Best regards, Lu Baolu > involved in fault

Re: [PATCH v3 12/16] iommu/vt-d: report unrecoverable device faults

Hi, On 11/18/2017 02:55 AM, Jacob Pan wrote: > Currently, when device DMA faults are detected by IOMMU the fault > reasons are printed but the driver of the offending device is "... but the driver of the offending device is not involved in ..." Best regards, Lu Baolu > involved in fault

Re: [alsa-devel] [PATCH v4 06/15] soundwire: Add IO transfer

On Sun, Dec 03, 2017 at 09:01:41PM -0600, Pierre-Louis Bossart wrote: > On 12/3/17 11:04 AM, Vinod Koul wrote: > >On Fri, Dec 01, 2017 at 05:27:31PM -0600, Pierre-Louis Bossart wrote: Sorry looks like I missed replying to this one earlier. > >>>+static inline int find_response_code(enum

Re: [alsa-devel] [PATCH v4 06/15] soundwire: Add IO transfer

On Sun, Dec 03, 2017 at 09:01:41PM -0600, Pierre-Louis Bossart wrote: > On 12/3/17 11:04 AM, Vinod Koul wrote: > >On Fri, Dec 01, 2017 at 05:27:31PM -0600, Pierre-Louis Bossart wrote: Sorry looks like I missed replying to this one earlier. > >>>+static inline int find_response_code(enum

[PATCH v3] scripts: leaking_addresses: add support for 32-bit kernel addresses

Currently, leaking_addresses.pl only supports scanning 64 bit architectures. This is due to how the regular expressions are formed. We can do better than this. 32 architectures can be supported if we take into consideration the kernel virtual address split (via the PAGE_OFFSET kernel

[PATCH v3] scripts: leaking_addresses: add support for 32-bit kernel addresses

Currently, leaking_addresses.pl only supports scanning 64 bit architectures. This is due to how the regular expressions are formed. We can do better than this. 32 architectures can be supported if we take into consideration the kernel virtual address split (via the PAGE_OFFSET kernel

Re: [PATCH 4.14 00/95] 4.14.4-stable review

On Mon, Dec 04, 2017 at 01:29:42PM -0700, Shuah Khan wrote: > On 12/04/2017 08:59 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.14.4 release. > > There are 95 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH 4.14 00/95] 4.14.4-stable review

On Mon, Dec 04, 2017 at 01:29:42PM -0700, Shuah Khan wrote: > On 12/04/2017 08:59 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.14.4 release. > > There are 95 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH 4.14 00/95] 4.14.4-stable review

On Mon, Dec 04, 2017 at 03:46:31PM -0800, Guenter Roeck wrote: > On Mon, Dec 04, 2017 at 04:59:24PM +0100, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.14.4 release. > > There are 95 patches in this series, all will be posted as a response > > to this one.

[PATCH v3 08/14] nubus: Clean up whitespace

Tested-by: Stan Johnson Signed-off-by: Finn Thain --- include/linux/nubus.h | 54 +-- 1 file changed, 27 insertions(+), 27 deletions(-) diff --git a/include/linux/nubus.h b/include/linux/nubus.h

Re: [PATCH 4.14 00/95] 4.14.4-stable review

On Mon, Dec 04, 2017 at 03:46:31PM -0800, Guenter Roeck wrote: > On Mon, Dec 04, 2017 at 04:59:24PM +0100, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.14.4 release. > > There are 95 patches in this series, all will be posted as a response > > to this one.

[PATCH v3 08/14] nubus: Clean up whitespace

Tested-by: Stan Johnson Signed-off-by: Finn Thain --- include/linux/nubus.h | 54 +-- 1 file changed, 27 insertions(+), 27 deletions(-) diff --git a/include/linux/nubus.h b/include/linux/nubus.h index 46e4d983feac..84f2e0fa1898 100644 ---

Re: [PATCH 4.14 00/95] 4.14.4-stable review

On Mon, Dec 04, 2017 at 03:12:45PM -0600, Tom Gall wrote: > > > > On Dec 4, 2017, at 9:59 AM, Greg Kroah-Hartman > > wrote: > > > > This is the start of the stable review cycle for the 4.14.4 release. > > There are 95 patches in this series, all will be posted as a

Re: [PATCH 4.14 00/95] 4.14.4-stable review

On Mon, Dec 04, 2017 at 03:12:45PM -0600, Tom Gall wrote: > > > > On Dec 4, 2017, at 9:59 AM, Greg Kroah-Hartman > > wrote: > > > > This is the start of the stable review cycle for the 4.14.4 release. > > There are 95 patches in this series, all will be posted as a response > > to this one.

[PATCH v3 04/14] nubus: Fix log spam

Testing shows that a single Radius PrecisionColor 24X display board, which has 95 functional resources, produces over a thousand lines of log messages. Suppress these messages with pr_debug(). Remove some redundant messages relating to nubus_get_subdir() calls. Fix the format block debug messages

[PATCH v3 04/14] nubus: Fix log spam

Testing shows that a single Radius PrecisionColor 24X display board, which has 95 functional resources, produces over a thousand lines of log messages. Suppress these messages with pr_debug(). Remove some redundant messages relating to nubus_get_subdir() calls. Fix the format block debug messages

[PATCH v3 09/14] nubus: Generalize block resource handling

Scrap the specialized code to unpack video mode name resources and driver resources. It isn't useful. Instead, add a re-usable function to handle lists of block resources of any kind, and descend into the video mode table resource directory. Rename callers as nubus_get_foo(), consistent with their

[PATCH v3 10/14] nubus: Rework /proc/bus/nubus/s/ implementation

The /proc/bus/nubus/s/ directory tree for any slot s is missing a lot of information. The struct file_operations methods have long been left unimplemented (hence the familiar compile-time warning, "Need to set some I/O handlers here"). Slot resources have a complex structure which varies

[PATCH v3 09/14] nubus: Generalize block resource handling

Scrap the specialized code to unpack video mode name resources and driver resources. It isn't useful. Instead, add a re-usable function to handle lists of block resources of any kind, and descend into the video mode table resource directory. Rename callers as nubus_get_foo(), consistent with their

[PATCH v3 10/14] nubus: Rework /proc/bus/nubus/s/ implementation

The /proc/bus/nubus/s/ directory tree for any slot s is missing a lot of information. The struct file_operations methods have long been left unimplemented (hence the familiar compile-time warning, "Need to set some I/O handlers here"). Slot resources have a complex structure which varies

  1   2   3   4   5   6   7   8   9   10   >