[PATCH 2/5] x86: msr-index.h: define HWP.EPP values

From: Len Brown The Hardware Performance State request MSR has a field to express the "Energy Performance Preference" (HWP.EPP). Decode that field so the definition may be shared by by the intel_pstate driver and any utilities that decode the same register. Signed-off-by: Len Brown ---

[PATCH 4/5] tools/power x86_energy_perf_policy: support HWP.EPP

From: Len Brown x86_energy_perf_policy(8) was created as an example of how the user, or upper-level OS, can manage MSR_IA32_ENERGY_PERF_BIAS (EPB). Hardware consults EPB when it makes internal decisions balancing energy-saving vs performance. For example, should HW quickly or slowly transition

[PATCH 2/2] defconfig: PCI: Enable Kirin PCIe defconfig

Cc: Guodong Xu Signed-off-by: Song Xiaowei --- arch/arm64/configs/defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig index 7c48028ec64a..d56d8f1062ab 100644 ---

[PATCH 2/2] defconfig: PCI: Enable Kirin PCIe defconfig

Cc: Guodong Xu Signed-off-by: Song Xiaowei --- arch/arm64/configs/defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig index 7c48028ec64a..d56d8f1062ab 100644 --- a/arch/arm64/configs/defconfig +++

[PATCH 1/2] PCI: dwc: kirin: add PCIe Driver for HiSilicon Kirin SoC

From: songxiaowei Hisilicon PCIe Driver shares the common functions fo PCIe dw-host The poweron functions is developed on hi3660 SoC, while Others Functions are common for Kirin series SoCs. Lowpower(L1ss and SR), hotplug and MSI feature are not supported currently.

[PATCH 1/2] PCI: dwc: kirin: add PCIe Driver for HiSilicon Kirin SoC

From: songxiaowei Hisilicon PCIe Driver shares the common functions fo PCIe dw-host The poweron functions is developed on hi3660 SoC, while Others Functions are common for Kirin series SoCs. Lowpower(L1ss and SR), hotplug and MSI feature are not supported currently. Cc: Guodong Xu

Re: [v6 PATCH 10/21] x86/insn-eval: Do not use R/EBP as base if mod in ModRM is zero

On Sun, 2017-05-07 at 19:20 +0200, Borislav Petkov wrote: > On Wed, Apr 26, 2017 at 06:29:59PM -0700, Ricardo Neri wrote: > > > if (X86_MODRM_MOD(insn->modrm.value) == 0 && > > > X86_MODRM_RM(insn->modrm.value) == 5) > > > > > > looks more understandable to me. > > > > Should I go with

Re: [v6 PATCH 10/21] x86/insn-eval: Do not use R/EBP as base if mod in ModRM is zero

On Sun, 2017-05-07 at 19:20 +0200, Borislav Petkov wrote: > On Wed, Apr 26, 2017 at 06:29:59PM -0700, Ricardo Neri wrote: > > > if (X86_MODRM_MOD(insn->modrm.value) == 0 && > > > X86_MODRM_RM(insn->modrm.value) == 5) > > > > > > looks more understandable to me. > > > > Should I go with

Re: [v6 PATCH 12/21] x86/insn: Support both signed 32-bit and 64-bit effective addresses

On Mon, 2017-05-08 at 13:42 +0200, Borislav Petkov wrote: > On Wed, Apr 26, 2017 at 08:33:46PM -0700, Ricardo Neri wrote: > > This is the reason I check the value of long_bytes. If long_bytes is not > > 4, being the only other possible value 8 (perhaps I need to issue an > > error when the value

Re: [v6 PATCH 12/21] x86/insn: Support both signed 32-bit and 64-bit effective addresses

On Mon, 2017-05-08 at 13:42 +0200, Borislav Petkov wrote: > On Wed, Apr 26, 2017 at 08:33:46PM -0700, Ricardo Neri wrote: > > This is the reason I check the value of long_bytes. If long_bytes is not > > 4, being the only other possible value 8 (perhaps I need to issue an > > error when the value

Re: Is there an recommended way to refer to bitkeepr commits?

Rob Landley writes: > On 05/11/2017 01:59 AM, Michael Ellerman wrote: >> Linus Torvalds writes: >> >>> On Wed, May 10, 2017 at 3:04 PM, Eric W. Biederman >>> wrote: Thomas Gleixner appears to have a tree with

Re: [PATCH] i2c-designware: add i2c gpio recovery option

On 11/05/2017 21:53, Andy Shevchenko wrote: +static int i2c_dw_init_recovery_info(struct dw_i2c_dev *dev, +struct i2c_adapter *adap) +{ + struct i2c_bus_recovery_info *rinfo = >rinfo; + + dev->gpio_scl = devm_gpiod_get_optional(dev->dev, +

Re: Is there an recommended way to refer to bitkeepr commits?

Rob Landley writes: > On 05/11/2017 01:59 AM, Michael Ellerman wrote: >> Linus Torvalds writes: >> >>> On Wed, May 10, 2017 at 3:04 PM, Eric W. Biederman >>> wrote: Thomas Gleixner appears to have a tree with all of those same commits except with the BKrev tags stripped out.

Re: [PATCH] i2c-designware: add i2c gpio recovery option

On 11/05/2017 21:53, Andy Shevchenko wrote: +static int i2c_dw_init_recovery_info(struct dw_i2c_dev *dev, +struct i2c_adapter *adap) +{ + struct i2c_bus_recovery_info *rinfo = >rinfo; + + dev->gpio_scl = devm_gpiod_get_optional(dev->dev, +

[PATCH 1/4] staging: rtl8723bs: checkpatch - remove multiple blank lines

Resolving checkpatch issue: CHECK: Please don't use multiple blank lines All instances resolved. --- drivers/staging/rtl8723bs/include/rtl8723b_spec.h | 5 - 1 file changed, 5 deletions(-) diff --git a/drivers/staging/rtl8723bs/include/rtl8723b_spec.h

[PATCH 1/4] staging: rtl8723bs: checkpatch - remove multiple blank lines

Resolving checkpatch issue: CHECK: Please don't use multiple blank lines All instances resolved. --- drivers/staging/rtl8723bs/include/rtl8723b_spec.h | 5 - 1 file changed, 5 deletions(-) diff --git a/drivers/staging/rtl8723bs/include/rtl8723b_spec.h

[PATCH 3/4] staging: rtl8723bs: checkpatch - fix typos in comments

Resolving checkpatch issue: CHECK: 'Regsiter' may be misspelled - perhaps 'Register'? CHECK: 'Interrup' may be misspelled - perhaps 'Interrupt'? All instances resolved. --- drivers/staging/rtl8723bs/include/rtl8723b_spec.h | 16 1 file changed, 8 insertions(+), 8 deletions(-)

[PATCH 3/4] staging: rtl8723bs: checkpatch - fix typos in comments

Resolving checkpatch issue: CHECK: 'Regsiter' may be misspelled - perhaps 'Register'? CHECK: 'Interrup' may be misspelled - perhaps 'Interrupt'? All instances resolved. --- drivers/staging/rtl8723bs/include/rtl8723b_spec.h | 16 1 file changed, 8 insertions(+), 8 deletions(-)

[PATCH 4/4] staging: rtl8723bs: checkpatch - resolve indentation and line width

Resolving checkpatch issue: WARNING: line over 80 characters Consolidated indentation so local blocks of macros are column-aligned. Slight slight change to make indentation more readable, assuming a 8-space hard-tab indentation style. --- drivers/staging/rtl8723bs/include/rtl8723b_spec.h | 262

[PATCH 2/4] staging: rtl8723bs: checkpatch - remove mixed spaces/hard-tabs

Resolving checkpatch issue: WARNING: please, no space before tabs All instances resolved. --- drivers/staging/rtl8723bs/include/rtl8723b_spec.h | 30 +++ 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/drivers/staging/rtl8723bs/include/rtl8723b_spec.h

[PATCH 2/4] staging: rtl8723bs: checkpatch - remove mixed spaces/hard-tabs

Resolving checkpatch issue: WARNING: please, no space before tabs All instances resolved. --- drivers/staging/rtl8723bs/include/rtl8723b_spec.h | 30 +++ 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/drivers/staging/rtl8723bs/include/rtl8723b_spec.h

[PATCH 4/4] staging: rtl8723bs: checkpatch - resolve indentation and line width

Resolving checkpatch issue: WARNING: line over 80 characters Consolidated indentation so local blocks of macros are column-aligned. Slight slight change to make indentation more readable, assuming a 8-space hard-tab indentation style. --- drivers/staging/rtl8723bs/include/rtl8723b_spec.h | 262

[PATCH 0/4] staging: rtl8723bs: resolve checkpatch issues

This set of patches resolves a large number of non-functional issues reported by checkpatch for the following header: drivers/staging/rtl8723bs/include/rtl8723b_spec.h *Typos in comments *Indentation consistency (original code not formatted for 8-wide hard-tabs) and 80+ column width lines.

[PATCH 0/4] staging: rtl8723bs: resolve checkpatch issues

This set of patches resolves a large number of non-functional issues reported by checkpatch for the following header: drivers/staging/rtl8723bs/include/rtl8723b_spec.h *Typos in comments *Indentation consistency (original code not formatted for 8-wide hard-tabs) and 80+ column width lines.

Re: [PATCH][V2] ethernet: aquantia: remove redundant checks on error status

From: Colin King Date: Thu, 11 May 2017 19:29:40 +0100 > From: Colin Ian King > > The error status err is initialized as zero and then being checked > several times to see if it is less than zero even when it has not > been updated. It may

Re: [PATCH][V2] ethernet: aquantia: remove redundant checks on error status

From: Colin King Date: Thu, 11 May 2017 19:29:40 +0100 > From: Colin Ian King > > The error status err is initialized as zero and then being checked > several times to see if it is less than zero even when it has not > been updated. It may seem that the err should be assigned to the > return

Re: [PATCH v2] xen-netfront: avoid crashing on resume after a failure in talk_to_netback()

From: Vitaly Kuznetsov Date: Thu, 11 May 2017 13:58:06 +0200 > Unavoidable crashes in netfront_resume() and netback_changed() after a > previous fail in talk_to_netback() (e.g. when we fail to read MAC from > xenstore) were discovered. The failure path in talk_to_netback()

Re: [PATCH v2] xen-netfront: avoid crashing on resume after a failure in talk_to_netback()

From: Vitaly Kuznetsov Date: Thu, 11 May 2017 13:58:06 +0200 > Unavoidable crashes in netfront_resume() and netback_changed() after a > previous fail in talk_to_netback() (e.g. when we fail to read MAC from > xenstore) were discovered. The failure path in talk_to_netback() does > unregister/free

Re: [PATCH -mm -v10 1/3] mm, THP, swap: Delay splitting THP during swap out

Hi Hannes, On Thu, May 11, 2017 at 06:40:58AM -0400, Johannes Weiner wrote: > On Thu, May 11, 2017 at 10:22:13AM +0900, Minchan Kim wrote: > > On Thu, May 11, 2017 at 08:25:56AM +0900, Minchan Kim wrote: > > > On Wed, May 10, 2017 at 09:56:54AM -0400, Johannes Weiner wrote: > > > > Hi Michan, > >

Re: [PATCH -mm -v10 1/3] mm, THP, swap: Delay splitting THP during swap out

Hi Hannes, On Thu, May 11, 2017 at 06:40:58AM -0400, Johannes Weiner wrote: > On Thu, May 11, 2017 at 10:22:13AM +0900, Minchan Kim wrote: > > On Thu, May 11, 2017 at 08:25:56AM +0900, Minchan Kim wrote: > > > On Wed, May 10, 2017 at 09:56:54AM -0400, Johannes Weiner wrote: > > > > Hi Michan, > >

[git pull] work.sane_pwd

Making sure that something like a referral point won't end up as pwd or root. The main part is the last commit (fixing mntns_install()); that one fixes a hard-to-hit race. fchdir() one is making fchdir(2) a bit more robust - it should be impossible to get opened files (even O_PATH ones)

[git pull] work.sane_pwd

Making sure that something like a referral point won't end up as pwd or root. The main part is the last commit (fixing mntns_install()); that one fixes a hard-to-hit race. fchdir() one is making fchdir(2) a bit more robust - it should be impossible to get opened files (even O_PATH ones)

[PATCH v3] KVM: x86: Fix potential preemption when get the current kvmclock timestamp

From: Wanpeng Li BUG: using __this_cpu_read() in preemptible [] code: qemu-system-x86/2809 caller is __this_cpu_preempt_check+0x13/0x20 CPU: 2 PID: 2809 Comm: qemu-system-x86 Not tainted 4.11.0+ #13 Call Trace: dump_stack+0x99/0xce

[PATCH v3] KVM: x86: Fix potential preemption when get the current kvmclock timestamp

From: Wanpeng Li BUG: using __this_cpu_read() in preemptible [] code: qemu-system-x86/2809 caller is __this_cpu_preempt_check+0x13/0x20 CPU: 2 PID: 2809 Comm: qemu-system-x86 Not tainted 4.11.0+ #13 Call Trace: dump_stack+0x99/0xce check_preemption_disabled+0xf5/0x100

Re: [PATCH v9 3/3] printk: fix double printing with earlycon

On (05/12/17 00:17), Aleksey Makarov wrote: > On 05/11/2017 02:32 PM, Sergey Senozhatsky wrote: > > On (05/11/17 17:41), Sergey Senozhatsky wrote: > > [..] > > > Alexey, > > > can we have preferred console at offset 0 (not at console_cmdline_cnt - 1) > > > and restore the previous

Re: [PATCH v9 3/3] printk: fix double printing with earlycon

On (05/12/17 00:17), Aleksey Makarov wrote: > On 05/11/2017 02:32 PM, Sergey Senozhatsky wrote: > > On (05/11/17 17:41), Sergey Senozhatsky wrote: > > [..] > > > Alexey, > > > can we have preferred console at offset 0 (not at console_cmdline_cnt - 1) > > > and restore the previous

[PATCH v2] KVM: x86: Fix potential preemption when get the current kvmclock timestamp

From: Wanpeng Li BUG: using __this_cpu_read() in preemptible [] code: qemu-system-x86/2809 caller is __this_cpu_preempt_check+0x13/0x20 CPU: 2 PID: 2809 Comm: qemu-system-x86 Not tainted 4.11.0+ #13 Call Trace: dump_stack+0x99/0xce

[PATCH v2] KVM: x86: Fix potential preemption when get the current kvmclock timestamp

From: Wanpeng Li BUG: using __this_cpu_read() in preemptible [] code: qemu-system-x86/2809 caller is __this_cpu_preempt_check+0x13/0x20 CPU: 2 PID: 2809 Comm: qemu-system-x86 Not tainted 4.11.0+ #13 Call Trace: dump_stack+0x99/0xce check_preemption_disabled+0xf5/0x100

[RESEND PATCH v3] sched/rt: Remove unnecessary condition in push_rt_task()

pick_next_pushable_task(rq) has BUG_ON(rq_cpu != task_cpu(task)) when it returns a task other than NULL, which means that task_cpu(task) must be rq->cpu. So if task == next_task, then task_cpu(next_task) must be rq->cpu as well. Remove the redundant condition and make code simpler. By this patch,

[RESEND PATCH v3] sched/rt: Remove unnecessary condition in push_rt_task()

pick_next_pushable_task(rq) has BUG_ON(rq_cpu != task_cpu(task)) when it returns a task other than NULL, which means that task_cpu(task) must be rq->cpu. So if task == next_task, then task_cpu(next_task) must be rq->cpu as well. Remove the redundant condition and make code simpler. By this patch,

[RESEND PATCH v3] sched/deadline: Remove unnecessary condition in push_dl_task()

pick_next_pushable_dl_task(rq) has BUG_ON(rq->cpu != task_cpu(task)) when it returns a task other than NULL, which means that task_cpu(task) must be rq->cpu. So if task == next_task, then task_cpu(next_task) must be rq->cpu as well. Remove the redundant condition and make code simpler. By this

[RESEND PATCH v3] sched/deadline: Remove unnecessary condition in push_dl_task()

pick_next_pushable_dl_task(rq) has BUG_ON(rq->cpu != task_cpu(task)) when it returns a task other than NULL, which means that task_cpu(task) must be rq->cpu. So if task == next_task, then task_cpu(next_task) must be rq->cpu as well. Remove the redundant condition and make code simpler. By this

Re: [PATCH] Input: elan_i2c - Add new ic and modify some functions for new IC infomation Signed-off-by: KT Liao <kt.l...@emc.com.tw>

On Tue, Nov 22, 2016 at 02:43:26PM +0800, KT Liao wrote: Applied, thank you. Sorry for the delay. > --- > drivers/input/mouse/elan_i2c.h | 6 ++- > drivers/input/mouse/elan_i2c_core.c | 40 +-- > drivers/input/mouse/elan_i2c_i2c.c | 74 >

Re: [PATCH] Input: elan_i2c - Add new ic and modify some functions for new IC infomation Signed-off-by: KT Liao

On Tue, Nov 22, 2016 at 02:43:26PM +0800, KT Liao wrote: Applied, thank you. Sorry for the delay. > --- > drivers/input/mouse/elan_i2c.h | 6 ++- > drivers/input/mouse/elan_i2c_core.c | 40 +-- > drivers/input/mouse/elan_i2c_i2c.c | 74 >

Re: [PATCH] Input: elantech - force a module ignore ABS mode

On Mon, Dec 12, 2016 at 03:11:03PM +0800, KT Liao wrote: > One Elan sample which sample version is 0x74 and hw_version is 0x04 has a bug > in abs mode, so let it run in default mode > Signed-off-by: KT Liao Applied, thank you. > --- > drivers/input/mouse/elantech.c | 7

Re: [PATCH] Input: elantech - force a module ignore ABS mode

On Mon, Dec 12, 2016 at 03:11:03PM +0800, KT Liao wrote: > One Elan sample which sample version is 0x74 and hw_version is 0x04 has a bug > in abs mode, so let it run in default mode > Signed-off-by: KT Liao Applied, thank you. > --- > drivers/input/mouse/elantech.c | 7 +++ > 1 file

[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] 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 +++

[RESEND PATCH] irq_work: 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 --- kernel/irq_work.c | 6 +- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/kernel/irq_work.c b/kernel/irq_work.c index bcf107c..e2ebe8c 100644 ---

[RESEND PATCH] irq_work: 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 --- kernel/irq_work.c | 6 +- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/kernel/irq_work.c b/kernel/irq_work.c index bcf107c..e2ebe8c 100644 --- a/kernel/irq_work.c +++

[RESEND PATCH] vhost/scsi: 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 Acked-by: Nicholas Bellinger --- drivers/vhost/scsi.c | 11 +++ 1 file changed, 3 insertions(+), 8 deletions(-) diff --git

[RESEND PATCH] vhost/scsi: 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 Acked-by: Nicholas Bellinger --- drivers/vhost/scsi.c | 11 +++ 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/drivers/vhost/scsi.c b/drivers/vhost/scsi.c index

[RESEND PATCH] sched: 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 --- kernel/sched/core.c | 15 +++ 1 file changed, 3 insertions(+), 12 deletions(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c index

[RESEND PATCH] sched: 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 --- kernel/sched/core.c | 15 +++ 1 file changed, 3 insertions(+), 12 deletions(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c index d01f9d0..8938125 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

[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] llist: Provide a safe version for llist_for_each

Sometimes we have to dereference next field of llist node before entering loop becasue the node might be deleted or the next field might be modified within the loop. So this adds the safe version of llist_for_each, that is, llist_for_each_safe. Signed-off-by: Byungchul Park

[RESEND PATCH] llist: Provide a safe version for llist_for_each

Sometimes we have to dereference next field of llist node before entering loop becasue the node might be deleted or the next field might be modified within the loop. So this adds the safe version of llist_for_each, that is, llist_for_each_safe. Signed-off-by: Byungchul Park Reviewed-by: "Huang,

[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

Re: [PATCH v2] ARM: dts: imx6sx-sdb: Remove OPP override

On Fri, May 05, 2017 at 02:00:17PM +0300, Leonard Crestez wrote: > The board file for imx6sx-sdb overrides cpufreq operating points to use > higher voltages. This is done because the board has a shared rail for > VDD_ARM_IN and VDD_SOC_IN and when using LDO bypass the shared voltage > needs to be

Re: [PATCH v2] ARM: dts: imx6sx-sdb: Remove OPP override

On Fri, May 05, 2017 at 02:00:17PM +0300, Leonard Crestez wrote: > The board file for imx6sx-sdb overrides cpufreq operating points to use > higher voltages. This is done because the board has a shared rail for > VDD_ARM_IN and VDD_SOC_IN and when using LDO bypass the shared voltage > needs to be

[RESEND] 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] 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

Re: [tip:smp/hotplug] trace/perf: Cure hotplug lock ordering issues

On Sun, 23 Apr 2017 04:30:01 -0700 tip-bot for Thomas Gleixner wrote: > Commit-ID: 24db7a671bd5eea76b17138b976eb9a4072f1b7a > Gitweb: http://git.kernel.org/tip/24db7a671bd5eea76b17138b976eb9a4072f1b7a > Author: Thomas Gleixner > AuthorDate: Sun, 23

Re: [tip:smp/hotplug] trace/perf: Cure hotplug lock ordering issues

On Sun, 23 Apr 2017 04:30:01 -0700 tip-bot for Thomas Gleixner wrote: > Commit-ID: 24db7a671bd5eea76b17138b976eb9a4072f1b7a > Gitweb: http://git.kernel.org/tip/24db7a671bd5eea76b17138b976eb9a4072f1b7a > Author: Thomas Gleixner > AuthorDate: Sun, 23 Apr 2017 12:17:13 +0200 > Committer:

Re: [PATCH v6 3/5] test: add new driver_data load tester

On Thu, May 11, 2017 at 11:32:30AM -0700, Luis R. Rodriguez wrote: > On Thu, May 11, 2017 at 11:26 AM, Luis R. Rodriguez wrote: > > > > It would seems to make sense to me to only need to verify files when read > > for the first time, once its cache I don't see why we would

Re: [PATCH v6 3/5] test: add new driver_data load tester

On Thu, May 11, 2017 at 11:32:30AM -0700, Luis R. Rodriguez wrote: > On Thu, May 11, 2017 at 11:26 AM, Luis R. Rodriguez wrote: > > > > It would seems to make sense to me to only need to verify files when read > > for the first time, once its cache I don't see why we would re-verify them ? > >

Re: [PATCH v6 3/5] test: add new driver_data load tester

On Thu, May 11, 2017 at 08:26:29PM +0200, Luis R. Rodriguez wrote: > On Thu, May 11, 2017 at 07:46:27PM +0900, AKASHI Takahiro wrote: > > On Fri, Apr 28, 2017 at 03:45:35AM +0200, Luis R. Rodriguez wrote: > > > > > diff --git a/tools/testing/selftests/firmware/driver_data.sh > > > > >

Re: [PATCH v6 3/5] test: add new driver_data load tester

On Thu, May 11, 2017 at 08:26:29PM +0200, Luis R. Rodriguez wrote: > On Thu, May 11, 2017 at 07:46:27PM +0900, AKASHI Takahiro wrote: > > On Fri, Apr 28, 2017 at 03:45:35AM +0200, Luis R. Rodriguez wrote: > > > > > diff --git a/tools/testing/selftests/firmware/driver_data.sh > > > > >

Re: [PATCH v9 7/9] coresight: add support for CPU debug module

On Thu, May 11, 2017 at 11:12:32AM -0600, Mathieu Poirier wrote: [...] > > +static int debug_probe(struct amba_device *adev, const struct amba_id *id) > > +{ > > + void __iomem *base; > > + struct device *dev = >dev; > > + struct debug_drvdata *drvdata; > > + struct resource *res = >res;

Re: [PATCH v9 7/9] coresight: add support for CPU debug module

On Thu, May 11, 2017 at 11:12:32AM -0600, Mathieu Poirier wrote: [...] > > +static int debug_probe(struct amba_device *adev, const struct amba_id *id) > > +{ > > + void __iomem *base; > > + struct device *dev = >dev; > > + struct debug_drvdata *drvdata; > > + struct resource *res = >res;

[PATCH 0/4] Raspberry Pi Touchscreen bridge/panel drivers

Here's the rewrite of the Raspberry Pi display support to split out a bridge driver representing the toshiba+atmel pair. It depends on the panel-bridge layer I've submitted. The RPi DSI stack isn't completely working yet -- I've got some flickery pixels on the display where it seems some color

[PATCH 0/4] Raspberry Pi Touchscreen bridge/panel drivers

Here's the rewrite of the Raspberry Pi display support to split out a bridge driver representing the toshiba+atmel pair. It depends on the panel-bridge layer I've submitted. The RPi DSI stack isn't completely working yet -- I've got some flickery pixels on the display where it seems some color

[PATCH 2/4] dt-bindings: Document the Raspberry Pi Touchscreen nodes.

The Raspberry Pi 7" Touchscreen is a DPI touchscreen panel with DSI->DPI bridge and touchscreen controller integrated, that connects to the Raspberry Pi through its 15-pin "DSI" connector (some lines are DSI, some lines are I2C). This device is represented in the DT as three nodes (DSI device,

[PATCH 1/4] drm/vc4: Adjust modes in DSI to work around the integer PLL divider.

BCM2835's PLLD_DSI1 divider doesn't give us many choices for our pixel clocks, so to support panels on the Raspberry Pi we need to set a higher pixel clock rate than requested and adjust the mode we program to extend out the HFP so that the refresh rate matches. Signed-off-by: Eric Anholt

[PATCH 2/4] dt-bindings: Document the Raspberry Pi Touchscreen nodes.

The Raspberry Pi 7" Touchscreen is a DPI touchscreen panel with DSI->DPI bridge and touchscreen controller integrated, that connects to the Raspberry Pi through its 15-pin "DSI" connector (some lines are DSI, some lines are I2C). This device is represented in the DT as three nodes (DSI device,

[PATCH 1/4] drm/vc4: Adjust modes in DSI to work around the integer PLL divider.

BCM2835's PLLD_DSI1 divider doesn't give us many choices for our pixel clocks, so to support panels on the Raspberry Pi we need to set a higher pixel clock rate than requested and adjust the mode we program to extend out the HFP so that the refresh rate matches. Signed-off-by: Eric Anholt ---

[PATCH 3/4] drm/bridge: Add support for the Raspberry Pi 7" Touchscreen.

This driver communicates with the Atmel microcontroller for sequencing the poweron of the TC358762 DSI-DPI bridge and controlling the backlight PWM. The following lines are required in config.txt, to keep the firmware from trying to bash our I2C lines and steal the DSI interrupts:

[PATCH 3/4] drm/bridge: Add support for the Raspberry Pi 7" Touchscreen.

This driver communicates with the Atmel microcontroller for sequencing the poweron of the TC358762 DSI-DPI bridge and controlling the backlight PWM. The following lines are required in config.txt, to keep the firmware from trying to bash our I2C lines and steal the DSI interrupts:

[PATCH 4/4] drm/panel: Add the Raspberry Pi 7" touchscreen's panel.

The timings are those that the firmware defines as the baseline, which will be modified by the bridge/host as necessary to get the clocking to work. Signed-off-by: Eric Anholt --- drivers/gpu/drm/panel/panel-simple.c | 30 ++ 1 file changed, 30

[PATCH 4/4] drm/panel: Add the Raspberry Pi 7" touchscreen's panel.

The timings are those that the firmware defines as the baseline, which will be modified by the bridge/host as necessary to get the clocking to work. Signed-off-by: Eric Anholt --- drivers/gpu/drm/panel/panel-simple.c | 30 ++ 1 file changed, 30 insertions(+) diff

[PATCH] fs: cifs: transport: Use time_after for time comparison

Use time_after kernel macro for time comparison that has safety check. Signed-off-by: Karim Eshapa --- fs/cifs/transport.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/cifs/transport.c b/fs/cifs/transport.c index 4d64b5b..a7f5168 100644 ---

[PATCH] fs: cifs: transport: Use time_after for time comparison

Use time_after kernel macro for time comparison that has safety check. Signed-off-by: Karim Eshapa --- fs/cifs/transport.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/cifs/transport.c b/fs/cifs/transport.c index 4d64b5b..a7f5168 100644 --- a/fs/cifs/transport.c +++

Re: [PATCH v2] sound: Disable the build of OSS drivers

On 05/11/17 13:58, Takashi Iwai wrote: > OSS drivers are left as badly unmaintained, and now we're facing a > problem to clean up the hackish set_fs() usage in their codes. Since > most of drivers have been covered by ALSA, and the others are dead old > and inactive, let's leave them RIP. > >

Re: [PATCH v2] sound: Disable the build of OSS drivers

On 05/11/17 13:58, Takashi Iwai wrote: > OSS drivers are left as badly unmaintained, and now we're facing a > problem to clean up the hackish set_fs() usage in their codes. Since > most of drivers have been covered by ALSA, and the others are dead old > and inactive, let's leave them RIP. > >

Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode

On Thu, May 11, 2017 at 4:17 PM, Thomas Garnier wrote: > > Ingo: Do you want the change as-is? Would you like it to be optional? > What do you think? I'm not ingo, but I don't like that patch. It's in the wrong place - that system call return code is too timing-critical to

Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode

On Thu, May 11, 2017 at 4:17 PM, Thomas Garnier wrote: > > Ingo: Do you want the change as-is? Would you like it to be optional? > What do you think? I'm not ingo, but I don't like that patch. It's in the wrong place - that system call return code is too timing-critical to add address limit

linux-next: error when fetching the target-bva tree

Hi Bart, Fetching the tagret-bva tree (git://git.kernel.org/pub/scm/linux/kernel/git/bvanassche/linux.git#for-next) today produces this error: fatal: Couldn't find remote ref refs/heads/for-next -- Cheers, Stephen Rothwell

linux-next: error when fetching the target-bva tree

Hi Bart, Fetching the tagret-bva tree (git://git.kernel.org/pub/scm/linux/kernel/git/bvanassche/linux.git#for-next) today produces this error: fatal: Couldn't find remote ref refs/heads/for-next -- Cheers, Stephen Rothwell

[PATCH] drm/radeon: Unbreak HPD handling for r600+

We end up reading the interrupt register for HPD5, and then writing it to HPD6 which on systems without anything using HPD5 results in permanently disabling hotplug on one of the display outputs after the first time we acknowledge a hotplug interrupt from the GPU. This code is really bad. But for

[PATCH] drm/radeon: Unbreak HPD handling for r600+

We end up reading the interrupt register for HPD5, and then writing it to HPD6 which on systems without anything using HPD5 results in permanently disabling hotplug on one of the display outputs after the first time we acknowledge a hotplug interrupt from the GPU. This code is really bad. But for

Re: Threads stuck in zap_pid_ns_processes()

Guenter Roeck writes: > On Thu, May 11, 2017 at 04:25:23PM -0500, Eric W. Biederman wrote: >> Guenter Roeck writes: >> >> > On Thu, May 11, 2017 at 12:31:21PM -0500, Eric W. Biederman wrote: >> >> Guenter Roeck writes: >> >> >> >> >

Re: Threads stuck in zap_pid_ns_processes()

Guenter Roeck writes: > On Thu, May 11, 2017 at 04:25:23PM -0500, Eric W. Biederman wrote: >> Guenter Roeck writes: >> >> > On Thu, May 11, 2017 at 12:31:21PM -0500, Eric W. Biederman wrote: >> >> Guenter Roeck writes: >> >> >> >> > Hi all, >> >> > >> >> > the test program attached below

handle_bad_irq and locking

Hi Thomas, I noticed that when you changed arm irq handling to use the generic implementation back in 2006 that you changed do_bad_IRQ() to the following: +#define do_bad_IRQ(irq,desc,regs) \ +do { \ + spin_lock(>lock);

handle_bad_irq and locking

Hi Thomas, I noticed that when you changed arm irq handling to use the generic implementation back in 2006 that you changed do_bad_IRQ() to the following: +#define do_bad_IRQ(irq,desc,regs) \ +do { \ + spin_lock(>lock);

Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode

On Tue, May 9, 2017 at 7:29 AM, Thomas Garnier wrote: > > On Tue, May 9, 2017 at 4:10 AM, Greg KH wrote: > > On Tue, May 09, 2017 at 08:56:19AM +0200, Ingo Molnar wrote: > >> > >> * Kees Cook wrote: > >> > >> > > There's the option of

Re: [kernel-hardening] Re: [PATCH v9 1/4] syscalls: Verify address limit before returning to user-mode

On Tue, May 9, 2017 at 7:29 AM, Thomas Garnier wrote: > > On Tue, May 9, 2017 at 4:10 AM, Greg KH wrote: > > On Tue, May 09, 2017 at 08:56:19AM +0200, Ingo Molnar wrote: > >> > >> * Kees Cook wrote: > >> > >> > > There's the option of using GCC plugins now that the infrastructure was > >> > >

Re: Threads stuck in zap_pid_ns_processes()

On Thu, May 11, 2017 at 04:25:23PM -0500, Eric W. Biederman wrote: > Guenter Roeck writes: > > > On Thu, May 11, 2017 at 12:31:21PM -0500, Eric W. Biederman wrote: > >> Guenter Roeck writes: > >> > >> > Hi all, > >> > > >> > the test program attached

Re: Threads stuck in zap_pid_ns_processes()

On Thu, May 11, 2017 at 04:25:23PM -0500, Eric W. Biederman wrote: > Guenter Roeck writes: > > > On Thu, May 11, 2017 at 12:31:21PM -0500, Eric W. Biederman wrote: > >> Guenter Roeck writes: > >> > >> > Hi all, > >> > > >> > the test program attached below almost always results in one of the

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