[PATCH 2/2] vhost: forbid IOTLB invalidation when not enabled

When IOTLB is not enabled, we should forbid IOTLB invalidation to avoid a NULL pointer dereference. Signed-off-by: Jason Wang --- drivers/vhost/vhost.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c index

[PATCH 2/2] vhost: forbid IOTLB invalidation when not enabled

When IOTLB is not enabled, we should forbid IOTLB invalidation to avoid a NULL pointer dereference. Signed-off-by: Jason Wang --- drivers/vhost/vhost.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c index c6f2d89..7d338d5 100644 ---

Bug in fs/gs_base PTRACE_SETREGS on pre-4.7 kernels

Hi Andy (), this is more of a heads up than a bug report, since it turns out you already fixed this in 731e33e: x86/arch_prctl/64: Remove FSBASE/GSBASE < 4G optimization In any case, without that commit, trying to use PTRACE_SETREGS to set either fs_base, or gs_base to 0 when it was previously

Bug in fs/gs_base PTRACE_SETREGS on pre-4.7 kernels

Hi Andy (), this is more of a heads up than a bug report, since it turns out you already fixed this in 731e33e: x86/arch_prctl/64: Remove FSBASE/GSBASE < 4G optimization In any case, without that commit, trying to use PTRACE_SETREGS to set either fs_base, or gs_base to 0 when it was previously

[PATCH 1/2] vhost: remove unused feature bit

Signed-off-by: Jason Wang --- include/uapi/linux/vhost.h | 2 -- 1 file changed, 2 deletions(-) diff --git a/include/uapi/linux/vhost.h b/include/uapi/linux/vhost.h index 56b7ab5..60180c0 100644 --- a/include/uapi/linux/vhost.h +++ b/include/uapi/linux/vhost.h @@ -172,8

[PATCH 1/2] vhost: remove unused feature bit

Signed-off-by: Jason Wang --- include/uapi/linux/vhost.h | 2 -- 1 file changed, 2 deletions(-) diff --git a/include/uapi/linux/vhost.h b/include/uapi/linux/vhost.h index 56b7ab5..60180c0 100644 --- a/include/uapi/linux/vhost.h +++ b/include/uapi/linux/vhost.h @@ -172,8 +172,6 @@ struct

Re: [PATCH v2] ARM: Drop fixed 200 Hz timer requirement from Samsung platforms

2016. 11. 18. 16:16 Krzysztof Kozlowski wrote: > All Samsung platforms, including the Exynos, are selecting HZ_FIXED with > 200 Hz. Unfortunately in case of multiplatform image this affects also > other platforms when Exynos is enabled. > > This looks like an very old legacy

Re: [PATCH v2] ARM: Drop fixed 200 Hz timer requirement from Samsung platforms

2016. 11. 18. 16:16 Krzysztof Kozlowski wrote: > All Samsung platforms, including the Exynos, are selecting HZ_FIXED with > 200 Hz. Unfortunately in case of multiplatform image this affects also > other platforms when Exynos is enabled. > > This looks like an very old legacy code, dating back

RE: [PATCH net 1/2] r8152: fix the sw rx checksum is unavailable

Mark Lord [mailto:ml...@pobox.com] > Sent: Thursday, November 17, 2016 9:42 PM [...] > What the above sample shows, is the URB transfer buffer ran out of space in > the > middle > of a packet, and the hardware then tried to just continue that same packet in > the > next URB, > without an rx_desc

RE: [PATCH net 1/2] r8152: fix the sw rx checksum is unavailable

Mark Lord [mailto:ml...@pobox.com] > Sent: Thursday, November 17, 2016 9:42 PM [...] > What the above sample shows, is the URB transfer buffer ran out of space in > the > middle > of a packet, and the hardware then tried to just continue that same packet in > the > next URB, > without an rx_desc

Re: [GIT PULL] STi DT update for v4.10 round 2

On Thu, Nov 10, 2016 at 10:00:48AM +0100, Patrice Chotard wrote: > Hi Arnd, Kevin, Olof > > PLease consider this second round of STi dts update for v4.10 : > > The following changes since commit 97a0b97f9e8197429eee5f87ce14373f73dbd9d3: > > ARM: dts: stih410-clocks: Add PROC_STFE as a

Re: [GIT PULL] STi defconfig updates for v4.10 round 2

On Thu, Nov 10, 2016 at 10:00:32AM +0100, Patrice Chotard wrote: > Hi Olof, Arnd and Kevin, > > Please consider the second round of multi_v7_defconfig updates for v4.10 : > > > The following changes since commit 620c52f4db4d47e1f33c64e641392fe575d5397f: > > ARM: multi_v7_defconfig: Remove

Re: [GIT PULL] STi DT update for v4.10 round 2

On Thu, Nov 10, 2016 at 10:00:48AM +0100, Patrice Chotard wrote: > Hi Arnd, Kevin, Olof > > PLease consider this second round of STi dts update for v4.10 : > > The following changes since commit 97a0b97f9e8197429eee5f87ce14373f73dbd9d3: > > ARM: dts: stih410-clocks: Add PROC_STFE as a

Re: [GIT PULL] STi defconfig updates for v4.10 round 2

On Thu, Nov 10, 2016 at 10:00:32AM +0100, Patrice Chotard wrote: > Hi Olof, Arnd and Kevin, > > Please consider the second round of multi_v7_defconfig updates for v4.10 : > > > The following changes since commit 620c52f4db4d47e1f33c64e641392fe575d5397f: > > ARM: multi_v7_defconfig: Remove

Re: [GIT PULL 1/3] ARM: dts: exynos: DT for v4.10

Hi, On Tue, Nov 08, 2016 at 08:26:28PM +0200, Krzysztof Kozlowski wrote: > Hi, > > Hurray! New board! ... Exynos4415 slowly is going away. > > Best regards, > Krzysztof > > > The following changes since commit 1001354ca34179f3db924eb66672442a173147dc: > > Linux 4.9-rc1 (2016-10-15 12:17:50

Re: [GIT PULL 1/3] ARM: dts: exynos: DT for v4.10

Hi, On Tue, Nov 08, 2016 at 08:26:28PM +0200, Krzysztof Kozlowski wrote: > Hi, > > Hurray! New board! ... Exynos4415 slowly is going away. > > Best regards, > Krzysztof > > > The following changes since commit 1001354ca34179f3db924eb66672442a173147dc: > > Linux 4.9-rc1 (2016-10-15 12:17:50

Re: [GIT PULL 2/3] ARM64: dts: exynos: DT for v4.10

On Tue, Nov 08, 2016 at 08:26:29PM +0200, Krzysztof Kozlowski wrote: > Hi, > > Exynos5433 + two boards using it. Mobile boards! :) > > I am really happy to push it. I know that it has been a lot of effort > in Samsung to mainline this. > > Best regards, > Krzysztof > > > The following changes

Re: [GIT PULL 3/3] ARM: defconfig: Samsung defconfigs for v4.10

On Tue, Nov 08, 2016 at 08:26:27PM +0200, Krzysztof Kozlowski wrote: > Hi, > > Nothing special. > > Best regards, > Krzysztof > > > The following changes since commit 1001354ca34179f3db924eb66672442a173147dc: > > Linux 4.9-rc1 (2016-10-15 12:17:50 -0700) > > are available in the git

Re: [GIT PULL 3/3] ARM: defconfig: Samsung defconfigs for v4.10

On Tue, Nov 08, 2016 at 08:26:27PM +0200, Krzysztof Kozlowski wrote: > Hi, > > Nothing special. > > Best regards, > Krzysztof > > > The following changes since commit 1001354ca34179f3db924eb66672442a173147dc: > > Linux 4.9-rc1 (2016-10-15 12:17:50 -0700) > > are available in the git

Re: [GIT PULL 2/3] ARM64: dts: exynos: DT for v4.10

On Tue, Nov 08, 2016 at 08:26:29PM +0200, Krzysztof Kozlowski wrote: > Hi, > > Exynos5433 + two boards using it. Mobile boards! :) > > I am really happy to push it. I know that it has been a lot of effort > in Samsung to mainline this. > > Best regards, > Krzysztof > > > The following changes

Re: [PATCH] crypto: sun4i-ss: support the Security System PRNG

On Thu, Nov 17, 2016 at 08:07:09PM -0500, Sandy Harris wrote: > Add Ted T'so to cc list. Shouldn't he be included on anything affecting > the random(4) driver? > Blindy used get_maintainer.pl, and since the file is in crypto, hw_random people were not set. Note that get_maintainer.pl on

Re: [PATCH] crypto: sun4i-ss: support the Security System PRNG

On Thu, Nov 17, 2016 at 08:07:09PM -0500, Sandy Harris wrote: > Add Ted T'so to cc list. Shouldn't he be included on anything affecting > the random(4) driver? > Blindy used get_maintainer.pl, and since the file is in crypto, hw_random people were not set. Note that get_maintainer.pl on

Re: [PATCH v3] staging: lustre: llog: fix wrong offset in llog_process_thread()

On Thu, Nov 17, 2016 at 06:29:08PM -0500, James Simmons wrote: > From: Mikhail Pershin > > - llh_cat_idx may become bigger than llog bitmap size in > llog_cat_set_first_idx() function > - it is wrong to use previous cur_offset as new buffer offset, > new offset should

Re: [PATCH v3] staging: lustre: llog: fix wrong offset in llog_process_thread()

On Thu, Nov 17, 2016 at 06:29:08PM -0500, James Simmons wrote: > From: Mikhail Pershin > > - llh_cat_idx may become bigger than llog bitmap size in > llog_cat_set_first_idx() function > - it is wrong to use previous cur_offset as new buffer offset, > new offset should be calculated from

Re: [PATCH 5/9] lib: radix-tree: check accounting of existing slot replacement users

On Thu 17-11-16 14:30:21, Johannes Weiner wrote: > The bug in khugepaged fixed earlier in this series shows that radix > tree slot replacement is fragile; and it will become more so when not > only NULL<->!NULL transitions need to be caught but transitions from > and to exceptional entries as

Re: [PATCH 5/9] lib: radix-tree: check accounting of existing slot replacement users

On Thu 17-11-16 14:30:21, Johannes Weiner wrote: > The bug in khugepaged fixed earlier in this series shows that radix > tree slot replacement is fragile; and it will become more so when not > only NULL<->!NULL transitions need to be caught but transitions from > and to exceptional entries as

Re: [PATCH v3 1/2] staging: slicoss: fix different address space warnings: 32 bits

On Thu, Nov 17, 2016 at 12:46:12PM +0100, Sergio Paracuellos wrote: > On Thu, Nov 17, 2016 at 12:33 PM, Dan Carpenter > wrote: > > Give it a shot and see if the warnings go away. I don't think the tag > > is correct. > > Just removing __iomem tag in shmem_data field of

Re: [PATCH v3 1/2] staging: slicoss: fix different address space warnings: 32 bits

On Thu, Nov 17, 2016 at 12:46:12PM +0100, Sergio Paracuellos wrote: > On Thu, Nov 17, 2016 at 12:33 PM, Dan Carpenter > wrote: > > Give it a shot and see if the warnings go away. I don't think the tag > > is correct. > > Just removing __iomem tag in shmem_data field of slic_shmemory struct >

Re: [PATCH 4/9] lib: radix-tree: native accounting of exceptional entries

On Thu 17-11-16 14:29:45, Johannes Weiner wrote: > The way the page cache is sneaking shadow entries of evicted pages > into the radix tree past the node entry accounting and tracking them > manually in the upper bits of node->count is fraught with problems. > > These shadow entries are marked in

Re: [PATCH 4/9] lib: radix-tree: native accounting of exceptional entries

On Thu 17-11-16 14:29:45, Johannes Weiner wrote: > The way the page cache is sneaking shadow entries of evicted pages > into the radix tree past the node entry accounting and tracking them > manually in the upper bits of node->count is fraught with problems. > > These shadow entries are marked in

Re: [PATCH v12 2/7] x86/arch_prctl/64: Rename do_arch_prctl to do_arch_prctl_64

On Fri, 18 Nov 2016, Ingo Molnar wrote: > > * Kyle Huey wrote: > > > In order to introduce new arch_prctls that are not 64 bit only, rename the > > existing 64 bit implementation to do_arch_prctl_64(). Also rename the second > > argument to arch_prctl(), which will no longer

Re: [PATCH v12 2/7] x86/arch_prctl/64: Rename do_arch_prctl to do_arch_prctl_64

On Fri, 18 Nov 2016, Ingo Molnar wrote: > > * Kyle Huey wrote: > > > In order to introduce new arch_prctls that are not 64 bit only, rename the > > existing 64 bit implementation to do_arch_prctl_64(). Also rename the second > > argument to arch_prctl(), which will no longer always be an

Re: [PATCH 3/9] mm: workingset: turn shadow node shrinker bugs into warnings

On Thu 17-11-16 14:11:32, Johannes Weiner wrote: > When the shadow page shrinker tries to reclaim a radix tree node but > finds it in an unexpected state - it should contain no pages, and > non-zero shadow entries - there is no need to kill the executing task > or even the entire system. Warn

Re: [PATCH 3/9] mm: workingset: turn shadow node shrinker bugs into warnings

On Thu 17-11-16 14:11:32, Johannes Weiner wrote: > When the shadow page shrinker tries to reclaim a radix tree node but > finds it in an unexpected state - it should contain no pages, and > non-zero shadow entries - there is no need to kill the executing task > or even the entire system. Warn

Re: [PATCH v12 4/7] x86/syscalls/32: Wire up arch_prctl on x86-32

* Kyle Huey wrote: > --- a/include/linux/compat.h > +++ b/include/linux/compat.h > @@ -716,16 +716,18 @@ int __compat_save_altstack(compat_stack_t __user *, > unsigned long); > } while (0); > > asmlinkage long compat_sys_sched_rr_get_interval(compat_pid_t pid, >

Re: [PATCH v12 4/7] x86/syscalls/32: Wire up arch_prctl on x86-32

* Kyle Huey wrote: > --- a/include/linux/compat.h > +++ b/include/linux/compat.h > @@ -716,16 +716,18 @@ int __compat_save_altstack(compat_stack_t __user *, > unsigned long); > } while (0); > > asmlinkage long compat_sys_sched_rr_get_interval(compat_pid_t pid, >

Re: [PATCH 2/9] mm: khugepaged: fix radix tree node leak in shmem collapse error path

On Thu 17-11-16 14:11:31, Johannes Weiner wrote: > The radix tree counts valid entries in each tree node. Entries stored > in the tree cannot be removed by simpling storing NULL in the slot or > the internal counters will be off and the node never gets freed again. > > When collapsing a shmem

Re: [PATCH 2/9] mm: khugepaged: fix radix tree node leak in shmem collapse error path

On Thu 17-11-16 14:11:31, Johannes Weiner wrote: > The radix tree counts valid entries in each tree node. Entries stored > in the tree cannot be removed by simpling storing NULL in the slot or > the internal counters will be off and the node never gets freed again. > > When collapsing a shmem

Re: [PATCH 1/9] mm: khugepaged: close use-after-free race during shmem collapsing

On Thu 17-11-16 14:11:30, Johannes Weiner wrote: > When a radix tree iteration drops the tree lock, another thread might > swoop in and free the node holding the current slot. The iteration > needs to do another tree lookup from the current index to continue. > > [kirill.shute...@linux.intel.com:

Re: [PATCH 1/9] mm: khugepaged: close use-after-free race during shmem collapsing

On Thu 17-11-16 14:11:30, Johannes Weiner wrote: > When a radix tree iteration drops the tree lock, another thread might > swoop in and free the node holding the current slot. The iteration > needs to do another tree lookup from the current index to continue. > > [kirill.shute...@linux.intel.com:

Re: [PATCH v12 2/7] x86/arch_prctl/64: Rename do_arch_prctl to do_arch_prctl_64

* Kyle Huey wrote: > In order to introduce new arch_prctls that are not 64 bit only, rename the > existing 64 bit implementation to do_arch_prctl_64(). Also rename the second > argument to arch_prctl(), which will no longer always be an address. > #ifdef CONFIG_X86_64 >

Re: [PATCH v12 2/7] x86/arch_prctl/64: Rename do_arch_prctl to do_arch_prctl_64

* Kyle Huey wrote: > In order to introduce new arch_prctls that are not 64 bit only, rename the > existing 64 bit implementation to do_arch_prctl_64(). Also rename the second > argument to arch_prctl(), which will no longer always be an address. > #ifdef CONFIG_X86_64 > void

[PATCH v2] ARM: Drop fixed 200 Hz timer requirement from Samsung platforms

All Samsung platforms, including the Exynos, are selecting HZ_FIXED with 200 Hz. Unfortunately in case of multiplatform image this affects also other platforms when Exynos is enabled. This looks like an very old legacy code, dating back to initial upstreaming of S3C24xx. Probably it was

[PATCH v2] ARM: Drop fixed 200 Hz timer requirement from Samsung platforms

All Samsung platforms, including the Exynos, are selecting HZ_FIXED with 200 Hz. Unfortunately in case of multiplatform image this affects also other platforms when Exynos is enabled. This looks like an very old legacy code, dating back to initial upstreaming of S3C24xx. Probably it was

[PATCH] clk: sunxi-ng: sun6i-a31: Enable PLL-MIPI LDOs when ungating it

The PLL-MIPI clock is somewhat special as it has its own LDOs which need to be turned on for this PLL to actually work and output a clock signal. Add the 2 LDO enable bits to the gate bits. This fixes issues with the TCON not sending vblank interrupts when the tcon and dot clock are indirectly

[PATCH] clk: sunxi-ng: sun6i-a31: Enable PLL-MIPI LDOs when ungating it

The PLL-MIPI clock is somewhat special as it has its own LDOs which need to be turned on for this PLL to actually work and output a clock signal. Add the 2 LDO enable bits to the gate bits. This fixes issues with the TCON not sending vblank interrupts when the tcon and dot clock are indirectly

Re: [PATCH 4.8 00/92] 4.8.9-stable review

On Thu, Nov 17, 2016 at 02:23:50PM -0800, Guenter Roeck wrote: > On Thu, Nov 17, 2016 at 11:31:33AM +0100, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.8.9 release. > > There are 92 patches in this series, all will be posted as a response > > to this one.

Re: [PATCH 4.8 00/92] 4.8.9-stable review

On Thu, Nov 17, 2016 at 02:23:50PM -0800, Guenter Roeck wrote: > On Thu, Nov 17, 2016 at 11:31:33AM +0100, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.8.9 release. > > There are 92 patches in this series, all will be posted as a response > > to this one.

[PATCH] arm64: dts: exynos: add the mshc_2 node for supporting T-Flash

Add the mshc_2 node for supporting T-flash. And it needs to add the "mshc*" aliases. Because dwmmc driver should be assigned to "ctrl_id" after parsing to "mshc". If there is no aliases for mshc, then it might be set to the wrong capabilities. Signed-off-by: Jaehoon Chung

[PATCH] arm64: dts: exynos: add the mshc_2 node for supporting T-Flash

Add the mshc_2 node for supporting T-flash. And it needs to add the "mshc*" aliases. Because dwmmc driver should be assigned to "ctrl_id" after parsing to "mshc". If there is no aliases for mshc, then it might be set to the wrong capabilities. Signed-off-by: Jaehoon Chung ---

Re: [PATCH/RFC] add "failfast" support for raid1/raid10.

(Seeing that it was me who initiated those patches I guess I should speak up here) On 11/18/2016 06:16 AM, NeilBrown wrote: > Hi, > > I've been sitting on these patches for a while because although they > solve a real problem, it is a fairly limited use-case, and I don't > really like some of

Re: [PATCH/RFC] add "failfast" support for raid1/raid10.

(Seeing that it was me who initiated those patches I guess I should speak up here) On 11/18/2016 06:16 AM, NeilBrown wrote: > Hi, > > I've been sitting on these patches for a while because although they > solve a real problem, it is a fairly limited use-case, and I don't > really like some of

Re: [PATCH] mm: support anonymous stable page

Hi Hugh, On Thu, Nov 17, 2016 at 08:35:10PM -0800, Hugh Dickins wrote: > On Fri, 11 Nov 2016, Minchan Kim wrote: > > Sorry for sending a wrong version. Here is new one. > > > > From 2d42ead9335cde51fd58d6348439ca03cf359ba2 Mon Sep 17 00:00:00 2001 > > From: Minchan Kim > >

Re: [PATCH] mm: support anonymous stable page

Hi Hugh, On Thu, Nov 17, 2016 at 08:35:10PM -0800, Hugh Dickins wrote: > On Fri, 11 Nov 2016, Minchan Kim wrote: > > Sorry for sending a wrong version. Here is new one. > > > > From 2d42ead9335cde51fd58d6348439ca03cf359ba2 Mon Sep 17 00:00:00 2001 > > From: Minchan Kim > > Date: Fri, 11 Nov

Re: [PATCH v4 05/10] IB/isert: Replace semaphore sem with completion

Hi Sagi, On 31 October 2016 at 02:42, Sagi Grimberg wrote: >> The semaphore 'sem' in isert_device is used as completion, so convert >> it to struct completion. Semaphores are going away in the future. > > > Umm, this is 100% *not* true. np->sem is designed as a counting to >

Re: [PATCH v4 05/10] IB/isert: Replace semaphore sem with completion

Hi Sagi, On 31 October 2016 at 02:42, Sagi Grimberg wrote: >> The semaphore 'sem' in isert_device is used as completion, so convert >> it to struct completion. Semaphores are going away in the future. > > > Umm, this is 100% *not* true. np->sem is designed as a counting to > sync the iscsi login

[PATCH] sched/rt: Change rt_nr_running to rt_queued in the comment

The code actually checks rt_queued not rt_nr_running in pick_next_task_rt(), so change the corresponding comment. Signed-off-by: T.Zhou --- kernel/sched/rt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/sched/rt.c b/kernel/sched/rt.c index

[PATCH] sched/rt: Change rt_nr_running to rt_queued in the comment

The code actually checks rt_queued not rt_nr_running in pick_next_task_rt(), so change the corresponding comment. Signed-off-by: T.Zhou --- kernel/sched/rt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/sched/rt.c b/kernel/sched/rt.c index 2516b8d..9b4a5c5 100644

Re: [PATCH] ARM: Drop fixed 200 Hz timer requirement from Exynos platforms

On Thu, Nov 17, 2016 at 01:35:45PM +0100, Arnd Bergmann wrote: > On Monday, November 14, 2016 8:27:05 PM CET Krzysztof Kozlowski wrote: > > @@ -1497,7 +1497,7 @@ source kernel/Kconfig.preempt > > config HZ_FIXED > > int > > default 200 if ARCH_EBSA110 || ARCH_S3C24XX || \ > > -

Re: [PATCH] ARM: Drop fixed 200 Hz timer requirement from Exynos platforms

On Thu, Nov 17, 2016 at 01:35:45PM +0100, Arnd Bergmann wrote: > On Monday, November 14, 2016 8:27:05 PM CET Krzysztof Kozlowski wrote: > > @@ -1497,7 +1497,7 @@ source kernel/Kconfig.preempt > > config HZ_FIXED > > int > > default 200 if ARCH_EBSA110 || ARCH_S3C24XX || \ > > -

Re: [PATCH 1/3] arm: hisi: add ARCH_MULTI_V5 support

Hi Marty, On 2016/11/17 11:03, Jiancheng Xue wrote: > Hi Wei， > > On 2016/11/16 17:31, Wei Xu wrote: >> Hi Pan, >> >> On 2016/11/16 8:56, wenpan wrote: >>> Hi Marty， >>> Does this confict with your patch？ If not，I hope this could be merged >>> first. Besides could you tell me the link to your

Re: [PATCH 1/3] arm: hisi: add ARCH_MULTI_V5 support

Hi Marty, On 2016/11/17 11:03, Jiancheng Xue wrote: > Hi Wei， > > On 2016/11/16 17:31, Wei Xu wrote: >> Hi Pan, >> >> On 2016/11/16 8:56, wenpan wrote: >>> Hi Marty， >>> Does this confict with your patch？ If not，I hope this could be merged >>> first. Besides could you tell me the link to your

[PATCH] sched/dl: Delete the argument flags of __dequeue_task_dl()

See @flags is not used there, so delete it. Signed-off-by: T.Zhou --- kernel/sched/deadline.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c index c61b461..f276a81 100644 --- a/kernel/sched/deadline.c

[PATCH] sched/dl: Delete the argument flags of __dequeue_task_dl()

See @flags is not used there, so delete it. Signed-off-by: T.Zhou --- kernel/sched/deadline.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c index c61b461..f276a81 100644 --- a/kernel/sched/deadline.c +++

[PATCH 4/5] x86: remove x86_test_and_clear_bit_percpu()

From: Len Brown Upon removal of the "is_idle" flag, x86_test_and_clear_bit_percpu() is no longer used. Signed-off-by: Len Brown Acked-by: Peter Zijlstra (Intel) --- arch/x86/include/asm/percpu.h | 11 --- 1 file changed,

[PATCH 2/5] x86: remove idle_notifier

From: Len Brown Upon removal of the i7300_idle driver, the idle_notifer is unused. Signed-off-by: Len Brown Acked-by: Peter Zijlstra (Intel) --- arch/x86/include/asm/idle.h | 7 --- arch/x86/kernel/process.c | 15

[PATCH 5/5] x86: remove enter_idle(), exit_idle()

From: Len Brown Upon removal of the is_idle flag, these routines became NOPs. Signed-off-by: Len Brown Acked-by: Peter Zijlstra (Intel) --- arch/x86/include/asm/apic.h | 1 - arch/x86/include/asm/idle.h | 9 -

[PATCH 4/5] x86: remove x86_test_and_clear_bit_percpu()

From: Len Brown Upon removal of the "is_idle" flag, x86_test_and_clear_bit_percpu() is no longer used. Signed-off-by: Len Brown Acked-by: Peter Zijlstra (Intel) --- arch/x86/include/asm/percpu.h | 11 --- 1 file changed, 11 deletions(-) diff --git a/arch/x86/include/asm/percpu.h

[PATCH 2/5] x86: remove idle_notifier

From: Len Brown Upon removal of the i7300_idle driver, the idle_notifer is unused. Signed-off-by: Len Brown Acked-by: Peter Zijlstra (Intel) --- arch/x86/include/asm/idle.h | 7 --- arch/x86/kernel/process.c | 15 --- 2 files changed, 22 deletions(-) diff --git

[PATCH 5/5] x86: remove enter_idle(), exit_idle()

From: Len Brown Upon removal of the is_idle flag, these routines became NOPs. Signed-off-by: Len Brown Acked-by: Peter Zijlstra (Intel) --- arch/x86/include/asm/apic.h | 1 - arch/x86/include/asm/idle.h | 9 - arch/x86/kernel/kvm.c| 2 --

[PATCH 1/5] i7300_idle: remove this driver

From: Len Brown In preparation for removing the idle_notifier, remove its only user, the i7300_idle driver. i7300_idle was deployed in 2008 to reduce idle memory power on systems using the i7300 chipset. The driver worked by throttling the fully-buffered DIMMs during idle

[PATCH 1/5] i7300_idle: remove this driver

From: Len Brown In preparation for removing the idle_notifier, remove its only user, the i7300_idle driver. i7300_idle was deployed in 2008 to reduce idle memory power on systems using the i7300 chipset. The driver worked by throttling the fully-buffered DIMMs during idle periods using the

[PATCH 0/5] x86: remove idle notifier

The return from idle path is latency sensitive, so the less code and fewer data accesses, the better. Remove the un-maintained i7300_idle driver, the only user of the x86 idle-notifier, and then remove the notifier itself.

[PATCH 3/5] x86: remove is_idle flag

From: Len Brown Upon removal of the idle_notifier, all accesses to the "is_idle" flag serve no purpose. Signed-off-by: Len Brown Acked-by: Peter Zijlstra (Intel) --- arch/x86/kernel/process.c | 7 --- 1 file changed, 7

[PATCH 0/5] x86: remove idle notifier

The return from idle path is latency sensitive, so the less code and fewer data accesses, the better. Remove the un-maintained i7300_idle driver, the only user of the x86 idle-notifier, and then remove the notifier itself.

[PATCH 3/5] x86: remove is_idle flag

From: Len Brown Upon removal of the idle_notifier, all accesses to the "is_idle" flag serve no purpose. Signed-off-by: Len Brown Acked-by: Peter Zijlstra (Intel) --- arch/x86/kernel/process.c | 7 --- 1 file changed, 7 deletions(-) diff --git a/arch/x86/kernel/process.c

[RFC PATCH v2 3/7] iio: inkern: api for manipulating ext_info of iio channels

Extend the inkern api with functions for reading and writing ext_info of iio channels. --- drivers/iio/inkern.c | 55 include/linux/iio/consumer.h | 6 + 2 files changed, 61 insertions(+) diff --git a/drivers/iio/inkern.c

Re: [RFC PATCH v2 2/2] module: When modifying a module's text ignore modules which are going away too

Aaron Tomlin writes: > By default, during the access permission modification of a module's core > and init pages, we only ignore modules that are malformed. Albeit for a > module which is going away, it does not make sense to change its text to > RO since the module should be

[RFC PATCH v2 3/7] iio: inkern: api for manipulating ext_info of iio channels

Extend the inkern api with functions for reading and writing ext_info of iio channels. --- drivers/iio/inkern.c | 55 include/linux/iio/consumer.h | 6 + 2 files changed, 61 insertions(+) diff --git a/drivers/iio/inkern.c

Re: [RFC PATCH v2 2/2] module: When modifying a module's text ignore modules which are going away too

Aaron Tomlin writes: > By default, during the access permission modification of a module's core > and init pages, we only ignore modules that are malformed. Albeit for a > module which is going away, it does not make sense to change its text to > RO since the module should be RW, before

Re: [PATCH v4] mm: don't cap request size based on read-ahead setting

On Friday, November 18, 2016 5:23 AM Jens Axboe wrote: > > We ran into a funky issue, where someone doing 256K buffered reads saw > 128K requests at the device level. Turns out it is read-ahead capping > the request size, since we use 128K as the default setting. This doesn't > make a lot of

Re: [PATCH v4] mm: don't cap request size based on read-ahead setting

On Friday, November 18, 2016 5:23 AM Jens Axboe wrote: > > We ran into a funky issue, where someone doing 256K buffered reads saw > 128K requests at the device level. Turns out it is read-ahead capping > the request size, since we use 128K as the default setting. This doesn't > make a lot of

[patch v8 1/1] i2c: add master driver for mellanox systems

From: Vadim Pasternak Device driver for Mellanox I2C controller logic, implemented in Lattice CPLD device. Device supports: - Master mode - One physical bus - Polling mode The Kconfig currently controlling compilation of this code is: drivers/i2c/busses/Kconfig:config

[patch v8 1/1] i2c: add master driver for mellanox systems

From: Vadim Pasternak Device driver for Mellanox I2C controller logic, implemented in Lattice CPLD device. Device supports: - Master mode - One physical bus - Polling mode The Kconfig currently controlling compilation of this code is: drivers/i2c/busses/Kconfig:config I2C_MLXCPLD

[PATCH v11 1/6] drivers/platform/x86/p2sb: New Primary to Sideband bridge support driver for Intel SOC's

From: Andy Shevchenko There is already one and at least one more user coming which require an access to Primary to Sideband bridge (P2SB) in order to get IO or MMIO bar hidden by BIOS. Create a driver to access P2SB for x86 devices. Signed-off-by: Yong,

[PATCH v11 1/6] drivers/platform/x86/p2sb: New Primary to Sideband bridge support driver for Intel SOC's

From: Andy Shevchenko There is already one and at least one more user coming which require an access to Primary to Sideband bridge (P2SB) in order to get IO or MMIO bar hidden by BIOS. Create a driver to access P2SB for x86 devices. Signed-off-by: Yong, Jonathan Signed-off-by: Andy Shevchenko

[PATCH v11 4/6] mfd: move enum lpc_chipsets into lpc_ich.h

Move the enum's definition into a standalone header file which can be used wherever its definition is needed. Signed-off-by: Tan Jui Nee Reviewed-by: Mika Westerberg --- Changes in V11: - No change Changes in V10: - No

[PATCH v11 5/6] mfd: lpc_ich: Add Device IDs for Intel Apollo Lake PCH

Adding Intel codename Apollo Lake platform device IDs for PCH. Signed-off-by: Tan Jui Nee Acked-for-MFD-by: Lee Jones --- Changes in V11: - No change Changes in V10: - No change Changes in V9: - No change Changes in V8:

[PATCH v11 6/6] mfd: lpc_ich: Add support for Intel Apollo Lake GPIO pinctrl in non-ACPI system

This driver uses the P2SB hide/unhide mechanism cooperatively to pass the PCI BAR address to the gpio platform driver. Signed-off-by: Tan Jui Nee Reviewed-by: Mika Westerberg --- Changes in V11: - Remove duplicated object file

[PATCH v11 3/6] x86/intel-ivi: Add Intel In-Vehicle Infotainment (IVI) systems used in cars support

Add support for non ACPI system, such as system that uses Advanced Boot Loader (ABL) whereby a platform device has to be created in order to bind with PINCTRL/GPIO. At the moment, Intel Apollo Lake SoC requires P2SB driver to hide and unhide P2SB to lookup P2SB BAR and pass the PCI BAR address to

[PATCH v11 4/6] mfd: move enum lpc_chipsets into lpc_ich.h

Move the enum's definition into a standalone header file which can be used wherever its definition is needed. Signed-off-by: Tan Jui Nee Reviewed-by: Mika Westerberg --- Changes in V11: - No change Changes in V10: - No change Changes in V9: - No change Changes in V8:

[PATCH v11 5/6] mfd: lpc_ich: Add Device IDs for Intel Apollo Lake PCH

Adding Intel codename Apollo Lake platform device IDs for PCH. Signed-off-by: Tan Jui Nee Acked-for-MFD-by: Lee Jones --- Changes in V11: - No change Changes in V10: - No change Changes in V9: - No change Changes in V8: - No change drivers/mfd/lpc_ich_core.c

[PATCH v11 6/6] mfd: lpc_ich: Add support for Intel Apollo Lake GPIO pinctrl in non-ACPI system

This driver uses the P2SB hide/unhide mechanism cooperatively to pass the PCI BAR address to the gpio platform driver. Signed-off-by: Tan Jui Nee Reviewed-by: Mika Westerberg --- Changes in V11: - Remove duplicated object file lpc_ich-objs in Makefile. - Put p2sb.h header file

[PATCH v11 3/6] x86/intel-ivi: Add Intel In-Vehicle Infotainment (IVI) systems used in cars support

Add support for non ACPI system, such as system that uses Advanced Boot Loader (ABL) whereby a platform device has to be created in order to bind with PINCTRL/GPIO. At the moment, Intel Apollo Lake SoC requires P2SB driver to hide and unhide P2SB to lookup P2SB BAR and pass the PCI BAR address to

[PATCH v11 2/6] mfd: lpc_ich: Rename lpc-ich driver

This patch follows the example of mfd/wm831x to rename the driver from "lpc_ich" to "lpc_ich_core". Signed-off-by: Tan Jui Nee Reviewed-by: Mika Westerberg --- Changes in V11: - No change Changes in V10: - No change

[PATCH v11 0/6] pinctrl/broxton: enable platform device in the absent of ACPI enumeration

Hi, The patches are to cater the need for non-ACPI system whereby a platform device has to be created in order to bind with Apollo Lake Pinctrl GPIO platform driver. The MMIO BAR is accessed over the Primary to Sideband bridge (P2SB). Since the BIOS prevents the P2SB device from being enumerated

[PATCH v11 2/6] mfd: lpc_ich: Rename lpc-ich driver

This patch follows the example of mfd/wm831x to rename the driver from "lpc_ich" to "lpc_ich_core". Signed-off-by: Tan Jui Nee Reviewed-by: Mika Westerberg --- Changes in V11: - No change Changes in V10: - No change Changes in V9: - Remove the filename from the header

[PATCH v11 0/6] pinctrl/broxton: enable platform device in the absent of ACPI enumeration

Hi, The patches are to cater the need for non-ACPI system whereby a platform device has to be created in order to bind with Apollo Lake Pinctrl GPIO platform driver. The MMIO BAR is accessed over the Primary to Sideband bridge (P2SB). Since the BIOS prevents the P2SB device from being enumerated

Re: [PATCH v5] drm/mediatek: fixed the calc method of data rate per lane

Hi, Daniel: On Fri, 2016-11-18 at 11:22 +0800, Daniel Kurtz wrote: > Hi CK, > > On Thu, Nov 17, 2016 at 1:36 PM, CK Hu wrote: > > Hi, Jitao: > > > > > > On Wed, 2016-11-16 at 11:20 +0800, Jitao Shi wrote: > >> Tune dsi frame rate by pixel clock, dsi add some extra signal

[md PATCH 4/6] md/raid1: add failfast handling for writes.

When writing to a fastfail device we use MD_FASTFAIL unless it is the only device being written to. For resync/recovery, assume there was a working device to read from so always use REQ_FASTFAIL_DEV. If a write for resync/recovery fails, we just fail the device - there is not much else to do.

  1   2   3   4   5   6   7   8   9   10   >