[PATCH 03/10] staging: slicoss: slic.h: add a macro IOMEM_SET_FIELD32 to fix sparse warnings

Signed-off-by: Peng Sun --- drivers/staging/slicoss/slic.h | 7 +++ 1 file changed, 7 insertions(+) diff --git a/drivers/staging/slicoss/slic.h b/drivers/staging/slicoss/slic.h index ff71070..4c22863 100644 --- a/drivers/staging/slicoss/slic.h +++ b/drivers/staging/slicoss/slic.h @@ -553,6

[PATCH 06/10] staging: slicoss: slicoss.c: fix different address space sparse warning

Signed-off-by: Peng Sun --- drivers/staging/slicoss/slicoss.c | 49 +-- 1 file changed, 32 insertions(+), 17 deletions(-) diff --git a/drivers/staging/slicoss/slicoss.c b/drivers/staging/slicoss/slicoss.c index 929a0d5..03b01c5 100644 ---

[PATCH 09/10] staging: slicoss: slicoss.c: fix different address space sparse warning

Signed-off-by: Peng Sun --- drivers/staging/slicoss/slicoss.c | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/drivers/staging/slicoss/slicoss.c b/drivers/staging/slicoss/slicoss.c index a2d9c77..6ecf71c 100644 ---

[PATCH 07/10] staging: slicoss: slicoss.c: fix different address space sparse warning

Signed-off-by: Peng Sun --- drivers/staging/slicoss/slicoss.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/drivers/staging/slicoss/slicoss.c b/drivers/staging/slicoss/slicoss.c index 03b01c5..2097d64 100644 ---

[PATCH 10/10] staging: slicoss: slicoss.c: fix different address space sparse warning

Signed-off-by: Peng Sun --- drivers/staging/slicoss/slicoss.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/slicoss/slicoss.c b/drivers/staging/slicoss/slicoss.c index 6ecf71c..e94dbd4 100644 --- a/drivers/staging/slicoss/slicoss.c

[PATCH 08/10] staging: slicoss: slicoss.c: fix different address space sparse warning

Signed-off-by: Peng Sun --- drivers/staging/slicoss/slicoss.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/staging/slicoss/slicoss.c b/drivers/staging/slicoss/slicoss.c index 2097d64..a2d9c77 100644 ---

[PATCH 09/10] staging: slicoss: slicoss.c: fix different address space sparse warning

Signed-off-by: Peng Sun --- drivers/staging/slicoss/slicoss.c | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/drivers/staging/slicoss/slicoss.c b/drivers/staging/slicoss/slicoss.c index a2d9c77..6ecf71c 100644 --- a/drivers/staging/slicoss/slicoss.c +++

[PATCH 07/10] staging: slicoss: slicoss.c: fix different address space sparse warning

Signed-off-by: Peng Sun --- drivers/staging/slicoss/slicoss.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/drivers/staging/slicoss/slicoss.c b/drivers/staging/slicoss/slicoss.c index 03b01c5..2097d64 100644 --- a/drivers/staging/slicoss/slicoss.c +++

[PATCH 10/10] staging: slicoss: slicoss.c: fix different address space sparse warning

Signed-off-by: Peng Sun --- drivers/staging/slicoss/slicoss.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/slicoss/slicoss.c b/drivers/staging/slicoss/slicoss.c index 6ecf71c..e94dbd4 100644 --- a/drivers/staging/slicoss/slicoss.c +++

[PATCH 08/10] staging: slicoss: slicoss.c: fix different address space sparse warning

Signed-off-by: Peng Sun --- drivers/staging/slicoss/slicoss.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/staging/slicoss/slicoss.c b/drivers/staging/slicoss/slicoss.c index 2097d64..a2d9c77 100644 --- a/drivers/staging/slicoss/slicoss.c +++

[PATCH 04/10] staging: slicoss: slic.h: add a macro IOMEM_GET_FIELD64 to fix sparse warnings

Signed-off-by: Peng Sun --- drivers/staging/slicoss/slic.h | 25 + 1 file changed, 25 insertions(+) diff --git a/drivers/staging/slicoss/slic.h b/drivers/staging/slicoss/slic.h index 4c22863..b9595c4 100644 --- a/drivers/staging/slicoss/slic.h

[PATCH 05/10] staging: slicoss: slicoss.c: fix different address space sparse warning

Signed-off-by: Peng Sun --- drivers/staging/slicoss/slicoss.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/staging/slicoss/slicoss.c b/drivers/staging/slicoss/slicoss.c index 21280a3..929a0d5 100644 ---

[PATCH 04/10] staging: slicoss: slic.h: add a macro IOMEM_GET_FIELD64 to fix sparse warnings

Signed-off-by: Peng Sun --- drivers/staging/slicoss/slic.h | 25 + 1 file changed, 25 insertions(+) diff --git a/drivers/staging/slicoss/slic.h b/drivers/staging/slicoss/slic.h index 4c22863..b9595c4 100644 --- a/drivers/staging/slicoss/slic.h +++

[PATCH 05/10] staging: slicoss: slicoss.c: fix different address space sparse warning

Signed-off-by: Peng Sun --- drivers/staging/slicoss/slicoss.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/staging/slicoss/slicoss.c b/drivers/staging/slicoss/slicoss.c index 21280a3..929a0d5 100644 --- a/drivers/staging/slicoss/slicoss.c +++

[PATCH 01/10] staging: slicoss: slic.h: add a macro IOMEM_GET_FIELDADDR to fix sparse warnings

Signed-off-by: Peng Sun --- drivers/staging/slicoss/slic.h | 7 +++ 1 file changed, 7 insertions(+) diff --git a/drivers/staging/slicoss/slic.h b/drivers/staging/slicoss/slic.h index fe1d2ce..7c23190 100644 --- a/drivers/staging/slicoss/slic.h +++

[PATCH 01/10] staging: slicoss: slic.h: add a macro IOMEM_GET_FIELDADDR to fix sparse warnings

Signed-off-by: Peng Sun --- drivers/staging/slicoss/slic.h | 7 +++ 1 file changed, 7 insertions(+) diff --git a/drivers/staging/slicoss/slic.h b/drivers/staging/slicoss/slic.h index fe1d2ce..7c23190 100644 --- a/drivers/staging/slicoss/slic.h +++ b/drivers/staging/slicoss/slic.h @@ -539,6

[PATCH 00/10] staging: slicoss: fix different address space sparse warnings

base commit-id d221eb9f14f9 Peng Sun (10): staging: slicoss: slic.h: add a macro IOMEM_GET_FIELDADDR to fix sparse warnings staging: slicoss: slic.h: add a macro IOMEM_GET_FIELD32 to fix sparse warnings staging: slicoss: slic.h: add a macro IOMEM_SET_FIELD32 to fix sparse

[PATCH 00/10] staging: slicoss: fix different address space sparse warnings

base commit-id d221eb9f14f9 Peng Sun (10): staging: slicoss: slic.h: add a macro IOMEM_GET_FIELDADDR to fix sparse warnings staging: slicoss: slic.h: add a macro IOMEM_GET_FIELD32 to fix sparse warnings staging: slicoss: slic.h: add a macro IOMEM_SET_FIELD32 to fix sparse

Re: [PATCH v2 3/4] ARM: dts: Add NextThing GR8 dtsi

Hi Linus, On Mon, Sep 12, 2016 at 8:40 PM, Linus Walleij wrote: > On Thu, Sep 8, 2016 at 9:37 AM, Maxime Ripard > wrote: >> On Thu, Sep 08, 2016 at 12:46:14PM +0800, Chen-Yu Tsai wrote: > >>> Also, I think we are needlessly using pin

Re: [PATCH v2 3/4] ARM: dts: Add NextThing GR8 dtsi

Hi Linus, On Mon, Sep 12, 2016 at 8:40 PM, Linus Walleij wrote: > On Thu, Sep 8, 2016 at 9:37 AM, Maxime Ripard > wrote: >> On Thu, Sep 08, 2016 at 12:46:14PM +0800, Chen-Yu Tsai wrote: > >>> Also, I think we are needlessly using pin groups, 1 pin per group. >>> Can pinconf/pinctrl work without

Re: [PATCH] usb: chipidea: Properly mark little endian descriptors

On Wed, Sep 14, 2016 at 10:37:40AM +0800, Peter Chen wrote: > On Tue, Sep 13, 2016 at 04:06:31PM -0700, Stephen Boyd wrote: > > The DMA descriptors are little endian, and we do a pretty good > > job of handling them with the proper le32_to_cpu() markings, but > > we don't actually mark them as

Re: [PATCH] usb: chipidea: Properly mark little endian descriptors

On Wed, Sep 14, 2016 at 10:37:40AM +0800, Peter Chen wrote: > On Tue, Sep 13, 2016 at 04:06:31PM -0700, Stephen Boyd wrote: > > The DMA descriptors are little endian, and we do a pretty good > > job of handling them with the proper le32_to_cpu() markings, but > > we don't actually mark them as

Re: [PATCH v2 3/4] ARM: dts: Add NextThing GR8 dtsi

On Thu, Sep 8, 2016 at 3:41 PM, Maxime Ripard wrote: > On Thu, Sep 08, 2016 at 12:32:48AM +0800, Chen-Yu Tsai wrote: >> On Wed, Sep 7, 2016 at 10:53 PM, Maxime Ripard >> wrote: >> > From: Mylène Josserand

Re: [PATCH v2 3/4] ARM: dts: Add NextThing GR8 dtsi

On Thu, Sep 8, 2016 at 3:41 PM, Maxime Ripard wrote: > On Thu, Sep 08, 2016 at 12:32:48AM +0800, Chen-Yu Tsai wrote: >> On Wed, Sep 7, 2016 at 10:53 PM, Maxime Ripard >> wrote: >> > From: Mylène Josserand >> > >> > The GR8 is an SoC made by Nextthing loosely based on the sun5i family. >> > >> >

Re: [RFC] fs: add userspace critical mounts event support

On 09/02/2016 07:20 PM, Luis R. Rodriguez wrote: > kernel_read_file_from_path() can try to read a file from > the system's filesystem. This is typically done for firmware > for instance, which lives in /lib/firmware. One issue with > this is that the kernel cannot know for sure when the real >

Re: [RFC] fs: add userspace critical mounts event support

On 09/02/2016 07:20 PM, Luis R. Rodriguez wrote: > kernel_read_file_from_path() can try to read a file from > the system's filesystem. This is typically done for firmware > for instance, which lives in /lib/firmware. One issue with > this is that the kernel cannot know for sure when the real >

Re: [PATCH] usb: chipidea: Properly mark little endian descriptors

On Tue, Sep 13, 2016 at 04:06:31PM -0700, Stephen Boyd wrote: > The DMA descriptors are little endian, and we do a pretty good > job of handling them with the proper le32_to_cpu() markings, but > we don't actually mark them as __le32. This means checkers like > sparse can't easily find new bugs.

Re: [PATCH] usb: chipidea: Properly mark little endian descriptors

On Tue, Sep 13, 2016 at 04:06:31PM -0700, Stephen Boyd wrote: > The DMA descriptors are little endian, and we do a pretty good > job of handling them with the proper le32_to_cpu() markings, but > we don't actually mark them as __le32. This means checkers like > sparse can't easily find new bugs.

Re: Build failure in -next due to 'kbuild: allow archs to select link dead code/data elimination'

On Tue, 13 Sep 2016 13:25:22 -0700 Guenter Roeck wrote: > On 09/12/2016 08:51 PM, Nicholas Piggin wrote: > > On Mon, 12 Sep 2016 20:17:30 -0700 > > Guenter Roeck wrote: > > > >> Hi Nicholas, > >> > >> On 09/12/2016 07:00 PM, Nicholas Piggin wrote: >

Re: Build failure in -next due to 'kbuild: allow archs to select link dead code/data elimination'

On Tue, 13 Sep 2016 13:25:22 -0700 Guenter Roeck wrote: > On 09/12/2016 08:51 PM, Nicholas Piggin wrote: > > On Mon, 12 Sep 2016 20:17:30 -0700 > > Guenter Roeck wrote: > > > >> Hi Nicholas, > >> > >> On 09/12/2016 07:00 PM, Nicholas Piggin wrote: > >>> On Mon, 12 Sep 2016 15:24:43 -0700 >

Re: [PATCH] crypto: squash lines for simple wrapper functions

On Wed, 2016-09-14 at 11:10 +0900, Masahiro Yamada wrote: > 2016-09-13 4:44 GMT+09:00 Joe Perches : > > On Tue, 2016-09-13 at 04:27 +0900, Masahiro Yamada wrote: > > > Remove unneeded variables and assignments. > > Was this found by visual inspection or some tool? > > If it's via

Re: [PATCH] crypto: squash lines for simple wrapper functions

On Wed, 2016-09-14 at 11:10 +0900, Masahiro Yamada wrote: > 2016-09-13 4:44 GMT+09:00 Joe Perches : > > On Tue, 2016-09-13 at 04:27 +0900, Masahiro Yamada wrote: > > > Remove unneeded variables and assignments. > > Was this found by visual inspection or some tool? > > If it's via a tool, it's good

Re: [PATCH v3 07/15] lockdep: Implement crossrelease feature

On Wed, Sep 14, 2016 at 4:38 AM, Peter Zijlstra wrote: > On Wed, Sep 14, 2016 at 02:12:51AM +0900, Byungchul Park wrote: >> On Wed, Sep 14, 2016 at 12:05 AM, Peter Zijlstra >> wrote: >> > >> > >> > So the idea is to add support for non-owner

Re: [PATCH v3 07/15] lockdep: Implement crossrelease feature

On Wed, Sep 14, 2016 at 4:38 AM, Peter Zijlstra wrote: > On Wed, Sep 14, 2016 at 02:12:51AM +0900, Byungchul Park wrote: >> On Wed, Sep 14, 2016 at 12:05 AM, Peter Zijlstra >> wrote: >> > >> > >> > So the idea is to add support for non-owner serialization primitives, >> > like

[PATCH v2] sched/core: remove unnecessary initialization in sched_init()

init_idle() is called immediately after current->sched_class = _sched_class, init_idle() sets current->sched_class = _sched_class. Signed-off-by: Cheng Chao Cc: sta...@vger.kernel.org --- kernel/sched/core.c | 5 - 1 file changed, 5 deletions(-) diff --git

[PATCH v2] sched/core: remove unnecessary initialization in sched_init()

init_idle() is called immediately after current->sched_class = _sched_class, init_idle() sets current->sched_class = _sched_class. Signed-off-by: Cheng Chao Cc: sta...@vger.kernel.org --- kernel/sched/core.c | 5 - 1 file changed, 5 deletions(-) diff --git a/kernel/sched/core.c

[PATCH] sched/core: emove unnecessary initialization in sched_init()

init_idle() is called immediately after current->sched_class = _sched_class, init_idle() sets current->sched_class = _sched_class. Signed-off-by: Cheng Chao Cc: sta...@vger.kernel.org --- kernel/sched/core.c | 5 - 1 file changed, 5 deletions(-) diff --git

[PATCH] sched/core: emove unnecessary initialization in sched_init()

init_idle() is called immediately after current->sched_class = _sched_class, init_idle() sets current->sched_class = _sched_class. Signed-off-by: Cheng Chao Cc: sta...@vger.kernel.org --- kernel/sched/core.c | 5 - 1 file changed, 5 deletions(-) diff --git a/kernel/sched/core.c

Re: [PATCH v4 22/22] phy: Add support for Qualcomm's USB HS phy

On Tue, Sep 13, 2016 at 01:41:44PM -0700, Stephen Boyd wrote: > Quoting Peter Chen (2016-09-13 00:03:58) > > On Wed, Sep 07, 2016 at 02:35:19PM -0700, Stephen Boyd wrote: > > > The high-speed phy on qcom SoCs is controlled via the ULPI > > > viewport. > > > > > > > Hi Stephen, I am a little

Re: [PATCH v4 22/22] phy: Add support for Qualcomm's USB HS phy

On Tue, Sep 13, 2016 at 01:41:44PM -0700, Stephen Boyd wrote: > Quoting Peter Chen (2016-09-13 00:03:58) > > On Wed, Sep 07, 2016 at 02:35:19PM -0700, Stephen Boyd wrote: > > > The high-speed phy on qcom SoCs is controlled via the ULPI > > > viewport. > > > > > > > Hi Stephen, I am a little

Re: [PATCH] crypto: squash lines for simple wrapper functions

Hi Joe, 2016-09-13 4:44 GMT+09:00 Joe Perches : > On Tue, 2016-09-13 at 04:27 +0900, Masahiro Yamada wrote: >> Remove unneeded variables and assignments. > > Was this found by visual inspection or some tool? > > If it's via a tool, it's good to mention that in the changelog. I

Re: [PATCH] crypto: squash lines for simple wrapper functions

Hi Joe, 2016-09-13 4:44 GMT+09:00 Joe Perches : > On Tue, 2016-09-13 at 04:27 +0900, Masahiro Yamada wrote: >> Remove unneeded variables and assignments. > > Was this found by visual inspection or some tool? > > If it's via a tool, it's good to mention that in the changelog. I used Coccinelle,

RE: [PATCH for-next 10/20] IB/hns: Modify the init of iboe lock

> -Original Message- > From: linux-rdma-ow...@vger.kernel.org [mailto:linux-rdma- > ow...@vger.kernel.org] On Behalf Of Leon Romanovsky > Sent: Tuesday, September 13, 2016 7:50 AM > To: Salil Mehta > Cc: dledf...@redhat.com; Huwei (Xavier); oulijun; Zhuangyuzeng (Yisen); > xuwei (O);

RE: [PATCH for-next 10/20] IB/hns: Modify the init of iboe lock

> -Original Message- > From: linux-rdma-ow...@vger.kernel.org [mailto:linux-rdma- > ow...@vger.kernel.org] On Behalf Of Leon Romanovsky > Sent: Tuesday, September 13, 2016 7:50 AM > To: Salil Mehta > Cc: dledf...@redhat.com; Huwei (Xavier); oulijun; Zhuangyuzeng (Yisen); > xuwei (O);

RE: [PATCH for-next 16/20] IB/hns: Validate mtu when modified qp

> -Original Message- > From: Leon Romanovsky [mailto:l...@kernel.org] > Sent: Tuesday, September 13, 2016 7:33 AM > To: Salil Mehta > Cc: dledf...@redhat.com; Huwei (Xavier); oulijun; Zhuangyuzeng (Yisen); > xuwei (O); mehta.salil@gmail.com; linux-r...@vger.kernel.org; >

RE: [PATCH for-next 16/20] IB/hns: Validate mtu when modified qp

> -Original Message- > From: Leon Romanovsky [mailto:l...@kernel.org] > Sent: Tuesday, September 13, 2016 7:33 AM > To: Salil Mehta > Cc: dledf...@redhat.com; Huwei (Xavier); oulijun; Zhuangyuzeng (Yisen); > xuwei (O); mehta.salil@gmail.com; linux-r...@vger.kernel.org; >

Re: [PATCH v3] stop_machine: Make migration_cpu_stop() does useful works for CONFIG_PREEMPT_NONE

great, __schedule() doesn't need pay any attention to the TASK_DEAD now. on 09/14/2016 12:37 AM, Peter Zijlstra wrote: > On Tue, Sep 13, 2016 at 06:14:27PM +0200, Oleg Nesterov wrote: > >> Me too, and I failed to find something which could be broken... So >> perhaps should make it nop and

Re: [PATCH v3] stop_machine: Make migration_cpu_stop() does useful works for CONFIG_PREEMPT_NONE

great, __schedule() doesn't need pay any attention to the TASK_DEAD now. on 09/14/2016 12:37 AM, Peter Zijlstra wrote: > On Tue, Sep 13, 2016 at 06:14:27PM +0200, Oleg Nesterov wrote: > >> Me too, and I failed to find something which could be broken... So >> perhaps should make it nop and

[PATCH v4] stop_machine: Avoid a sleep and wakeup in the stop_one_cpu()

In case @cpu == smp_proccessor_id(), we can avoid a sleep+wakeup by doing a preemption. the caller such as sched_exec can benefit from this change. Signed-off-by: Cheng Chao Cc: Oleg Nesterov Cc: Peter Zijlstra ---

[PATCH v4] stop_machine: Avoid a sleep and wakeup in the stop_one_cpu()

In case @cpu == smp_proccessor_id(), we can avoid a sleep+wakeup by doing a preemption. the caller such as sched_exec can benefit from this change. Signed-off-by: Cheng Chao Cc: Oleg Nesterov Cc: Peter Zijlstra --- kernel/sched/core.c | 8 ++-- kernel/stop_machine.c | 5 + 2 files

Re: [PATCH v20 00/20] perf, tools: Add support for PMU events in JSON format

Jiri Olsa writes: > On Wed, Aug 31, 2016 at 09:15:30AM -0700, Andi Kleen wrote: >> > > >> > > > >> > > > I've already made some changes in pmu-events/* to support >> > > > this hierarchy to see how bad the change would be.. and >> > > > it's not that bad ;-) >> > > >> > >

Re: [PATCH v20 00/20] perf, tools: Add support for PMU events in JSON format

Jiri Olsa writes: > On Wed, Aug 31, 2016 at 09:15:30AM -0700, Andi Kleen wrote: >> > > >> > > > >> > > > I've already made some changes in pmu-events/* to support >> > > > this hierarchy to see how bad the change would be.. and >> > > > it's not that bad ;-) >> > > >> > > Everything has to be

[RFC/PATCH] usb: misc: Add a driver for TC7USB40MU

On the db410c 96boards platform we have a TC7USB40MU[1] on the board to mux the D+/D- lines from the SoC between a micro usb "device" port and a USB hub for "host" roles. Upon a role switch, we need to change this mux to forward the D+/D- lines to either the port or the hub. Therefore, introduce a

[RFC/PATCH] usb: misc: Add a driver for TC7USB40MU

On the db410c 96boards platform we have a TC7USB40MU[1] on the board to mux the D+/D- lines from the SoC between a micro usb "device" port and a USB hub for "host" roles. Upon a role switch, we need to change this mux to forward the D+/D- lines to either the port or the hub. Therefore, introduce a

[PATCH 0/2] nfit: fail DSMs that return an unknown status value

When the kernel knows the format of a DSM and is consuming the data internal to the kernel, it needs to be careful to fail DSMs that return an error. Recall that DSMs, ACPI Device Specific Methods, are used by the kernel to manipulate namespace label data, and scan for media errors. For example,

[PATCH 1/2] nfit: fail DSMs that return non-zero status by default

For the DSMs where the kernel knows the format of the output buffer and originates those DSMs from within the kernel, return -EIO for any non-zero status. If the BIOS is indicating a status that we do not know how to handle, fail the DSM. Signed-off-by: Dan Williams

[PATCH 2/2] tools/testing/nvdimm: test get_config_size DSM failures

Add an nfit_test specific attribute for gating whether a get_config_size DSM, or any DSM for that matter, succeeds or fails. The get_config_size DSM is initial motivation since that is the first command libnvdimm core issues to determine the state of the namespace label area. Signed-off-by: Dan

[PATCH 0/2] nfit: fail DSMs that return an unknown status value

When the kernel knows the format of a DSM and is consuming the data internal to the kernel, it needs to be careful to fail DSMs that return an error. Recall that DSMs, ACPI Device Specific Methods, are used by the kernel to manipulate namespace label data, and scan for media errors. For example,

[PATCH 1/2] nfit: fail DSMs that return non-zero status by default

For the DSMs where the kernel knows the format of the output buffer and originates those DSMs from within the kernel, return -EIO for any non-zero status. If the BIOS is indicating a status that we do not know how to handle, fail the DSM. Signed-off-by: Dan Williams ---

[PATCH 2/2] tools/testing/nvdimm: test get_config_size DSM failures

Add an nfit_test specific attribute for gating whether a get_config_size DSM, or any DSM for that matter, succeeds or fails. The get_config_size DSM is initial motivation since that is the first command libnvdimm core issues to determine the state of the namespace label area. Signed-off-by: Dan

Re: KVM patches applied in weird order in -stable

On Tue, Sep 13, 2016 at 06:58:40PM +0200, Paolo Bonzini wrote: > > > On 13/09/2016 18:57, Greg KH wrote: > > >> [0] commit 4e422bdd2f84 ("KVM: x86: fix missed hardware > > >> breakpoints") > > >> [1] commit 172b2386ed16 ("KVM: x86: fix missed hardware > > >> breakpoints")

Re: KVM patches applied in weird order in -stable

On Tue, Sep 13, 2016 at 06:58:40PM +0200, Paolo Bonzini wrote: > > > On 13/09/2016 18:57, Greg KH wrote: > > >> [0] commit 4e422bdd2f84 ("KVM: x86: fix missed hardware > > >> breakpoints") > > >> [1] commit 172b2386ed16 ("KVM: x86: fix missed hardware > > >> breakpoints")

Re: [RFC/RFT][PATCH v2 2/7] driver core: Functional dependencies tracking support

On Sunday, September 11, 2016 10:43:36 PM Lukas Wunner wrote: > On Sun, Sep 11, 2016 at 03:40:58PM +0200, Lukas Wunner wrote: > > On Thu, Sep 08, 2016 at 11:27:45PM +0200, Rafael J. Wysocki wrote: > > > +/** > > > + * device_is_dependent - Check if one device depends on another one > > > + * @dev:

Re: [RFC/RFT][PATCH v2 2/7] driver core: Functional dependencies tracking support

On Sunday, September 11, 2016 10:43:36 PM Lukas Wunner wrote: > On Sun, Sep 11, 2016 at 03:40:58PM +0200, Lukas Wunner wrote: > > On Thu, Sep 08, 2016 at 11:27:45PM +0200, Rafael J. Wysocki wrote: > > > +/** > > > + * device_is_dependent - Check if one device depends on another one > > > + * @dev:

Re: [RFC/RFT][PATCH v2 6/7] PM / runtime: Use device links

On Monday, September 12, 2016 03:57:02 PM Rafael J. Wysocki wrote: > On Monday, September 12, 2016 11:47:58 AM Lukas Wunner wrote: > > On Thu, Sep 08, 2016 at 11:30:26PM +0200, Rafael J. Wysocki wrote: > > > Modify the runtime PM framework to use device links to ensure that > > > supplier devices

Re: [RFC/RFT][PATCH v2 6/7] PM / runtime: Use device links

On Monday, September 12, 2016 03:57:02 PM Rafael J. Wysocki wrote: > On Monday, September 12, 2016 11:47:58 AM Lukas Wunner wrote: > > On Thu, Sep 08, 2016 at 11:30:26PM +0200, Rafael J. Wysocki wrote: > > > Modify the runtime PM framework to use device links to ensure that > > > supplier devices

Re: [PATCH v5] Force cppc_cpufreq to report values in KHz to fix user space reporting

On Wednesday, July 20, 2016 03:10:04 PM Al Stone wrote: > When CPPC is being used by ACPI on arm64, user space tools such as > cpupower report CPU frequency values from sysfs that are incorrect. > > What the driver was doing was reporting the values given by ACPI tables > in whatever scale was

Re: [PATCH v5] Force cppc_cpufreq to report values in KHz to fix user space reporting

On Wednesday, July 20, 2016 03:10:04 PM Al Stone wrote: > When CPPC is being used by ACPI on arm64, user space tools such as > cpupower report CPU frequency values from sysfs that are incorrect. > > What the driver was doing was reporting the values given by ACPI tables > in whatever scale was

Re: [PATCH v5 0/3] arm64: hibernate: Resume when hibernate image created on non-boot CPU

On Wednesday, August 17, 2016 01:50:24 PM James Morse wrote: > Hi all, > > These patches allow arm64 to hibernate on any CPU saving the cpu-id in the > arch header, then switch to it during resume using > hibernate_resume_nonboot_cpu_disable(). > > I hoped to avoid patch 1 by duplicating the

Re: [PATCH v5 0/3] arm64: hibernate: Resume when hibernate image created on non-boot CPU

On Wednesday, August 17, 2016 01:50:24 PM James Morse wrote: > Hi all, > > These patches allow arm64 to hibernate on any CPU saving the cpu-id in the > arch header, then switch to it during resume using > hibernate_resume_nonboot_cpu_disable(). > > I hoped to avoid patch 1 by duplicating the

Re: [PATCH v3 07/15] lockdep: Implement crossrelease feature

On Wed, Sep 14, 2016 at 6:42 AM, Peter Zijlstra wrote: > On Tue, Sep 13, 2016 at 09:38:29PM +0200, Peter Zijlstra wrote: > >> > > I _think_ you propose to keep track of all prior held locks and then use >> > > the union of the held list on the block-chain with the prior held

Re: [PATCH v3 07/15] lockdep: Implement crossrelease feature

On Wed, Sep 14, 2016 at 6:42 AM, Peter Zijlstra wrote: > On Tue, Sep 13, 2016 at 09:38:29PM +0200, Peter Zijlstra wrote: > >> > > I _think_ you propose to keep track of all prior held locks and then use >> > > the union of the held list on the block-chain with the prior held list >> > > from the

Re: [PATCH v3] PM / sleep: enable suspend-to-idle even without registered suspend_ops

On Friday, August 19, 2016 02:41:00 PM Sudeep Holla wrote: > Suspend-to-idle (aka the "freeze" sleep state) is a system sleep state > in which all of the processors enter deepest possible idle state and > wait for interrupts right after suspending all the devices. > > There is no hard requirement

Re: [PATCH v3] PM / sleep: enable suspend-to-idle even without registered suspend_ops

On Friday, August 19, 2016 02:41:00 PM Sudeep Holla wrote: > Suspend-to-idle (aka the "freeze" sleep state) is a system sleep state > in which all of the processors enter deepest possible idle state and > wait for interrupts right after suspending all the devices. > > There is no hard requirement

Re: [PATCH][v2] PM / sleep: Increase default DPM watchdog timeout to 120

On Friday, August 19, 2016 09:19:55 AM Pavel Machek wrote: > On Fri 2016-08-19 12:37:23, Chen Yu wrote: > > Recently we have a new report that, the harddisk can not > > resume on time due to firmware issues, and got a kernel > > panic because of DPM watchdog timeout. So adjust the > > default

Re: [PATCH v3 4/7] palmetto: Request relevant mux functions in devicetree

On Wed, Sep 14, 2016 at 6:28 AM, Benjamin Herrenschmidt wrote: > On Tue, 2016-09-13 at 22:11 +0930, Joel Stanley wrote: >> It's not clear that all systems use these pins in that way. I will >> not >> include this one for now. > > Well, it has VGA so the VGA hsync, vsync

Re: [PATCH][v2] PM / sleep: Increase default DPM watchdog timeout to 120

On Friday, August 19, 2016 09:19:55 AM Pavel Machek wrote: > On Fri 2016-08-19 12:37:23, Chen Yu wrote: > > Recently we have a new report that, the harddisk can not > > resume on time due to firmware issues, and got a kernel > > panic because of DPM watchdog timeout. So adjust the > > default

Re: [PATCH v3 4/7] palmetto: Request relevant mux functions in devicetree

On Wed, Sep 14, 2016 at 6:28 AM, Benjamin Herrenschmidt wrote: > On Tue, 2016-09-13 at 22:11 +0930, Joel Stanley wrote: >> It's not clear that all systems use these pins in that way. I will >> not >> include this one for now. > > Well, it has VGA so the VGA hsync, vsync and DDC should be there at

Re: [PATCH 0/2] minor x86 PM source file cleanup

On Saturday, August 20, 2016 06:15:10 PM Al Stone wrote: > On 08/20/2016 04:55 AM, Pavel Machek wrote: > > On Fri 2016-08-19 17:24:00, Al Stone wrote: > >> Really minor patches: one to cleanup whitespace, the second just makes > >> the code a wee bit more maintainable by correcting some variable

Re: [PATCH 0/2] minor x86 PM source file cleanup

On Saturday, August 20, 2016 06:15:10 PM Al Stone wrote: > On 08/20/2016 04:55 AM, Pavel Machek wrote: > > On Fri 2016-08-19 17:24:00, Al Stone wrote: > >> Really minor patches: one to cleanup whitespace, the second just makes > >> the code a wee bit more maintainable by correcting some variable

Re: [PATCH 1/3] cpufreq: dt: Remove unused code

On Friday, September 09, 2016 04:48:06 PM Viresh Kumar wrote: > This is leftover from an earlier patch which removed the usage of > platform data but forgot to remove this line. Remove it now. > > Signed-off-by: Viresh Kumar All [1-3/3] applied. Thanks, Rafael

Re: [PATCH 1/3] cpufreq: dt: Remove unused code

On Friday, September 09, 2016 04:48:06 PM Viresh Kumar wrote: > This is leftover from an earlier patch which removed the usage of > platform data but forgot to remove this line. Remove it now. > > Signed-off-by: Viresh Kumar All [1-3/3] applied. Thanks, Rafael

Re: [PATCH V2] cpufreq: create link to policy only for registered CPUs

On Monday, September 12, 2016 12:07:05 PM Viresh Kumar wrote: > If a cpufreq driver is registered very early in the boot stage (e.g. > registered from postcore_initcall()), then cpufreq core may generate > kernel warnings for it. > > In this case, the CPUs are brought online, then the cpufreq

Re: [PATCH V2] cpufreq: create link to policy only for registered CPUs

On Monday, September 12, 2016 12:07:05 PM Viresh Kumar wrote: > If a cpufreq driver is registered very early in the boot stage (e.g. > registered from postcore_initcall()), then cpufreq core may generate > kernel warnings for it. > > In this case, the CPUs are brought online, then the cpufreq

Re: [PATCH] PM / Hibernate: allow hibernation with PAGE_POISONING_ZERO

On Friday, September 09, 2016 10:43:32 AM Anisse Astier wrote: > PAGE_POISONING_ZERO disables zeroing new pages on alloc, they are > poisoned (zeroed) as they become available. > In the hibernate use case, free pages will appear in the system without > being cleared, left there by the loading

Re: [PATCH] PM / Hibernate: allow hibernation with PAGE_POISONING_ZERO

On Friday, September 09, 2016 10:43:32 AM Anisse Astier wrote: > PAGE_POISONING_ZERO disables zeroing new pages on alloc, they are > poisoned (zeroed) as they become available. > In the hibernate use case, free pages will appear in the system without > being cleared, left there by the loading

Re: [PATCH 19/26] intel_pstate: constify local structures

On Monday, September 12, 2016 12:12:30 PM Viresh Kumar wrote: > On 11-09-16, 15:06, Julia Lawall wrote: > > For structure types defined in the same file or local header files, find > > top-level static structure declarations that have the following > > properties: > > 1. Never reassigned. > > 2.

Re: [PATCH 19/26] intel_pstate: constify local structures

On Monday, September 12, 2016 12:12:30 PM Viresh Kumar wrote: > On 11-09-16, 15:06, Julia Lawall wrote: > > For structure types defined in the same file or local header files, find > > top-level static structure declarations that have the following > > properties: > > 1. Never reassigned. > > 2.

Re: [PATCH] rk808: fix RK818_IRQ_DISCHG_ILIM initializer

Hi: On 2016年09月13日 18:48, Lee Jones wrote: On Tue, 06 Sep 2016, Arnd Bergmann wrote: When building with -Woverride-init, we get a warning about an incorrect initializer: drivers/mfd/rk808.c:244:8: error: initialized field overwritten [-Werror=override-init] [RK818_IRQ_DISCHG_ILIM] = {

Re: [PATCH] rk808: fix RK818_IRQ_DISCHG_ILIM initializer

Hi: On 2016年09月13日 18:48, Lee Jones wrote: On Tue, 06 Sep 2016, Arnd Bergmann wrote: When building with -Woverride-init, we get a warning about an incorrect initializer: drivers/mfd/rk808.c:244:8: error: initialized field overwritten [-Werror=override-init] [RK818_IRQ_DISCHG_ILIM] = {

Re: [PATCH 24/26] ACPI / APD: constify local structures

On Sunday, September 11, 2016 03:06:06 PM Julia Lawall wrote: > For structure types defined in the same file or local header files, find > top-level static structure declarations that have the following > properties: > 1. Never reassigned. > 2. Address never taken > 3. Not passed to a top-level

Re: [PATCH 24/26] ACPI / APD: constify local structures

On Sunday, September 11, 2016 03:06:06 PM Julia Lawall wrote: > For structure types defined in the same file or local header files, find > top-level static structure declarations that have the following > properties: > 1. Never reassigned. > 2. Address never taken > 3. Not passed to a top-level

STRICTLY CONFIDENTIAL

I have important transaction for you as next of kin to claim US$18.37m Mail me on my private email: chimwia...@gmail.com so i can send you more details Thanks Mr.Chim Wai Kim === DISCLAIMER: This email and

STRICTLY CONFIDENTIAL

I have important transaction for you as next of kin to claim US$18.37m Mail me on my private email: chimwia...@gmail.com so i can send you more details Thanks Mr.Chim Wai Kim === DISCLAIMER: This email and

[RFC/PATCH] usb: chipidea: Emulate OTGSC interrupt enable path

In the case of an extcon-usb-gpio device being used with the chipidea driver we'll sometimes miss the BSVIS event in the OTGSC register. Consider the case where we don't have a cable attached and the id pin is indicating "host" mode. When we plug in the usb cable for "device" mode a gpio goes high

[RFC/PATCH] usb: chipidea: Emulate OTGSC interrupt enable path

In the case of an extcon-usb-gpio device being used with the chipidea driver we'll sometimes miss the BSVIS event in the OTGSC register. Consider the case where we don't have a cable attached and the id pin is indicating "host" mode. When we plug in the usb cable for "device" mode a gpio goes high

Re: [RFC/RFT][PATCH v2 5/7] PM / runtime: Flag to indicate PM sleep transitions in progress

On Tuesday, September 13, 2016 09:21:23 AM Marek Szyprowski wrote: > Hi Rafael, > > > On 2016-09-12 23:25, Rafael J. Wysocki wrote: > > On Monday, September 12, 2016 04:07:27 PM Lukas Wunner wrote: > >> On Thu, Sep 08, 2016 at 11:29:48PM +0200, Rafael J. Wysocki wrote: > >>> Introduce a new flag

Re: [RFC/RFT][PATCH v2 5/7] PM / runtime: Flag to indicate PM sleep transitions in progress

On Tuesday, September 13, 2016 09:21:23 AM Marek Szyprowski wrote: > Hi Rafael, > > > On 2016-09-12 23:25, Rafael J. Wysocki wrote: > > On Monday, September 12, 2016 04:07:27 PM Lukas Wunner wrote: > >> On Thu, Sep 08, 2016 at 11:29:48PM +0200, Rafael J. Wysocki wrote: > >>> Introduce a new flag

[Update][PATCH 3/3] cpufreq: intel_pstate: Use IOWAIT flag in Atom algorithm

From: Rafael J. Wysocki Modify the P-state selection algorithm for Atom processors to use the new SCHED_CPUFREQ_IOWAIT flag instead of the questionable get_cpu_iowait_time_us() function. Signed-off-by: Rafael J. Wysocki --- The PID uses

[Update][PATCH 3/3] cpufreq: intel_pstate: Use IOWAIT flag in Atom algorithm

From: Rafael J. Wysocki Modify the P-state selection algorithm for Atom processors to use the new SCHED_CPUFREQ_IOWAIT flag instead of the questionable get_cpu_iowait_time_us() function. Signed-off-by: Rafael J. Wysocki --- The PID uses percents not fractions, so pass sample->busy_scaled

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