[PATCH v4 7/7] cpufreq: schedutil: New governor based on scheduler utilization data

From: Rafael J. Wysocki Add a new cpufreq scaling governor, called "schedutil", that uses scheduler-provided CPU utilization information as input for making its decisions. Doing that is possible after commit 34e2c555f3e1 (cpufreq: Add mechanism for registering

[PATCH v4 7/7] cpufreq: schedutil: New governor based on scheduler utilization data

From: Rafael J. Wysocki Add a new cpufreq scaling governor, called "schedutil", that uses scheduler-provided CPU utilization information as input for making its decisions. Doing that is possible after commit 34e2c555f3e1 (cpufreq: Add mechanism for registering utilization update callbacks) that

Re: [PATCH RT 4/6] rt/locking: Reenable migration accross schedule

On Sat, 2016-02-13 at 00:02 +0100, Sebastian Andrzej Siewior wrote: > From: Thomas Gleixner > > We currently disable migration across lock acquisition. That includes the part > where we block on the lock and schedule out. We cannot disable migration after > taking the lock as

Re: [PATCH RT 4/6] rt/locking: Reenable migration accross schedule

On Sat, 2016-02-13 at 00:02 +0100, Sebastian Andrzej Siewior wrote: > From: Thomas Gleixner > > We currently disable migration across lock acquisition. That includes the part > where we block on the lock and schedule out. We cannot disable migration after > taking the lock as that would cause a

Re: N900 sleep mode (in 4.5-rc0, if that matters)

Hi! First, sorry for the delay. Busy with other projects, then tried to keep USB in 4.5 from regressing. I'm now back on 4.4 branch. > > > > (I assume I have to insmod and rmmod, right? Because powersave is not > > > > entered if I simply compile-out usb). > > > > > > Depending on what the

Re: N900 sleep mode (in 4.5-rc0, if that matters)

Hi! First, sorry for the delay. Busy with other projects, then tried to keep USB in 4.5 from regressing. I'm now back on 4.4 branch. > > > > (I assume I have to insmod and rmmod, right? Because powersave is not > > > > entered if I simply compile-out usb). > > > > > > Depending on what the

Re: N900 sleep mode (in 4.5-rc0, if that matters)

Hi! > > Oh and I also have the MMC PM runtime regression fix here that I > > have not yet posted. Will post today. But I guess you're on > > v4.4 right now still. > > And looks like the USB RNDIS gadget has some extra issues > breaking reboot. So I'd stick to ECM if possible and leave out >

Re: N900 sleep mode (in 4.5-rc0, if that matters)

Hi! > > Oh and I also have the MMC PM runtime regression fix here that I > > have not yet posted. Will post today. But I guess you're on > > v4.4 right now still. > > And looks like the USB RNDIS gadget has some extra issues > breaking reboot. So I'd stick to ECM if possible and leave out >

[PATCH v2 03/11] ARM: davinci: da850: use clk->set_parent for async3

The da850 family of processors has an async3 clock domain that can be muxed to either pll0_sysclk2 or pll1_sysclk2. Now that the davinci clocks have a set_parent callback, we can use this to control the async3 mux instead of a stand-alone function. This adds a new async3_clk and sets the

[PATCH v2 03/11] ARM: davinci: da850: use clk->set_parent for async3

The da850 family of processors has an async3 clock domain that can be muxed to either pll0_sysclk2 or pll1_sysclk2. Now that the davinci clocks have a set_parent callback, we can use this to control the async3 mux instead of a stand-alone function. This adds a new async3_clk and sets the

[tip:x86/urgent] x86/iopl: Fix iopl capability check on Xen PV

Commit-ID: c29016cf41fe9fa994a5ecca607cf5f1cd98801e Gitweb: http://git.kernel.org/tip/c29016cf41fe9fa994a5ecca607cf5f1cd98801e Author: Andy Lutomirski AuthorDate: Wed, 16 Mar 2016 14:14:22 -0700 Committer: Ingo Molnar CommitDate: Thu, 17 Mar 2016

[tip:x86/urgent] x86/iopl: Fix iopl capability check on Xen PV

Commit-ID: c29016cf41fe9fa994a5ecca607cf5f1cd98801e Gitweb: http://git.kernel.org/tip/c29016cf41fe9fa994a5ecca607cf5f1cd98801e Author: Andy Lutomirski AuthorDate: Wed, 16 Mar 2016 14:14:22 -0700 Committer: Ingo Molnar CommitDate: Thu, 17 Mar 2016 09:49:27 +0100 x86/iopl: Fix iopl

Re: 4.5.0+ panic when setup loop device

On Thu, 17 Mar 2016, Jens Axboe wrote: > On 03/17/2016 09:42 AM, Jens Axboe wrote: > > On 03/17/2016 05:01 AM, Thomas Gleixner wrote: > > > On Thu, 17 Mar 2016, Peter Zijlstra wrote: > > > > On Thu, Mar 17, 2016 at 12:39:46PM +0100, Thomas Gleixner wrote: > > > > > But we have to clarify and

Re: 4.5.0+ panic when setup loop device

On Thu, 17 Mar 2016, Jens Axboe wrote: > On 03/17/2016 09:42 AM, Jens Axboe wrote: > > On 03/17/2016 05:01 AM, Thomas Gleixner wrote: > > > On Thu, 17 Mar 2016, Peter Zijlstra wrote: > > > > On Thu, Mar 17, 2016 at 12:39:46PM +0100, Thomas Gleixner wrote: > > > > > But we have to clarify and

Re: [PATCH 5/5] ftrace: Update dynamic ftrace calls only if necessary

Patches 4 and 5 seem agnostic to patches 1-3. I'll pull 4,5 into my tree and 1-3 can go though tip. I'd like to run theses through my tests. OK? -- Steve On Wed, 16 Mar 2016 15:34:33 +0100 Jiri Olsa wrote: > Currently dynamic ftrace calls are updated any time > the

Re: [PATCH 5/5] ftrace: Update dynamic ftrace calls only if necessary

Patches 4 and 5 seem agnostic to patches 1-3. I'll pull 4,5 into my tree and 1-3 can go though tip. I'd like to run theses through my tests. OK? -- Steve On Wed, 16 Mar 2016 15:34:33 +0100 Jiri Olsa wrote: > Currently dynamic ftrace calls are updated any time > the ftrace_ops is

[RESEND PATCH v4 0/5] acpi, clocksource: add GTDT and ARM memory-mapped timer support

From: Fu Wei This patchset: (1)Move some enums and marcos to header file for arm_arch_timer, improve the pr_* code by defining "pr_fmt(fmt)" in arm_arch_timer.c (2)Introduce ACPI GTDT parser: drivers/acpi/gtdt.c Parse all kinds of timer in GTDT table of

[RESEND PATCH v4 0/5] acpi, clocksource: add GTDT and ARM memory-mapped timer support

From: Fu Wei This patchset: (1)Move some enums and marcos to header file for arm_arch_timer, improve the pr_* code by defining "pr_fmt(fmt)" in arm_arch_timer.c (2)Introduce ACPI GTDT parser: drivers/acpi/gtdt.c Parse all kinds of timer in GTDT table of ACPI:arch timer,

Re: linux-next: Tree for Mar 14 (mips qemu failure bisected)

On 16/03/2016 13:22, Guenter Roeck wrote: On Tue, Mar 15, 2016 at 05:17:13PM -0700, Guenter Roeck wrote: On Tue, Mar 15, 2016 at 09:55:06PM +, Qais Yousef wrote: Hi Guenter, [ ... ] Qemu test results: total: 96 pass: 69 fail: 27 Failed tests: [ ... ]

Re: linux-next: Tree for Mar 14 (mips qemu failure bisected)

On 16/03/2016 13:22, Guenter Roeck wrote: On Tue, Mar 15, 2016 at 05:17:13PM -0700, Guenter Roeck wrote: On Tue, Mar 15, 2016 at 09:55:06PM +, Qais Yousef wrote: Hi Guenter, [ ... ] Qemu test results: total: 96 pass: 69 fail: 27 Failed tests: [ ... ]

Re: [PATCH 3.4 098/107] kernel/watchdog.c: touch_nmi_watchdog should only touch local cpu not every one

>> diff --git a/kernel/watchdog.c b/kernel/watchdog.c >> index 991aa93..7527c8c 100644 >> --- a/kernel/watchdog.c >> +++ b/kernel/watchdog.c >> @@ -162,6 +162,14 @@ void touch_nmi_watchdog(void) >> per_cpu(watchdog_nmi_touch, cpu) = true; >> } >> } >

Re: [PATCH 3.4 098/107] kernel/watchdog.c: touch_nmi_watchdog should only touch local cpu not every one

>> diff --git a/kernel/watchdog.c b/kernel/watchdog.c >> index 991aa93..7527c8c 100644 >> --- a/kernel/watchdog.c >> +++ b/kernel/watchdog.c >> @@ -162,6 +162,14 @@ void touch_nmi_watchdog(void) >> per_cpu(watchdog_nmi_touch, cpu) = true; >> } >> } >

Re: [GIT PULL] USB driver patches for 4.6-rc1

On Wed, Mar 16, 2016 at 5:09 PM, Greg KH wrote: > > USB patches for 4.6-rc1 > > Here is the big USB patchset for 4.6-rc1. Something in this - or possibly the tty pull, but that doesn't sound very likely - has killed my USB keyboard on my desktop. I'm bisecting right

Re: [GIT PULL] USB driver patches for 4.6-rc1

On Wed, Mar 16, 2016 at 5:09 PM, Greg KH wrote: > > USB patches for 4.6-rc1 > > Here is the big USB patchset for 4.6-rc1. Something in this - or possibly the tty pull, but that doesn't sound very likely - has killed my USB keyboard on my desktop. I'm bisecting right now. Expect a likely revert.

Re: [PATCH v2] phy: hi6220: Add missing MFD_SYSCON dependency on HAS_IOMEM

On Wed, 16 Mar 2016, Krzysztof Kozlowski wrote: > The MFD_SYSCON depends on HAS_IOMEM so when selecting it avoid unmet > direct dependencies. > > This fixes warning on allyesconfig on ARCH=um: > > warning: (ST_IRQCHIP && HIP04_ETH && STMMAC_PLATFORM && DWMAC_IPQ806X && > DWMAC_LPC18XX &&

Re: [PATCH v2] phy: hi6220: Add missing MFD_SYSCON dependency on HAS_IOMEM

On Wed, 16 Mar 2016, Krzysztof Kozlowski wrote: > The MFD_SYSCON depends on HAS_IOMEM so when selecting it avoid unmet > direct dependencies. > > This fixes warning on allyesconfig on ARCH=um: > > warning: (ST_IRQCHIP && HIP04_ETH && STMMAC_PLATFORM && DWMAC_IPQ806X && > DWMAC_LPC18XX &&

Re: [PATCH 3/5] ARM: davinci: da8xx: add cfgchip2 to resources

On 03/16/2016 09:22 PM, Sergei Shtylyov wrote: Also, I am not finding any existing data structure to pass the musb set_mode function to the phy in either usb_phy or usb_otg. Setting the mode (host/peripheral/otg) is done in the same PHY register, so it seems like it should be implemented in the

Re: [PATCH 3/5] ARM: davinci: da8xx: add cfgchip2 to resources

On 03/16/2016 09:22 PM, Sergei Shtylyov wrote: Also, I am not finding any existing data structure to pass the musb set_mode function to the phy in either usb_phy or usb_otg. Setting the mode (host/peripheral/otg) is done in the same PHY register, so it seems like it should be implemented in the

Re: [PATCH] staging/comedi/dt282x: avoid integer overflow warning

On Wednesday 16 March 2016 17:04:15 Hartley Sweeten wrote: > > #define DT2821_SUPCSR_DS_AD_TRIG (3 << 10) > > Use a helper macro for those bits: > > #define DT2821_SUPCSR_DS(x) (((x) & 0x3) << 10) > #define DT2821_SUPCSR_DS_PIODT2821_SUPCSR_DS(0) > #define

Re: [PATCH] staging/comedi/dt282x: avoid integer overflow warning

On Wednesday 16 March 2016 17:04:15 Hartley Sweeten wrote: > > #define DT2821_SUPCSR_DS_AD_TRIG (3 << 10) > > Use a helper macro for those bits: > > #define DT2821_SUPCSR_DS(x) (((x) & 0x3) << 10) > #define DT2821_SUPCSR_DS_PIODT2821_SUPCSR_DS(0) > #define

[RESEND] [PATCH v11 1/6] fixed typo in ufshcd-pltfrm

Fixed typo in ufshcd-pltfrm. Signed-off-by: Joao Pinto Acked-by: Arnd Bergmann --- Changes v0->v11: - Nothing changed (just to keep up with patch set version). drivers/scsi/ufs/ufshcd-pltfrm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[RESEND] [PATCH v11 1/6] fixed typo in ufshcd-pltfrm

Fixed typo in ufshcd-pltfrm. Signed-off-by: Joao Pinto Acked-by: Arnd Bergmann --- Changes v0->v11: - Nothing changed (just to keep up with patch set version). drivers/scsi/ufs/ufshcd-pltfrm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/scsi/ufs/ufshcd-pltfrm.c

Re: [PATCH][RFC,v4] ACPI / PM: Introduce efi poweroff for HW-full platforms without _S5

On Wed, 16 Mar, at 05:59:29AM, Chen, Yu C wrote: > Hi Matt, > > > -Original Message- > > From: Matt Fleming [mailto:m...@codeblueprint.co.uk] > > Sent: Tuesday, March 15, 2016 4:01 AM > > To: Chen, Yu C > > Cc: linux-a...@vger.kernel.org; linux...@vger.kernel.org; Rafael J. Wysocki; > >

Re: [PATCH][RFC,v4] ACPI / PM: Introduce efi poweroff for HW-full platforms without _S5

On Wed, 16 Mar, at 05:59:29AM, Chen, Yu C wrote: > Hi Matt, > > > -Original Message- > > From: Matt Fleming [mailto:m...@codeblueprint.co.uk] > > Sent: Tuesday, March 15, 2016 4:01 AM > > To: Chen, Yu C > > Cc: linux-a...@vger.kernel.org; linux...@vger.kernel.org; Rafael J. Wysocki; > >

Re: [RFC PATCH v4 3/7] PCI: Ignore resource_alignment if PCI_PROBE_ONLY was set

On Mon, 7 Mar 2016 15:48:34 +0800 Yongji Xie wrote: > The resource_alignment will releases memory resources > allocated by firmware so that kernel can reassign new > resources later on. But this will cause the problem > that no resources can be allocated by kernel if

Re: [RFC PATCH v4 3/7] PCI: Ignore resource_alignment if PCI_PROBE_ONLY was set

On Mon, 7 Mar 2016 15:48:34 +0800 Yongji Xie wrote: > The resource_alignment will releases memory resources > allocated by firmware so that kernel can reassign new > resources later on. But this will cause the problem > that no resources can be allocated by kernel if > PCI_PROBE_ONLY was set,

Re: [RFC5 PATCH v6 00/21] ILP32 for ARM64

Hi, Yury On 2016/3/19 0:46, Yury Norov wrote: On Fri, Mar 18, 2016 at 04:55:26PM +0100, Alexander Graf wrote: On 18.03.16 16:49, Yury Norov wrote: On Fri, Mar 18, 2016 at 06:28:29PM +0800, Zhangjian (Bamvor) wrote: For the glibc part, I found that there are 11 patches of ilp32 in top, but

Re: [RFC5 PATCH v6 00/21] ILP32 for ARM64

Hi, Yury On 2016/3/19 0:46, Yury Norov wrote: On Fri, Mar 18, 2016 at 04:55:26PM +0100, Alexander Graf wrote: On 18.03.16 16:49, Yury Norov wrote: On Fri, Mar 18, 2016 at 06:28:29PM +0800, Zhangjian (Bamvor) wrote: For the glibc part, I found that there are 11 patches of ilp32 in top, but

Re: [PATCH] sound: usb: add Microsoft HD-5001 to quirks

On Sat, 19 Mar 2016 13:17:42 +0100, Victor Clément wrote: > > The Microsoft HD-5001 webcam microphone does not support sample rate > reading as the HD-5000 one. > This results in dmesg errors and sound hanging with pulseaudio. > > Signed-off-by: Victor Clément

Re: [PATCH] sound: usb: add Microsoft HD-5001 to quirks

On Sat, 19 Mar 2016 13:17:42 +0100, Victor Clément wrote: > > The Microsoft HD-5001 webcam microphone does not support sample rate > reading as the HD-5000 one. > This results in dmesg errors and sound hanging with pulseaudio. > > Signed-off-by: Victor Clément Applied, thanks. Takashi > ---

[GIT PULL] Mailbox changes for v4.6

Hi Linus, The following changes since commit 1926e54f115725a9248d0c4c65c22acaf94de4c4: MAINTAINERS: Update mailing list for Renesas ARM64 SoC Development (2016-02-14 18:38:15 -0800) are available in the git repository at: git://git.linaro.org/landing-teams/working/fujitsu/integration.git

[GIT PULL] Mailbox changes for v4.6

Hi Linus, The following changes since commit 1926e54f115725a9248d0c4c65c22acaf94de4c4: MAINTAINERS: Update mailing list for Renesas ARM64 SoC Development (2016-02-14 18:38:15 -0800) are available in the git repository at: git://git.linaro.org/landing-teams/working/fujitsu/integration.git

Re: [PATCH 08/15] genirq: Add runtime power management support for IRQ chips

On 18/03/16 14:40, Jon Hunter wrote: > On 18/03/16 14:23, Grygorii Strashko wrote: >> On 03/18/2016 02:27 PM, Jon Hunter wrote: >>> >>> On 18/03/16 11:11, Grygorii Strashko wrote: [snip] >> oh :( That will require updating of all drivers (and if it will be taken >> into account that >> wakeup

Re: [PATCH 08/15] genirq: Add runtime power management support for IRQ chips

On 18/03/16 14:40, Jon Hunter wrote: > On 18/03/16 14:23, Grygorii Strashko wrote: >> On 03/18/2016 02:27 PM, Jon Hunter wrote: >>> >>> On 18/03/16 11:11, Grygorii Strashko wrote: [snip] >> oh :( That will require updating of all drivers (and if it will be taken >> into account that >> wakeup

Re: [PATCH v2 1/2] drm: bridge: sil902x

Le 06/01/2016 13:25, Boris Brezillon a écrit : > Add basic support for the sil902x RGB -> HDMI bridge. > This driver does not support audio output yet. > > Signed-off-by: Boris Brezillon You can add my: Tested-by: Nicolas Ferre I

Re: [PATCH v2 1/2] drm: bridge: sil902x

Le 06/01/2016 13:25, Boris Brezillon a écrit : > Add basic support for the sil902x RGB -> HDMI bridge. > This driver does not support audio output yet. > > Signed-off-by: Boris Brezillon You can add my: Tested-by: Nicolas Ferre I tested it on a SAMA5D4 Xplained board with a Dell HDMI monitor.

Re: [PATCH v2 10/11] usb: musb: da8xx: Use devm in probe

Hello. On 3/17/2016 5:26 AM, David Lechner wrote: Simplify things a bit by using devm functions where possible. Signed-off-by: David Lechner --- v2 changes: This is part of a previous patch that was split. No changes from previous version. drivers/usb/musb/da8xx.c

Re: [PATCH v2 10/11] usb: musb: da8xx: Use devm in probe

Hello. On 3/17/2016 5:26 AM, David Lechner wrote: Simplify things a bit by using devm functions where possible. Signed-off-by: David Lechner --- v2 changes: This is part of a previous patch that was split. No changes from previous version. drivers/usb/musb/da8xx.c | 28

Re: [PATCH 1/2] mm/vmap: Add a notifier for when we run out of vmap address space

On Thu, Mar 17, 2016 at 02:21:40PM +0100, Roman Peniaev wrote: > On Thu, Mar 17, 2016 at 1:57 PM, Chris Wilson > wrote: > > On Thu, Mar 17, 2016 at 01:37:06PM +0100, Roman Peniaev wrote: > >> > + freed = 0; > >> > + blocking_notifier_call_chain(_notify_list,

Re: [PATCH 1/2] mm/vmap: Add a notifier for when we run out of vmap address space

On Thu, Mar 17, 2016 at 02:21:40PM +0100, Roman Peniaev wrote: > On Thu, Mar 17, 2016 at 1:57 PM, Chris Wilson > wrote: > > On Thu, Mar 17, 2016 at 01:37:06PM +0100, Roman Peniaev wrote: > >> > + freed = 0; > >> > + blocking_notifier_call_chain(_notify_list, 0, ); > >> > >> It seems

Re: [PATCH] powerpc: rename to_user_ptr to __to_user_ptr

Hi, 2016-03-17 Gustavo Padovan : > From: Gustavo Padovan > > to_user_ptr() is a local macro defined by signal_32.c, rename it to > __to_user_ptr() as now we will have a global to_user_ptr() defined by > kernel.h that has a different meaning

Re: [PATCH] powerpc: rename to_user_ptr to __to_user_ptr

Hi, 2016-03-17 Gustavo Padovan : > From: Gustavo Padovan > > to_user_ptr() is a local macro defined by signal_32.c, rename it to > __to_user_ptr() as now we will have a global to_user_ptr() defined by > kernel.h that has a different meaning from this one. > > Cc: Benjamin Herrenschmidt > Cc:

[PATCH] Documentation: mmc: Add the introduction for mmc-utils

This patch introduces one mmc test tool called mmc-utils, which is convenient if someone want to exercise and test MMC/SD devices from userspace. Signed-off-by: Baolin Wang --- Documentation/mmc/00-INDEX |2 ++ Documentation/mmc/mmc-tools.txt | 34

[PATCH] Documentation: mmc: Add the introduction for mmc-utils

This patch introduces one mmc test tool called mmc-utils, which is convenient if someone want to exercise and test MMC/SD devices from userspace. Signed-off-by: Baolin Wang --- Documentation/mmc/00-INDEX |2 ++ Documentation/mmc/mmc-tools.txt | 34 ++

[PATCH 02/15] ARM: OMAP: Correct interrupt type for ARM TWD

The ARM TWD interrupt is a private peripheral interrupt (PPI) and per the ARM GIC documentation, whether the type for PPIs can be set is IMPLEMENTATION DEFINED. For OMAP4 devices the PPI type cannot be set and so when we attempt to set the type for the ARM TWD interrupt it fails. This has done

[PATCH 02/15] ARM: OMAP: Correct interrupt type for ARM TWD

The ARM TWD interrupt is a private peripheral interrupt (PPI) and per the ARM GIC documentation, whether the type for PPIs can be set is IMPLEMENTATION DEFINED. For OMAP4 devices the PPI type cannot be set and so when we attempt to set the type for the ARM TWD interrupt it fails. This has done

[PATCH] cpufreq: powernv: Define per_cpu chip pointer to optimize hot-path

From: Michael Neuling "cpufreq: powernv: Remove cpu_to_chip_id() from hot-path" introduced 'core_to_chip_map' array to cache the chip-id of all cores. Replace this with per_cpu variable that stores the pointer to the chip-array. This removes the linear lookup and provides a

[PATCH] cpufreq: powernv: Define per_cpu chip pointer to optimize hot-path

From: Michael Neuling "cpufreq: powernv: Remove cpu_to_chip_id() from hot-path" introduced 'core_to_chip_map' array to cache the chip-id of all cores. Replace this with per_cpu variable that stores the pointer to the chip-array. This removes the linear lookup and provides a neater and simpler

[PATCH 2/3] drm: atmel_hldc - use generic drm_connector_plug_all() helper

This driver used to have its own implementation of connector_plug_all() which actually was taken as a prototype of drm_connector_plug_all(). Now when drm_connector_plug_all() exists reusing it here. And while at it getting rid of mutex in both plug() and unplug() because they were moved to

[PATCH 2/3] drm: atmel_hldc - use generic drm_connector_plug_all() helper

This driver used to have its own implementation of connector_plug_all() which actually was taken as a prototype of drm_connector_plug_all(). Now when drm_connector_plug_all() exists reusing it here. And while at it getting rid of mutex in both plug() and unplug() because they were moved to

Re: 4.5.0+ panic when setup loop device

On Thu, 17 Mar 2016, Jens Axboe wrote: > On 03/17/2016 01:20 PM, Thomas Gleixner wrote: > > > This might be better, we need to start at -1 to not miss the first one... > > > Still untested. > > > > > +static inline struct blk_mq_ctx *next_ctx(struct request_queue *q, int > > > *i) > > > +{ > > >

Re: 4.5.0+ panic when setup loop device

On Thu, 17 Mar 2016, Jens Axboe wrote: > On 03/17/2016 01:20 PM, Thomas Gleixner wrote: > > > This might be better, we need to start at -1 to not miss the first one... > > > Still untested. > > > > > +static inline struct blk_mq_ctx *next_ctx(struct request_queue *q, int > > > *i) > > > +{ > > >

[PATCH v2] iwlwifi: dvm: use alloc_ordered_workqueue()

Use alloc_ordered_workqueue() to allocate the workqueue instead of create_singlethread_workqueue() since the latter is deprecated and is scheduled for removal. There are work items doing related operations that shouldn't be swapped when queued in a certain order hence preserve the strict

Re: 4.5.0+ panic when setup loop device

On 03/17/2016 01:20 PM, Thomas Gleixner wrote: On Thu, 17 Mar 2016, Jens Axboe wrote: On 03/17/2016 09:42 AM, Jens Axboe wrote: On 03/17/2016 05:01 AM, Thomas Gleixner wrote: On Thu, 17 Mar 2016, Peter Zijlstra wrote: On Thu, Mar 17, 2016 at 12:39:46PM +0100, Thomas Gleixner wrote: But we

[PATCH v2] iwlwifi: dvm: use alloc_ordered_workqueue()

Use alloc_ordered_workqueue() to allocate the workqueue instead of create_singlethread_workqueue() since the latter is deprecated and is scheduled for removal. There are work items doing related operations that shouldn't be swapped when queued in a certain order hence preserve the strict

Re: 4.5.0+ panic when setup loop device

On 03/17/2016 01:20 PM, Thomas Gleixner wrote: On Thu, 17 Mar 2016, Jens Axboe wrote: On 03/17/2016 09:42 AM, Jens Axboe wrote: On 03/17/2016 05:01 AM, Thomas Gleixner wrote: On Thu, 17 Mar 2016, Peter Zijlstra wrote: On Thu, Mar 17, 2016 at 12:39:46PM +0100, Thomas Gleixner wrote: But we

Re: [PATCH 1/3] powerpc/powernv: Move CHECK_HMI_INTERRUPT to exception-64s header

On Mon, Feb 29, 2016 at 05:52:58PM +0530, Shreyas B. Prabhu wrote: > CHECK_HMI_INTERRUPT is used to check for HMI's in reset vector. Move > the macro to a common location (exception-64s.h) > This patch does not change any functionality. Comments below... > diff --git

Re: [PATCH 1/3] powerpc/powernv: Move CHECK_HMI_INTERRUPT to exception-64s header

On Mon, Feb 29, 2016 at 05:52:58PM +0530, Shreyas B. Prabhu wrote: > CHECK_HMI_INTERRUPT is used to check for HMI's in reset vector. Move > the macro to a common location (exception-64s.h) > This patch does not change any functionality. Comments below... > diff --git

[PART1 RFC v3 04/12] KVM: split kvm_vcpu_wake_up from kvm_vcpu_kick

From: Radim Krčmář AVIC has a use for kvm_vcpu_wake_up. Signed-off-by: Radim Krčmář Tested-by: Suravee Suthikulpanit --- include/linux/kvm_host.h | 1 + virt/kvm/kvm_main.c | 19 +-- 2 files changed,

[PART1 RFC v3 04/12] KVM: split kvm_vcpu_wake_up from kvm_vcpu_kick

From: Radim Krčmář AVIC has a use for kvm_vcpu_wake_up. Signed-off-by: Radim Krčmář Tested-by: Suravee Suthikulpanit --- include/linux/kvm_host.h | 1 + virt/kvm/kvm_main.c | 19 +-- 2 files changed, 14 insertions(+), 6 deletions(-) diff --git

Re: [PATCH] cpufreq: Do not schedule policy update work in cpufreq_resume()

On Wed, Mar 16, 2016 at 5:52 AM, Viresh Kumar wrote: > On 16-03-16, 01:51, Rafael J. Wysocki wrote: >> OK, so the problem with doing that in syscore ops is that the I2C bus >> needed for it may not be available at that point, which is fair >> enough. > > Not just that. We

Re: [PATCH] cpufreq: Do not schedule policy update work in cpufreq_resume()

On Wed, Mar 16, 2016 at 5:52 AM, Viresh Kumar wrote: > On 16-03-16, 01:51, Rafael J. Wysocki wrote: >> OK, so the problem with doing that in syscore ops is that the I2C bus >> needed for it may not be available at that point, which is fair >> enough. > > Not just that. We wouldn't call

Re: Suspicious error for CMA stress test

On 03/17/2016 07:54 AM, Joonsoo Kim wrote: On Wed, Mar 16, 2016 at 05:44:28PM +0800, Hanjun Guo wrote: On 2016/3/14 15:18, Joonsoo Kim wrote: Hmm, this one is not work, I still can see the bug is there after applying this patch, did I miss something? I may find that there is a bug which was

Re: Suspicious error for CMA stress test

On 03/17/2016 07:54 AM, Joonsoo Kim wrote: On Wed, Mar 16, 2016 at 05:44:28PM +0800, Hanjun Guo wrote: On 2016/3/14 15:18, Joonsoo Kim wrote: Hmm, this one is not work, I still can see the bug is there after applying this patch, did I miss something? I may find that there is a bug which was

Re: UFS V11 patch-set

Hi! On 3/18/2016 2:49 PM, Arnd Bergmann wrote: > On Friday 18 March 2016 12:52:13 Joao Pinto wrote: >> Hi! >> >> Could you please check the following patch-set in order to evaluate if it is >> ready for v4.6? >> > > I think the code is ok now, but the timing apparently didn't work for 4.6. > I'd

Re: UFS V11 patch-set

Hi! On 3/18/2016 2:49 PM, Arnd Bergmann wrote: > On Friday 18 March 2016 12:52:13 Joao Pinto wrote: >> Hi! >> >> Could you please check the following patch-set in order to evaluate if it is >> ready for v4.6? >> > > I think the code is ok now, but the timing apparently didn't work for 4.6. > I'd

[PATCH 1/1] Btrfs: Code Cleanup

From: Flex Liu In fs/btrfs/volumes.c:2328 if (seeding_dev) { sb->s_flags &= ~MS_RDONLY; ret = btrfs_prepare_sprout(root); BUG_ON(ret); /* -ENOMEM */ } the error code would be return from: fs_devs =

[PATCH 1/1] Btrfs: Code Cleanup

From: Flex Liu In fs/btrfs/volumes.c:2328 if (seeding_dev) { sb->s_flags &= ~MS_RDONLY; ret = btrfs_prepare_sprout(root); BUG_ON(ret); /* -ENOMEM */ } the error code would be return from: fs_devs =

Re: [PATCH v2 3/5] dt-bindings: Add documentation for GM20B GPU

On Sat, Mar 19, 2016 at 5:47 AM, Rob Herring wrote: > On Tue, Mar 15, 2016 at 11:58:42AM +0900, Alexandre Courbot wrote: >> GM20B's definition is mostly similar to GK20A's, but requires an >> additional clock. >> >> Signed-off-by: Alexandre Courbot >> --- >>

Build failure in mainline kernel due to 'lan78xx: add ndo_get_stats64'

Hi, your commit a59f8c5b048 ("lan78xx: add ndo_get_stats64") is causing the following build failure if CONFIG_PM is not enabled. drivers/net/usb/lan78xx.c: In function 'lan78xx_get_stats64': drivers/net/usb/lan78xx.c:3274:27: error: 'struct dev_pm_info' has no member named 'runtime_auto'

Re: [PATCH v2 3/5] dt-bindings: Add documentation for GM20B GPU

On Sat, Mar 19, 2016 at 5:47 AM, Rob Herring wrote: > On Tue, Mar 15, 2016 at 11:58:42AM +0900, Alexandre Courbot wrote: >> GM20B's definition is mostly similar to GK20A's, but requires an >> additional clock. >> >> Signed-off-by: Alexandre Courbot >> --- >>

Build failure in mainline kernel due to 'lan78xx: add ndo_get_stats64'

Hi, your commit a59f8c5b048 ("lan78xx: add ndo_get_stats64") is causing the following build failure if CONFIG_PM is not enabled. drivers/net/usb/lan78xx.c: In function 'lan78xx_get_stats64': drivers/net/usb/lan78xx.c:3274:27: error: 'struct dev_pm_info' has no member named 'runtime_auto'

Re: [PATCH v2 1/5] dt-bindings: gk20a: Fix typo in compatible name

On Sat, Mar 19, 2016 at 5:31 AM, Rob Herring wrote: > On Tue, Mar 15, 2016 at 11:58:40AM +0900, Alexandre Courbot wrote: >> The correct compatible name is "nvidia,gk20a". >> >> Signed-off-by: Alexandre Courbot >> --- >>

Re: [PATCH v2 1/5] dt-bindings: gk20a: Fix typo in compatible name

On Sat, Mar 19, 2016 at 5:31 AM, Rob Herring wrote: > On Tue, Mar 15, 2016 at 11:58:40AM +0900, Alexandre Courbot wrote: >> The correct compatible name is "nvidia,gk20a". >> >> Signed-off-by: Alexandre Courbot >> --- >> Documentation/devicetree/bindings/gpu/nvidia,gk20a.txt | 4 ++-- >> 1 file

RE: [PATCH] cpuidle: menu: Fall back to polling if next timer event is near

On 2016.03.19 17:34 Rafael J. Wysocki wrote: > Commit a9ceb78bc75c (cpuidle,menu: use interactivity_req to disable > polling) changed the behavior of the fallback state selection part > of menu_select() so it looks at interactivity_req instead of > data->next_timer_us when it makes its decision.

RE: [PATCH] cpuidle: menu: Fall back to polling if next timer event is near

On 2016.03.19 17:34 Rafael J. Wysocki wrote: > Commit a9ceb78bc75c (cpuidle,menu: use interactivity_req to disable > polling) changed the behavior of the fallback state selection part > of menu_select() so it looks at interactivity_req instead of > data->next_timer_us when it makes its decision.

Re: [PATCH v2] ARM: DMA: Fix kzalloc flags in __dma_alloc

On Fri, Mar 18, 2016 at 7:58 PM, Russell King - ARM Linux wrote: > On Fri, Mar 18, 2016 at 06:28:49PM +0900, Alexandre Courbot wrote: >> Commit 19e6e5e5392b ("ARM: 8547/1: dma-mapping: store buffer >> information") allocates a structure meant for internal buffer management

Re: [PATCH v2] ARM: DMA: Fix kzalloc flags in __dma_alloc

On Fri, Mar 18, 2016 at 7:58 PM, Russell King - ARM Linux wrote: > On Fri, Mar 18, 2016 at 06:28:49PM +0900, Alexandre Courbot wrote: >> Commit 19e6e5e5392b ("ARM: 8547/1: dma-mapping: store buffer >> information") allocates a structure meant for internal buffer management >> with the GFP flags

Re: [PATCH v3 2/3] IB/hns: Add HiSilicon RoCE driver support

On Sat, Mar 19, 2016 at 06:50:57PM +0800, Lijun Ou wrote: > The driver for HiSilicon RoCE is a platform driver. > The driver will support multiple versions of hardware. Currently only "v1" > for hip06 SoC is supported. > The driver includes two parts: common driver and hardware-specific >

Re: [PATCH v3 2/3] IB/hns: Add HiSilicon RoCE driver support

On Sat, Mar 19, 2016 at 06:50:57PM +0800, Lijun Ou wrote: > The driver for HiSilicon RoCE is a platform driver. > The driver will support multiple versions of hardware. Currently only "v1" > for hip06 SoC is supported. > The driver includes two parts: common driver and hardware-specific >

[PATCH v4 4/8] arm, dts: add TC2 cpu capacity information

Add TC2 cpu capacity binding information. Cc: Liviu Dudau Cc: Sudeep Holla Cc: Lorenzo Pieralisi Cc: Rob Herring Cc: Pawel Moll Cc: Mark Rutland Cc: Ian

[PATCH v4 4/8] arm, dts: add TC2 cpu capacity information

Add TC2 cpu capacity binding information. Cc: Liviu Dudau Cc: Sudeep Holla Cc: Lorenzo Pieralisi Cc: Rob Herring Cc: Pawel Moll Cc: Mark Rutland Cc: Ian Campbell Cc: Kumar Gala Cc: Russell King Cc: devicet...@vger.kernel.org Signed-off-by: Juri Lelli --- Changes from v1: -

[PATCH v2 10/11] usb: musb: da8xx: Use devm in probe

Simplify things a bit by using devm functions where possible. Signed-off-by: David Lechner --- v2 changes: This is part of a previous patch that was split. No changes from previous version. drivers/usb/musb/da8xx.c | 28 1 file changed, 8

[PATCH v2 10/11] usb: musb: da8xx: Use devm in probe

Simplify things a bit by using devm functions where possible. Signed-off-by: David Lechner --- v2 changes: This is part of a previous patch that was split. No changes from previous version. drivers/usb/musb/da8xx.c | 28 1 file changed, 8 insertions(+), 20

Re: [PATCH] ARC: build: Turn off -Wmaybe-uninitialized for ARC gcc 4.8

On Friday 18 March 2016 14:16:23 Vineet Gupta wrote: > diff --git a/arch/arc/Makefile b/arch/arc/Makefile > index fed12f39d8ce..aeb101e8e674 100644 > --- a/arch/arc/Makefile > +++ b/arch/arc/Makefile > @@ -48,9 +48,14 @@ endif > upto_gcc44:= $(call cc-ifversion, -le, 0404, y) >

Re: [PATCH] ARC: build: Turn off -Wmaybe-uninitialized for ARC gcc 4.8

On Friday 18 March 2016 14:16:23 Vineet Gupta wrote: > diff --git a/arch/arc/Makefile b/arch/arc/Makefile > index fed12f39d8ce..aeb101e8e674 100644 > --- a/arch/arc/Makefile > +++ b/arch/arc/Makefile > @@ -48,9 +48,14 @@ endif > upto_gcc44:= $(call cc-ifversion, -le, 0404, y) >

Re: [PATCH V5 02/10] perf/amd/iommu: Consolidate and move perf_event_amd_iommu header

On Fri, Mar 18, 2016 at 04:09:33PM +0700, Suravee Suthikulpanit wrote: > But the whole point is that since we are moving it to consolidate these > duplicated declarations, I think we should just put it in the most common > place. The include/linux/amd-iommu.h file is already there. It's not like

Re: [PATCH V5 02/10] perf/amd/iommu: Consolidate and move perf_event_amd_iommu header

On Fri, Mar 18, 2016 at 04:09:33PM +0700, Suravee Suthikulpanit wrote: > But the whole point is that since we are moving it to consolidate these > duplicated declarations, I think we should just put it in the most common > place. The include/linux/amd-iommu.h file is already there. It's not like

[PATCH v4 6/8] arm64: dts: rockchip: Add power key to GeekBox

Cc: Julien Chauveau Signed-off-by: Andreas Färber --- v3 -> v4: * Renamed power button sub-node name (Julien) v2 -> v3: * Adopted wakeup-source instead of gpio-key,wakeup (Julien) * Dropped gpio-keys #address-cells and #size-cells properties

[PATCH v4 6/8] arm64: dts: rockchip: Add power key to GeekBox

Cc: Julien Chauveau Signed-off-by: Andreas Färber --- v3 -> v4: * Renamed power button sub-node name (Julien) v2 -> v3: * Adopted wakeup-source instead of gpio-key,wakeup (Julien) * Dropped gpio-keys #address-cells and #size-cells properties (Julien) * Dropped power button reg property

<    4   5   6   7   8   9   10   >