Re: [PATCH 1/2] x86/dumpstack: on oops do not rewind stack for kthread

On Thu, Oct 20, 2016 at 04:07:28PM -0700, Andy Lutomirski wrote: > On Wed, Sep 21, 2016 at 8:43 AM, Roman Pen > wrote: > > kthread uses stack and keeps completion structure on it to be woken up > > on vfork_done completion. > > > > In commit 2deb4be28 Andy

Re: [PATCH 1/2] x86/dumpstack: on oops do not rewind stack for kthread

On Thu, Oct 20, 2016 at 04:07:28PM -0700, Andy Lutomirski wrote: > On Wed, Sep 21, 2016 at 8:43 AM, Roman Pen > wrote: > > kthread uses stack and keeps completion structure on it to be woken up > > on vfork_done completion. > > > > In commit 2deb4be28 Andy Lutomirski rewinds the stack

[PATCH v2.1 2/2] MIPS: loongson1: Add watchdog support for Loongson1 board

The patch adds watchdog support for Loongson1 board. Signed-off-by: Yang Ling --- V2.1: No change. V2.0: Add watchdog support for loongson1b_defconfig. V1.1: Add watchdog support for Loongson1B. --- arch/mips/configs/loongson1b_defconfig | 4

[PATCH v2.1 2/2] MIPS: loongson1: Add watchdog support for Loongson1 board

The patch adds watchdog support for Loongson1 board. Signed-off-by: Yang Ling --- V2.1: No change. V2.0: Add watchdog support for loongson1b_defconfig. V1.1: Add watchdog support for Loongson1B. --- arch/mips/configs/loongson1b_defconfig | 4

[tip:x86/asm] entry/64: Remove unused ZERO_EXTRA_REGS macro

Commit-ID: 29a6d7964d6853f5bcd84dfb92c074fb41d00563 Gitweb: http://git.kernel.org/tip/29a6d7964d6853f5bcd84dfb92c074fb41d00563 Author: Alexander Kuleshov AuthorDate: Thu, 20 Oct 2016 18:07:04 +0600 Committer: Ingo Molnar CommitDate: Fri, 21 Oct

[tip:x86/asm] entry/64: Remove unused ZERO_EXTRA_REGS macro

Commit-ID: 29a6d7964d6853f5bcd84dfb92c074fb41d00563 Gitweb: http://git.kernel.org/tip/29a6d7964d6853f5bcd84dfb92c074fb41d00563 Author: Alexander Kuleshov AuthorDate: Thu, 20 Oct 2016 18:07:04 +0600 Committer: Ingo Molnar CommitDate: Fri, 21 Oct 2016 07:47:36 +0200 entry/64: Remove

[tip:x86/urgent] sched/core, x86: Make struct thread_info arch specific again

Commit-ID: c8061485a0d7569a865a3cc3c63347b0f42b3765 Gitweb: http://git.kernel.org/tip/c8061485a0d7569a865a3cc3c63347b0f42b3765 Author: Heiko Carstens AuthorDate: Wed, 19 Oct 2016 19:28:11 +0100 Committer: Ingo Molnar CommitDate: Thu, 20 Oct

[tip:x86/urgent] sched/core, x86: Make struct thread_info arch specific again

Commit-ID: c8061485a0d7569a865a3cc3c63347b0f42b3765 Gitweb: http://git.kernel.org/tip/c8061485a0d7569a865a3cc3c63347b0f42b3765 Author: Heiko Carstens AuthorDate: Wed, 19 Oct 2016 19:28:11 +0100 Committer: Ingo Molnar CommitDate: Thu, 20 Oct 2016 13:27:47 +0200 sched/core, x86: Make

[tip:x86/urgent] x86/platform/UV: Fix support for EFI_OLD_MEMMAP after BIOS callback updates

Commit-ID: caef78b6cdeddf4ad364f95910bba6b43b8eb9bf Gitweb: http://git.kernel.org/tip/caef78b6cdeddf4ad364f95910bba6b43b8eb9bf Author: Alex Thorlton AuthorDate: Wed, 19 Oct 2016 20:48:51 -0500 Committer: Ingo Molnar CommitDate: Thu, 20 Oct 2016

[tip:x86/urgent] x86/platform/UV: Fix support for EFI_OLD_MEMMAP after BIOS callback updates

Commit-ID: caef78b6cdeddf4ad364f95910bba6b43b8eb9bf Gitweb: http://git.kernel.org/tip/caef78b6cdeddf4ad364f95910bba6b43b8eb9bf Author: Alex Thorlton AuthorDate: Wed, 19 Oct 2016 20:48:51 -0500 Committer: Ingo Molnar CommitDate: Thu, 20 Oct 2016 08:47:58 +0200 x86/platform/UV: Fix

[tip:x86/urgent] x86/signal: Remove bogus user_64bit_mode() check from sigaction_compat_abi()

Commit-ID: ed1e7db33c3354e4f8b594738c5e793690213b43 Gitweb: http://git.kernel.org/tip/ed1e7db33c3354e4f8b594738c5e793690213b43 Author: Dmitry Safonov <0x7f454...@gmail.com> AuthorDate: Thu, 20 Oct 2016 00:53:08 +0300 Committer: Ingo Molnar CommitDate: Thu, 20 Oct 2016

[tip:x86/urgent] x86/signal: Remove bogus user_64bit_mode() check from sigaction_compat_abi()

Commit-ID: ed1e7db33c3354e4f8b594738c5e793690213b43 Gitweb: http://git.kernel.org/tip/ed1e7db33c3354e4f8b594738c5e793690213b43 Author: Dmitry Safonov <0x7f454...@gmail.com> AuthorDate: Thu, 20 Oct 2016 00:53:08 +0300 Committer: Ingo Molnar CommitDate: Thu, 20 Oct 2016 13:05:15 +0200

Re: [PATCH v3] x86/tsc: add X86_FEATURE_TSC_KNOWN_FREQ flag

On Thu, Oct 20, 2016 at 09:37:50PM +0200, Thomas Gleixner wrote: > Well, we have the same issue on other platforms/models which set the > reliable flag. I was not aware we had other platforms doing this, git grep tells me intel-mid does this as well.. > So one sanity check we can do is to read

Re: [PATCH v3] x86/tsc: add X86_FEATURE_TSC_KNOWN_FREQ flag

On Thu, Oct 20, 2016 at 09:37:50PM +0200, Thomas Gleixner wrote: > Well, we have the same issue on other platforms/models which set the > reliable flag. I was not aware we had other platforms doing this, git grep tells me intel-mid does this as well.. > So one sanity check we can do is to read

Re: [PATCH 20/23] ASoC: add simple-graph-card document

Hi Rob Can I continue this idea (= property on port/endpoint) ? Of course I will remove "type" from OF graph. > > > + type = "sound"; > > > > I'm still not convinced this is necessary. This is implied either by > > the fact there is only one port or perhaps the compatible string.

[PATCH v2.1 1/2] watchdog: loongson1: Add Loongson1 SoC watchdog driver

Add watchdog timer specific driver for Loongson1 SoC. Signed-off-by: Yang Ling --- V2.1 from Kelvin Cheung: Use max_hw_heartbeat_ms instead of max_timeout. V2: Increase the value of the default heartbeat. Modify the setup process for register. Order include files and

Re: [PATCH 20/23] ASoC: add simple-graph-card document

Hi Rob Can I continue this idea (= property on port/endpoint) ? Of course I will remove "type" from OF graph. > > > + type = "sound"; > > > > I'm still not convinced this is necessary. This is implied either by > > the fact there is only one port or perhaps the compatible string.

[PATCH v2.1 1/2] watchdog: loongson1: Add Loongson1 SoC watchdog driver

Add watchdog timer specific driver for Loongson1 SoC. Signed-off-by: Yang Ling --- V2.1 from Kelvin Cheung: Use max_hw_heartbeat_ms instead of max_timeout. V2: Increase the value of the default heartbeat. Modify the setup process for register. Order include files and Makefile

Re: [PATCH v5 0/9] implement vcpu preempted check

On Thu, Oct 20, 2016 at 05:27:45PM -0400, Pan Xinhui wrote: > > This patch set aims to fix lock holder preemption issues. Thanks, this looks very good. I'll wait for ACKs from at least the KVM people, since that was I think the most contentious patch.

Re: [PATCH v5 0/9] implement vcpu preempted check

On Thu, Oct 20, 2016 at 05:27:45PM -0400, Pan Xinhui wrote: > > This patch set aims to fix lock holder preemption issues. Thanks, this looks very good. I'll wait for ACKs from at least the KVM people, since that was I think the most contentious patch.

Re: [PATCH 2/2] sched: do not call workqueue sleep hook if task is already dead

On Wed, Sep 21, 2016 at 05:43:50PM +0200, Roman Pen wrote: > If panic_on_oops is not set and oops happens inside workqueue kthread, > kernel kills this kthread. Current patch fixes recursive GPF which > happens in that case with the following stack: > The root cause is that zeroed

Re: [PATCH 2/2] sched: do not call workqueue sleep hook if task is already dead

On Wed, Sep 21, 2016 at 05:43:50PM +0200, Roman Pen wrote: > If panic_on_oops is not set and oops happens inside workqueue kthread, > kernel kills this kthread. Current patch fixes recursive GPF which > happens in that case with the following stack: > The root cause is that zeroed

Re: [PATCH] kexec: Export kexec_in_progress to modules

David Miller writes: > From: Florian Fainelli > Date: Thu, 20 Oct 2016 18:15:16 -0700 > >> The bcm_sf2 driver uses kexec_in_progress to know whether it can power >> down an integrated PHY during shutdown, and can be built as a module. >> Other modules

Re: [PATCH] kexec: Export kexec_in_progress to modules

David Miller writes: > From: Florian Fainelli > Date: Thu, 20 Oct 2016 18:15:16 -0700 > >> The bcm_sf2 driver uses kexec_in_progress to know whether it can power >> down an integrated PHY during shutdown, and can be built as a module. >> Other modules may be using this in the future, so export

Re: [PATCH] net: skip genenerating uevents for network namespaces that are exiting

On Thu, Oct 20, 2016 at 8:10 PM, Cong Wang wrote: > On Thu, Oct 20, 2016 at 7:46 PM, Andrei Vagin wrote: >> No one can see these events, because a network namespace can not be >> destroyed, if it has sockets. >> > > Are you sure? kobject_uevent_env()

Re: [PATCH] net: skip genenerating uevents for network namespaces that are exiting

On Thu, Oct 20, 2016 at 8:10 PM, Cong Wang wrote: > On Thu, Oct 20, 2016 at 7:46 PM, Andrei Vagin wrote: >> No one can see these events, because a network namespace can not be >> destroyed, if it has sockets. >> > > Are you sure? kobject_uevent_env() seems sending uevents to all > network

[PATCH 6/6] FRV-setup: Move statements for "case" to separate lines

From: Markus Elfring Date: Thu, 20 Oct 2016 22:33:56 +0200 The script "checkpatch.pl" pointed information out like the following. ERROR: trailing statements should be on next line Thus fix the affected source code places. Signed-off-by: Markus Elfring

[PATCH 6/6] FRV-setup: Move statements for "case" to separate lines

From: Markus Elfring Date: Thu, 20 Oct 2016 22:33:56 +0200 The script "checkpatch.pl" pointed information out like the following. ERROR: trailing statements should be on next line Thus fix the affected source code places. Signed-off-by: Markus Elfring --- arch/frv/kernel/setup.c | 8

[PATCH 5/6] FRV-setup: Fix indentation in two lines

From: Markus Elfring Date: Thu, 20 Oct 2016 22:25:18 +0200 The script "checkpatch.pl" pointed information out like the following. WARNING: please, no spaces at the start of a line Thus fix the affected source code places. Signed-off-by: Markus Elfring

[PATCH 5/6] FRV-setup: Fix indentation in two lines

From: Markus Elfring Date: Thu, 20 Oct 2016 22:25:18 +0200 The script "checkpatch.pl" pointed information out like the following. WARNING: please, no spaces at the start of a line Thus fix the affected source code places. Signed-off-by: Markus Elfring --- arch/frv/kernel/setup.c | 4 ++-- 1

[PATCH 4/6] FRV-setup: Move "else" closer to a brace

From: Markus Elfring Date: Thu, 20 Oct 2016 22:12:27 +0200 The script "checkpatch.pl" pointed information out like the following. ERROR: else should follow close brace '}' Thus fix the affected source code places. Signed-off-by: Markus Elfring

[PATCH 4/6] FRV-setup: Move "else" closer to a brace

From: Markus Elfring Date: Thu, 20 Oct 2016 22:12:27 +0200 The script "checkpatch.pl" pointed information out like the following. ERROR: else should follow close brace '}' Thus fix the affected source code places. Signed-off-by: Markus Elfring --- arch/frv/kernel/setup.c | 6 ++ 1 file

Re: [PATCH v5 7/9] x86, xen: support vcpu preempted check

Corrected xen-devel mailing list address, added other Xen maintainers On 20/10/16 23:27, Pan Xinhui wrote: > From: Juergen Gross > > Support the vcpu_is_preempted() functionality under Xen. This will > enhance lock performance on overcommitted hosts (more runnable vcpus > than

[PATCH 3/6] FRV-setup: Add some spaces for better code readability

From: Markus Elfring Date: Thu, 20 Oct 2016 22:05:55 +0200 Use space characters at some source code places according to the Linux coding style convention. Signed-off-by: Markus Elfring --- arch/frv/kernel/setup.c | 40

Re: [PATCH v5 7/9] x86, xen: support vcpu preempted check

Corrected xen-devel mailing list address, added other Xen maintainers On 20/10/16 23:27, Pan Xinhui wrote: > From: Juergen Gross > > Support the vcpu_is_preempted() functionality under Xen. This will > enhance lock performance on overcommitted hosts (more runnable vcpus > than physical cpus in

[PATCH 3/6] FRV-setup: Add some spaces for better code readability

From: Markus Elfring Date: Thu, 20 Oct 2016 22:05:55 +0200 Use space characters at some source code places according to the Linux coding style convention. Signed-off-by: Markus Elfring --- arch/frv/kernel/setup.c | 40 1 file changed, 20 insertions(+),

[PATCH 2/6] FRV-setup: Use seq_putc() in show_cpuinfo()

From: Markus Elfring Date: Thu, 20 Oct 2016 21:39:00 +0200 A single character (line break) should be put into a sequence. Thus use the corresponding function "seq_putc". This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring

[PATCH 2/6] FRV-setup: Use seq_putc() in show_cpuinfo()

From: Markus Elfring Date: Thu, 20 Oct 2016 21:39:00 +0200 A single character (line break) should be put into a sequence. Thus use the corresponding function "seq_putc". This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- arch/frv/kernel/setup.c | 2 +-

[PATCH 1/6] FRV-setup: Use seq_puts() in show_cpuinfo()

From: Markus Elfring Date: Thu, 20 Oct 2016 21:36:43 +0200 A string which did not contain a data format specification should be put into a sequence. Thus use the corresponding function "seq_puts". This issue was detected by using the Coccinelle software.

[PATCH 1/6] FRV-setup: Use seq_puts() in show_cpuinfo()

From: Markus Elfring Date: Thu, 20 Oct 2016 21:36:43 +0200 A string which did not contain a data format specification should be put into a sequence. Thus use the corresponding function "seq_puts". This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH 0/6] FRV-setup: Fine-tuning for six function implementations

From: Markus Elfring Date: Thu, 20 Oct 2016 22:44:22 +0200 Some update suggestions were taken into account from static source code analysis. Markus Elfring (6): Use seq_puts() in show_cpuinfo() Use seq_putc() in show_cpuinfo() Add some spaces for better code

[PATCH 0/6] FRV-setup: Fine-tuning for six function implementations

From: Markus Elfring Date: Thu, 20 Oct 2016 22:44:22 +0200 Some update suggestions were taken into account from static source code analysis. Markus Elfring (6): Use seq_puts() in show_cpuinfo() Use seq_putc() in show_cpuinfo() Add some spaces for better code readability Move "else"

Re: [PATCH] toshiba-wmi: Fix loading the driver on non Toshiba laptops

On Wed, Oct 19, 2016 at 05:27:49PM -0600, Azael Avalos wrote: > Hi Darren, > > 2016-10-19 14:26 GMT-06:00 Darren Hart : > > > > > Want to going to stable? > > If possible, yes, as this issue affects other laptop manufacturers, > we may never know if someone might try to

Re: [PATCH] toshiba-wmi: Fix loading the driver on non Toshiba laptops

On Wed, Oct 19, 2016 at 05:27:49PM -0600, Azael Avalos wrote: > Hi Darren, > > 2016-10-19 14:26 GMT-06:00 Darren Hart : > > > > > Want to going to stable? > > If possible, yes, as this issue affects other laptop manufacturers, > we may never know if someone might try to load an older kernel >

Re: [PATCH] shmem: avoid huge pages for small files

On Thu, Oct 20, 2016 at 07:01:16PM -0700, Andi Kleen wrote: > > Ugh, no, please don't use mount options for file specific behaviours > > in filesystems like ext4 and XFS. This is exactly the sort of > > behaviour that should either just work automatically (i.e. be > > completely controlled by the

Re: [PATCH] shmem: avoid huge pages for small files

On Thu, Oct 20, 2016 at 07:01:16PM -0700, Andi Kleen wrote: > > Ugh, no, please don't use mount options for file specific behaviours > > in filesystems like ext4 and XFS. This is exactly the sort of > > behaviour that should either just work automatically (i.e. be > > completely controlled by the

Re: [RESEND PATCH v4] clk: x86: Add Atom PMC platform clocks

On Thu, Oct 20, 2016 at 11:52:38PM +0200, Thomas Gleixner wrote: > On Mon, 17 Oct 2016, Irina Tirdea wrote: > > The patch has already been reviewed by Stephen Boyd [1]. > > The only remaining question is the one pointed out by Stephen: > > "Will there be problems if this merges through clk tree?

Re: [RESEND PATCH v4] clk: x86: Add Atom PMC platform clocks

On Thu, Oct 20, 2016 at 11:52:38PM +0200, Thomas Gleixner wrote: > On Mon, 17 Oct 2016, Irina Tirdea wrote: > > The patch has already been reviewed by Stephen Boyd [1]. > > The only remaining question is the one pointed out by Stephen: > > "Will there be problems if this merges through clk tree?

[patch] perf_event_open.2: update time_shift sample code

Linux 4.3 (b20112edeadf0b8a1416de061caa4beb11539902) improved the accuracy of the clock/ns conversion routines. As a result the shift factor can now be 32. This value is directly exported in the perf_event_open() mmap page, and this potentially breaks the sample code that shifts 1 left by the

[patch] perf_event_open.2: update time_shift sample code

Linux 4.3 (b20112edeadf0b8a1416de061caa4beb11539902) improved the accuracy of the clock/ns conversion routines. As a result the shift factor can now be 32. This value is directly exported in the perf_event_open() mmap page, and this potentially breaks the sample code that shifts 1 left by the

Re: [PATCH v4] mmc: sdhci-msm: Add pm_runtime and system PM support

Hi Ritesh, On 20 October 2016 at 20:20, Ritesh Harjani wrote: > Hi Pramod, > > Thanks for this patch. Few minor comments. > > I have tested your patch on db410c and 8996 based internal platform and it > works fine. Thanks for the review and testing. > > > > On 10/18/2016

Re: [PATCH v4] mmc: sdhci-msm: Add pm_runtime and system PM support

Hi Ritesh, On 20 October 2016 at 20:20, Ritesh Harjani wrote: > Hi Pramod, > > Thanks for this patch. Few minor comments. > > I have tested your patch on db410c and 8996 based internal platform and it > works fine. Thanks for the review and testing. > > > > On 10/18/2016 3:46 PM, Pramod Gurav

Re: [PATCH v4] mmc: sdhci-msm: Add pm_runtime and system PM support

Thanks Georgi for the review. On 20 October 2016 at 18:38, Georgi Djakov wrote: > Hi Pramod, > > Thanks for the patch! > > On 10/18/2016 01:16 PM, Pramod Gurav wrote: >> >> Provides runtime PM callbacks to enable and disable clock resources >> when idle. Also support

Re: [PATCH v4] mmc: sdhci-msm: Add pm_runtime and system PM support

Thanks Georgi for the review. On 20 October 2016 at 18:38, Georgi Djakov wrote: > Hi Pramod, > > Thanks for the patch! > > On 10/18/2016 01:16 PM, Pramod Gurav wrote: >> >> Provides runtime PM callbacks to enable and disable clock resources >> when idle. Also support system PM callbacks to be

[PATCH] clk: rockchip: add 533.25MHz to rk3399 clock rates table

We need to get the accurate 533.25MHz for the DP display. Signed-off-by: Xing Zheng --- drivers/clk/rockchip/clk-rk3399.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/clk/rockchip/clk-rk3399.c b/drivers/clk/rockchip/clk-rk3399.c index 2c7cba7..a87cb49

[PATCH] clk: rockchip: add 533.25MHz to rk3399 clock rates table

We need to get the accurate 533.25MHz for the DP display. Signed-off-by: Xing Zheng --- drivers/clk/rockchip/clk-rk3399.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/clk/rockchip/clk-rk3399.c b/drivers/clk/rockchip/clk-rk3399.c index 2c7cba7..a87cb49 100644 ---

[git pull] drm fixes for 4.9-rc2 (part 2)

Hi Linus, Second part of the fixes for rc2, main one being some vmwgfx fixes, also some armada, etnaviv and fsl-dcu fixes. There is a pretty large regression in -rc1 that affects radeon/amdgpu/nouveau and possibly other ttm using drivers with real VRAM on PAT systems, this was due to a change in

[git pull] drm fixes for 4.9-rc2 (part 2)

Hi Linus, Second part of the fixes for rc2, main one being some vmwgfx fixes, also some armada, etnaviv and fsl-dcu fixes. There is a pretty large regression in -rc1 that affects radeon/amdgpu/nouveau and possibly other ttm using drivers with real VRAM on PAT systems, this was due to a change in

Re: [PATCH 1/2] mm: memcontrol: use special workqueue for creating per-memcg caches

On Tue, 4 Oct 2016 16:14:17 +0300 Vladimir Davydov wrote: > Creating a lot of cgroups at the same time might stall all worker > threads with kmem cache creation works, because kmem cache creation is > done with the slab_mutex held. The problem was amplified by commits >

Re: [PATCH 1/2] mm: memcontrol: use special workqueue for creating per-memcg caches

On Tue, 4 Oct 2016 16:14:17 +0300 Vladimir Davydov wrote: > Creating a lot of cgroups at the same time might stall all worker > threads with kmem cache creation works, because kmem cache creation is > done with the slab_mutex held. The problem was amplified by commits > 801faf0db894 ("mm/slab:

Re: [PATCH net] net: remove MTU limits on a few ether_setup callers

Le 20/10/2016 à 20:25, Jarod Wilson a écrit : > These few drivers call ether_setup(), but have no ndo_change_mtu, and thus > were overlooked for changes to MTU range checking behavior. They > previously had no range checks, so for feature-parity, set their min_mtu > to 0 and max_mtu to ETH_MAX_MTU

Re: [PATCH net] net: remove MTU limits on a few ether_setup callers

Le 20/10/2016 à 20:25, Jarod Wilson a écrit : > These few drivers call ether_setup(), but have no ndo_change_mtu, and thus > were overlooked for changes to MTU range checking behavior. They > previously had no range checks, so for feature-parity, set their min_mtu > to 0 and max_mtu to ETH_MAX_MTU

Re: [PATCH] uapi: linux: acct: Remove redundant type comp2_t from kernel

On Wed, 5 Oct 2016 21:40:10 +0800 cheng...@emindsoft.com.cn wrote: > In api itself, kernel does not use it -- it is divided into ac_etime_hi > and ac_etime_lo. So kernel side only need generate the correct > ac_etime_hi and ac_etime_lo, but need not know about comp2_t. > > At present, kernel

Re: [PATCH] uapi: linux: acct: Remove redundant type comp2_t from kernel

On Wed, 5 Oct 2016 21:40:10 +0800 cheng...@emindsoft.com.cn wrote: > In api itself, kernel does not use it -- it is divided into ac_etime_hi > and ac_etime_lo. So kernel side only need generate the correct > ac_etime_hi and ac_etime_lo, but need not know about comp2_t. > > At present, kernel

Re: [PATCH net-next v2 6/9] net: use core MTU range checking in virt drivers

On Thu, Oct 20, 2016 at 10:37:20PM -0400, Jarod Wilson wrote: > On Thu, Oct 20, 2016 at 11:23:54PM +0300, Michael S. Tsirkin wrote: > > On Thu, Oct 20, 2016 at 01:55:21PM -0400, Jarod Wilson wrote: > ... > > > diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c > > > index

Re: [PATCH net-next v2 6/9] net: use core MTU range checking in virt drivers

On Thu, Oct 20, 2016 at 10:37:20PM -0400, Jarod Wilson wrote: > On Thu, Oct 20, 2016 at 11:23:54PM +0300, Michael S. Tsirkin wrote: > > On Thu, Oct 20, 2016 at 01:55:21PM -0400, Jarod Wilson wrote: > ... > > > diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c > > > index

[PATCH v14 3/4] arm: dts: mt2701: Add clock controller device nodes

From: James Liao Add clock controller nodes for MT2701, include topckgen, infracfg, pericfg, apmixedsys, mmsys, imgsys, vdecsys, hifsys, ethsys and bdpsys. This patch also add two oscillators that provide clocks for MT2701. Signed-off-by: James Liao

[PATCH v14 2/4] reset: mediatek: Add MT2701 reset driver

From: Shunli Wang In infrasys and perifsys, there are many reset control bits for kinds of modules. These bits are used as actual reset controllers to be registered into kernel's generic reset controller framework. Signed-off-by: Shunli Wang

[PATCH v14 3/4] arm: dts: mt2701: Add clock controller device nodes

From: James Liao Add clock controller nodes for MT2701, include topckgen, infracfg, pericfg, apmixedsys, mmsys, imgsys, vdecsys, hifsys, ethsys and bdpsys. This patch also add two oscillators that provide clocks for MT2701. Signed-off-by: James Liao Signed-off-by: Erin Lo ---

[PATCH v14 2/4] reset: mediatek: Add MT2701 reset driver

From: Shunli Wang In infrasys and perifsys, there are many reset control bits for kinds of modules. These bits are used as actual reset controllers to be registered into kernel's generic reset controller framework. Signed-off-by: Shunli Wang Signed-off-by: James Liao Signed-off-by: Erin Lo

[PATCH v14 4/4] arm: dts: mt2701: Use real clock for UARTs

We used to use a fixed rate clock for the UARTs. Now that we have clock support we can associate the correct clocks to the UARTs and drop the 26MHz fixed rate UART clock. Signed-off-by: Erin Lo --- arch/arm/boot/dts/mt2701.dtsi | 18 -- 1 file changed, 8

[PATCH v14 0/4] Add clock support for Mediatek MT2701

This series is based on v4.9-rc1, add clock and reset controller support for Mediatek MT2701. changes since v13: - Rebase to v4.9-rc1. changes since v12: - Rebase to clk-next. - Use CLK_OF_DECLARE_DRIVER() instead of CLK_OF_DECLARE(). - Use dev_* and devm_* APIs instead of pr_* and ioremap(). -

[PATCH v14 1/4] clk: mediatek: Add MT2701 clock support

From: Shunli Wang Add MT2701 clock support, include topckgen, apmixedsys, infracfg, pericfg and subsystem clocks. Signed-off-by: Shunli Wang Signed-off-by: James Liao Signed-off-by: Erin Lo

[PATCH v14 4/4] arm: dts: mt2701: Use real clock for UARTs

We used to use a fixed rate clock for the UARTs. Now that we have clock support we can associate the correct clocks to the UARTs and drop the 26MHz fixed rate UART clock. Signed-off-by: Erin Lo --- arch/arm/boot/dts/mt2701.dtsi | 18 -- 1 file changed, 8 insertions(+), 10

[PATCH v14 0/4] Add clock support for Mediatek MT2701

This series is based on v4.9-rc1, add clock and reset controller support for Mediatek MT2701. changes since v13: - Rebase to v4.9-rc1. changes since v12: - Rebase to clk-next. - Use CLK_OF_DECLARE_DRIVER() instead of CLK_OF_DECLARE(). - Use dev_* and devm_* APIs instead of pr_* and ioremap(). -

[PATCH v14 1/4] clk: mediatek: Add MT2701 clock support

From: Shunli Wang Add MT2701 clock support, include topckgen, apmixedsys, infracfg, pericfg and subsystem clocks. Signed-off-by: Shunli Wang Signed-off-by: James Liao Signed-off-by: Erin Lo Tested-by: John Crispin --- drivers/clk/mediatek/Kconfig | 43 ++

linux-next: Tree for Oct 21

Hi all, Changes since 20161020: New trees: phy, phy-next The net tree gained a build failure so I used the version from next-20161020. The net-next tree gained a conflict against the net tree. The staging tree gained a conflict against the net-next tree. The akpm-current tree still had its

linux-next: Tree for Oct 21

Hi all, Changes since 20161020: New trees: phy, phy-next The net tree gained a build failure so I used the version from next-20161020. The net-next tree gained a conflict against the net tree. The staging tree gained a conflict against the net-next tree. The akpm-current tree still had its

Re: [PATCH v2] prctl: remove one-shot limitation for changing exe link

Gentlemen, ping. Let's decide something, how to get rid of this strange solution. It doesn't provide the security it was aimed to, looks ugly and obfuscates the user of the feature. It looks like it can be just thrown away. But if not, please, advice, what should be changed to make is safe

Re: [PATCH v2] prctl: remove one-shot limitation for changing exe link

Gentlemen, ping. Let's decide something, how to get rid of this strange solution. It doesn't provide the security it was aimed to, looks ugly and obfuscates the user of the feature. It looks like it can be just thrown away. But if not, please, advice, what should be changed to make is safe

Re: [PATCH] m32r: add simple dma

On Sat, 8 Oct 2016 23:23:18 +0530 Sudip Mukherjee wrote: > Some builds of m32r were failing as it tried to build few drivers which > needed dma but m32r is not having dma support. Objections were raised > when it was tried to make those drivers depend on HAS_DMA.

Re: [PATCH] m32r: add simple dma

On Sat, 8 Oct 2016 23:23:18 +0530 Sudip Mukherjee wrote: > Some builds of m32r were failing as it tried to build few drivers which > needed dma but m32r is not having dma support. Objections were raised > when it was tried to make those drivers depend on HAS_DMA. Huh. What were these

[PATCH net] net: remove MTU limits on a few ether_setup callers

These few drivers call ether_setup(), but have no ndo_change_mtu, and thus were overlooked for changes to MTU range checking behavior. They previously had no range checks, so for feature-parity, set their min_mtu to 0 and max_mtu to ETH_MAX_MTU (65535), instead of the 68 and 1500 inherited from

[PATCH net] net: remove MTU limits on a few ether_setup callers

These few drivers call ether_setup(), but have no ndo_change_mtu, and thus were overlooked for changes to MTU range checking behavior. They previously had no range checks, so for feature-parity, set their min_mtu to 0 and max_mtu to ETH_MAX_MTU (65535), instead of the 68 and 1500 inherited from

Re: [PATCH v2 1/2] watchdog: Introduce arch_watchdog_nmi_enable and arch_watchdog_nmi_disable

On Thu, 20 Oct 2016 12:14:14 -0400 Don Zickus wrote: > > > -static int watchdog_nmi_enable(unsigned int cpu) { return 0; } > > > -static void watchdog_nmi_disable(unsigned int cpu) { return; } > > > +/* > > > + * These two functions are mostly architecture specific > > > + *

Re: [PATCH v2 1/2] watchdog: Introduce arch_watchdog_nmi_enable and arch_watchdog_nmi_disable

On Thu, 20 Oct 2016 12:14:14 -0400 Don Zickus wrote: > > > -static int watchdog_nmi_enable(unsigned int cpu) { return 0; } > > > -static void watchdog_nmi_disable(unsigned int cpu) { return; } > > > +/* > > > + * These two functions are mostly architecture specific > > > + * defining them as

Re: [PATCH 1/4] kconfig: introduce the "imply" keyword

On Thu, 20 Oct 2016, Nicolas Pitre wrote: > On Thu, 20 Oct 2016, Edward Cree wrote: > > > I'm interpreting "imply" as being more a way of saying "if you want FOO you > > probably want BAZ as well". But maybe that should be yet another new > > keyword if it's so different from what you want

Re: [PATCH 1/4] kconfig: introduce the "imply" keyword

On Thu, 20 Oct 2016, Nicolas Pitre wrote: > On Thu, 20 Oct 2016, Edward Cree wrote: > > > I'm interpreting "imply" as being more a way of saying "if you want FOO you > > probably want BAZ as well". But maybe that should be yet another new > > keyword if it's so different from what you want

Re: [PATCH 2/4] iio: dpot-dac: DAC driver based on a digital potentiometer

On 2016-10-20 16:08, Peter Meerwald-Stadler wrote: + u32 max_ohms; +}; + +static const struct iio_chan_spec dpot_dac_iio_channel = { + .type = IIO_VOLTAGE, + .info_mask_separate = BIT(IIO_CHAN_INFO_RAW) + | BIT(IIO_CHAN_INFO_SCALE), +

Re: [PATCH 2/4] iio: dpot-dac: DAC driver based on a digital potentiometer

On 2016-10-20 16:08, Peter Meerwald-Stadler wrote: + u32 max_ohms; +}; + +static const struct iio_chan_spec dpot_dac_iio_channel = { + .type = IIO_VOLTAGE, + .info_mask_separate = BIT(IIO_CHAN_INFO_RAW) + | BIT(IIO_CHAN_INFO_SCALE), +

Re: [PATCH v9 10/12] vfio: Add function to get device_api string from vfio_device_info.flags

On Fri, 21 Oct 2016 08:30:53 +0530 Kirti Wankhede wrote: > On 10/21/2016 2:52 AM, Alex Williamson wrote: > > On Fri, 21 Oct 2016 02:44:37 +0530 > > Kirti Wankhede wrote: > > > ... > > >> > >> +extern const char

Re: [PATCH v9 10/12] vfio: Add function to get device_api string from vfio_device_info.flags

On Fri, 21 Oct 2016 08:30:53 +0530 Kirti Wankhede wrote: > On 10/21/2016 2:52 AM, Alex Williamson wrote: > > On Fri, 21 Oct 2016 02:44:37 +0530 > > Kirti Wankhede wrote: > > > ... > > >> > >> +extern const char *vfio_device_api_string(u32 flags); > >> + > >> struct

Re: [PATCH] net: l2tp_eth: fix max_mtu

On Thu, Oct 20, 2016 at 09:19:29PM +, Asbjoern Sloth Toennesen wrote: > On Thu, 20 Oct 2016 20:08:26 + (UTC), a...@asbjorn.biz wrote: > > diff --git a/net/l2tp/l2tp_eth.c b/net/l2tp/l2tp_eth.c > > index 965f7e3..ba82dcc 100644 > > --- a/net/l2tp/l2tp_eth.c > > +++ b/net/l2tp/l2tp_eth.c > >

Re: [PATCH] net: l2tp_eth: fix max_mtu

On Thu, Oct 20, 2016 at 09:19:29PM +, Asbjoern Sloth Toennesen wrote: > On Thu, 20 Oct 2016 20:08:26 + (UTC), a...@asbjorn.biz wrote: > > diff --git a/net/l2tp/l2tp_eth.c b/net/l2tp/l2tp_eth.c > > index 965f7e3..ba82dcc 100644 > > --- a/net/l2tp/l2tp_eth.c > > +++ b/net/l2tp/l2tp_eth.c > >

Re: [PATCH] mm, compaction: fix NR_ISOLATED_* stats for pfn based migration

On Wed, 19 Oct 2016 10:02:40 +0200 Michal Hocko wrote: > Since bda807d44454 ("mm: migrate: support non-lru movable page > migration") isolate_migratepages_block) can isolate !PageLRU pages which > would acct_isolated account as NR_ISOLATED_*. Accounting these non-lru > pages

Re: [PATCH] mm, compaction: fix NR_ISOLATED_* stats for pfn based migration

On Wed, 19 Oct 2016 10:02:40 +0200 Michal Hocko wrote: > Since bda807d44454 ("mm: migrate: support non-lru movable page > migration") isolate_migratepages_block) can isolate !PageLRU pages which > would acct_isolated account as NR_ISOLATED_*. Accounting these non-lru > pages

Re: [PATCH] drm/sun4i: Add a few formats

On Tue, Oct 18, 2016 at 4:46 PM, Maxime Ripard wrote: > The planes can do more than what was previously exposed. Add support for > them. > > Signed-off-by: Maxime Ripard > --- > drivers/gpu/drm/sun4i/sun4i_backend.c | 20

Re: [PATCH] drm/sun4i: Add a few formats

On Tue, Oct 18, 2016 at 4:46 PM, Maxime Ripard wrote: > The planes can do more than what was previously exposed. Add support for > them. > > Signed-off-by: Maxime Ripard > --- > drivers/gpu/drm/sun4i/sun4i_backend.c | 20 > drivers/gpu/drm/sun4i/sun4i_layer.c | 6 ++

Re: [PATCH] crypto: cmac - fix alignment of 'consts'

On Mon, Oct 10, 2016 at 10:15:15AM -0700, Eric Biggers wrote: > The per-transform 'consts' array is accessed as __be64 in > crypto_cmac_digest_setkey() but was only guaranteed to be aligned to > __alignof__(long). Fix this by aligning it to __alignof__(__be64). > > Signed-off-by: Eric Biggers

Re: [PATCH] crypto: cmac - fix alignment of 'consts'

On Mon, Oct 10, 2016 at 10:15:15AM -0700, Eric Biggers wrote: > The per-transform 'consts' array is accessed as __be64 in > crypto_cmac_digest_setkey() but was only guaranteed to be aligned to > __alignof__(long). Fix this by aligning it to __alignof__(__be64). > > Signed-off-by: Eric Biggers

  1   2   3   4   5   6   7   8   9   10   >