Re: [RFC v5 34/38] procfs: display the protection-key number associated with a vma

On 07/06/2017 02:52 AM, Ram Pai wrote: > Display the pkey number associated with the vma in smaps of a task. > The key will be seen as below: > > ProtectionKey: 0 > > Signed-off-by: Ram Pai > --- > arch/powerpc/kernel/setup_64.c |8 > 1 files changed, 8

Re: [RFC v5 38/38] Documentation: PowerPC specific updates to memory protection keys

On 07/06/2017 02:52 AM, Ram Pai wrote: > Add documentation updates that capture PowerPC specific changes. > > Signed-off-by: Ram Pai > --- > Documentation/vm/protection-keys.txt | 85 > ++ > 1 files changed, 65 insertions(+), 20

Re: [RFC v5 34/38] procfs: display the protection-key number associated with a vma

On 07/06/2017 02:52 AM, Ram Pai wrote: > Display the pkey number associated with the vma in smaps of a task. > The key will be seen as below: > > ProtectionKey: 0 > > Signed-off-by: Ram Pai > --- > arch/powerpc/kernel/setup_64.c |8 > 1 files changed, 8 insertions(+), 0

Re: [RFC v5 38/38] Documentation: PowerPC specific updates to memory protection keys

On 07/06/2017 02:52 AM, Ram Pai wrote: > Add documentation updates that capture PowerPC specific changes. > > Signed-off-by: Ram Pai > --- > Documentation/vm/protection-keys.txt | 85 > ++ > 1 files changed, 65 insertions(+), 20 deletions(-) > > diff --git

Re: [git pull] drm for v4.13

On Sun, Jul 9, 2017 at 8:01 PM, Dave Airlie wrote: > > Forgot to add, because I just checked now, there are 2 conflicts, > the drm one with patches from Al, and one in i915_gem_execbuffer.c > which I think resolves best by just taking the code from the pull in place > of code

Re: [git pull] drm for v4.13

On Sun, Jul 9, 2017 at 8:01 PM, Dave Airlie wrote: > > Forgot to add, because I just checked now, there are 2 conflicts, > the drm one with patches from Al, and one in i915_gem_execbuffer.c > which I think resolves best by just taking the code from the pull in place > of code in your tree. Heh.

Re: [git pull] drm for v4.13

On 10 July 2017 at 10:43, Dave Airlie wrote: > Hi Linus, > > Sorry this is a bit late, I was on holidays start of last week and now > I've got a post holiday illness. > I had nearly all this ready pre holidays, just had one set of fixes > and a cleanup on top, but I hadn't >

Re: [git pull] drm for v4.13

On 10 July 2017 at 10:43, Dave Airlie wrote: > Hi Linus, > > Sorry this is a bit late, I was on holidays start of last week and now > I've got a post holiday illness. > I had nearly all this ready pre holidays, just had one set of fixes > and a cleanup on top, but I hadn't > written the summary.

[PATCH] usb: gadget: legacy: ncm: compress return logic into one line

Simplify return logic to avoid unnecessary variable assignment. This issue was detected using Coccinelle and the following semantic patch: @@ local idexpression ret; expression e; @@ -ret = +return e; -return ret; Signed-off-by: Gustavo A. R. Silva ---

[PATCH] usb: gadget: legacy: ncm: compress return logic into one line

Simplify return logic to avoid unnecessary variable assignment. This issue was detected using Coccinelle and the following semantic patch: @@ local idexpression ret; expression e; @@ -ret = +return e; -return ret; Signed-off-by: Gustavo A. R. Silva --- drivers/usb/gadget/legacy/ncm.c |

Re: [PATCH v4 4/4] x86/boot/KASLR: Restrict kernel to be randomized in mirror regions

On Mon, Jul 10, 2017 at 09:47:29AM +0800, Baoquan He wrote: >On 07/09/17 at 07:11am, Kees Cook wrote: >> On Sun, Jul 9, 2017 at 5:37 AM, Baoquan He wrote: >> > Signed-off-by: Baoquan He >> > +/* Marks if efi mirror regions have been found and handled. */ >> >

Re: [PATCH v4 4/4] x86/boot/KASLR: Restrict kernel to be randomized in mirror regions

On Mon, Jul 10, 2017 at 09:47:29AM +0800, Baoquan He wrote: >On 07/09/17 at 07:11am, Kees Cook wrote: >> On Sun, Jul 9, 2017 at 5:37 AM, Baoquan He wrote: >> > Signed-off-by: Baoquan He >> > +/* Marks if efi mirror regions have been found and handled. */ >> > +static bool efi_mirror_found; >>

[PATCH] usb: gadget: legacy: dbgp: compress return logic into one line

Simplify return logic to avoid unnecessary variable declaration and assignment. This issue was detected using Coccinelle and the following semantic patch: @@ local idexpression ret; expression e; @@ -ret = +return e; -return ret; Signed-off-by: Gustavo A. R. Silva

[PATCH] usb: gadget: legacy: dbgp: compress return logic into one line

Simplify return logic to avoid unnecessary variable declaration and assignment. This issue was detected using Coccinelle and the following semantic patch: @@ local idexpression ret; expression e; @@ -ret = +return e; -return ret; Signed-off-by: Gustavo A. R. Silva ---

[PATCH] usb: gadget: legacy: compress return logic into one line

Simplify return logic to avoid unnecessary variable assignments. These issues were detected using Coccinelle and the following semantic patch: @@ local idexpression ret; expression e; @@ -ret = +return e; -return ret; Signed-off-by: Gustavo A. R. Silva ---

[PATCH] usb: gadget: legacy: compress return logic into one line

Simplify return logic to avoid unnecessary variable assignments. These issues were detected using Coccinelle and the following semantic patch: @@ local idexpression ret; expression e; @@ -ret = +return e; -return ret; Signed-off-by: Gustavo A. R. Silva ---

[lkp-robot] [mm] a99d848d3b: kernel_BUG_at_mm/mmap.c

FYI, we noticed the following commit: commit: a99d848d3bc6586e922584ce8ec673a451a09cf1 ("mm: larger stack guard gap, between vmas") url: https://github.com/0day-ci/linux/commits/Ben-Hutchings/mmap-Skip-a-single-VM_NONE-mapping-when-checking-the-stack/20170707-131750 in testcase: trinity with

[lkp-robot] [mm] a99d848d3b: kernel_BUG_at_mm/mmap.c

FYI, we noticed the following commit: commit: a99d848d3bc6586e922584ce8ec673a451a09cf1 ("mm: larger stack guard gap, between vmas") url: https://github.com/0day-ci/linux/commits/Ben-Hutchings/mmap-Skip-a-single-VM_NONE-mapping-when-checking-the-stack/20170707-131750 in testcase: trinity with

Re: [PATCH v4 2/2] i2c: Add Spreadtrum I2C controller driver

Hi Wolfram, On 四, 7月 06, 2017 at 05:10:21下午 +0800, Baolin Wang wrote: > Hi Andy, > > On 四, 7月 06, 2017 at 12:00:29下午 +0300, Andy Shevchenko wrote: > > On Thu, Jul 6, 2017 at 11:47 AM, Baolin Wang > > wrote: > > > This patch adds the I2C controller driver for

Re: [PATCH v4 2/2] i2c: Add Spreadtrum I2C controller driver

Hi Wolfram, On 四, 7月 06, 2017 at 05:10:21下午 +0800, Baolin Wang wrote: > Hi Andy, > > On 四, 7月 06, 2017 at 12:00:29下午 +0300, Andy Shevchenko wrote: > > On Thu, Jul 6, 2017 at 11:47 AM, Baolin Wang > > wrote: > > > This patch adds the I2C controller driver for Spreadtrum SC9860 platform. > > >

[RESEND PATCH] bcache: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- drivers/md/bcache/closure.c | 17 +++-- 1 file changed, 3 insertions(+), 14 deletions(-) diff --git a/drivers/md/bcache/closure.c

[RESEND PATCH] bcache: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- drivers/md/bcache/closure.c | 17 +++-- 1 file changed, 3 insertions(+), 14 deletions(-) diff --git a/drivers/md/bcache/closure.c b/drivers/md/bcache/closure.c index

[RESEND PATCH] mm: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- mm/vmalloc.c | 10 -- 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/mm/vmalloc.c b/mm/vmalloc.c index 3ca82d4..8c0eb45 100644 ---

[RESEND PATCH] mm: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- mm/vmalloc.c | 10 -- 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/mm/vmalloc.c b/mm/vmalloc.c index 3ca82d4..8c0eb45 100644 --- a/mm/vmalloc.c +++ b/mm/vmalloc.c

[RESEND PATCH] fput: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park Reviewed-by: Oleg Nesterov --- fs/file_table.c | 12 +--- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/fs/file_table.c

[RESEND PATCH] Don't reinvent the wheel but use existing llilst API

Hello Linus, Even though llist APIs exist, serveral code in kernel reinvent the implementation again and again. Since I think it's *worth* making it use existing APIs, I submit patches doing it. Actually I've submitted them to maintainers and commiters about 10 times for 4 months, but they seem

[RESEND PATCH] namespace.c: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- fs/namespace.c | 12 +--- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/fs/namespace.c b/fs/namespace.c index b5b1259..5cb2229 100644 ---

[RESEND PATCH] fput: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park Reviewed-by: Oleg Nesterov --- fs/file_table.c | 12 +--- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/fs/file_table.c b/fs/file_table.c index 6d982b5..3209da2 100644

[RESEND PATCH] Don't reinvent the wheel but use existing llilst API

Hello Linus, Even though llist APIs exist, serveral code in kernel reinvent the implementation again and again. Since I think it's *worth* making it use existing APIs, I submit patches doing it. Actually I've submitted them to maintainers and commiters about 10 times for 4 months, but they seem

[RESEND PATCH] namespace.c: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- fs/namespace.c | 12 +--- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/fs/namespace.c b/fs/namespace.c index b5b1259..5cb2229 100644 --- a/fs/namespace.c +++

[PATCH 2/2] usb: gadget: use unsigned int instead of unsigned in usb_otg_descriptor_alloc()

Prefer unsigned int to bare use of unsigned. Signed-off-by: Gustavo A. R. Silva --- drivers/usb/gadget/config.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/usb/gadget/config.c b/drivers/usb/gadget/config.c index 23bfa7d..968179d 100644

[PATCH 2/2] usb: gadget: use unsigned int instead of unsigned in usb_otg_descriptor_alloc()

Prefer unsigned int to bare use of unsigned. Signed-off-by: Gustavo A. R. Silva --- drivers/usb/gadget/config.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/usb/gadget/config.c b/drivers/usb/gadget/config.c index 23bfa7d..968179d 100644 ---

[PATCH 1/2] usb: gadget: compress return logic into one line

Simplify return logic to avoid unnecessary variable declaration and assignment. This issue was detected using Coccinelle and the following semantic patch: @@ local idexpression ret; expression e; @@ -ret = +return e; -return ret; Signed-off-by: Gustavo A. R. Silva

[PATCH 1/2] usb: gadget: compress return logic into one line

Simplify return logic to avoid unnecessary variable declaration and assignment. This issue was detected using Coccinelle and the following semantic patch: @@ local idexpression ret; expression e; @@ -ret = +return e; -return ret; Signed-off-by: Gustavo A. R. Silva ---

Re: linux-next: build failure after merge of the vfs tree

On Mon, Jul 10, 2017 at 12:15:11PM +1000, Stephen Rothwell wrote: > Hi Al, > Caused by commit > > 4f9365d9e2e7 ("spufs: Implement show_options") Obvious incremental follows, will fold and push diff --git a/arch/powerpc/platforms/cell/spufs/inode.c b/arch/powerpc/platforms/cell/spufs/inode.c

Re: linux-next: build failure after merge of the vfs tree

On Mon, Jul 10, 2017 at 12:15:11PM +1000, Stephen Rothwell wrote: > Hi Al, > Caused by commit > > 4f9365d9e2e7 ("spufs: Implement show_options") Obvious incremental follows, will fold and push diff --git a/arch/powerpc/platforms/cell/spufs/inode.c b/arch/powerpc/platforms/cell/spufs/inode.c

Re: [PATCH v16 2/7] power: add power sequence library

On Sat, Jul 08, 2017 at 02:14:56PM +0200, Rafael J. Wysocki wrote: > On Saturday, July 08, 2017 01:51:15 PM Peter Chen wrote: > > On Fri, Jul 07, 2017 at 03:03:06PM +0200, Rafael J. Wysocki wrote: > > > On Friday, July 07, 2017 04:01:07 PM Peter Chen wrote: > > > > On Fri, Jul 07, 2017 at

Re: [PATCH v16 2/7] power: add power sequence library

On Sat, Jul 08, 2017 at 02:14:56PM +0200, Rafael J. Wysocki wrote: > On Saturday, July 08, 2017 01:51:15 PM Peter Chen wrote: > > On Fri, Jul 07, 2017 at 03:03:06PM +0200, Rafael J. Wysocki wrote: > > > On Friday, July 07, 2017 04:01:07 PM Peter Chen wrote: > > > > On Fri, Jul 07, 2017 at

Re: blk-mq timeout question

On Fri, Jul 7, 2017 at 9:45 PM, Stefan Haberland wrote: > While changing the DASD device driver to use the blk-mq interfaces I found > the following unexpected behavior: > > In case of a timeout our complete callback is never called. Here is the > sequence of events as I

Re: blk-mq timeout question

On Fri, Jul 7, 2017 at 9:45 PM, Stefan Haberland wrote: > While changing the DASD device driver to use the blk-mq interfaces I found > the following unexpected behavior: > > In case of a timeout our complete callback is never called. Here is the > sequence of events as I understood: > > -

linux-next: build failure after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: arch/powerpc/platforms/cell/spufs/inode.c: In function 'spufs_show_options': arch/powerpc/platforms/cell/spufs/inode.c:612:18: error: 'struct dentry' has no member named 'i_uid' if

linux-next: build failure after merge of the vfs tree

Hi Al, After merging the vfs tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: arch/powerpc/platforms/cell/spufs/inode.c: In function 'spufs_show_options': arch/powerpc/platforms/cell/spufs/inode.c:612:18: error: 'struct dentry' has no member named 'i_uid' if

[PATCH] usb: gadget: configfs: compress return logic into one line

Simplify return logic to avoid unnecessary variable assignment. This issue was detected using Coccinelle and the following semantic patch: @@ local idexpression ret; expression e; @@ -ret = +return e; -return ret; Signed-off-by: Gustavo A. R. Silva ---

[PATCH] usb: gadget: configfs: compress return logic into one line

Simplify return logic to avoid unnecessary variable assignment. This issue was detected using Coccinelle and the following semantic patch: @@ local idexpression ret; expression e; @@ -ret = +return e; -return ret; Signed-off-by: Gustavo A. R. Silva --- drivers/usb/gadget/configfs.c | 5

Re: [RFC PATCH] x86: enable dead code and data elimination (LTO)

On Sun, 9 Jul 2017 09:59:44 -0400 (EDT) Nicolas Pitre wrote: > On Sun, 9 Jul 2017, Masahiro Yamada wrote: > > > Hi. > > > > 2017-07-09 18:05 GMT+09:00 Ingo Molnar : > > > > > > * Nicholas Piggin wrote: > > > > > >> FYI,

Re: [RFC PATCH] x86: enable dead code and data elimination (LTO)

On Sun, 9 Jul 2017 09:59:44 -0400 (EDT) Nicolas Pitre wrote: > On Sun, 9 Jul 2017, Masahiro Yamada wrote: > > > Hi. > > > > 2017-07-09 18:05 GMT+09:00 Ingo Molnar : > > > > > > * Nicholas Piggin wrote: > > > > > >> FYI, easiest way to check if you forgot to KEEP a linker table is > > >>

[PATCH] usb: chipidea: udc: compress return logic into line

Simplify return logic to avoid unnecessary variable assignment. This issue was detected using Coccinelle and the following semantic patch: @@ local idexpression ret; expression e; @@ -ret = +return e; -return ret; Signed-off-by: Gustavo A. R. Silva ---

[PATCH] usb: chipidea: udc: compress return logic into line

Simplify return logic to avoid unnecessary variable assignment. This issue was detected using Coccinelle and the following semantic patch: @@ local idexpression ret; expression e; @@ -ret = +return e; -return ret; Signed-off-by: Gustavo A. R. Silva --- drivers/usb/chipidea/udc.c | 5

[PATCH] ddbridge: constify i2c_algorithm structure

Check for i2c_algorithm structures that are only stored in the algo field of an i2c_adapter structure. This field is declared const, so i2c_algorithm structures that have this property can be declared as const also. This issue was identified using Coccinelle and the following semantic patch: @r

[PATCH] ddbridge: constify i2c_algorithm structure

Check for i2c_algorithm structures that are only stored in the algo field of an i2c_adapter structure. This field is declared const, so i2c_algorithm structures that have this property can be declared as const also. This issue was identified using Coccinelle and the following semantic patch: @r

[PATCH] usb: isp1760: compress return logic into one line

Simplify return logic to avoid unnecessary variable assignment. This issue was detected using Coccinelle and the following semantic patch: @@ local idexpression ret; expression e; @@ -ret = +return e; -return ret; Signed-off-by: Gustavo A. R. Silva ---

[PATCH] usb: isp1760: compress return logic into one line

Simplify return logic to avoid unnecessary variable assignment. This issue was detected using Coccinelle and the following semantic patch: @@ local idexpression ret; expression e; @@ -ret = +return e; -return ret; Signed-off-by: Gustavo A. R. Silva --- drivers/usb/isp1760/isp1760-hcd.c

[RFC PATCH v1 01/11] sched/idle: create a fast path for short idle periods

From: Aubrey Li Short idle periods occur common under some workloads, and the idle entry and exit path starts to dominate, so it's important to optimize them. A fast idle routine is introduced here for short idle periods. - tick nohz enter/exit are exclued - RCU idle

[RFC PATCH v1 02/11] cpuidle: attach cpuidle governor statistics to the per-CPU device

From: Aubrey Li A generic CPU idle governor is required to make the prediction of how long the coming idle. The statistic data taken from the existing menu governor is attached to the per-CPU device data structure --- include/linux/cpuidle.h | 30

[RFC PATCH v1 01/11] sched/idle: create a fast path for short idle periods

From: Aubrey Li Short idle periods occur common under some workloads, and the idle entry and exit path starts to dominate, so it's important to optimize them. A fast idle routine is introduced here for short idle periods. - tick nohz enter/exit are exclued - RCU idle enter/exit are excluded

[RFC PATCH v1 02/11] cpuidle: attach cpuidle governor statistics to the per-CPU device

From: Aubrey Li A generic CPU idle governor is required to make the prediction of how long the coming idle. The statistic data taken from the existing menu governor is attached to the per-CPU device data structure --- include/linux/cpuidle.h | 30 ++ 1 file changed,

[RFC PATCH v1 04/11] sched/idle: make the fast idle path for short idle periods

From: Aubrey Li The system will enter a fast idle loop if the predicted idle period is shorter than the threshold. --- kernel/sched/idle.c | 9 - 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/kernel/sched/idle.c b/kernel/sched/idle.c index

[RFC PATCH v1 03/11] cpuidle: introduce cpuidle governor for idle prediction

From: Aubrey Li Two factors taken from menu governor for idle prediction in the cpu idle governor: - Energy break even point - Repeatable interval detector Based on the actual known "next timer event" time, and coordinate with the algorithm in the above two factors,

[RFC PATCH v1 03/11] cpuidle: introduce cpuidle governor for idle prediction

From: Aubrey Li Two factors taken from menu governor for idle prediction in the cpu idle governor: - Energy break even point - Repeatable interval detector Based on the actual known "next timer event" time, and coordinate with the algorithm in the above two factors, we'll make a prediction of

[RFC PATCH v1 04/11] sched/idle: make the fast idle path for short idle periods

From: Aubrey Li The system will enter a fast idle loop if the predicted idle period is shorter than the threshold. --- kernel/sched/idle.c | 9 - 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/kernel/sched/idle.c b/kernel/sched/idle.c index cf6c11f..16a766c 100644 ---

[RFC PATCH v1 08/11] cpuidle: menu: remove reduplicative implementation

From: Aubrey Li For what cpuidle governor already does, we remove them from menu governor --- drivers/cpuidle/governors/menu.c | 163 --- 1 file changed, 163 deletions(-) diff --git a/drivers/cpuidle/governors/menu.c

[RFC PATCH v1 08/11] cpuidle: menu: remove reduplicative implementation

From: Aubrey Li For what cpuidle governor already does, we remove them from menu governor --- drivers/cpuidle/governors/menu.c | 163 --- 1 file changed, 163 deletions(-) diff --git a/drivers/cpuidle/governors/menu.c b/drivers/cpuidle/governors/menu.c index

[RFC PATCH v1 07/11] cpuidle: make idle residency update more generic

From: Aubrey Li Current cpuidle governor updates the last idle residency with the hardware c-state exit latency, which is not applicable for fast idle path, so we update idle residency in idle routine instead. --- drivers/cpuidle/cpuidle.c | 13 + 1 file

[RFC PATCH v1 09/11] cpuidle: menu: feed cpuidle prediction to menu governor

From: Aubrey Li cpuidle already makes the prediction of how long the coming idle is. We take it as the input for menu governor to select the target c-state. --- drivers/cpuidle/governors/menu.c | 29 + 1 file changed, 5 insertions(+), 24

[RFC PATCH v1 10/11] cpuidle: update cpuidle governor when needed

From: Aubrey Li Reflect the data to cpuidle governor when there is an update --- drivers/cpuidle/cpuidle.c | 6 -- include/linux/cpuidle.h | 1 + kernel/sched/idle.c | 14 ++ 3 files changed, 19 insertions(+), 2 deletions(-) diff --git

[RFC PATCH v1 07/11] cpuidle: make idle residency update more generic

From: Aubrey Li Current cpuidle governor updates the last idle residency with the hardware c-state exit latency, which is not applicable for fast idle path, so we update idle residency in idle routine instead. --- drivers/cpuidle/cpuidle.c | 13 + 1 file changed, 5 insertions(+), 8

[RFC PATCH v1 09/11] cpuidle: menu: feed cpuidle prediction to menu governor

From: Aubrey Li cpuidle already makes the prediction of how long the coming idle is. We take it as the input for menu governor to select the target c-state. --- drivers/cpuidle/governors/menu.c | 29 + 1 file changed, 5 insertions(+), 24 deletions(-) diff --git

[RFC PATCH v1 10/11] cpuidle: update cpuidle governor when needed

From: Aubrey Li Reflect the data to cpuidle governor when there is an update --- drivers/cpuidle/cpuidle.c | 6 -- include/linux/cpuidle.h | 1 + kernel/sched/idle.c | 14 ++ 3 files changed, 19 insertions(+), 2 deletions(-) diff --git a/drivers/cpuidle/cpuidle.c

[RFC PATCH v1 05/11] cpuidle: update idle statistics before cpuidle governor

From: Aubrey Li Promote menu governor update functionality into cpuidle governor, so that cpuidle can make a prediction based on the fresh data. --- drivers/cpuidle/cpuidle.c | 77 +++ 1 file changed, 77 insertions(+) diff

[RFC PATCH v1 11/11] sched/idle: Add a tuning knob to allow changing fast idle threshold

From: Aubrey Li Short idle periods varies from different workload, make the switch tunable --- include/linux/sched/sysctl.h | 1 + kernel/sched/idle.c | 5 +++-- kernel/sysctl.c | 10 ++ 3 files changed, 14 insertions(+), 2 deletions(-)

[RFC PATCH v1 05/11] cpuidle: update idle statistics before cpuidle governor

From: Aubrey Li Promote menu governor update functionality into cpuidle governor, so that cpuidle can make a prediction based on the fresh data. --- drivers/cpuidle/cpuidle.c | 77 +++ 1 file changed, 77 insertions(+) diff --git

[RFC PATCH v1 11/11] sched/idle: Add a tuning knob to allow changing fast idle threshold

From: Aubrey Li Short idle periods varies from different workload, make the switch tunable --- include/linux/sched/sysctl.h | 1 + kernel/sched/idle.c | 5 +++-- kernel/sysctl.c | 10 ++ 3 files changed, 14 insertions(+), 2 deletions(-) diff --git

[RFC PATCH v1 00/11] Create fast idle path for short idle periods

From: Aubrey Li Under some latency intensive workloads, short idle periods occurs very common, so that idle entry and exit path starts to dominate. It's important to optimize them for the short idle period pattern. A fast idle path proposal is introduced here for this

[RFC PATCH v1 06/11] timers: keep sleep length updated as needed

From: Aubrey Li sleep length indicates how long we'll be idle. Currently, it's updated only when tick nohz enters. These patch series make a new requirement with tick, so we should keep sleep length updated as needed --- kernel/time/tick-sched.c | 3 +++ 1 file

[RFC PATCH v1 00/11] Create fast idle path for short idle periods

From: Aubrey Li Under some latency intensive workloads, short idle periods occurs very common, so that idle entry and exit path starts to dominate. It's important to optimize them for the short idle period pattern. A fast idle path proposal is introduced here for this purpose. This proposal

[RFC PATCH v1 06/11] timers: keep sleep length updated as needed

From: Aubrey Li sleep length indicates how long we'll be idle. Currently, it's updated only when tick nohz enters. These patch series make a new requirement with tick, so we should keep sleep length updated as needed --- kernel/time/tick-sched.c | 3 +++ 1 file changed, 3 insertions(+) diff

Re: [PATCH v4 4/4] x86/boot/KASLR: Restrict kernel to be randomized in mirror regions

On 07/09/17 at 07:11am, Kees Cook wrote: > On Sun, Jul 9, 2017 at 5:37 AM, Baoquan He wrote: > > Signed-off-by: Baoquan He > > +/* Marks if efi mirror regions have been found and handled. */ > > +static bool efi_mirror_found; > > I think this is only ever

Re: [PATCH v4 4/4] x86/boot/KASLR: Restrict kernel to be randomized in mirror regions

On 07/09/17 at 07:11am, Kees Cook wrote: > On Sun, Jul 9, 2017 at 5:37 AM, Baoquan He wrote: > > Signed-off-by: Baoquan He > > +/* Marks if efi mirror regions have been found and handled. */ > > +static bool efi_mirror_found; > > I think this is only ever checked once? How about having >

[PATCH] mantis: constify i2c_algorithm structure

Check for i2c_algorithm structures that are only stored in the algo field of an i2c_adapter structure. This field is declared const, so i2c_algorithm structures that have this property can be declared as const also. This issue was identified using Coccinelle and the following semantic patch: @r

[PATCH] mantis: constify i2c_algorithm structure

Check for i2c_algorithm structures that are only stored in the algo field of an i2c_adapter structure. This field is declared const, so i2c_algorithm structures that have this property can be declared as const also. This issue was identified using Coccinelle and the following semantic patch: @r

Re: [PATCH 2/2] nvmem: rockchip-efuse: add support for rk3328-efuse

On Thu, Jul 06, 2017 at 03:36:37PM +0800, Finley Xiao wrote: > This adds the necessary data for handling eFuse on the rk3328. > > Signed-off-by: Finley Xiao > --- > .../devicetree/bindings/nvmem/rockchip-efuse.txt | 1 + Acked-by: Rob Herring >

Re: [PATCH 2/2] nvmem: rockchip-efuse: add support for rk3328-efuse

On Thu, Jul 06, 2017 at 03:36:37PM +0800, Finley Xiao wrote: > This adds the necessary data for handling eFuse on the rk3328. > > Signed-off-by: Finley Xiao > --- > .../devicetree/bindings/nvmem/rockchip-efuse.txt | 1 + Acked-by: Rob Herring > drivers/nvmem/rockchip-efuse.c

Re: [PATCH 1/2] nvmem: rockchip-efuse: parse 'rockchip,efuse-size'

On Thu, Jul 06, 2017 at 03:36:36PM +0800, Finley Xiao wrote: > The eFuse size is defined in property before, but the length > of registers is not equal to the size on some platforms, so we > add a new property to redefine it. > > Signed-off-by: Finley Xiao > --- >

Re: [PATCH 1/2] nvmem: rockchip-efuse: parse 'rockchip,efuse-size'

On Thu, Jul 06, 2017 at 03:36:36PM +0800, Finley Xiao wrote: > The eFuse size is defined in property before, but the length > of registers is not equal to the size on some platforms, so we > add a new property to redefine it. > > Signed-off-by: Finley Xiao > --- >

Re: [PATCH v2 5/5] Documentation/devicetree/bindings: Add FSI device documentation

On Wed, Jul 05, 2017 at 04:36:57PM -0500, Eddie James wrote: > From: "Edward A. James" "dt-bindings: fsi: ..." for the subject. > > Document the bindings for the SBE and OCC devices. SBE devices are > located on a CFAM on an FSI bus, and OCC devices are accessed through >

Re: [PATCH v2 5/5] Documentation/devicetree/bindings: Add FSI device documentation

On Wed, Jul 05, 2017 at 04:36:57PM -0500, Eddie James wrote: > From: "Edward A. James" "dt-bindings: fsi: ..." for the subject. > > Document the bindings for the SBE and OCC devices. SBE devices are > located on a CFAM on an FSI bus, and OCC devices are accessed through > the SBEFIFO. > >

[PATCH] dm1105: constify i2c_algorithm structure

Check for i2c_algorithm structures that are only stored in the algo field of an i2c_adapter structure. This field is declared const, so i2c_algorithm structures that have this property can be declared as const also. This issue was identified using Coccinelle and the following semantic patch: @r

[PATCH] dm1105: constify i2c_algorithm structure

Check for i2c_algorithm structures that are only stored in the algo field of an i2c_adapter structure. This field is declared const, so i2c_algorithm structures that have this property can be declared as const also. This issue was identified using Coccinelle and the following semantic patch: @r

[PATCH] ngene: constify i2c_algorithm structure

Check for i2c_algorithm structures that are only stored in the algo field of an i2c_adapter structure. This field is declared const, so i2c_algorithm structures that have this property can be declared as const also. This issue was identified using Coccinelle and the following semantic patch: @r

[PATCH] ngene: constify i2c_algorithm structure

Check for i2c_algorithm structures that are only stored in the algo field of an i2c_adapter structure. This field is declared const, so i2c_algorithm structures that have this property can be declared as const also. This issue was identified using Coccinelle and the following semantic patch: @r

[PATCH] cx24123: constify i2c_algorithm structure

Check for i2c_algorithm structures that are only stored in the algo field of an i2c_adapter structure. This field is declared const, so i2c_algorithm structures that have this property can be declared as const also. This issue was identified using Coccinelle and the following semantic patch: @r

[PATCH] cx24123: constify i2c_algorithm structure

Check for i2c_algorithm structures that are only stored in the algo field of an i2c_adapter structure. This field is declared const, so i2c_algorithm structures that have this property can be declared as const also. This issue was identified using Coccinelle and the following semantic patch: @r

[PATCH] zd1301_demod: constify i2c_algorithm structure

Check for i2c_algorithm structures that are only stored in the algo field of an i2c_adapter structure. This field is declared const, so i2c_algorithm structures that have this property can be declared as const also. This issue was identified using Coccinelle and the following semantic patch: @r

[PATCH] zd1301_demod: constify i2c_algorithm structure

Check for i2c_algorithm structures that are only stored in the algo field of an i2c_adapter structure. This field is declared const, so i2c_algorithm structures that have this property can be declared as const also. This issue was identified using Coccinelle and the following semantic patch: @r

Re: [PATCH v2 7/9] ASoC: atmel-classd: remove aclk clock from DT binding

On Tue, Jul 04, 2017 at 01:59:25PM +0200, Quentin Schulz wrote: > Since gclk (generated-clk) is now able to determine the rate of the > audio_pll, there is no need for classd to have a direct phandle to the > audio_pll while already having a phandle to gclk. > > This binding is used by no board

Re: [PATCH v2 7/9] ASoC: atmel-classd: remove aclk clock from DT binding

On Tue, Jul 04, 2017 at 01:59:25PM +0200, Quentin Schulz wrote: > Since gclk (generated-clk) is now able to determine the rate of the > audio_pll, there is no need for classd to have a direct phandle to the > audio_pll while already having a phandle to gclk. > > This binding is used by no board

[PATCH] dib8000: constify i2c_algorithm structure

Check for i2c_algorithm structures that are only stored in the algo field of an i2c_adapter structure. This field is declared const, so i2c_algorithm structures that have this property can be declared as const also. This issue was identified using Coccinelle and the following semantic patch: @r

[PATCH] dib8000: constify i2c_algorithm structure

Check for i2c_algorithm structures that are only stored in the algo field of an i2c_adapter structure. This field is declared const, so i2c_algorithm structures that have this property can be declared as const also. This issue was identified using Coccinelle and the following semantic patch: @r

Re: [PATCH] dt-bindings: nvmem: mediatek: add support for MediaTek MT7623 and MT7622 SoC

On Fri, Jun 30, 2017 at 03:49:00PM +0800, sean.w...@mediatek.com wrote: > From: Sean Wang > > This updates dt-binding documentation for MediaTek MT7622 and > MT7623 SoC. For the both SoCs supported all rely on the fallback > binding of the generic case with

Re: [PATCH] dt-bindings: nvmem: mediatek: add support for MediaTek MT7623 and MT7622 SoC

On Fri, Jun 30, 2017 at 03:49:00PM +0800, sean.w...@mediatek.com wrote: > From: Sean Wang > > This updates dt-binding documentation for MediaTek MT7622 and > MT7623 SoC. For the both SoCs supported all rely on the fallback > binding of the generic case with "mediatek,efuse". > > Signed-off-by:

<    1   2   3   4   5   6   >