Re: [PATCH v3 1/2] Add sw2_sw4 voltage table to cpcap regulator.

On 07/24/2018 10:36 AM, Mark Brown wrote: On Tue, Jul 24, 2018 at 09:25:40AM -0400, Peter Geis wrote: SW2 and SW4 use a shared table to provide voltage to the cpu core and devices on Tegra hardware. Added this table to the cpcap regulator driver as the first step to supporting this device on

Re: [PATCH v3 1/2] Add sw2_sw4 voltage table to cpcap regulator.

On 07/24/2018 10:36 AM, Mark Brown wrote: On Tue, Jul 24, 2018 at 09:25:40AM -0400, Peter Geis wrote: SW2 and SW4 use a shared table to provide voltage to the cpu core and devices on Tegra hardware. Added this table to the cpcap regulator driver as the first step to supporting this device on

Re: [PATCH 09/10] psi: cgroup support

Hi Peter, On Tue, Jul 17, 2018 at 05:40:59PM +0200, Peter Zijlstra wrote: > On Thu, Jul 12, 2018 at 01:29:41PM -0400, Johannes Weiner wrote: > > +/** > > + * cgroup_move_task - move task to a different cgroup > > + * @task: the task > > + * @to: the target css_set > > + * > > + * Move task to a

Re: [PATCH 09/10] psi: cgroup support

Hi Peter, On Tue, Jul 17, 2018 at 05:40:59PM +0200, Peter Zijlstra wrote: > On Thu, Jul 12, 2018 at 01:29:41PM -0400, Johannes Weiner wrote: > > +/** > > + * cgroup_move_task - move task to a different cgroup > > + * @task: the task > > + * @to: the target css_set > > + * > > + * Move task to a

Re: [PATCH v2 10/12] sched/core: uclamp: use TG's clamps to restrict Task's clamps

On 24-Jul 08:28, Suren Baghdasaryan wrote: > Hi Patrick. Thanks for the explanation and links. No more questions > from me on this one :) No problems at all! The important question is instead: does it makes sense for you too? I think the important bits are that we are all on the same page about

Re: [PATCH v2 10/12] sched/core: uclamp: use TG's clamps to restrict Task's clamps

On 24-Jul 08:28, Suren Baghdasaryan wrote: > Hi Patrick. Thanks for the explanation and links. No more questions > from me on this one :) No problems at all! The important question is instead: does it makes sense for you too? I think the important bits are that we are all on the same page about

Re: [RFC v5 PATCH 2/2] mm: mmap: zap pages with read mmap_sem in munmap

On 7/24/18 2:26 AM, Kirill A. Shutemov wrote: On Thu, Jul 19, 2018 at 07:21:41AM +0800, Yang Shi wrote: When running some mmap/munmap scalability tests with large memory (i.e. 300GB), the below hung task issue may happen occasionally. INFO: task ps:14018 blocked for more than 120 seconds.

Re: [RFC v5 PATCH 2/2] mm: mmap: zap pages with read mmap_sem in munmap

On 7/24/18 2:26 AM, Kirill A. Shutemov wrote: On Thu, Jul 19, 2018 at 07:21:41AM +0800, Yang Shi wrote: When running some mmap/munmap scalability tests with large memory (i.e. 300GB), the below hung task issue may happen occasionally. INFO: task ps:14018 blocked for more than 120 seconds.

Re: [PATCH 00/15] ARM: dts: tegra: apalis-tk1: major revamp

On 07/24/2018 10:48 AM, Dmitry Osipenko wrote: On Tuesday, 24 July 2018 17:45:01 MSK Marcel Ziswiler wrote: On Tue, 2018-07-24 at 17:31 +0300, Dmitry Osipenko wrote: On Tuesday, 24 July 2018 17:16:33 MSK Marcel Ziswiler wrote: On Tue, 2018-07-24 at 15:44 +0300, Dmitry Osipenko wrote: On

Re: [PATCH 00/15] ARM: dts: tegra: apalis-tk1: major revamp

On 07/24/2018 10:48 AM, Dmitry Osipenko wrote: On Tuesday, 24 July 2018 17:45:01 MSK Marcel Ziswiler wrote: On Tue, 2018-07-24 at 17:31 +0300, Dmitry Osipenko wrote: On Tuesday, 24 July 2018 17:16:33 MSK Marcel Ziswiler wrote: On Tue, 2018-07-24 at 15:44 +0300, Dmitry Osipenko wrote: On

Re: [PATCH] thermal: samsung: Remove Exynos5440 clock handling left-overs

On Tuesday, July 17, 2018 05:46:17 PM Krzysztof Kozlowski wrote: > Commit 8014220d48e7 ("thermal: samsung: Remove support for Exynos5440") > removed the Exynos5440 specific part of code for accessing TMU interrupt > registers but the surrounding clock handling was left. > > Clean it up. > >

Re: [PATCH] thermal: samsung: Remove Exynos5440 clock handling left-overs

On Tuesday, July 17, 2018 05:46:17 PM Krzysztof Kozlowski wrote: > Commit 8014220d48e7 ("thermal: samsung: Remove support for Exynos5440") > removed the Exynos5440 specific part of code for accessing TMU interrupt > registers but the surrounding clock handling was left. > > Clean it up. > >

Re: [PATCH v9 1/2] regulator: dt-bindings: add QCOM RPMh regulator bindings

Hi, On Tue, Jul 24, 2018 at 8:25 AM, Mark Brown wrote: > On Tue, Jul 24, 2018 at 08:11:30AM -0700, Doug Anderson wrote: > >> RPMh itself landed in Andy's tree and he sent a pull request on >> Saturday. Feel free to refer to the request ("[GIT PULL] Qualcomm >> Driver updates for 4.19") AKA >>

Re: [PATCH v9 1/2] regulator: dt-bindings: add QCOM RPMh regulator bindings

Hi, On Tue, Jul 24, 2018 at 8:25 AM, Mark Brown wrote: > On Tue, Jul 24, 2018 at 08:11:30AM -0700, Doug Anderson wrote: > >> RPMh itself landed in Andy's tree and he sent a pull request on >> Saturday. Feel free to refer to the request ("[GIT PULL] Qualcomm >> Driver updates for 4.19") AKA >>

Re: [PATCH v2 08/12] sched/core: uclamp: extend cpu's cgroup controller

Hi Tejun, I apologize in advance for the (yet another) long reply, however I did my best hereafter to try to resume all the controversial points discussed so far. If you will have (one more time) the patience to go through the following text you'll find a set of precise clarifications and

Re: [PATCH v2 08/12] sched/core: uclamp: extend cpu's cgroup controller

Hi Tejun, I apologize in advance for the (yet another) long reply, however I did my best hereafter to try to resume all the controversial points discussed so far. If you will have (one more time) the patience to go through the following text you'll find a set of precise clarifications and

Re: ftrace global trace_pipe_raw

Hello Steve, thank you for your answer, On 07/24/2018 04:25 PM, Steven Rostedt wrote: > On Tue, 24 Jul 2018 10:23:16 -0400 > Steven Rostedt wrote: > >>> >>> Would work in the direction of adding a global trace_pipe_raw be considered >>> for inclusion? >> >> The design of the lockless ring

Re: ftrace global trace_pipe_raw

Hello Steve, thank you for your answer, On 07/24/2018 04:25 PM, Steven Rostedt wrote: > On Tue, 24 Jul 2018 10:23:16 -0400 > Steven Rostedt wrote: > >>> >>> Would work in the direction of adding a global trace_pipe_raw be considered >>> for inclusion? >> >> The design of the lockless ring

Re: [PATCH v2 10/12] sched/core: uclamp: use TG's clamps to restrict Task's clamps

Hi Patrick. Thanks for the explanation and links. No more questions from me on this one :) On Tue, Jul 24, 2018 at 2:56 AM, Patrick Bellasi wrote: > On 23-Jul 10:11, Suren Baghdasaryan wrote: >> On Mon, Jul 23, 2018 at 8:40 AM, Patrick Bellasi >> wrote: >> > On 21-Jul 20:05, Suren Baghdasaryan

Re: [PATCH v2 10/12] sched/core: uclamp: use TG's clamps to restrict Task's clamps

Hi Patrick. Thanks for the explanation and links. No more questions from me on this one :) On Tue, Jul 24, 2018 at 2:56 AM, Patrick Bellasi wrote: > On 23-Jul 10:11, Suren Baghdasaryan wrote: >> On Mon, Jul 23, 2018 at 8:40 AM, Patrick Bellasi >> wrote: >> > On 21-Jul 20:05, Suren Baghdasaryan

Re: [PATCH v9 1/2] regulator: dt-bindings: add QCOM RPMh regulator bindings

On Tue, Jul 24, 2018 at 08:11:30AM -0700, Doug Anderson wrote: > RPMh itself landed in Andy's tree and he sent a pull request on > Saturday. Feel free to refer to the request ("[GIT PULL] Qualcomm > Driver updates for 4.19") AKA > . > It doesn't

Re: [PATCH v9 1/2] regulator: dt-bindings: add QCOM RPMh regulator bindings

On Tue, Jul 24, 2018 at 08:11:30AM -0700, Doug Anderson wrote: > RPMh itself landed in Andy's tree and he sent a pull request on > Saturday. Feel free to refer to the request ("[GIT PULL] Qualcomm > Driver updates for 4.19") AKA > . > It doesn't

Re: [PATCH] Revert "ata: ahci_platform: convert kcalloc to devm_kcalloc"

On 18/07/18 07:30, Marcel Ziswiler wrote: > On Tue, 2018-07-17 at 13:57 +0300, Mikko Perttunen wrote: >> Thanks! > > Yes, that fixes Apalis TK1 crashing as of late as well. > >> Reviewed-by: Mikko Perttunen > > Tested-by: Marcel Ziswiler Tested-by: Jon Hunter Can someone pick this up?

Re: [PATCH] Revert "ata: ahci_platform: convert kcalloc to devm_kcalloc"

On 18/07/18 07:30, Marcel Ziswiler wrote: > On Tue, 2018-07-17 at 13:57 +0300, Mikko Perttunen wrote: >> Thanks! > > Yes, that fixes Apalis TK1 crashing as of late as well. > >> Reviewed-by: Mikko Perttunen > > Tested-by: Marcel Ziswiler Tested-by: Jon Hunter Can someone pick this up?

[PATCH v2] n_tty: Protect tty->disc_data using refcount.

>From 118c64e86641a97d44dec39e313a95b12d9bc3b2 Mon Sep 17 00:00:00 2001 From: Tetsuo Handa Date: Wed, 25 Jul 2018 00:15:18 +0900 Subject: [PATCH v2] n_tty: Protect tty->disc_data using refcount. syzbot is reporting NULL pointer dereference at n_tty_set_termios() [1]. This is because

[PATCH v2] n_tty: Protect tty->disc_data using refcount.

>From 118c64e86641a97d44dec39e313a95b12d9bc3b2 Mon Sep 17 00:00:00 2001 From: Tetsuo Handa Date: Wed, 25 Jul 2018 00:15:18 +0900 Subject: [PATCH v2] n_tty: Protect tty->disc_data using refcount. syzbot is reporting NULL pointer dereference at n_tty_set_termios() [1]. This is because

Re: INFO: task hung in fuse_reverse_inval_entry

On Mon, Jul 23, 2018 at 5:19 PM, Dmitry Vyukov wrote: > On Mon, Jul 23, 2018 at 5:09 PM, Miklos Szeredi wrote: >> On Mon, Jul 23, 2018 at 3:37 PM, Dmitry Vyukov wrote: >>> On Mon, Jul 23, 2018 at 3:05 PM, Miklos Szeredi wrote: >> Biggest conceptual problem: your definition of fuse-server

Re: INFO: task hung in fuse_reverse_inval_entry

On Mon, Jul 23, 2018 at 5:19 PM, Dmitry Vyukov wrote: > On Mon, Jul 23, 2018 at 5:09 PM, Miklos Szeredi wrote: >> On Mon, Jul 23, 2018 at 3:37 PM, Dmitry Vyukov wrote: >>> On Mon, Jul 23, 2018 at 3:05 PM, Miklos Szeredi wrote: >> Biggest conceptual problem: your definition of fuse-server

Re: [PATCH RT v2] arm64: fpsimd: use a local_lock() in addition to local_bh_disable()

On 24 July 2018 at 16:45, Dave Martin wrote: > On Wed, Jul 18, 2018 at 11:24:48AM +0200, Sebastian Andrzej Siewior wrote: >> On 2018-07-18 11:12:10 [+0200], To Dave Martin wrote: >> > > > - if (may_use_simd()) { >> > > > + if (!IS_ENABLED(CONFIG_PREEMPT_RT_BASE) && may_use_simd()) {

Re: [PATCH 6/7] x86/vdso: Add vDSO functions for user wait instructions

On Mon, Jul 23, 2018 at 7:11 PM, Andy Lutomirski wrote: > On 07/23/2018 05:55 AM, Fenghua Yu wrote: >> >> User wants to query if user wait instructions (umonitor, umwait, and >> tpause) are supported and use the instructions. The vDSO functions >> provides fast interface for user to check the

Re: [PATCH RT v2] arm64: fpsimd: use a local_lock() in addition to local_bh_disable()

On 24 July 2018 at 16:45, Dave Martin wrote: > On Wed, Jul 18, 2018 at 11:24:48AM +0200, Sebastian Andrzej Siewior wrote: >> On 2018-07-18 11:12:10 [+0200], To Dave Martin wrote: >> > > > - if (may_use_simd()) { >> > > > + if (!IS_ENABLED(CONFIG_PREEMPT_RT_BASE) && may_use_simd()) {

Re: [PATCH 6/7] x86/vdso: Add vDSO functions for user wait instructions

On Mon, Jul 23, 2018 at 7:11 PM, Andy Lutomirski wrote: > On 07/23/2018 05:55 AM, Fenghua Yu wrote: >> >> User wants to query if user wait instructions (umonitor, umwait, and >> tpause) are supported and use the instructions. The vDSO functions >> provides fast interface for user to check the

Re: [PATCH] arm64: enable RapidIO config options in Kconfig

On Tue, Jul 24, 2018 at 09:45:14AM -0400, Alexei Colin wrote: > ARM64 SoCs with a PCI bus present the RapiodIO options; SoCs with > RapidIO IP blocks but without a PCI bus, need to select HAS_RAPIDIO in > Kconfig.platforms. > > HAS_RAPIDIO was chosen over HAVE_RAPIDIO to be consistent with >

Re: [PATCH] arm64: enable RapidIO config options in Kconfig

On Tue, Jul 24, 2018 at 09:45:14AM -0400, Alexei Colin wrote: > ARM64 SoCs with a PCI bus present the RapiodIO options; SoCs with > RapidIO IP blocks but without a PCI bus, need to select HAS_RAPIDIO in > Kconfig.platforms. > > HAS_RAPIDIO was chosen over HAVE_RAPIDIO to be consistent with >

Re: [PATCH] [SUBMITTED 20180724] arm64: fix ACPI dependencies

On Tue, Jul 24, 2018 at 12:23:48PM +0200, Rafael J. Wysocki wrote: > On Tue, Jul 24, 2018 at 12:21 PM, Will Deacon wrote: > > On Tue, Jul 24, 2018 at 11:54:25AM +0200, Rafael J. Wysocki wrote: > >> On Tue, Jul 24, 2018 at 11:48 AM, Arnd Bergmann wrote: > >> > Kconfig reports a warning on x86

Re: [PATCH] [SUBMITTED 20180724] arm64: fix ACPI dependencies

On Tue, Jul 24, 2018 at 12:23:48PM +0200, Rafael J. Wysocki wrote: > On Tue, Jul 24, 2018 at 12:21 PM, Will Deacon wrote: > > On Tue, Jul 24, 2018 at 11:54:25AM +0200, Rafael J. Wysocki wrote: > >> On Tue, Jul 24, 2018 at 11:48 AM, Arnd Bergmann wrote: > >> > Kconfig reports a warning on x86

[PATCH v2] kthread, tracing: Don't expose half-written comm when creating kthreads

There is a window for racing when printing directly to task->comm, allowing other threads to see a non-terminated string. The vsnprintf function fills the buffer, counts the truncated chars, then finally writes the \0 at the end. creator other vsnprintf:

[PATCH v2] kthread, tracing: Don't expose half-written comm when creating kthreads

There is a window for racing when printing directly to task->comm, allowing other threads to see a non-terminated string. The vsnprintf function fills the buffer, counts the truncated chars, then finally writes the \0 at the end. creator other vsnprintf:

Re: [PATCH 0/10] psi: pressure stall information for CPU, memory, and IO v2

Hi Balbir, On Tue, Jul 24, 2018 at 07:14:02AM +1000, Balbir Singh wrote: > Does the mechanism scale? I am a little concerned about how frequently > this infrastructure is monitored/read/acted upon. I expect most users to poll in the frequency ballpark of the running averages (10s, 1m, 5m). Our

Re: [PATCH 0/10] psi: pressure stall information for CPU, memory, and IO v2

Hi Balbir, On Tue, Jul 24, 2018 at 07:14:02AM +1000, Balbir Singh wrote: > Does the mechanism scale? I am a little concerned about how frequently > this infrastructure is monitored/read/acted upon. I expect most users to poll in the frequency ballpark of the running averages (10s, 1m, 5m). Our

Re: [PATCH v3 5/8] proc/kcore: hold lock during read

eneric pata_acpi vmwgfx drm_kms_helper syscopyarea ahci sysfillrect libahci sysimgblt fb_sys_fops mptspi ata_piix ttm scsi_transport_spi mptscsih drm e1000 mptbase libata i2c_core serio_raw ipv6 crc_ccitt [ 43.517692] CPU: 0 PID: 7933 Comm: kexec Not tainted 4.18.0-rc6-next-20180724+ #715 [

Re: [PATCH v3 5/8] proc/kcore: hold lock during read

eneric pata_acpi vmwgfx drm_kms_helper syscopyarea ahci sysfillrect libahci sysimgblt fb_sys_fops mptspi ata_piix ttm scsi_transport_spi mptscsih drm e1000 mptbase libata i2c_core serio_raw ipv6 crc_ccitt [ 43.517692] CPU: 0 PID: 7933 Comm: kexec Not tainted 4.18.0-rc6-next-20180724+ #715 [

[PATCH v2] firmware: vpd: Fix section enabled flag on vpd_section_destroy

static struct ro_vpd and rw_vpd are initialized by vpd_sections_init() in vpd_probe() based on header's ro and rw sizes. In vpd_remove() vpd_section_destroy() performs deinitialization based on enabled flag, which is set to true by vpd_sections_init(). This leads to call of vpd_section_destroy()

[PATCH v2] firmware: vpd: Fix section enabled flag on vpd_section_destroy

static struct ro_vpd and rw_vpd are initialized by vpd_sections_init() in vpd_probe() based on header's ro and rw sizes. In vpd_remove() vpd_section_destroy() performs deinitialization based on enabled flag, which is set to true by vpd_sections_init(). This leads to call of vpd_section_destroy()

Re: [PATCH v9 1/2] regulator: dt-bindings: add QCOM RPMh regulator bindings

Hi, On Tue, Jul 24, 2018 at 7:57 AM, Mark Brown wrote: > On Mon, Jul 23, 2018 at 01:09:05PM -0700, Doug Anderson wrote: > >> I know you are still looking for time to review the RPMh-regulator >> driver and that's fine. One idea I had though: if the bindings look >> OK to you and are less

Re: [PATCH v9 1/2] regulator: dt-bindings: add QCOM RPMh regulator bindings

Hi, On Tue, Jul 24, 2018 at 7:57 AM, Mark Brown wrote: > On Mon, Jul 23, 2018 at 01:09:05PM -0700, Doug Anderson wrote: > >> I know you are still looking for time to review the RPMh-regulator >> driver and that's fine. One idea I had though: if the bindings look >> OK to you and are less

Re: [PATCH 1/3] [BUGFIX] tracing: Fix double free of event_trigger_data

On Mon, 23 Jul 2018 22:10:06 -0400 Steven Rostedt wrote: > On Sat, 14 Jul 2018 01:27:47 +0900 > Masami Hiramatsu wrote: > > > Fix a double free bug of event_trigger_data caused by > > calling unregister_trigger() from register_snapshot_trigger(). > > This kicks a kernel BUG if double free

Re: [PATCH 1/3] [BUGFIX] tracing: Fix double free of event_trigger_data

On Mon, 23 Jul 2018 22:10:06 -0400 Steven Rostedt wrote: > On Sat, 14 Jul 2018 01:27:47 +0900 > Masami Hiramatsu wrote: > > > Fix a double free bug of event_trigger_data caused by > > calling unregister_trigger() from register_snapshot_trigger(). > > This kicks a kernel BUG if double free

[tip:perf/urgent] MAINTAINERS: Add Naveen N. Rao as kprobes co-maintainer

Commit-ID: 4799f6856fdd38c8078a190eca3288029287cf66 Gitweb: https://git.kernel.org/tip/4799f6856fdd38c8078a190eca3288029287cf66 Author: Ananth N Mavinakayanahalli AuthorDate: Tue, 17 Jul 2018 11:32:37 +0530 Committer: Ingo Molnar CommitDate: Tue, 24 Jul 2018 17:01:28 +0200

[tip:perf/urgent] MAINTAINERS: Add Naveen N. Rao as kprobes co-maintainer

Commit-ID: 4799f6856fdd38c8078a190eca3288029287cf66 Gitweb: https://git.kernel.org/tip/4799f6856fdd38c8078a190eca3288029287cf66 Author: Ananth N Mavinakayanahalli AuthorDate: Tue, 17 Jul 2018 11:32:37 +0530 Committer: Ingo Molnar CommitDate: Tue, 24 Jul 2018 17:01:28 +0200

Re: [PATCHv4 01/12] atomic/tty: Fix up atomic abuse in ldsem

On Tue, Jul 24, 2018 at 03:40:48PM +0200, Ingo Molnar wrote: > > * Mark Rutland wrote: > > > > Ok, then these bits will have to wait until Greg's tree goes upstream > > > in about two weeks. > > > > Ok. > > > > > Which patches can I apply as a preparatory step? > > > > Patches 2-6 can be

Re: [PATCHv4 01/12] atomic/tty: Fix up atomic abuse in ldsem

On Tue, Jul 24, 2018 at 03:40:48PM +0200, Ingo Molnar wrote: > > * Mark Rutland wrote: > > > > Ok, then these bits will have to wait until Greg's tree goes upstream > > > in about two weeks. > > > > Ok. > > > > > Which patches can I apply as a preparatory step? > > > > Patches 2-6 can be

Re: [PATCH v3 07/18] dmaengine: dma-jz4780: Add support for the JZ4770 SoC

Hi Vinod, Le mar. 24 juil. 2018 à 15:32, Vinod a écrit : On 21-07-18, 13:06, Paul Cercueil wrote: +static inline void jz4780_dma_chan_enable(struct jz4780_dma_dev *jzdma, + unsigned int chn) right justified and aligned with preceding please. While adding new code to a existing

Re: [PATCH v3 07/18] dmaengine: dma-jz4780: Add support for the JZ4770 SoC

Hi Vinod, Le mar. 24 juil. 2018 à 15:32, Vinod a écrit : On 21-07-18, 13:06, Paul Cercueil wrote: +static inline void jz4780_dma_chan_enable(struct jz4780_dma_dev *jzdma, + unsigned int chn) right justified and aligned with preceding please. While adding new code to a existing

Re: [PATCH 02/10] mm: workingset: tell cache transitions from workingset thrashing

On Mon, Jul 23, 2018 at 12:27:35PM -0400, Johannes Weiner wrote: > On Mon, Jul 23, 2018 at 05:35:35PM +0200, Arnd Bergmann wrote: > > On Mon, Jul 23, 2018 at 5:23 PM, Johannes Weiner wrote: > > > diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c > > > index 1b18b4722420..72c9b6778b0a

Re: [PATCH 02/10] mm: workingset: tell cache transitions from workingset thrashing

On Mon, Jul 23, 2018 at 12:27:35PM -0400, Johannes Weiner wrote: > On Mon, Jul 23, 2018 at 05:35:35PM +0200, Arnd Bergmann wrote: > > On Mon, Jul 23, 2018 at 5:23 PM, Johannes Weiner wrote: > > > diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c > > > index 1b18b4722420..72c9b6778b0a

[tip:x86/urgent] x86/entry/64: Remove %ebx handling from error_entry/exit

Commit-ID: b3681dd548d06deb2e1573890829dff4b15abf46 Gitweb: https://git.kernel.org/tip/b3681dd548d06deb2e1573890829dff4b15abf46 Author: Andy Lutomirski AuthorDate: Sun, 22 Jul 2018 11:05:09 -0700 Committer: Ingo Molnar CommitDate: Tue, 24 Jul 2018 10:07:36 +0200 x86/entry/64: Remove

[tip:x86/urgent] x86/entry/64: Remove %ebx handling from error_entry/exit

Commit-ID: b3681dd548d06deb2e1573890829dff4b15abf46 Gitweb: https://git.kernel.org/tip/b3681dd548d06deb2e1573890829dff4b15abf46 Author: Andy Lutomirski AuthorDate: Sun, 22 Jul 2018 11:05:09 -0700 Committer: Ingo Molnar CommitDate: Tue, 24 Jul 2018 10:07:36 +0200 x86/entry/64: Remove

[PATCH 0/3] Add Actions Semi Owl family sirq support

This patch series add support for external interrupt controller in Actions Semi Owl famil of SoC's (S500, S700 and S900). Actions provides support for external interrupt controller to be connected with it's SoC's using 3 SIRQ pins. Each line can be configures independently, i.e 3 independent

[PATCH 0/3] Add Actions Semi Owl family sirq support

This patch series add support for external interrupt controller in Actions Semi Owl famil of SoC's (S500, S700 and S900). Actions provides support for external interrupt controller to be connected with it's SoC's using 3 SIRQ pins. Each line can be configures independently, i.e 3 independent

[tip:x86/urgent] x86/apic: Future-proof the TSC_DEADLINE quirk for SKX

Commit-ID: d9e6dbcf28f383bf08e6a3180972f5722e514a54 Gitweb: https://git.kernel.org/tip/d9e6dbcf28f383bf08e6a3180972f5722e514a54 Author: Len Brown AuthorDate: Sat, 21 Jul 2018 17:19:19 -0400 Committer: Ingo Molnar CommitDate: Tue, 24 Jul 2018 10:05:13 +0200 x86/apic: Future-proof the

[tip:x86/urgent] x86/apic: Future-proof the TSC_DEADLINE quirk for SKX

Commit-ID: d9e6dbcf28f383bf08e6a3180972f5722e514a54 Gitweb: https://git.kernel.org/tip/d9e6dbcf28f383bf08e6a3180972f5722e514a54 Author: Len Brown AuthorDate: Sat, 21 Jul 2018 17:19:19 -0400 Committer: Ingo Molnar CommitDate: Tue, 24 Jul 2018 10:05:13 +0200 x86/apic: Future-proof the

[PATCH 2/3] drivers/irqchip: Add Actions external interrupts support

Actions Semi Owl family SoC's S500, S700 and S900 provides support for 3 external interrupt controllers through SIRQ pins. Each line can be independently configured as interrupt or wake-up source, and triggers either on rising, falling or both edges. Each line can also be masked independently.

[PATCH 3/3] arm64: dts: actions: Add sirq node for Actions Semi S700

Add sirq node for Actions Semi S700 SoC with 3 SIRQ pins support, in which external interrupt controllers can be connected. Example: atc260x: atc2603c@65 { interrupt-parent = <>; interrupts = <2 IRQ_TYPE_LEVEL_HIGH>; }; Signed-off-by: Parthiban Nallathambi Signed-off-by:

[PATCH 2/3] drivers/irqchip: Add Actions external interrupts support

Actions Semi Owl family SoC's S500, S700 and S900 provides support for 3 external interrupt controllers through SIRQ pins. Each line can be independently configured as interrupt or wake-up source, and triggers either on rising, falling or both edges. Each line can also be masked independently.

[PATCH 3/3] arm64: dts: actions: Add sirq node for Actions Semi S700

Add sirq node for Actions Semi S700 SoC with 3 SIRQ pins support, in which external interrupt controllers can be connected. Example: atc260x: atc2603c@65 { interrupt-parent = <>; interrupts = <2 IRQ_TYPE_LEVEL_HIGH>; }; Signed-off-by: Parthiban Nallathambi Signed-off-by:

[PATCH 1/3] dt-bindings: interrupt-controller: Actions external interrupt controller

Actions Semi OWL family SoC's provides support for external interrupt controller to be connected and controlled using SIRQ pins. S500, S700 and S900 provides 3 SIRQ lines and works independently for 3 external interrupt controllers. Signed-off-by: Parthiban Nallathambi Signed-off-by: Saravanan

[PATCH 1/3] dt-bindings: interrupt-controller: Actions external interrupt controller

Actions Semi OWL family SoC's provides support for external interrupt controller to be connected and controlled using SIRQ pins. S500, S700 and S900 provides 3 SIRQ lines and works independently for 3 external interrupt controllers. Signed-off-by: Parthiban Nallathambi Signed-off-by: Saravanan

Re: [PATCH RESEND] kthread, tracing: Don't expose half-written comm when creating kthreads

On 07/24/2018 04:48 PM, Steven Rostedt wrote: > On Tue, 24 Jul 2018 10:17:37 +0200 > Snild Dolkow wrote: > >> creator other >> vsnprintf: >>fill (not terminated) >>count the restread/use comm > > I think it would be better to

Re: [PATCH RESEND] kthread, tracing: Don't expose half-written comm when creating kthreads

On 07/24/2018 04:48 PM, Steven Rostedt wrote: > On Tue, 24 Jul 2018 10:17:37 +0200 > Snild Dolkow wrote: > >> creator other >> vsnprintf: >>fill (not terminated) >>count the restread/use comm > > I think it would be better to

[tip:perf/urgent] perf/x86/amd/ibs: Don't access non-started event

Commit-ID: d2753e6b4882a637a0e8fb3b9c2e15f33265300e Gitweb: https://git.kernel.org/tip/d2753e6b4882a637a0e8fb3b9c2e15f33265300e Author: Thomas Gleixner AuthorDate: Fri, 20 Jul 2018 10:39:07 +0200 Committer: Ingo Molnar CommitDate: Tue, 24 Jul 2018 09:51:10 +0200 perf/x86/amd/ibs:

[tip:perf/urgent] perf/x86/amd/ibs: Don't access non-started event

Commit-ID: d2753e6b4882a637a0e8fb3b9c2e15f33265300e Gitweb: https://git.kernel.org/tip/d2753e6b4882a637a0e8fb3b9c2e15f33265300e Author: Thomas Gleixner AuthorDate: Fri, 20 Jul 2018 10:39:07 +0200 Committer: Ingo Molnar CommitDate: Tue, 24 Jul 2018 09:51:10 +0200 perf/x86/amd/ibs:

[tip:x86/mm] x86/mm/tlb: Make clear_asid_other() static

Commit-ID: 387048f51aecaa083e660fe0f15ad339354b116e Gitweb: https://git.kernel.org/tip/387048f51aecaa083e660fe0f15ad339354b116e Author: zhong jiang AuthorDate: Sat, 21 Jul 2018 15:55:32 +0800 Committer: Ingo Molnar CommitDate: Tue, 24 Jul 2018 09:52:32 +0200 x86/mm/tlb: Make

[tip:x86/mm] x86/mm/tlb: Make clear_asid_other() static

Commit-ID: 387048f51aecaa083e660fe0f15ad339354b116e Gitweb: https://git.kernel.org/tip/387048f51aecaa083e660fe0f15ad339354b116e Author: zhong jiang AuthorDate: Sat, 21 Jul 2018 15:55:32 +0800 Committer: Ingo Molnar CommitDate: Tue, 24 Jul 2018 09:52:32 +0200 x86/mm/tlb: Make

[tip:x86/cleanups] x86/platform/pcspeaker: Use PTR_ERR_OR_ZERO() to fix ptr_ret.cocci warning

Commit-ID: 2397134ce2d73dcf1d4846579f594c9f3880b2ec Gitweb: https://git.kernel.org/tip/2397134ce2d73dcf1d4846579f594c9f3880b2ec Author: YueHaibing AuthorDate: Fri, 20 Jul 2018 15:32:13 +0800 Committer: Ingo Molnar CommitDate: Tue, 24 Jul 2018 09:46:42 +0200 x86/platform/pcspeaker: Use

[tip:x86/cleanups] x86/platform/pcspeaker: Use PTR_ERR_OR_ZERO() to fix ptr_ret.cocci warning

Commit-ID: 2397134ce2d73dcf1d4846579f594c9f3880b2ec Gitweb: https://git.kernel.org/tip/2397134ce2d73dcf1d4846579f594c9f3880b2ec Author: YueHaibing AuthorDate: Fri, 20 Jul 2018 15:32:13 +0800 Committer: Ingo Molnar CommitDate: Tue, 24 Jul 2018 09:46:42 +0200 x86/platform/pcspeaker: Use

for your photos

I would like to speak with the person that managing photos for your company? We provide image editing like – photos cutting out and retouching. Enhancing your images is just a part of what we can do for your business. Whether you’re an ecommerce store or portrait photographer, real estate

for your photos

I would like to speak with the person that managing photos for your company? We provide image editing like – photos cutting out and retouching. Enhancing your images is just a part of what we can do for your business. Whether you’re an ecommerce store or portrait photographer, real estate

for your photos

I would like to speak with the person that managing photos for your company? We provide image editing like – photos cutting out and retouching. Enhancing your images is just a part of what we can do for your business. Whether you’re an ecommerce store or portrait photographer, real estate

for your photos

I would like to speak with the person that managing photos for your company? We provide image editing like – photos cutting out and retouching. Enhancing your images is just a part of what we can do for your business. Whether you’re an ecommerce store or portrait photographer, real estate

Re: [PATCH v1] tracing: Trivia spelling fix containerof() -> container_of()

On Mon, 23 Jul 2018 11:31:59 +0300 Andy Shevchenko wrote: > This is the only location on kernel that has wrong spelling > of the container_of() helper. Fix it. > > Signed-off-by: Andy Shevchenko Acked-by: Steven Rostedt (VMware) -- Steve > --- > kernel/trace/trace_printk.c | 2 +- > 1

Re: [PATCH v1] tracing: Trivia spelling fix containerof() -> container_of()

On Mon, 23 Jul 2018 11:31:59 +0300 Andy Shevchenko wrote: > This is the only location on kernel that has wrong spelling > of the container_of() helper. Fix it. > > Signed-off-by: Andy Shevchenko Acked-by: Steven Rostedt (VMware) -- Steve > --- > kernel/trace/trace_printk.c | 2 +- > 1

Re: [PATCH v9 1/2] regulator: dt-bindings: add QCOM RPMh regulator bindings

On Mon, Jul 23, 2018 at 01:09:05PM -0700, Doug Anderson wrote: > I know you are still looking for time to review the RPMh-regulator > driver and that's fine. One idea I had though: if the bindings look > OK to you and are less controversial, is there any chance they could > land in the meantime?

Re: [PATCH v9 1/2] regulator: dt-bindings: add QCOM RPMh regulator bindings

On Mon, Jul 23, 2018 at 01:09:05PM -0700, Doug Anderson wrote: > I know you are still looking for time to review the RPMh-regulator > driver and that's fine. One idea I had though: if the bindings look > OK to you and are less controversial, is there any chance they could > land in the meantime?

Re: [PATCH 1/2] sparc: move MSI related definitions to where they are used

Hi Thomas. > > > > The SPARC way to format comments follows netdev style. > > So put it all in one line and everyone are happy: > > Well, the code is being moved from arch/sparc to arch/sparc, so > apparently, it was already non-compliant to this specific coding style > rule. Should the

Re: [PATCH 1/2] sparc: move MSI related definitions to where they are used

Hi Thomas. > > > > The SPARC way to format comments follows netdev style. > > So put it all in one line and everyone are happy: > > Well, the code is being moved from arch/sparc to arch/sparc, so > apparently, it was already non-compliant to this specific coding style > rule. Should the

Re: [PATCH 01/28] ARM: tegra: apalis_t30: enable broken-hpi on emmc

On Tuesday, 24 July 2018 17:26:58 MSK Marcel Ziswiler wrote: > On Tue, 2018-07-24 at 17:03 +0300, Dmitry Osipenko wrote: > > > On Sunday, 22 July 2018 19:49:09 MSK Marcel Ziswiler wrote: > > > > > From: Marcel Ziswiler > > > > > > Avoid eMMC issues by specifying broken-hpi. > > > > > >

Re: [PATCH 01/28] ARM: tegra: apalis_t30: enable broken-hpi on emmc

On Tuesday, 24 July 2018 17:26:58 MSK Marcel Ziswiler wrote: > On Tue, 2018-07-24 at 17:03 +0300, Dmitry Osipenko wrote: > > > On Sunday, 22 July 2018 19:49:09 MSK Marcel Ziswiler wrote: > > > > > From: Marcel Ziswiler > > > > > > Avoid eMMC issues by specifying broken-hpi. > > > > > >

Re: [PATCH v2 5/5] arm64: dts: allwinner: h5: Add SID for H5

On Tue, 24 Jul 2018 16:42:18 +0200 Maxime Ripard wrote: > On Tue, Jul 24, 2018 at 03:34:32PM +0200, Emmanuel Vadot wrote: > > On Tue, 24 Jul 2018 15:00:04 +0200 > > Maxime Ripard wrote: > > > > > On Tue, Jul 24, 2018 at 12:15:22PM +0200, Emmanuel Vadot wrote: > > > > The SID controller on H5

Re: [PATCH v2 5/5] arm64: dts: allwinner: h5: Add SID for H5

On Tue, 24 Jul 2018 16:42:18 +0200 Maxime Ripard wrote: > On Tue, Jul 24, 2018 at 03:34:32PM +0200, Emmanuel Vadot wrote: > > On Tue, 24 Jul 2018 15:00:04 +0200 > > Maxime Ripard wrote: > > > > > On Tue, Jul 24, 2018 at 12:15:22PM +0200, Emmanuel Vadot wrote: > > > > The SID controller on H5

Re: [PATCH] cpu/hotplug: Fix cpuhp_step name for timers

Hi All, Please review V2 where i will be updating(minor) commit text. Thanks. Mukesh On 7/24/2018 8:07 PM, Mukesh Ojha wrote: After commit 249d4a9b3246 ("timers: Reinitialize per cpu bases on hotplug") i.e introduction of state CPUHP_TIMERS_PREPARE instead of CPUHP_TIMERS_DEAD the cpuhp_step

Re: [PATCH] cpu/hotplug: Fix cpuhp_step name for timers

Hi All, Please review V2 where i will be updating(minor) commit text. Thanks. Mukesh On 7/24/2018 8:07 PM, Mukesh Ojha wrote: After commit 249d4a9b3246 ("timers: Reinitialize per cpu bases on hotplug") i.e introduction of state CPUHP_TIMERS_PREPARE instead of CPUHP_TIMERS_DEAD the cpuhp_step

Re: [PATCH 00/15] ARM: dts: tegra: apalis-tk1: major revamp

On Tuesday, 24 July 2018 17:45:01 MSK Marcel Ziswiler wrote: > On Tue, 2018-07-24 at 17:31 +0300, Dmitry Osipenko wrote: > > > On Tuesday, 24 July 2018 17:16:33 MSK Marcel Ziswiler wrote: > > > > > On Tue, 2018-07-24 at 15:44 +0300, Dmitry Osipenko wrote: > > > > > > > > > > On Tuesday, 24

Re: [PATCH RESEND] kthread, tracing: Don't expose half-written comm when creating kthreads

On Tue, 24 Jul 2018 10:17:37 +0200 Snild Dolkow wrote: > On 07/23/2018 06:41 PM, Steven Rostedt wrote: > > On Mon, 23 Jul 2018 17:49:36 +0200 > > Snild Dolkow wrote: > >> Any issues with the commit message? Reading it back again now, it doesn't > >> seem quite as clear as when I wrote it. >

[PATCH v2] cpu/hotplug: Fix cpuhp_step name for timers

After commit 249d4a9b3246 ("timers: Reinitialize per cpu bases on hotplug") i.e introduction of state CPUHP_TIMERS_PREPARE instead of CPUHP_TIMERS_DEAD the cpuhp_step name "timers:dead" for timer looks to be invalid. So, better to name it as "timers:prepare". Signed-off-by: Mukesh Ojha Cc:

Re: [PATCH 00/15] ARM: dts: tegra: apalis-tk1: major revamp

On Tuesday, 24 July 2018 17:45:01 MSK Marcel Ziswiler wrote: > On Tue, 2018-07-24 at 17:31 +0300, Dmitry Osipenko wrote: > > > On Tuesday, 24 July 2018 17:16:33 MSK Marcel Ziswiler wrote: > > > > > On Tue, 2018-07-24 at 15:44 +0300, Dmitry Osipenko wrote: > > > > > > > > > > On Tuesday, 24

Re: [PATCH RESEND] kthread, tracing: Don't expose half-written comm when creating kthreads

On Tue, 24 Jul 2018 10:17:37 +0200 Snild Dolkow wrote: > On 07/23/2018 06:41 PM, Steven Rostedt wrote: > > On Mon, 23 Jul 2018 17:49:36 +0200 > > Snild Dolkow wrote: > >> Any issues with the commit message? Reading it back again now, it doesn't > >> seem quite as clear as when I wrote it. >

[PATCH v2] cpu/hotplug: Fix cpuhp_step name for timers

After commit 249d4a9b3246 ("timers: Reinitialize per cpu bases on hotplug") i.e introduction of state CPUHP_TIMERS_PREPARE instead of CPUHP_TIMERS_DEAD the cpuhp_step name "timers:dead" for timer looks to be invalid. So, better to name it as "timers:prepare". Signed-off-by: Mukesh Ojha Cc:

Re: [PATCH RT v2] arm64: fpsimd: use a local_lock() in addition to local_bh_disable()

On Wed, Jul 18, 2018 at 11:24:48AM +0200, Sebastian Andrzej Siewior wrote: > On 2018-07-18 11:12:10 [+0200], To Dave Martin wrote: > > > > - if (may_use_simd()) { > > > > + if (!IS_ENABLED(CONFIG_PREEMPT_RT_BASE) && may_use_simd()) { > > > > > > I suspect this is wrong -- see comments

Re: [PATCH RT v2] arm64: fpsimd: use a local_lock() in addition to local_bh_disable()

On Wed, Jul 18, 2018 at 11:24:48AM +0200, Sebastian Andrzej Siewior wrote: > On 2018-07-18 11:12:10 [+0200], To Dave Martin wrote: > > > > - if (may_use_simd()) { > > > > + if (!IS_ENABLED(CONFIG_PREEMPT_RT_BASE) && may_use_simd()) { > > > > > > I suspect this is wrong -- see comments

<    3   4   5   6   7   8   9   10   11   12   >