[PATCH v2 1/3] clocksource/drivers/atcpit100: Add andestech atcpit100 timer

ATCPIT100 is often used on the Andes architecture, This timer provide 4 PIT channels. Each PIT channel is a multi-function timer, can be configured as 32,16,8 bit timers or PWM as well. For system timer it will set 32-bit timer0 as clock source and count downwards until underflow and restart

[PATCH v2 1/3] clocksource/drivers/atcpit100: Add andestech atcpit100 timer

ATCPIT100 is often used on the Andes architecture, This timer provide 4 PIT channels. Each PIT channel is a multi-function timer, can be configured as 32,16,8 bit timers or PWM as well. For system timer it will set 32-bit timer0 as clock source and count downwards until underflow and restart

[PATCH v2 3/3] dt-bindings: timer: Add andestech atcpit100 timer binding doc

Add a document to describe Andestech atcpit100 timer and binding information. Signed-off-by: Greentime Hu Signed-off-by: Rick Chen --- .../bindings/timer/andestech,atcpit100-timer.txt | 31 ++ 1 file changed, 31 insertions(+)

[PATCH v2 2/3] clocksource/drivers/Kconfig: Support andestech atcpit100 timer

Add CLKSRC_ATCPIT100 for Andestech atcpit100 timer selection. It often be used in Andestech AE3XX platform. Signed-off-by: Greentime Hu Signed-off-by: Rick Chen --- drivers/clocksource/Kconfig | 6 ++ drivers/clocksource/Makefile | 1 + 2 files

[PATCH v2 3/3] dt-bindings: timer: Add andestech atcpit100 timer binding doc

Add a document to describe Andestech atcpit100 timer and binding information. Signed-off-by: Greentime Hu Signed-off-by: Rick Chen --- .../bindings/timer/andestech,atcpit100-timer.txt | 31 ++ 1 file changed, 31 insertions(+) create mode 100644

[PATCH v2 2/3] clocksource/drivers/Kconfig: Support andestech atcpit100 timer

Add CLKSRC_ATCPIT100 for Andestech atcpit100 timer selection. It often be used in Andestech AE3XX platform. Signed-off-by: Greentime Hu Signed-off-by: Rick Chen --- drivers/clocksource/Kconfig | 6 ++ drivers/clocksource/Makefile | 1 + 2 files changed, 7 insertions(+) diff --git

[PATCH V1] rpmsg: glink: Initialize the "intent_req_comp" completion variable

The "intent_req_comp" variable is used without initialization which results in NULL pointer dereference in qcom_glink_request_intent(). we need to initialize the completion variable before using it. Fixes: 27b9c5b66b23 ("rpmsg: glink: Request for intents when unavailable") Signed-off-by: Arun

[PATCH V1] rpmsg: glink: Initialize the "intent_req_comp" completion variable

The "intent_req_comp" variable is used without initialization which results in NULL pointer dereference in qcom_glink_request_intent(). we need to initialize the completion variable before using it. Fixes: 27b9c5b66b23 ("rpmsg: glink: Request for intents when unavailable") Signed-off-by: Arun

[PATCH v4] KVM: arm/arm64: fix the incompatible matching for external abort

kvm_vcpu_dabt_isextabt() tries to match a full fault syndrome, but calls kvm_vcpu_trap_get_fault_type() that only returns the fault class, thus reducing the scope of the check. This doesn't cause any observable bug yet as we end-up matching a closely related syndrome for which we return the same

[PATCH v4] KVM: arm/arm64: fix the incompatible matching for external abort

kvm_vcpu_dabt_isextabt() tries to match a full fault syndrome, but calls kvm_vcpu_trap_get_fault_type() that only returns the fault class, thus reducing the scope of the check. This doesn't cause any observable bug yet as we end-up matching a closely related syndrome for which we return the same

[PATCH v4 1/1] xen/time: do not decrease steal time after live migration on xen

After guest live migration on xen, steal time in /proc/stat (cpustat[CPUTIME_STEAL]) might decrease because steal returned by xen_steal_lock() might be less than this_rq()->prev_steal_time which is derived from previous return value of xen_steal_clock(). For instance, steal time of each vcpu is

[PATCH v4 1/1] xen/time: do not decrease steal time after live migration on xen

After guest live migration on xen, steal time in /proc/stat (cpustat[CPUTIME_STEAL]) might decrease because steal returned by xen_steal_lock() might be less than this_rq()->prev_steal_time which is derived from previous return value of xen_steal_clock(). For instance, steal time of each vcpu is

Re: [PATCH 2/3] drivers: phy: broadcom: Add driver for Cygnus USB phy controller

Hi Chanwoo, On Mon, Oct 30, 2017 at 5:32 AM, Chanwoo Choi wrote: > Hi, > > On 2017년 10월 27일 17:35, Kishon Vijay Abraham I wrote: >> +Chanwoo, for reviewing extcon >> >> Hi. >> >> On Tuesday 24 October 2017 10:07 AM, Raveendra Padasalagi wrote: >>> Add driver for Broadcom's

Re: [PATCH 2/3] drivers: phy: broadcom: Add driver for Cygnus USB phy controller

Hi Chanwoo, On Mon, Oct 30, 2017 at 5:32 AM, Chanwoo Choi wrote: > Hi, > > On 2017년 10월 27일 17:35, Kishon Vijay Abraham I wrote: >> +Chanwoo, for reviewing extcon >> >> Hi. >> >> On Tuesday 24 October 2017 10:07 AM, Raveendra Padasalagi wrote: >>> Add driver for Broadcom's USB phy controller's

Re: [lkp-robot] [perf/x86] a5df70c354: perf-sanity-tests.Parse_event_definition_strings.fail

attached to full output: root@lkp-hsw-ep5 /usr/src/linux-perf-x86_64-rhel-7.2-bb176f67090ca54869fc1262c913aa69d2ede070/tools/perf# ./perf test -F 6 -v 6: Parse event definition strings: --- start --- running test 0 'syscalls:sys_enter_openat' Using CPUID

Re: [lkp-robot] [perf/x86] a5df70c354: perf-sanity-tests.Parse_event_definition_strings.fail

attached to full output: root@lkp-hsw-ep5 /usr/src/linux-perf-x86_64-rhel-7.2-bb176f67090ca54869fc1262c913aa69d2ede070/tools/perf# ./perf test -F 6 -v 6: Parse event definition strings: --- start --- running test 0 'syscalls:sys_enter_openat' Using CPUID

[PATCH 08/10] staging: lustre: lov: use list_for_each_entry in lov_obd.c

Signed-off-by: NeilBrown --- drivers/staging/lustre/lustre/lov/lov_obd.c |6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/drivers/staging/lustre/lustre/lov/lov_obd.c b/drivers/staging/lustre/lustre/lov/lov_obd.c index fefd3c588681..7e013229d7b5 100644

[PATCH 10/10] staging: lustre: obdclass: simplify cl_lock_fini()

Using list_first_entry_or_null() makes this (slightly) simpler. Signed-off-by: NeilBrown --- drivers/staging/lustre/lustre/obdclass/cl_lock.c |9 - 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/drivers/staging/lustre/lustre/obdclass/cl_lock.c

[PATCH 08/10] staging: lustre: lov: use list_for_each_entry in lov_obd.c

Signed-off-by: NeilBrown --- drivers/staging/lustre/lustre/lov/lov_obd.c |6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/drivers/staging/lustre/lustre/lov/lov_obd.c b/drivers/staging/lustre/lustre/lov/lov_obd.c index fefd3c588681..7e013229d7b5 100644 ---

[PATCH 10/10] staging: lustre: obdclass: simplify cl_lock_fini()

Using list_first_entry_or_null() makes this (slightly) simpler. Signed-off-by: NeilBrown --- drivers/staging/lustre/lustre/obdclass/cl_lock.c |9 - 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/drivers/staging/lustre/lustre/obdclass/cl_lock.c

[PATCH 09/10] staging: lustre: simplfy lov_finish_set()

When deleting everything from a list, a while loop is cleaner than list_for_each_safe(). Signed-off-by: NeilBrown --- drivers/staging/lustre/lustre/lov/lov_request.c | 10 -- 1 file changed, 4 insertions(+), 6 deletions(-) diff --git

[PATCH 09/10] staging: lustre: simplfy lov_finish_set()

When deleting everything from a list, a while loop is cleaner than list_for_each_safe(). Signed-off-by: NeilBrown --- drivers/staging/lustre/lustre/lov/lov_request.c | 10 -- 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/drivers/staging/lustre/lustre/lov/lov_request.c

[PATCH 05/10] staging: lustre: ldlm: use list_first_entry in ldlm_lockd.c

Signed-off-by: NeilBrown --- drivers/staging/lustre/lustre/ldlm/ldlm_lockd.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/drivers/staging/lustre/lustre/ldlm/ldlm_lockd.c b/drivers/staging/lustre/lustre/ldlm/ldlm_lockd.c index

[PATCH 06/10] staging: lustre: ldlm: minor list_entry improvements in ldlm_request.c

Signed-off-by: NeilBrown --- drivers/staging/lustre/lustre/ldlm/ldlm_request.c | 12 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/drivers/staging/lustre/lustre/ldlm/ldlm_request.c b/drivers/staging/lustre/lustre/ldlm/ldlm_request.c index

[PATCH 07/10] staging: lustre: ldlm: use list_for_each_entry in ldlm_resource.c

Signed-off-by: NeilBrown --- drivers/staging/lustre/lustre/ldlm/ldlm_resource.c | 20 +++- 1 file changed, 7 insertions(+), 13 deletions(-) diff --git a/drivers/staging/lustre/lustre/ldlm/ldlm_resource.c b/drivers/staging/lustre/lustre/ldlm/ldlm_resource.c

[PATCH 04/10] staging: lustre: ldlm: use list_for_each_entry in ldlm_lock.c

This makes some slightly-confusing code a bit clearer, and avoids the need for 'tmp'. Signed-off-by: NeilBrown --- drivers/staging/lustre/lustre/ldlm/ldlm_lock.c | 10 +++--- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git

[PATCH 05/10] staging: lustre: ldlm: use list_first_entry in ldlm_lockd.c

Signed-off-by: NeilBrown --- drivers/staging/lustre/lustre/ldlm/ldlm_lockd.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/drivers/staging/lustre/lustre/ldlm/ldlm_lockd.c b/drivers/staging/lustre/lustre/ldlm/ldlm_lockd.c index e2707336586c..2aaa5e91c66c 100644

[PATCH 06/10] staging: lustre: ldlm: minor list_entry improvements in ldlm_request.c

Signed-off-by: NeilBrown --- drivers/staging/lustre/lustre/ldlm/ldlm_request.c | 12 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/drivers/staging/lustre/lustre/ldlm/ldlm_request.c b/drivers/staging/lustre/lustre/ldlm/ldlm_request.c index

[PATCH 07/10] staging: lustre: ldlm: use list_for_each_entry in ldlm_resource.c

Signed-off-by: NeilBrown --- drivers/staging/lustre/lustre/ldlm/ldlm_resource.c | 20 +++- 1 file changed, 7 insertions(+), 13 deletions(-) diff --git a/drivers/staging/lustre/lustre/ldlm/ldlm_resource.c b/drivers/staging/lustre/lustre/ldlm/ldlm_resource.c index

[PATCH 04/10] staging: lustre: ldlm: use list_for_each_entry in ldlm_lock.c

This makes some slightly-confusing code a bit clearer, and avoids the need for 'tmp'. Signed-off-by: NeilBrown --- drivers/staging/lustre/lustre/ldlm/ldlm_lock.c | 10 +++--- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/drivers/staging/lustre/lustre/ldlm/ldlm_lock.c

[PATCH 03/10] staging: lustre: ldlm: use list_first_entry in ldlm_lock

This make the code (slightly) more readable. Signed-off-by: NeilBrown --- drivers/staging/lustre/lustre/ldlm/ldlm_lock.c |8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/staging/lustre/lustre/ldlm/ldlm_lock.c

[PATCH 03/10] staging: lustre: ldlm: use list_first_entry in ldlm_lock

This make the code (slightly) more readable. Signed-off-by: NeilBrown --- drivers/staging/lustre/lustre/ldlm/ldlm_lock.c |8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/staging/lustre/lustre/ldlm/ldlm_lock.c

[PATCH 00/10] staging: lustre: assorted code improvements for list manipulations.

There are mostly conversions of list_for_each() to list_for_each_entry() and similar. list_first_entry() also makes a few appearances. Thanks, NeilBrown --- NeilBrown (10): staging: lustre: use list_last_entry to simplify fld_cache_shrink staging: lustre: ldlm: use

[PATCH 02/10] staging: lustre: ldlm: use list_for_each_entry in ldlm_extent_shift_kms()

Signed-off-by: NeilBrown --- drivers/staging/lustre/lustre/ldlm/ldlm_extent.c |4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/drivers/staging/lustre/lustre/ldlm/ldlm_extent.c b/drivers/staging/lustre/lustre/ldlm/ldlm_extent.c index

[PATCH 01/10] staging: lustre: use list_last_entry to simplify fld_cache_shrink

Signed-off-by: NeilBrown --- drivers/staging/lustre/lustre/fld/fld_cache.c | 13 ++--- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/drivers/staging/lustre/lustre/fld/fld_cache.c b/drivers/staging/lustre/lustre/fld/fld_cache.c index

[PATCH 00/10] staging: lustre: assorted code improvements for list manipulations.

There are mostly conversions of list_for_each() to list_for_each_entry() and similar. list_first_entry() also makes a few appearances. Thanks, NeilBrown --- NeilBrown (10): staging: lustre: use list_last_entry to simplify fld_cache_shrink staging: lustre: ldlm: use

[PATCH 02/10] staging: lustre: ldlm: use list_for_each_entry in ldlm_extent_shift_kms()

Signed-off-by: NeilBrown --- drivers/staging/lustre/lustre/ldlm/ldlm_extent.c |4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/drivers/staging/lustre/lustre/ldlm/ldlm_extent.c b/drivers/staging/lustre/lustre/ldlm/ldlm_extent.c index 2cc6dc2b281f..c9bf9ae40f7d 100644 ---

[PATCH 01/10] staging: lustre: use list_last_entry to simplify fld_cache_shrink

Signed-off-by: NeilBrown --- drivers/staging/lustre/lustre/fld/fld_cache.c | 13 ++--- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/drivers/staging/lustre/lustre/fld/fld_cache.c b/drivers/staging/lustre/lustre/fld/fld_cache.c index b723ece02eff..c01709cd22a1 100644

Re: [PATCH v2 2/3] mailbox: Add support for Hi3660 mailbox

Hi Mark, On Fri, Oct 27, 2017 at 11:46:00AM +0100, Mark Rutland wrote: > On Fri, Oct 27, 2017 at 02:15:03PM +0800, Kaihua Zhong wrote: > > Hi3660 mailbox controller is used to send message within multiple > > processors, MCU, HIFI, etc. It supports 32 mailbox channels and every > > channel can

Re: [PATCH v2 2/3] mailbox: Add support for Hi3660 mailbox

Hi Mark, On Fri, Oct 27, 2017 at 11:46:00AM +0100, Mark Rutland wrote: > On Fri, Oct 27, 2017 at 02:15:03PM +0800, Kaihua Zhong wrote: > > Hi3660 mailbox controller is used to send message within multiple > > processors, MCU, HIFI, etc. It supports 32 mailbox channels and every > > channel can

Re: [PATCH] kernel/kprobes: add check to avoid memory leaks

On Mon, 30 Oct 2017 09:10:57 +0800 Bixuan Cui wrote: > On 2017/10/25 20:29, Bixuan Cui wrote: > And test again with this patch: > > insmod testRegKretprobes_004.ko > [ 163.853281] register_kretprobe failed, returned -22 > insmod: can't insert 'testRegKretprobes_004.ko':

Re: [PATCH] kernel/kprobes: add check to avoid memory leaks

On Mon, 30 Oct 2017 09:10:57 +0800 Bixuan Cui wrote: > On 2017/10/25 20:29, Bixuan Cui wrote: > And test again with this patch: > > insmod testRegKretprobes_004.ko > [ 163.853281] register_kretprobe failed, returned -22 > insmod: can't insert 'testRegKretprobes_004.ko': Operation not permitted

Re: [PATCH 2/3] drivers: phy: broadcom: Add driver for Cygnus USB phy controller

Hi Kishon, On Fri, Oct 27, 2017 at 2:05 PM, Kishon Vijay Abraham I wrote: > +Chanwoo, for reviewing extcon > > Hi. > > On Tuesday 24 October 2017 10:07 AM, Raveendra Padasalagi wrote: >> Add driver for Broadcom's USB phy controller's used in Cygnus >> familyof SoC. Cygnus has

Re: [PATCH 2/3] drivers: phy: broadcom: Add driver for Cygnus USB phy controller

Hi Kishon, On Fri, Oct 27, 2017 at 2:05 PM, Kishon Vijay Abraham I wrote: > +Chanwoo, for reviewing extcon > > Hi. > > On Tuesday 24 October 2017 10:07 AM, Raveendra Padasalagi wrote: >> Add driver for Broadcom's USB phy controller's used in Cygnus >> familyof SoC. Cygnus has three USB phy

[PATCH] Fix writing mtdoops to nand flash.

From: Brent Taylor When mtdoops calls mtd_panic_write, it eventually calls panic_nand_write in nand_base.c. In order to properly wait for the nand chip to be ready in panic_nand_wait, the chip must first be selected. When using the atmel nand flash controller, a panic would

[PATCH] Fix writing mtdoops to nand flash.

From: Brent Taylor When mtdoops calls mtd_panic_write, it eventually calls panic_nand_write in nand_base.c. In order to properly wait for the nand chip to be ready in panic_nand_wait, the chip must first be selected. When using the atmel nand flash controller, a panic would occur due to a NULL

Re: [PATCH v4 05/13] irqchip: add initial support for ompic

On Mon, Oct 30, 2017 at 02:29:18AM +, Marc Zyngier wrote: > On Mon, Oct 30 2017 at 8:11:15 am GMT, Stafford Horne > wrote: > > From: Stefan Kristiansson > > > > IPI driver for the Open Multi-Processor Interrupt Controller (ompic) as > >

Re: [PATCH v4 05/13] irqchip: add initial support for ompic

On Mon, Oct 30, 2017 at 02:29:18AM +, Marc Zyngier wrote: > On Mon, Oct 30 2017 at 8:11:15 am GMT, Stafford Horne > wrote: > > From: Stefan Kristiansson > > > > IPI driver for the Open Multi-Processor Interrupt Controller (ompic) as > > described in the Multi-core support section of the

[PATCH] st-hva: hva-h264: use swap macro in hva_h264_encode

Make use of the swap macro and remove unnecessary variable tmp_frame. This makes the code easier to read and maintain. This code was detected with the help of Coccinelle. Signed-off-by: Gustavo A. R. Silva --- drivers/media/platform/sti/hva/hva-h264.c | 5 + 1 file

[PATCH] st-hva: hva-h264: use swap macro in hva_h264_encode

Make use of the swap macro and remove unnecessary variable tmp_frame. This makes the code easier to read and maintain. This code was detected with the help of Coccinelle. Signed-off-by: Gustavo A. R. Silva --- drivers/media/platform/sti/hva/hva-h264.c | 5 + 1 file changed, 1 insertion(+),

Re: [PATCH] Coccinelle: use false positive annotation

On Mon, 30 Oct 2017, Masahiro Yamada wrote: > Hi Julia, > > > 2017-10-29 8:43 GMT+09:00 Julia Lawall : > > /// is to describe the semantic patch, while //# indicates reasons > > for false positives. > > > > Signed-off-by: Julia Lawall > > > > --- > >

Re: [PATCH] Coccinelle: use false positive annotation

On Mon, 30 Oct 2017, Masahiro Yamada wrote: > Hi Julia, > > > 2017-10-29 8:43 GMT+09:00 Julia Lawall : > > /// is to describe the semantic patch, while //# indicates reasons > > for false positives. > > > > Signed-off-by: Julia Lawall > > > > --- > > scripts/coccinelle/misc/ifcol.cocci |6

Re: [PATCH] Coccinelle: use false positive annotation

Hi Julia, 2017-10-29 8:43 GMT+09:00 Julia Lawall : > /// is to describe the semantic patch, while //# indicates reasons > for false positives. > > Signed-off-by: Julia Lawall > > --- > scripts/coccinelle/misc/ifcol.cocci |6 +++--- > 1 file

Re: [PATCH] Coccinelle: use false positive annotation

Hi Julia, 2017-10-29 8:43 GMT+09:00 Julia Lawall : > /// is to describe the semantic patch, while //# indicates reasons > for false positives. > > Signed-off-by: Julia Lawall > > --- > scripts/coccinelle/misc/ifcol.cocci |6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff

[PATCH v3] i2c: aspeed: Deassert reset in probe

In order to use i2c from a cold boot, the i2c peripheral must be taken out of reset. We request a shared reset controller each time a bus driver is loaded, as the reset is shared between the 14 i2c buses. On remove the reset is asserted, which only touches the hardware once the last i2c bus is

[PATCH v3] i2c: aspeed: Deassert reset in probe

In order to use i2c from a cold boot, the i2c peripheral must be taken out of reset. We request a shared reset controller each time a bus driver is loaded, as the reset is shared between the 14 i2c buses. On remove the reset is asserted, which only touches the hardware once the last i2c bus is

Re: [PATCH V4 07/12] boot_constraint: Add debugfs support

On 10/29/17 20:37, Viresh Kumar wrote: > On 29-10-17, 08:09, Randy Dunlap wrote: >> On 10/29/17 06:48, Viresh Kumar wrote: >>> This patch adds debugfs support for boot constraints. This is how it >>> looks for a "vmmc-supply" constraint for the MMC device. >>> >>> Tested-by: Rajendra Nayak

Re: [PATCH V4 07/12] boot_constraint: Add debugfs support

On 10/29/17 20:37, Viresh Kumar wrote: > On 29-10-17, 08:09, Randy Dunlap wrote: >> On 10/29/17 06:48, Viresh Kumar wrote: >>> This patch adds debugfs support for boot constraints. This is how it >>> looks for a "vmmc-supply" constraint for the MMC device. >>> >>> Tested-by: Rajendra Nayak >>>

Re: [PATCH] Check all .c files for bad kernel-doc comments

Hi Matthew, 2017-10-28 4:41 GMT+09:00 Matthew Wilcox : > From: Matthew Wilcox > > Implement a '-none' output mode for kernel-doc which will only output > warning messages, and suppresses the warning message about there being > no kernel-doc in the

Re: [PATCH] Check all .c files for bad kernel-doc comments

Hi Matthew, 2017-10-28 4:41 GMT+09:00 Matthew Wilcox : > From: Matthew Wilcox > > Implement a '-none' output mode for kernel-doc which will only output > warning messages, and suppresses the warning message about there being > no kernel-doc in the file. Add it to the rule to build .o files

Re: [PATCH v2 RESEND] Revert "f2fs: handle dirty segments inside refresh_sit_entry"

On 2017/10/30 9:33, Yunlong Song wrote: > This reverts commit 5e443818fa0b2a2845561ee25bec181424fb2889 > > The commit should be reverted because call sequence of below two parts > of code must be kept: > a. update sit information, it needs to be updated before segment > allocation since latter

Re: [PATCH v2 RESEND] Revert "f2fs: handle dirty segments inside refresh_sit_entry"

On 2017/10/30 9:33, Yunlong Song wrote: > This reverts commit 5e443818fa0b2a2845561ee25bec181424fb2889 > > The commit should be reverted because call sequence of below two parts > of code must be kept: > a. update sit information, it needs to be updated before segment > allocation since latter

Re: [PATCH V4 07/12] boot_constraint: Add debugfs support

On 29-10-17, 08:09, Randy Dunlap wrote: > On 10/29/17 06:48, Viresh Kumar wrote: > > This patch adds debugfs support for boot constraints. This is how it > > looks for a "vmmc-supply" constraint for the MMC device. > > > > Tested-by: Rajendra Nayak > > Signed-off-by:

Re: [PATCH V4 07/12] boot_constraint: Add debugfs support

On 29-10-17, 08:09, Randy Dunlap wrote: > On 10/29/17 06:48, Viresh Kumar wrote: > > This patch adds debugfs support for boot constraints. This is how it > > looks for a "vmmc-supply" constraint for the MMC device. > > > > Tested-by: Rajendra Nayak > > Signed-off-by: Viresh Kumar > > --- > >

[Part2 PATCH v6.2 18/38] crypto: ccp: Implement SEV_PEK_CSR ioctl command

The SEV_PEK_CSR command can be used to generate a PEK certificate signing request. The command is defined in SEV spec section 5.7. Cc: Paolo Bonzini Cc: "Radim Krčmář" Cc: Borislav Petkov Cc: Herbert Xu Cc:

[Part2 PATCH v6.2 18/38] crypto: ccp: Implement SEV_PEK_CSR ioctl command

The SEV_PEK_CSR command can be used to generate a PEK certificate signing request. The command is defined in SEV spec section 5.7. Cc: Paolo Bonzini Cc: "Radim Krčmář" Cc: Borislav Petkov Cc: Herbert Xu Cc: Gary Hook Cc: Tom Lendacky Cc: linux-cry...@vger.kernel.org Cc: k...@vger.kernel.org

Re: [PATCH v6 9/9] KVM: arm/arm64: vgic-its: Implement KVM_DEV_ARM_ITS_CTRL_RESET

On Thu, Oct 26 2017 at 6:23:11 pm BST, Eric Auger wrote: > On reset we clear the valid bits of GITS_CBASER and GITS_BASER. > We also clear command queue registers and free the cache (device, > collection, and lpi lists). > > As we need to take the same locks as

Re: [PATCH v6 9/9] KVM: arm/arm64: vgic-its: Implement KVM_DEV_ARM_ITS_CTRL_RESET

On Thu, Oct 26 2017 at 6:23:11 pm BST, Eric Auger wrote: > On reset we clear the valid bits of GITS_CBASER and GITS_BASER. > We also clear command queue registers and free the cache (device, > collection, and lpi lists). > > As we need to take the same locks as save/restore functions, we >

Re: [PATCH v6 8/9] KVM: arm/arm64: Document KVM_DEV_ARM_ITS_CTRL_RESET

On Thu, Oct 26 2017 at 6:23:10 pm BST, Eric Auger wrote: > At the moment, the in-kernel emulated ITS is not properly reset. > On guest restart/reset some registers keep their old values and > internal structures like device, ITE, and collection lists are not > freed. > >

Re: [PATCH v6 8/9] KVM: arm/arm64: Document KVM_DEV_ARM_ITS_CTRL_RESET

On Thu, Oct 26 2017 at 6:23:10 pm BST, Eric Auger wrote: > At the moment, the in-kernel emulated ITS is not properly reset. > On guest restart/reset some registers keep their old values and > internal structures like device, ITE, and collection lists are not > freed. > > This may lead to

Re: [PATCH v6 6/9] KVM: arm/arm64: vgic-its: New helper functions to free the caches

On Thu, Oct 26 2017 at 6:23:08 pm BST, Eric Auger wrote: > From: wanghaibin > > We create two new functions that free the device and > collection lists. They are currently called by vgic_its_destroy() > and other callers will be added in

Re: [PATCH v6 6/9] KVM: arm/arm64: vgic-its: New helper functions to free the caches

On Thu, Oct 26 2017 at 6:23:08 pm BST, Eric Auger wrote: > From: wanghaibin > > We create two new functions that free the device and > collection lists. They are currently called by vgic_its_destroy() > and other callers will be added in subsequent patches. > > We also remove the check on

Re: [PATCH v6 7/9] KVM: arm/arm64: vgic-its: Free caches when GITS_BASER Valid bit is cleared

On Thu, Oct 26 2017 at 6:23:09 pm BST, Eric Auger wrote: > When the GITS_BASER.Valid gets cleared, the data structures in > guest RAM are not valid anymore. The device, collection > and LPI lists stored in the in-kernel ITS represent the same > information in some form of

Re: [PATCH v6 7/9] KVM: arm/arm64: vgic-its: Free caches when GITS_BASER Valid bit is cleared

On Thu, Oct 26 2017 at 6:23:09 pm BST, Eric Auger wrote: > When the GITS_BASER.Valid gets cleared, the data structures in > guest RAM are not valid anymore. The device, collection > and LPI lists stored in the in-kernel ITS represent the same > information in some form of cache. So let's void

[PATCH] selftests/vm: Add tests validating mremap mirror functionality

This adds two tests to validate mirror functionality with mremap() system call on shared and private anon mappings. After the commit dba58d3b8c5 ("mm/mremap: fail map duplication attempts for private mappings"), any attempt to mirror private anon mapping will fail. Suggested-by: Mike Kravetz

[PATCH] selftests/vm: Add tests validating mremap mirror functionality

This adds two tests to validate mirror functionality with mremap() system call on shared and private anon mappings. After the commit dba58d3b8c5 ("mm/mremap: fail map duplication attempts for private mappings"), any attempt to mirror private anon mapping will fail. Suggested-by: Mike Kravetz

Re: [PATCH v2] i2c: aspeed: Deassert reset in probe

On Fri, Oct 27, 2017 at 7:23 AM, Wolfram Sang wrote: >> > + bus->rst = devm_reset_control_get_optional_shared(>dev, >> > NULL); >> >> This could return error values in case of broken device trees, so you >> may want to check IS_ERR(bus->rst) and handle the error here.

Re: [PATCH v2] i2c: aspeed: Deassert reset in probe

On Fri, Oct 27, 2017 at 7:23 AM, Wolfram Sang wrote: >> > + bus->rst = devm_reset_control_get_optional_shared(>dev, >> > NULL); >> >> This could return error values in case of broken device trees, so you >> may want to check IS_ERR(bus->rst) and handle the error here. >From my

[Part2 PATCH v6.1 15/38] crypto: ccp: Implement SEV_PEK_GEN ioctl command

The SEV_PEK_GEN command is used to generate a new Platform Endorsement Key (PEK). The command is defined in SEV spec section 5.6. Cc: Paolo Bonzini Cc: "Radim Krčmář" Cc: Borislav Petkov Cc: Herbert Xu Cc:

[Part2 PATCH v6.1 15/38] crypto: ccp: Implement SEV_PEK_GEN ioctl command

The SEV_PEK_GEN command is used to generate a new Platform Endorsement Key (PEK). The command is defined in SEV spec section 5.6. Cc: Paolo Bonzini Cc: "Radim Krčmář" Cc: Borislav Petkov Cc: Herbert Xu Cc: Gary Hook Cc: Tom Lendacky Cc: linux-cry...@vger.kernel.org Cc: k...@vger.kernel.org

Re: [PATCH stable-4.1.y] tools include: Add a __fallthrough statement

On Fri, Oct 27, 2017 at 12:05:58PM -0700, Florian Fainelli wrote: >From: Arnaldo Carvalho de Melo > >commit b5bf1733d6a391c4e90ea8f8468d83023be74a2a upstream. > >For cases where implicit fall through case labels are intended, >to let us inform that to gcc >= 7: > >CC

Re: [PATCH stable-4.1.y] tools include: Add a __fallthrough statement

On Fri, Oct 27, 2017 at 12:05:58PM -0700, Florian Fainelli wrote: >From: Arnaldo Carvalho de Melo > >commit b5bf1733d6a391c4e90ea8f8468d83023be74a2a upstream. > >For cases where implicit fall through case labels are intended, >to let us inform that to gcc >= 7: > >CC

[PATCH] HID: i2c-hid: add reset gpio property

some i2c hid devices have reset gpio, need to control it in the driver. Change-Id: I87bca954bffc7eb7b35711406f522cb3d0fc2ded Signed-off-by: Lin Huang --- drivers/hid/i2c-hid/i2c-hid.c | 63 +++ include/linux/platform_data/i2c-hid.h |

[PATCH] HID: i2c-hid: add reset gpio property

some i2c hid devices have reset gpio, need to control it in the driver. Change-Id: I87bca954bffc7eb7b35711406f522cb3d0fc2ded Signed-off-by: Lin Huang --- drivers/hid/i2c-hid/i2c-hid.c | 63 +++ include/linux/platform_data/i2c-hid.h | 4 +++ 2 files

Re: [PATCH v6 5/9] KVM: arm/arm64: vgic-its: Remove kvm_its_unmap_device

On Thu, Oct 26 2017 at 6:23:07 pm BST, Eric Auger wrote: > Let's remove kvm_its_unmap_device and use kvm_its_free_device > as both functions are identical. > > Signed-off-by: Eric Auger > Acked-by: Christoffer Dall

Re: [PATCH v6 5/9] KVM: arm/arm64: vgic-its: Remove kvm_its_unmap_device

On Thu, Oct 26 2017 at 6:23:07 pm BST, Eric Auger wrote: > Let's remove kvm_its_unmap_device and use kvm_its_free_device > as both functions are identical. > > Signed-off-by: Eric Auger > Acked-by: Christoffer Dall Acked-by: Marc Zyngier M. -- Jazz is not dead. It just smells

[PATCH V1] regulator: da9211: update for supporting da9223/4/5

From: James Ban This is update for supporting additional devices da9223/4/5. Only device strings is added because only package type is different. Signed-off-by: James Ban --- This patch applies against linux-next and

[PATCH V1] regulator: da9211: update for supporting da9223/4/5

From: James Ban This is update for supporting additional devices da9223/4/5. Only device strings is added because only package type is different. Signed-off-by: James Ban --- This patch applies against linux-next and next-20171018 .../devicetree/bindings/regulator/da9211.txt | 82

Re: [PATCH v4 05/13] irqchip: add initial support for ompic

On Mon, Oct 30 2017 at 8:11:15 am GMT, Stafford Horne wrote: > From: Stefan Kristiansson > > IPI driver for the Open Multi-Processor Interrupt Controller (ompic) as > described in the Multi-core support section of the OpenRISC 1.2 >

Re: [PATCH v4 05/13] irqchip: add initial support for ompic

On Mon, Oct 30 2017 at 8:11:15 am GMT, Stafford Horne wrote: > From: Stefan Kristiansson > > IPI driver for the Open Multi-Processor Interrupt Controller (ompic) as > described in the Multi-core support section of the OpenRISC 1.2 > architecture specification: > >

Re: [RFC PATCH v10 0/7] PCI: rockchip: Move PCIe WAKE# handling into pci core

Hi Rafael, thanks for your reply. On 10/28/2017 05:07 PM, Rafael J. Wysocki wrote: Overall, I don't quite like the direction this is going into, but I need to have a deeper look. Which may take some time, so please bear with me. ok, i'll wait for your comments, thanks :) Thanks, Rafael

Re: [RFC PATCH v10 0/7] PCI: rockchip: Move PCIe WAKE# handling into pci core

Hi Rafael, thanks for your reply. On 10/28/2017 05:07 PM, Rafael J. Wysocki wrote: Overall, I don't quite like the direction this is going into, but I need to have a deeper look. Which may take some time, so please bear with me. ok, i'll wait for your comments, thanks :) Thanks, Rafael

[PATCH] irqdomain: Update the comments of fwnode field of irq_domain structure

Commit: f110711a6053 ("irqdomain: Convert irqdomain-%3Eof_node to fwnode") converted of_node field to fwnode, but didn't update its comments. Update it. Signed-off-by: Dou Liyang --- include/linux/irqdomain.h | 4 ++-- 1 file changed, 2 insertions(+), 2

[PATCH] irqdomain: Update the comments of fwnode field of irq_domain structure

Commit: f110711a6053 ("irqdomain: Convert irqdomain-%3Eof_node to fwnode") converted of_node field to fwnode, but didn't update its comments. Update it. Signed-off-by: Dou Liyang --- include/linux/irqdomain.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

Re: [RFC PATCH v8 4/7] of/irq: Adjust of pci irq parsing for multiple interrupts

Hi Rob, On 10/27/2017 10:38 PM, Rob Herring wrote: + prop = of_find_property(dn, "interrupt-names", NULL); >+ for (name = of_prop_next_string(prop, NULL); name; >+name = of_prop_next_string(prop, name), index++) { >+ if (!strcmp(name,

Re: [RFC PATCH v8 4/7] of/irq: Adjust of pci irq parsing for multiple interrupts

Hi Rob, On 10/27/2017 10:38 PM, Rob Herring wrote: + prop = of_find_property(dn, "interrupt-names", NULL); >+ for (name = of_prop_next_string(prop, NULL); name; >+name = of_prop_next_string(prop, name), index++) { >+ if (!strcmp(name,

Re: [PATCH v3 00/13] dax: fix dma vs truncate and remove 'page-less' support

On Sun, Oct 29, 2017 at 04:46:44PM -0700, Dan Williams wrote: > On Thu, Oct 26, 2017 at 3:58 AM, Jan Kara wrote: > > On Fri 20-10-17 11:31:48, Christoph Hellwig wrote: > >> On Fri, Oct 20, 2017 at 09:47:50AM +0200, Christoph Hellwig wrote: > >> > I'd like to brainstorm how we can do

Re: [PATCH v3 00/13] dax: fix dma vs truncate and remove 'page-less' support

On Sun, Oct 29, 2017 at 04:46:44PM -0700, Dan Williams wrote: > On Thu, Oct 26, 2017 at 3:58 AM, Jan Kara wrote: > > On Fri 20-10-17 11:31:48, Christoph Hellwig wrote: > >> On Fri, Oct 20, 2017 at 09:47:50AM +0200, Christoph Hellwig wrote: > >> > I'd like to brainstorm how we can do something

[PATCH v3 3/3] MAINTAINERS: Add a new entry of the ov7740 driver

Add a new entry of the ov7740 sensor driver to the MAINTAINERS file. Signed-off-by: Wenyou Yang --- Changes in v3: - Put the MAINTAINERS change to a separate patch. Changes in v2: - Split off the bindings into a separate patch. - Add a new entry to the MAINTAINERS

[PATCH v3 3/3] MAINTAINERS: Add a new entry of the ov7740 driver

Add a new entry of the ov7740 sensor driver to the MAINTAINERS file. Signed-off-by: Wenyou Yang --- Changes in v3: - Put the MAINTAINERS change to a separate patch. Changes in v2: - Split off the bindings into a separate patch. - Add a new entry to the MAINTAINERS file. MAINTAINERS | 8

  1   2   3   4   5   6   >