[PATCH] rcu: Fix up pending cbs check in rcu_prepare_for_idle

Pending cbs check in rcu_prepare_for_idle is inversed in the sense that, it should accelerate if there are pending cbs; but, the check does the opposite. So, fix it. Fixes: 15fecf89e46a ("srcu: Abstract multi-tail callback list handling") Signed-off-by: Neeraj Upadhyay

[PATCH] rcu: Fix up pending cbs check in rcu_prepare_for_idle

Pending cbs check in rcu_prepare_for_idle is inversed in the sense that, it should accelerate if there are pending cbs; but, the check does the opposite. So, fix it. Fixes: 15fecf89e46a ("srcu: Abstract multi-tail callback list handling") Signed-off-by: Neeraj Upadhyay ---

Re: [PATCH 1/5] mtip32xx: Delete an error message for a failed memory allocation in five functions

Hi Markus, [auto build test WARNING on linus/master] [also build test WARNING on v4.13-rc4 next-20170804] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 1/5] mtip32xx: Delete an error message for a failed memory allocation in five functions

Hi Markus, [auto build test WARNING on linus/master] [also build test WARNING on v4.13-rc4 next-20170804] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[v4 PATCH 1/2] powerpc/powernv: Save/Restore additional SPRs for stop4 cpuidle

From: "Gautham R. Shenoy" The stop4 idle state on POWER9 is a deep idle state which loses hypervisor resources, but whose latency is low enough that it can be exposed via cpuidle. Until now, the deep idle states which lose hypervisor resources (eg: winkle) were only

[v4 PATCH 1/2] powerpc/powernv: Save/Restore additional SPRs for stop4 cpuidle

From: "Gautham R. Shenoy" The stop4 idle state on POWER9 is a deep idle state which loses hypervisor resources, but whose latency is low enough that it can be exposed via cpuidle. Until now, the deep idle states which lose hypervisor resources (eg: winkle) were only exposed via CPU-Hotplug.

[v4 PATCH 0/2] powerpc/powernv: Enable stop4 via cpuidle

From: "Gautham R. Shenoy" Hi, This is the fourth iteration of the patchset to enable exploitation of stop4 idle state on POWER9 via cpuidle. The earlier version can be found here : [v3]: https://lkml.org/lkml/2017/7/21/209 [v2]: https://lkml.org/lkml/2017/7/19/152

[v4 PATCH 2/2] powerpc/powernv: Clear PECE1 in LPCR via stop-api only on Hotplug

From: "Gautham R. Shenoy" Currently we use the stop-api provided by the firmware to program the SLW engine to restore the values of hypervisor resources that get lost on deeper idle states (such as winkle). Since the deep states were only used for CPU-Hotplug on POWER8

[v4 PATCH 0/2] powerpc/powernv: Enable stop4 via cpuidle

From: "Gautham R. Shenoy" Hi, This is the fourth iteration of the patchset to enable exploitation of stop4 idle state on POWER9 via cpuidle. The earlier version can be found here : [v3]: https://lkml.org/lkml/2017/7/21/209 [v2]: https://lkml.org/lkml/2017/7/19/152 [v1]:

[v4 PATCH 2/2] powerpc/powernv: Clear PECE1 in LPCR via stop-api only on Hotplug

From: "Gautham R. Shenoy" Currently we use the stop-api provided by the firmware to program the SLW engine to restore the values of hypervisor resources that get lost on deeper idle states (such as winkle). Since the deep states were only used for CPU-Hotplug on POWER8 systems, we would program

[PATCH -mm -v4 5/5] mm, swap: Don't use VMA based swap readahead if HDD is used as swap

From: Huang Ying VMA based swap readahead will readahead the virtual pages that is continuous in the virtual address space. While the original swap readahead will readahead the swap slots that is continuous in the swap device. Although VMA based swap readahead is more

[PATCH -mm -v4 5/5] mm, swap: Don't use VMA based swap readahead if HDD is used as swap

From: Huang Ying VMA based swap readahead will readahead the virtual pages that is continuous in the virtual address space. While the original swap readahead will readahead the swap slots that is continuous in the swap device. Although VMA based swap readahead is more correct for the swap

[PATCH -mm -v4 4/5] mm, swap: Add sysfs interface for VMA based swap readahead

From: Huang Ying The sysfs interface to control the VMA based swap readahead is added as follow, /sys/kernel/mm/swap/vma_ra_enabled Enable the VMA based swap readahead algorithm, or use the original global swap readahead algorithm. /sys/kernel/mm/swap/vma_ra_max_order

[PATCH -mm -v4 1/5] mm, swap: Add swap readahead hit statistics

From: Huang Ying The statistics for total readahead pages and total readahead hits are recorded and exported via the following sysfs interface. /sys/kernel/mm/swap/ra_hits /sys/kernel/mm/swap/ra_total With them, the efficiency of the swap readahead could be measured, so

[PATCH -mm -v4 3/5] mm, swap: VMA based swap readahead

From: Huang Ying The swap readahead is an important mechanism to reduce the swap in latency. Although pure sequential memory access pattern isn't very popular for anonymous memory, the space locality is still considered valid. In the original swap readahead

[PATCH -mm -v4 4/5] mm, swap: Add sysfs interface for VMA based swap readahead

From: Huang Ying The sysfs interface to control the VMA based swap readahead is added as follow, /sys/kernel/mm/swap/vma_ra_enabled Enable the VMA based swap readahead algorithm, or use the original global swap readahead algorithm. /sys/kernel/mm/swap/vma_ra_max_order Set the max order of

[PATCH -mm -v4 1/5] mm, swap: Add swap readahead hit statistics

From: Huang Ying The statistics for total readahead pages and total readahead hits are recorded and exported via the following sysfs interface. /sys/kernel/mm/swap/ra_hits /sys/kernel/mm/swap/ra_total With them, the efficiency of the swap readahead could be measured, so that the swap readahead

[PATCH -mm -v4 3/5] mm, swap: VMA based swap readahead

From: Huang Ying The swap readahead is an important mechanism to reduce the swap in latency. Although pure sequential memory access pattern isn't very popular for anonymous memory, the space locality is still considered valid. In the original swap readahead implementation, the consecutive

[PATCH -mm -v4 2/5] mm, swap: Fix swap readahead marking

From: Huang Ying In the original implementation, it is possible that the existing pages in the swap cache (not newly readahead) could be marked as the readahead pages. This will cause the statistics of swap readahead be wrong and influence the swap readahead algorithm too.

[PATCH -mm -v4 2/5] mm, swap: Fix swap readahead marking

From: Huang Ying In the original implementation, it is possible that the existing pages in the swap cache (not newly readahead) could be marked as the readahead pages. This will cause the statistics of swap readahead be wrong and influence the swap readahead algorithm too. This is fixed via

[PATCH -mm -v4 0/5] mm, swap: VMA based swap readahead

The swap readahead is an important mechanism to reduce the swap in latency. Although pure sequential memory access pattern isn't very popular for anonymous memory, the space locality is still considered valid. In the original swap readahead implementation, the consecutive blocks in swap device

[PATCH -mm -v4 0/5] mm, swap: VMA based swap readahead

The swap readahead is an important mechanism to reduce the swap in latency. Although pure sequential memory access pattern isn't very popular for anonymous memory, the space locality is still considered valid. In the original swap readahead implementation, the consecutive blocks in swap device

[PATCH] ASoC: mediatek: Fix an error checking code

Check the value returned by 'devm_clk_get()' instead of the clock identifier which can never be an ERR code. Fixes: d6f3710a56e1 ("ASoC: mediatek: add structure define and clock control for 2701") Signed-off-by: Christophe JAILLET ---

[PATCH] ASoC: mediatek: Fix an error checking code

Check the value returned by 'devm_clk_get()' instead of the clock identifier which can never be an ERR code. Fixes: d6f3710a56e1 ("ASoC: mediatek: add structure define and clock control for 2701") Signed-off-by: Christophe JAILLET --- sound/soc/mediatek/mt2701/mt2701-afe-clock-ctrl.c | 2 +- 1

Re: [PATCH] Allow automatic kernel taint on unsigned module load to be disabled

On Sun, Aug 6, 2017 at 9:47 PM, Rusty Russell wrote: > Matthew Garrett writes: >> And then you need an entire trusted userland, at which point you can >> assert that the modules are trustworthy without having to validate >> them so you don't need

Re: [PATCH] Allow automatic kernel taint on unsigned module load to be disabled

On Sun, Aug 6, 2017 at 9:47 PM, Rusty Russell wrote: > Matthew Garrett writes: >> And then you need an entire trusted userland, at which point you can >> assert that the modules are trustworthy without having to validate >> them so you don't need CONFIG_MODULE_SIG anyway. > > Yep. But your

Re: [PATCH] devfreq: replace sscanf with kstrtol

Hi, On 2017년 08월 07일 13:47, gsant...@codeaurora.org wrote: > On 2017-08-04 20:42, Chanwoo Choi wrote: >> Hi, >> >> On Fri, Aug 4, 2017 at 12:57 PM, wrote: >>> Hi, >>> >>> Adding error checks to devfreq userspace governor, the current >>> implementation results in

Re: [PATCH] devfreq: replace sscanf with kstrtol

Hi, On 2017년 08월 07일 13:47, gsant...@codeaurora.org wrote: > On 2017-08-04 20:42, Chanwoo Choi wrote: >> Hi, >> >> On Fri, Aug 4, 2017 at 12:57 PM, wrote: >>> Hi, >>> >>> Adding error checks to devfreq userspace governor, the current >>> implementation results in setting wrong >>> frequency

Re: [v3 PATCH 1/2] powernv/powerpc:Save/Restore additional SPRs for stop4 cpuidle

Hi Michael, On Tue, Aug 01, 2017 at 08:56:18PM +1000, Michael Ellerman wrote: > "Gautham R. Shenoy" writes: > > > > Subject: [v3 PATCH 1/2] powernv/powerpc:Save/Restore additional SPRs for > > stop4 cpuidle > > I know it's not a big deal, but can we agree on the

Re: [v3 PATCH 1/2] powernv/powerpc:Save/Restore additional SPRs for stop4 cpuidle

Hi Michael, On Tue, Aug 01, 2017 at 08:56:18PM +1000, Michael Ellerman wrote: > "Gautham R. Shenoy" writes: > > > > Subject: [v3 PATCH 1/2] powernv/powerpc:Save/Restore additional SPRs for > > stop4 cpuidle > > I know it's not a big deal, but can we agree on the subject format? > >

Re: [PATCH 2/2] Save current timestamp part of dmesg while writing oops message to pstore

Hi Kees, On Tuesday 23 May 2017 02:19 PM, Ankit Kumar wrote: Hi Kees, On Tuesday 23 May 2017 05:21 AM, Kees Cook wrote: On Mon, May 22, 2017 at 3:20 AM, Ankit Kumar wrote: Currently on panic or Oops, kernel saves the last few bytes from dmesg buffer to nvram.

Re: [PATCH 2/2] Save current timestamp part of dmesg while writing oops message to pstore

Hi Kees, On Tuesday 23 May 2017 02:19 PM, Ankit Kumar wrote: Hi Kees, On Tuesday 23 May 2017 05:21 AM, Kees Cook wrote: On Mon, May 22, 2017 at 3:20 AM, Ankit Kumar wrote: Currently on panic or Oops, kernel saves the last few bytes from dmesg buffer to nvram. Usually kdump does capture

[PATCHv2] arm64:kexec: have own crash_smp_send_stop() for crash dump for nonpanic cores

Commit 0ee5941 : (x86/panic: replace smp_send_stop() with kdump friendly version in panic path) introduced crash_smp_send_stop() which is a weak function and can be overriden by architecture codes to fix the side effect caused by commit f06e515 : (kernel/panic.c: add "crash_kexec_post_ notifiers"

[PATCHv2] arm64:kexec: have own crash_smp_send_stop() for crash dump for nonpanic cores

Commit 0ee5941 : (x86/panic: replace smp_send_stop() with kdump friendly version in panic path) introduced crash_smp_send_stop() which is a weak function and can be overriden by architecture codes to fix the side effect caused by commit f06e515 : (kernel/panic.c: add "crash_kexec_post_ notifiers"

[PATCH] perf report: calculate the average cycles of iterations

The branch history code has a loop detection function. With this, we can get the number of iterations by calculating the removed loops. While it would be nice for knowing the average cycles of iterations. This patch adds up the cycles in branch entries of removed loops and save the result to the

[PATCH] perf report: calculate the average cycles of iterations

The branch history code has a loop detection function. With this, we can get the number of iterations by calculating the removed loops. While it would be nice for knowing the average cycles of iterations. This patch adds up the cycles in branch entries of removed loops and save the result to the

Re: [PATCH] osq_lock: fix osq_lock queue corruption

On 07/31/2017 10:54 PM, Prateek Sood wrote: > Fix ordering of link creation between node->prev and prev->next in > osq_lock(). A case in which the status of optimistic spin queue is > CPU6->CPU2 in which CPU6 has acquired the lock. > > tail > v > ,-. <- ,-. > |6||2| >

Re: [PATCH] osq_lock: fix osq_lock queue corruption

On 07/31/2017 10:54 PM, Prateek Sood wrote: > Fix ordering of link creation between node->prev and prev->next in > osq_lock(). A case in which the status of optimistic spin queue is > CPU6->CPU2 in which CPU6 has acquired the lock. > > tail > v > ,-. <- ,-. > |6||2| >

[PATCH] i2c: imx: Remove a useless test in 'i2c_imx_init_recovery_info()'

'devm_pinctrl_get()' never returns NULL, so this test can be simplified. Signed-off-by: Christophe JAILLET --- drivers/i2c/busses/i2c-imx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/i2c/busses/i2c-imx.c

[PATCH] i2c: imx: Remove a useless test in 'i2c_imx_init_recovery_info()'

'devm_pinctrl_get()' never returns NULL, so this test can be simplified. Signed-off-by: Christophe JAILLET --- drivers/i2c/busses/i2c-imx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/i2c/busses/i2c-imx.c b/drivers/i2c/busses/i2c-imx.c index

[PATCH v2] rtlwifi: constify rate_control_ops structure

rate_control_ops structure is only passed as an argument to the function ieee80211_rate_control_{register/unregister}. This argument is of type const, so declare the structure as const. Signed-off-by: Bhumika Goyal --- Changes in v2: * Change subject line.

[PATCH v2] rtlwifi: constify rate_control_ops structure

rate_control_ops structure is only passed as an argument to the function ieee80211_rate_control_{register/unregister}. This argument is of type const, so declare the structure as const. Signed-off-by: Bhumika Goyal --- Changes in v2: * Change subject line.

Re: linux-next: manual merge of the net-next tree with the net tree

Hi Neal, On Sun, 6 Aug 2017 22:21:43 -0400 Neal Cardwell wrote: > > > I fixed it up (see below) and can carry the fix as necessary. This > > is now fixed as far as linux-next is concerned, but any non trivial > > conflicts should be mentioned to your upstream maintainer

Re: linux-next: manual merge of the net-next tree with the net tree

Hi Neal, On Sun, 6 Aug 2017 22:21:43 -0400 Neal Cardwell wrote: > > > I fixed it up (see below) and can carry the fix as necessary. This > > is now fixed as far as linux-next is concerned, but any non trivial > > conflicts should be mentioned to your upstream maintainer when your tree > > is

Re: [PATCH] devfreq: replace sscanf with kstrtol

On 2017-08-04 20:42, Chanwoo Choi wrote: Hi, On Fri, Aug 4, 2017 at 12:57 PM, wrote: Hi, Adding error checks to devfreq userspace governor, the current implementation results in setting wrong frequency when sscanf returns error. From

Re: [PATCH] devfreq: replace sscanf with kstrtol

On 2017-08-04 20:42, Chanwoo Choi wrote: Hi, On Fri, Aug 4, 2017 at 12:57 PM, wrote: Hi, Adding error checks to devfreq userspace governor, the current implementation results in setting wrong frequency when sscanf returns error. From 12e0a347addd70529b2c378299b27b65f0766f99 Mon Sep 17

Re: [PATCH] Allow automatic kernel taint on unsigned module load to be disabled

Matthew Garrett writes: > On Sun, Aug 6, 2017 at 7:49 PM, Rusty Russell wrote: >> Matthew Garrett writes: >>> Binary modules will still be tainted by the license checker. The issue >>> is that if you want to enforce module signatures

Re: [PATCH] Allow automatic kernel taint on unsigned module load to be disabled

Matthew Garrett writes: > On Sun, Aug 6, 2017 at 7:49 PM, Rusty Russell wrote: >> Matthew Garrett writes: >>> Binary modules will still be tainted by the license checker. The issue >>> is that if you want to enforce module signatures under *some* >>> circumstances, you need to build with

Re: Suspend-resume failure on Intel Eagle Lake Core2Duo

Hi Marc, 2017-08-03 22:30 GMT+09:00 Marc Zyngier : > On 03/08/17 13:52, Masahiro Yamada wrote: >> Hi Marc, >> >> 2017-08-03 17:41 GMT+09:00 Marc Zyngier : >>> Hi Masahiro, >>> >>> On 03/08/17 08:32, Masahiro Yamada wrote: Hi. 2017-08-01

Re: Suspend-resume failure on Intel Eagle Lake Core2Duo

Hi Marc, 2017-08-03 22:30 GMT+09:00 Marc Zyngier : > On 03/08/17 13:52, Masahiro Yamada wrote: >> Hi Marc, >> >> 2017-08-03 17:41 GMT+09:00 Marc Zyngier : >>> Hi Masahiro, >>> >>> On 03/08/17 08:32, Masahiro Yamada wrote: Hi. 2017-08-01 0:55 GMT+09:00 Thomas Gleixner : > On

Re: [PATCH net-next] net: dsa: User per-cpu 64-bit statistics

From: Florian Fainelli Date: Thu, 3 Aug 2017 21:33:27 -0700 > During testing with a background iperf pushing 1Gbit/sec worth of > traffic and having both ifconfig and ethtool collect statistics, we > could see quite frequent deadlocks. Convert the often accessed DSA slave

Re: [PATCH net-next] net: dsa: User per-cpu 64-bit statistics

From: Florian Fainelli Date: Thu, 3 Aug 2017 21:33:27 -0700 > During testing with a background iperf pushing 1Gbit/sec worth of > traffic and having both ifconfig and ethtool collect statistics, we > could see quite frequent deadlocks. Convert the often accessed DSA slave > network devices

Re: [PATCH v9 0/4] Add new PCI_DEV_FLAGS_NO_RELAXED_ORDERING flag

On 2017/8/7 11:47, David Miller wrote: > From: Ding Tianhong > Date: Sat, 5 Aug 2017 15:15:09 +0800 > >> Some devices have problems with Transaction Layer Packets with the Relaxed >> Ordering Attribute set. This patch set adds a new PCIe Device Flag, >>

Re: [PATCH v9 0/4] Add new PCI_DEV_FLAGS_NO_RELAXED_ORDERING flag

On 2017/8/7 11:47, David Miller wrote: > From: Ding Tianhong > Date: Sat, 5 Aug 2017 15:15:09 +0800 > >> Some devices have problems with Transaction Layer Packets with the Relaxed >> Ordering Attribute set. This patch set adds a new PCIe Device Flag, >> PCI_DEV_FLAGS_NO_RELAXED_ORDERING, a

Re: [PATCH v2] drm: dw-hdmi-i2s: add missing company name on Copyright

On 08/07/2017 09:39 AM, Kuninori Morimoto wrote: From: Kuninori Morimoto This driver's Copyright is under Renesas Solutions Corp. This patch updates the year, because this driver was moved into synopsys folder in 2017. Thanks. Queued to drm-misc-next.

Re: [PATCH v2] drm: dw-hdmi-i2s: add missing company name on Copyright

On 08/07/2017 09:39 AM, Kuninori Morimoto wrote: From: Kuninori Morimoto This driver's Copyright is under Renesas Solutions Corp. This patch updates the year, because this driver was moved into synopsys folder in 2017. Thanks. Queued to drm-misc-next. Archit Signed-off-by: Kuninori

[PATCH v2] drm: dw-hdmi-i2s: add missing company name on Copyright

From: Kuninori Morimoto This driver's Copyright is under Renesas Solutions Corp. This patch updates the year, because this driver was moved into synopsys folder in 2017. Signed-off-by: Kuninori Morimoto --- v1 -> v2 -

[PATCH v2] drm: dw-hdmi-i2s: add missing company name on Copyright

From: Kuninori Morimoto This driver's Copyright is under Renesas Solutions Corp. This patch updates the year, because this driver was moved into synopsys folder in 2017. Signed-off-by: Kuninori Morimoto --- v1 -> v2 - update year 2016 -> 2017

Re: [PATCH][resend] drm: dw-hdmi-i2s: add missing company name on Copyright

Hi Archit > >> On 08/07/2017 07:41 AM, Kuninori Morimoto wrote: > >>> > >>> From: Kuninori Morimoto > >>> > >>> This driver's Copyright is under Renesas Solutions Corp > >> > >> Can we update the year to 2017 while we're at it? > > > > The original patch was

Re: [PATCH 2/5] edac: synopsys: Add EDAC ECC support for ZynqMP DDRC

On Fri, Aug 04, 2017 at 02:00:24PM +0200, Michal Simek wrote: > From: Naga Sureshkumar Relli > > This patch adds EDAC ECC support for ZynqMP DDRC IP > > Signed-off-by: Naga Sureshkumar Relli > Signed-off-by: Michal Simek

Re: [PATCH][resend] drm: dw-hdmi-i2s: add missing company name on Copyright

Hi Archit > >> On 08/07/2017 07:41 AM, Kuninori Morimoto wrote: > >>> > >>> From: Kuninori Morimoto > >>> > >>> This driver's Copyright is under Renesas Solutions Corp > >> > >> Can we update the year to 2017 while we're at it? > > > > The original patch was created and applied on 2016 > > > >

Re: [PATCH 2/5] edac: synopsys: Add EDAC ECC support for ZynqMP DDRC

On Fri, Aug 04, 2017 at 02:00:24PM +0200, Michal Simek wrote: > From: Naga Sureshkumar Relli > > This patch adds EDAC ECC support for ZynqMP DDRC IP > > Signed-off-by: Naga Sureshkumar Relli > Signed-off-by: Michal Simek > --- > > drivers/edac/Kconfig | 2 +- >

Re: [PATCH v4 net-next 02/13] nfp: change bpf verifier hooks to match new verifier data structures

From: Edward Cree Date: Thu, 3 Aug 2017 17:11:34 +0100 > Signed-off-by: Edward Cree Sorry, this doesn't work. The entire source tree must compile properly after each patch in the patch series. So if you change a datastructure, you have to update

Re: [PATCH v4 net-next 02/13] nfp: change bpf verifier hooks to match new verifier data structures

From: Edward Cree Date: Thu, 3 Aug 2017 17:11:34 +0100 > Signed-off-by: Edward Cree Sorry, this doesn't work. The entire source tree must compile properly after each patch in the patch series. So if you change a datastructure, you have to update all of the users in that patch to keep

[regression] tty console panic for 4.13-rcx

Hi, I saw the log at the bottom and bisect the issue to the commits of 065ea0a7afd64d6c ("tty: improve tty_insert_flip_char() slow path") 979990c628481461 ("tty: improve tty_insert_flip_char() fast path") I nearly could 100% reproduce this. Any thought? [ 154.823106] Unable to handle

[regression] tty console panic for 4.13-rcx

Hi, I saw the log at the bottom and bisect the issue to the commits of 065ea0a7afd64d6c ("tty: improve tty_insert_flip_char() slow path") 979990c628481461 ("tty: improve tty_insert_flip_char() fast path") I nearly could 100% reproduce this. Any thought? [ 154.823106] Unable to handle

Re: [PATCH][resend] drm: dw-hdmi-i2s: add missing company name on Copyright

On 08/07/2017 09:25 AM, Kuninori Morimoto wrote: Hi Archit Thank you for your feedback On 08/07/2017 07:41 AM, Kuninori Morimoto wrote: From: Kuninori Morimoto This driver's Copyright is under Renesas Solutions Corp Can we update the year to 2017

Re: [PATCH][resend] drm: dw-hdmi-i2s: add missing company name on Copyright

On 08/07/2017 09:25 AM, Kuninori Morimoto wrote: Hi Archit Thank you for your feedback On 08/07/2017 07:41 AM, Kuninori Morimoto wrote: From: Kuninori Morimoto This driver's Copyright is under Renesas Solutions Corp Can we update the year to 2017 while we're at it? The original

Re: [PATCH][resend] drm: dw-hdmi-i2s: add missing company name on Copyright

Hi Archit Thank you for your feedback > On 08/07/2017 07:41 AM, Kuninori Morimoto wrote: > > > > From: Kuninori Morimoto > > > > This driver's Copyright is under Renesas Solutions Corp > > Can we update the year to 2017 while we're at it? The original patch

Re: [PATCH][resend] drm: dw-hdmi-i2s: add missing company name on Copyright

Hi Archit Thank you for your feedback > On 08/07/2017 07:41 AM, Kuninori Morimoto wrote: > > > > From: Kuninori Morimoto > > > > This driver's Copyright is under Renesas Solutions Corp > > Can we update the year to 2017 while we're at it? The original patch was created and applied on 2016

Re: [PATCH] intel-vbtn: match power button on press rather than release

On Mon, Aug 07, 2017 at 08:59:30AM +0800, AceLan Kao wrote: > Looks like I'm one hour late to ack the patch. > Thanks any way for the quick response. Thanks for chiming in all the same - and normally I'd have provided for more time. In this case, I will be away for a few days, and it was

Re: [PATCH] intel-vbtn: match power button on press rather than release

On Mon, Aug 07, 2017 at 08:59:30AM +0800, AceLan Kao wrote: > Looks like I'm one hour late to ack the patch. > Thanks any way for the quick response. Thanks for chiming in all the same - and normally I'd have provided for more time. In this case, I will be away for a few days, and it was

[PATCH v6 0/2] Make find_later_rq() choose a closer cpu in topology

When cpudl_find() returns any among free_cpus, the cpu might not be closer than others, considering sched domain. For example: this_cpu: 15 free_cpus: 0, 1,..., 14 (== later_mask) best_cpu: 0 topology: 0 --+ +--+ 1 --+ | +-- ... --+ 2 --+ | |

[PATCH v6 0/2] Make find_later_rq() choose a closer cpu in topology

When cpudl_find() returns any among free_cpus, the cpu might not be closer than others, considering sched domain. For example: this_cpu: 15 free_cpus: 0, 1,..., 14 (== later_mask) best_cpu: 0 topology: 0 --+ +--+ 1 --+ | +-- ... --+ 2 --+ | |

[PATCH v6 2/2] sched/rt: Add support for SD_PREFER_SIBLING on find_lowest_rq()

It would be better to avoid pushing tasks to other cpu within a SD_PREFER_SIBLING domain, instead, get more chances to check other siblings. Signed-off-by: Byungchul Park --- kernel/sched/rt.c | 47 --- 1 file changed, 44

[PATCH v6 1/2] sched/deadline: Add support for SD_PREFER_SIBLING on find_later_rq()

It would be better to avoid pushing tasks to other cpu within a SD_PREFER_SIBLING domain, instead, get more chances to check other siblings. Signed-off-by: Byungchul Park --- kernel/sched/deadline.c | 46 +++--- 1 file changed, 43

[PATCH v6 1/2] sched/deadline: Add support for SD_PREFER_SIBLING on find_later_rq()

It would be better to avoid pushing tasks to other cpu within a SD_PREFER_SIBLING domain, instead, get more chances to check other siblings. Signed-off-by: Byungchul Park --- kernel/sched/deadline.c | 46 +++--- 1 file changed, 43 insertions(+), 3

[PATCH v6 2/2] sched/rt: Add support for SD_PREFER_SIBLING on find_lowest_rq()

It would be better to avoid pushing tasks to other cpu within a SD_PREFER_SIBLING domain, instead, get more chances to check other siblings. Signed-off-by: Byungchul Park --- kernel/sched/rt.c | 47 --- 1 file changed, 44 insertions(+), 3 deletions(-)

Re: [RFC Part1 PATCH v3 12/17] x86/mm: DMA support for SEV memory encryption

On Mon, Jul 24, 2017 at 02:07:52PM -0500, Brijesh Singh wrote: > From: Tom Lendacky > > DMA access to memory mapped as encrypted while SEV is active can not be > encrypted during device write or decrypted during device read. Yeah, definitely rewrite that sentence. > In

Re: [RFC Part1 PATCH v3 12/17] x86/mm: DMA support for SEV memory encryption

On Mon, Jul 24, 2017 at 02:07:52PM -0500, Brijesh Singh wrote: > From: Tom Lendacky > > DMA access to memory mapped as encrypted while SEV is active can not be > encrypted during device write or decrypted during device read. Yeah, definitely rewrite that sentence. > In order > for DMA to

Re: [PATCH v9 0/4] Add new PCI_DEV_FLAGS_NO_RELAXED_ORDERING flag

From: Ding Tianhong Date: Sat, 5 Aug 2017 15:15:09 +0800 > Some devices have problems with Transaction Layer Packets with the Relaxed > Ordering Attribute set. This patch set adds a new PCIe Device Flag, > PCI_DEV_FLAGS_NO_RELAXED_ORDERING, a set of PCI Quirks to catch

Re: [PATCH v9 0/4] Add new PCI_DEV_FLAGS_NO_RELAXED_ORDERING flag

From: Ding Tianhong Date: Sat, 5 Aug 2017 15:15:09 +0800 > Some devices have problems with Transaction Layer Packets with the Relaxed > Ordering Attribute set. This patch set adds a new PCIe Device Flag, > PCI_DEV_FLAGS_NO_RELAXED_ORDERING, a set of PCI Quirks to catch some known > devices with

Re: [PATCH v2 4/5] PCI: mediatek: Add new generation controller support

On Sat, 2017-08-05 at 14:16 +0800, Ryder Lee wrote: > On Sat, 2017-08-05 at 12:52 +0800, Ryder Lee wrote: > > Hi Honghui, Bjorn, > > > > On Fri, 2017-08-04 at 08:18 -0500, Bjorn Helgaas wrote: > > > On Fri, Aug 04, 2017 at 04:39:36PM +0800, Honghui Zhang wrote: > > > > On Thu, 2017-08-03 at 17:42

Re: [PATCH v2 4/5] PCI: mediatek: Add new generation controller support

On Sat, 2017-08-05 at 14:16 +0800, Ryder Lee wrote: > On Sat, 2017-08-05 at 12:52 +0800, Ryder Lee wrote: > > Hi Honghui, Bjorn, > > > > On Fri, 2017-08-04 at 08:18 -0500, Bjorn Helgaas wrote: > > > On Fri, Aug 04, 2017 at 04:39:36PM +0800, Honghui Zhang wrote: > > > > On Thu, 2017-08-03 at 17:42

Re: [PATCH][resend] drm: dw-hdmi-i2s: add missing company name on Copyright

On 08/07/2017 07:41 AM, Kuninori Morimoto wrote: From: Kuninori Morimoto This driver's Copyright is under Renesas Solutions Corp Can we update the year to 2017 while we're at it? Archit Signed-off-by: Kuninori Morimoto

Re: [PATCH][resend] drm: dw-hdmi-i2s: add missing company name on Copyright

On 08/07/2017 07:41 AM, Kuninori Morimoto wrote: From: Kuninori Morimoto This driver's Copyright is under Renesas Solutions Corp Can we update the year to 2017 while we're at it? Archit Signed-off-by: Kuninori Morimoto --- drivers/gpu/drm/bridge/synopsys/dw-hdmi-i2s-audio.c | 3 ++-

Re: [PATCH] cpufreq: Simplify cpufreq_can_do_remote_dvfs()

On 04-08-17, 14:57, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > The if () in cpufreq_can_do_remote_dvfs() is superfluous, so drop > it and simply return the value of the expression under it. > > Signed-off-by: Rafael J. Wysocki

Re: [PATCH] cpufreq: Simplify cpufreq_can_do_remote_dvfs()

On 04-08-17, 14:57, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > The if () in cpufreq_can_do_remote_dvfs() is superfluous, so drop > it and simply return the value of the expression under it. > > Signed-off-by: Rafael J. Wysocki > --- > > On top of the current linux-next. > > --- >

Re: [PATCH V3] get_maintainer: Prepare for separate MAINTAINERS files

On Sun, 2017-08-06 at 19:16 -0700, Frank Rowand wrote: > On 08/04/17 21:45, Joe Perches wrote: > > Allow for MAINTAINERS to become a directory and if it is, > > read all the files in the directory for maintained sections. > > > > Optionally look for all files named MAINTAINERS in directories > >

Re: [PATCH V3] get_maintainer: Prepare for separate MAINTAINERS files

On Sun, 2017-08-06 at 19:16 -0700, Frank Rowand wrote: > On 08/04/17 21:45, Joe Perches wrote: > > Allow for MAINTAINERS to become a directory and if it is, > > read all the files in the directory for maintained sections. > > > > Optionally look for all files named MAINTAINERS in directories > >

[PATCH v10 2/4] irqchip/qeic: merge qeic init code from platforms to a common function

The codes of qe_ic init from a variety of platforms are redundant, merge them to a common function and put it to irqchip/irq-qeic.c For non-p1021_mds mpc85xx_mds boards, use "qe_ic_init(np, 0, qe_ic_cascade_low_mpic, qe_ic_cascade_high_mpic);" instead of "qe_ic_init(np, 0,

[PATCH v10 2/4] irqchip/qeic: merge qeic init code from platforms to a common function

The codes of qe_ic init from a variety of platforms are redundant, merge them to a common function and put it to irqchip/irq-qeic.c For non-p1021_mds mpc85xx_mds boards, use "qe_ic_init(np, 0, qe_ic_cascade_low_mpic, qe_ic_cascade_high_mpic);" instead of "qe_ic_init(np, 0,

[PATCH v10 4/4] irqchip/qeic: remove PPCisms for QEIC

QEIC was supported on PowerPC, and dependent on PPC, Now it is supported on other platforms, so remove PPCisms. Signed-off-by: Zhao Qiang --- arch/powerpc/platforms/83xx/km83xx.c | 1 - arch/powerpc/platforms/83xx/misc.c| 1 -

[PATCH v10 1/4] irqchip/qeic: move qeic driver from drivers/soc/fsl/qe

move the driver from drivers/soc/fsl/qe to drivers/irqchip, merge qe_ic.h and qe_ic.c into irq-qeic.c. Signed-off-by: Zhao Qiang --- MAINTAINERS| 6 ++ drivers/irqchip/Makefile | 1 +

[PATCH v10 4/4] irqchip/qeic: remove PPCisms for QEIC

QEIC was supported on PowerPC, and dependent on PPC, Now it is supported on other platforms, so remove PPCisms. Signed-off-by: Zhao Qiang --- arch/powerpc/platforms/83xx/km83xx.c | 1 - arch/powerpc/platforms/83xx/misc.c| 1 - arch/powerpc/platforms/83xx/mpc832x_mds.c

[PATCH v10 1/4] irqchip/qeic: move qeic driver from drivers/soc/fsl/qe

move the driver from drivers/soc/fsl/qe to drivers/irqchip, merge qe_ic.h and qe_ic.c into irq-qeic.c. Signed-off-by: Zhao Qiang --- MAINTAINERS| 6 ++ drivers/irqchip/Makefile | 1 + drivers/{soc/fsl/qe/qe_ic.c =>

[PATCH v10 3/4] irqchip/qeic: merge qeic_of_init into qe_ic_init

qeic_of_init just get device_node of qeic from dtb and call qe_ic_init, pass the device_node to qe_ic_init. So merge qeic_of_init into qe_ic_init to get the qeic node in qe_ic_init. Signed-off-by: Zhao Qiang --- drivers/irqchip/irq-qeic.c | 90

[PATCH v10 3/4] irqchip/qeic: merge qeic_of_init into qe_ic_init

qeic_of_init just get device_node of qeic from dtb and call qe_ic_init, pass the device_node to qe_ic_init. So merge qeic_of_init into qe_ic_init to get the qeic node in qe_ic_init. Signed-off-by: Zhao Qiang --- drivers/irqchip/irq-qeic.c | 90 --

[PATCH v10 0/4] this patchset is to remove PPCisms for QEIC

QEIC is supported more than just powerpc boards, so remove PPCisms. changelog: Changes for v8: - use IRQCHIP_DECLARE() instead of subsys_initcall in qeic driver - remove include/soc/fsl/qe/qe_ic.h Changes for v9: - rebase - fix the compile issue

[PATCH v10 0/4] this patchset is to remove PPCisms for QEIC

QEIC is supported more than just powerpc boards, so remove PPCisms. changelog: Changes for v8: - use IRQCHIP_DECLARE() instead of subsys_initcall in qeic driver - remove include/soc/fsl/qe/qe_ic.h Changes for v9: - rebase - fix the compile issue

  1   2   3   4   5   6   7   8   >