Re: [PATCH 2/2] ARM: Wrap '--pic-veneer' with ld-option

On Wed, Dec 5, 2018 at 12:10 AM Ard Biesheuvel wrote: > > (+ Arnd) > > On Wed, 5 Dec 2018 at 09:06, Nathan Chancellor > wrote: > > > > On Wed, Dec 05, 2018 at 08:37:05AM +0100, Ard Biesheuvel wrote: > > > On Wed, 5 Dec 2018 at 02:42, Nathan Chancellor > > > wrote: > > > > > > > > This flag is

Re: [PATCH 2/2] ARM: Wrap '--pic-veneer' with ld-option

On Wed, Dec 5, 2018 at 12:10 AM Ard Biesheuvel wrote: > > (+ Arnd) > > On Wed, 5 Dec 2018 at 09:06, Nathan Chancellor > wrote: > > > > On Wed, Dec 05, 2018 at 08:37:05AM +0100, Ard Biesheuvel wrote: > > > On Wed, 5 Dec 2018 at 02:42, Nathan Chancellor > > > wrote: > > > > > > > > This flag is

Re: [PATCH v3] signal: add procfd_send_signal() syscall

Christian Brauner writes: > The kill() syscall operates on process identifiers (pid). After a process > has exited its pid can be reused by another process. If a caller sends a > signal to a reused pid it will end up signaling the wrong process. This > issue has often surfaced and there has been

Re: [PATCH v3] signal: add procfd_send_signal() syscall

Christian Brauner writes: > The kill() syscall operates on process identifiers (pid). After a process > has exited its pid can be reused by another process. If a caller sends a > signal to a reused pid it will end up signaling the wrong process. This > issue has often surfaced and there has been

Re: [GIT PULL] MFD fixes for v4.20

The pull request you sent on Wed, 5 Dec 2018 10:08:56 +: > git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git mfd-fixes-4.20 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/5e0dc1a7ce1f322c06e993845def2c73cfc485fd Thank you! -- Deet-doot-dot, I am a bot.

Re: [GIT PULL] MFD fixes for v4.20

The pull request you sent on Wed, 5 Dec 2018 10:08:56 +: > git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git mfd-fixes-4.20 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/5e0dc1a7ce1f322c06e993845def2c73cfc485fd Thank you! -- Deet-doot-dot, I am a bot.

Re: [GIT PULL] parisc architecture fix for kernel v4.20-rc6

The pull request you sent on Tue, 4 Dec 2018 16:00:32 +0100: > git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git > parisc-4.20-4 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/a517af52cb57f972cee2378765e1c5dd10141f0d Thank you! --

Re: [RFC PATCH 02/14] mm/hms: heterogenenous memory system (HMS) documentation

On 2018-12-05 11:07 a.m., Jerome Glisse wrote: >> Well multiple links are easy when you have a 'link' bus. Just add >> another link device under the bus. > > So you are telling do what i am doing in this patchset but not under > HMS directory ? No, it's completely different. I'm talking about

Re: [RFC PATCH 02/14] mm/hms: heterogenenous memory system (HMS) documentation

On 2018-12-05 11:07 a.m., Jerome Glisse wrote: >> Well multiple links are easy when you have a 'link' bus. Just add >> another link device under the bus. > > So you are telling do what i am doing in this patchset but not under > HMS directory ? No, it's completely different. I'm talking about

Re: [GIT PULL] parisc architecture fix for kernel v4.20-rc6

The pull request you sent on Tue, 4 Dec 2018 16:00:32 +0100: > git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git > parisc-4.20-4 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/a517af52cb57f972cee2378765e1c5dd10141f0d Thank you! --

Re: [GIT PULL] Power management fix for v4.20-rc6

The pull request you sent on Wed, 5 Dec 2018 12:53:50 +0100: > git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git pm-4.20-rc6 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/91dd51f6e7ce7f1eba5d7b583790e134367d0fbb Thank you! -- Deet-doot-dot, I am a

Re: [GIT PULL] Power management fix for v4.20-rc6

The pull request you sent on Wed, 5 Dec 2018 12:53:50 +0100: > git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git pm-4.20-rc6 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/91dd51f6e7ce7f1eba5d7b583790e134367d0fbb Thank you! -- Deet-doot-dot, I am a

Re: [git pull] Input updates for v4.20-rc5

The pull request you sent on Mon, 3 Dec 2018 19:37:46 -0800: > git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/adac0753c25217a2365b132c87cb2540b51fa89b Thank you! -- Deet-doot-dot, I am a bot.

Re: [git pull] Input updates for v4.20-rc5

The pull request you sent on Mon, 3 Dec 2018 19:37:46 -0800: > git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/adac0753c25217a2365b132c87cb2540b51fa89b Thank you! -- Deet-doot-dot, I am a bot.

Re: [PATCH v3] signal: add procfd_send_signal() syscall

Christian Brauner writes: > The kill() syscall operates on process identifiers (pid). After a process > has exited its pid can be reused by another process. If a caller sends a > signal to a reused pid it will end up signaling the wrong process. This > issue has often surfaced and there has been

Re: [PATCH v3] signal: add procfd_send_signal() syscall

Christian Brauner writes: > The kill() syscall operates on process identifiers (pid). After a process > has exited its pid can be reused by another process. If a caller sends a > signal to a reused pid it will end up signaling the wrong process. This > issue has often surfaced and there has been

Re: [PATCH 2/5] ARC: perf: introduce Kernel PMU events support

On 12/5/18 9:06 AM, Eugeniy Paltsev wrote: > Export all available ARC architected hardware events as > kernel PMU events to make non-generic events accessible. > > ARC PMU HW allow us to read the list of all available > events names. So we generate kernel PMU event list > dynamically in

Re: [PATCH 2/5] ARC: perf: introduce Kernel PMU events support

On 12/5/18 9:06 AM, Eugeniy Paltsev wrote: > Export all available ARC architected hardware events as > kernel PMU events to make non-generic events accessible. > > ARC PMU HW allow us to read the list of all available > events names. So we generate kernel PMU event list > dynamically in

Re: [PATCH v2 00/22] mfd: demodularization of non-modular drivers

[RE: [PATCH v2 00/22] mfd: demodularization of non-modular drivers] On 05/12/2018 (Wed 12:01) Steve Twiss wrote: > Hi Paul, > > On 03 December 2018 04:23, Paul Gortmaker wrote: > > > Subject: [PATCH v2 00/22] mfd: demodularization of non-modular drivers > > > > [v1 --> v2: add some more

Re: [PATCH v2 00/22] mfd: demodularization of non-modular drivers

[RE: [PATCH v2 00/22] mfd: demodularization of non-modular drivers] On 05/12/2018 (Wed 12:01) Steve Twiss wrote: > Hi Paul, > > On 03 December 2018 04:23, Paul Gortmaker wrote: > > > Subject: [PATCH v2 00/22] mfd: demodularization of non-modular drivers > > > > [v1 --> v2: add some more

Re: Re: Re: [PATCH] proc/sysctl: fix return error forproc_doulongvec_minmax

On Wed, Dec 05, 2018 at 03:10:07PM +0800, cheng.lin...@zte.com.cn wrote: > > On Mon, Dec 03, 2018 at 01:12:39PM +0800, cheng.lin...@zte.com.cn wrote: > > > >Cheng, thanks for the patch! > > > > > > > >On Fri, Nov 30, 2018 at 02:35:17PM +0800, Cheng Lin wrote: > > > >> If the number of input

Re: Re: Re: [PATCH] proc/sysctl: fix return error forproc_doulongvec_minmax

On Wed, Dec 05, 2018 at 03:10:07PM +0800, cheng.lin...@zte.com.cn wrote: > > On Mon, Dec 03, 2018 at 01:12:39PM +0800, cheng.lin...@zte.com.cn wrote: > > > >Cheng, thanks for the patch! > > > > > > > >On Fri, Nov 30, 2018 at 02:35:17PM +0800, Cheng Lin wrote: > > > >> If the number of input

Re: [RFC PATCH 02/14] mm/hms: heterogenenous memory system (HMS) documentation

On Wed, Dec 05, 2018 at 10:41:56AM -0700, Logan Gunthorpe wrote: > > > On 2018-12-04 7:31 p.m., Jerome Glisse wrote: > > How can i express multiple link, or memory that is only accessible > > by a subset of the devices/CPUs. In today model they are back in > > assumption like everyone can access

Re: [RFC PATCH 02/14] mm/hms: heterogenenous memory system (HMS) documentation

On Wed, Dec 05, 2018 at 10:41:56AM -0700, Logan Gunthorpe wrote: > > > On 2018-12-04 7:31 p.m., Jerome Glisse wrote: > > How can i express multiple link, or memory that is only accessible > > by a subset of the devices/CPUs. In today model they are back in > > assumption like everyone can access

[tip:x86/mm] x86/mm: Drop usage of __flush_tlb_all() in kernel_physical_mapping_init()

Commit-ID: ba6f508d0ec4adb09f0a939af6d5e19cdfa8667d Gitweb: https://git.kernel.org/tip/ba6f508d0ec4adb09f0a939af6d5e19cdfa8667d Author: Dan Williams AuthorDate: Tue, 4 Dec 2018 13:37:27 -0800 Committer: Ingo Molnar CommitDate: Wed, 5 Dec 2018 09:03:07 +0100 x86/mm: Drop usage of

[tip:x86/mm] x86/mm: Drop usage of __flush_tlb_all() in kernel_physical_mapping_init()

Commit-ID: ba6f508d0ec4adb09f0a939af6d5e19cdfa8667d Gitweb: https://git.kernel.org/tip/ba6f508d0ec4adb09f0a939af6d5e19cdfa8667d Author: Dan Williams AuthorDate: Tue, 4 Dec 2018 13:37:27 -0800 Committer: Ingo Molnar CommitDate: Wed, 5 Dec 2018 09:03:07 +0100 x86/mm: Drop usage of

[tip:x86/mm] generic/pgtable: Introduce set_pte_safe()

Commit-ID: 4369deaa2f022ef92da45a0e7eec8a4a52e8e8a4 Gitweb: https://git.kernel.org/tip/4369deaa2f022ef92da45a0e7eec8a4a52e8e8a4 Author: Dan Williams AuthorDate: Tue, 4 Dec 2018 13:37:16 -0800 Committer: Ingo Molnar CommitDate: Wed, 5 Dec 2018 09:03:06 +0100 generic/pgtable: Introduce

[tip:x86/mm] generic/pgtable: Introduce set_pte_safe()

Commit-ID: 4369deaa2f022ef92da45a0e7eec8a4a52e8e8a4 Gitweb: https://git.kernel.org/tip/4369deaa2f022ef92da45a0e7eec8a4a52e8e8a4 Author: Dan Williams AuthorDate: Tue, 4 Dec 2018 13:37:16 -0800 Committer: Ingo Molnar CommitDate: Wed, 5 Dec 2018 09:03:06 +0100 generic/pgtable: Introduce

[tip:x86/mm] x86/mm: Validate kernel_physical_mapping_init() PTE population

Commit-ID: 0a9fe8ca844d43f3f547f0e166122b6048121c8f Gitweb: https://git.kernel.org/tip/0a9fe8ca844d43f3f547f0e166122b6048121c8f Author: Dan Williams AuthorDate: Tue, 4 Dec 2018 13:37:21 -0800 Committer: Ingo Molnar CommitDate: Wed, 5 Dec 2018 09:03:06 +0100 x86/mm: Validate

[tip:x86/mm] x86/mm: Validate kernel_physical_mapping_init() PTE population

Commit-ID: 0a9fe8ca844d43f3f547f0e166122b6048121c8f Gitweb: https://git.kernel.org/tip/0a9fe8ca844d43f3f547f0e166122b6048121c8f Author: Dan Williams AuthorDate: Tue, 4 Dec 2018 13:37:21 -0800 Committer: Ingo Molnar CommitDate: Wed, 5 Dec 2018 09:03:06 +0100 x86/mm: Validate

[tip:x86/asm] x86/vdso: Remove a stale/misleading comment from the linker script

Commit-ID: 29434801e7e9c6d05fbea4533b3c0bd6be612f62 Gitweb: https://git.kernel.org/tip/29434801e7e9c6d05fbea4533b3c0bd6be612f62 Author: Sean Christopherson AuthorDate: Tue, 4 Dec 2018 13:25:58 -0800 Committer: Ingo Molnar CommitDate: Wed, 5 Dec 2018 08:58:12 +0100 x86/vdso: Remove a

[tip:x86/asm] x86/vdso: Remove a stale/misleading comment from the linker script

Commit-ID: 29434801e7e9c6d05fbea4533b3c0bd6be612f62 Gitweb: https://git.kernel.org/tip/29434801e7e9c6d05fbea4533b3c0bd6be612f62 Author: Sean Christopherson AuthorDate: Tue, 4 Dec 2018 13:25:58 -0800 Committer: Ingo Molnar CommitDate: Wed, 5 Dec 2018 08:58:12 +0100 x86/vdso: Remove a

[tip:x86/mm] generic/pgtable: Introduce {p4d,pgd}_same()

Commit-ID: 0cebbb60f759a709dabb3c87b9704f9844878850 Gitweb: https://git.kernel.org/tip/0cebbb60f759a709dabb3c87b9704f9844878850 Author: Dan Williams AuthorDate: Tue, 4 Dec 2018 13:37:11 -0800 Committer: Ingo Molnar CommitDate: Wed, 5 Dec 2018 09:03:06 +0100 generic/pgtable: Introduce

[tip:x86/mm] generic/pgtable: Introduce {p4d,pgd}_same()

Commit-ID: 0cebbb60f759a709dabb3c87b9704f9844878850 Gitweb: https://git.kernel.org/tip/0cebbb60f759a709dabb3c87b9704f9844878850 Author: Dan Williams AuthorDate: Tue, 4 Dec 2018 13:37:11 -0800 Committer: Ingo Molnar CommitDate: Wed, 5 Dec 2018 09:03:06 +0100 generic/pgtable: Introduce

[tip:x86/mm] generic/pgtable: Make {pmd, pud}_same() unconditionally available

Commit-ID: c683c37cd13246941924c48f6c6a9863425e0cec Gitweb: https://git.kernel.org/tip/c683c37cd13246941924c48f6c6a9863425e0cec Author: Dan Williams AuthorDate: Tue, 4 Dec 2018 13:37:06 -0800 Committer: Ingo Molnar CommitDate: Wed, 5 Dec 2018 09:03:05 +0100 generic/pgtable: Make {pmd,

[tip:x86/mm] generic/pgtable: Make {pmd, pud}_same() unconditionally available

Commit-ID: c683c37cd13246941924c48f6c6a9863425e0cec Gitweb: https://git.kernel.org/tip/c683c37cd13246941924c48f6c6a9863425e0cec Author: Dan Williams AuthorDate: Tue, 4 Dec 2018 13:37:06 -0800 Committer: Ingo Molnar CommitDate: Wed, 5 Dec 2018 09:03:05 +0100 generic/pgtable: Make {pmd,

[tip:x86/asm] x86/vdso: Remove obsolete "fake section table" reservation

Commit-ID: 24b7c77bbb24f129beead93574ff248c3db1288e Gitweb: https://git.kernel.org/tip/24b7c77bbb24f129beead93574ff248c3db1288e Author: Sean Christopherson AuthorDate: Tue, 4 Dec 2018 13:25:57 -0800 Committer: Ingo Molnar CommitDate: Wed, 5 Dec 2018 08:58:11 +0100 x86/vdso: Remove

[tip:x86/asm] x86/vdso: Remove obsolete "fake section table" reservation

Commit-ID: 24b7c77bbb24f129beead93574ff248c3db1288e Gitweb: https://git.kernel.org/tip/24b7c77bbb24f129beead93574ff248c3db1288e Author: Sean Christopherson AuthorDate: Tue, 4 Dec 2018 13:25:57 -0800 Committer: Ingo Molnar CommitDate: Wed, 5 Dec 2018 08:58:11 +0100 x86/vdso: Remove

Re: [PATCH v1 5/5] perf cs-etm: Track exception number

On Tue, 4 Dec 2018 at 20:49, wrote: > > On Mon, Nov 19, 2018 at 01:47:49PM -0700, Mathieu Poirier wrote: > > On Sun, Nov 11, 2018 at 12:59:43PM +0800, Leo Yan wrote: > > > When an exception packet comes, it contains the info for exception > > > number; the exception number indicates the exception

Re: [PATCH v1 5/5] perf cs-etm: Track exception number

On Tue, 4 Dec 2018 at 20:49, wrote: > > On Mon, Nov 19, 2018 at 01:47:49PM -0700, Mathieu Poirier wrote: > > On Sun, Nov 11, 2018 at 12:59:43PM +0800, Leo Yan wrote: > > > When an exception packet comes, it contains the info for exception > > > number; the exception number indicates the exception

Re: [PATCH] x86/mce: Streamline MCE subsystem's naming

* Borislav Petkov wrote: > On Wed, Dec 05, 2018 at 05:30:37PM +0100, Ingo Molnar wrote: > > Would it make sense to organize it a bit more and separate out vendor > > specific functionality: > > > > mce/cpu/intel.c > > mce/cpu/intel-p5.c > > mce/cpu/amd.c > > mce/cpu/winchip.c > >

Re: [PATCH] x86/mce: Streamline MCE subsystem's naming

* Borislav Petkov wrote: > On Wed, Dec 05, 2018 at 05:30:37PM +0100, Ingo Molnar wrote: > > Would it make sense to organize it a bit more and separate out vendor > > specific functionality: > > > > mce/cpu/intel.c > > mce/cpu/intel-p5.c > > mce/cpu/amd.c > > mce/cpu/winchip.c > >

Re: [RFC PATCH 02/14] mm/hms: heterogenenous memory system (HMS) documentation

On Wed, Dec 05, 2018 at 10:25:31AM -0700, Logan Gunthorpe wrote: > > > On 2018-12-04 7:37 p.m., Jerome Glisse wrote: > >> > >> This came up before for apis even better defined than HMS as well as > >> more limited scope, i.e. experimental ABI availability only for -rc > >> kernels. Linus said

Re: [RFC PATCH 02/14] mm/hms: heterogenenous memory system (HMS) documentation

On Wed, Dec 05, 2018 at 10:25:31AM -0700, Logan Gunthorpe wrote: > > > On 2018-12-04 7:37 p.m., Jerome Glisse wrote: > >> > >> This came up before for apis even better defined than HMS as well as > >> more limited scope, i.e. experimental ABI availability only for -rc > >> kernels. Linus said

Re: [PATCH v6 0/8] AXP8x3 AC and battery power supply support

Hi, On Fri, Nov 30, 2018 at 04:31:28PM +0800, Chen-Yu Tsai wrote: > On Wed, Nov 21, 2018 at 1:52 AM Oskari Lemmela wrote: > > > > AXP813 AC power supply support with input current and > > voltage limiting support. > > > > AXP803 AC and battery power supply support. > > > > Changes in v6: > > *

Re: [PATCH v6 0/8] AXP8x3 AC and battery power supply support

Hi, On Fri, Nov 30, 2018 at 04:31:28PM +0800, Chen-Yu Tsai wrote: > On Wed, Nov 21, 2018 at 1:52 AM Oskari Lemmela wrote: > > > > AXP813 AC power supply support with input current and > > voltage limiting support. > > > > AXP803 AC and battery power supply support. > > > > Changes in v6: > > *

Re: edac driver injection of uncorrected errors & utils

On 12/5/18 8:38 AM, Tracy Smith wrote: > This is more directed toward York for layerscape. I see some edac code > that seem to do periodic scrubs based on intervals or scrub rate, but > that is not needed for the layerscape driver to correct errors because > errors are scrubbed when found by the

Re: edac driver injection of uncorrected errors & utils

On 12/5/18 8:38 AM, Tracy Smith wrote: > This is more directed toward York for layerscape. I see some edac code > that seem to do periodic scrubs based on intervals or scrub rate, but > that is not needed for the layerscape driver to correct errors because > errors are scrubbed when found by the

Re: [PATCH] auxdisplay: charlcd: fix x/y command parsing

Miguel Ojeda writes: > Hi Mans, > > [CC'ing a few people involved previously on this] > > On Wed, Dec 5, 2018 at 2:53 PM Mans Rullgard wrote: >> >> Commit b34050fadb86 ("auxdisplay: charlcd: Fix and clean up handling of >> x/y commands") fixed some problems by rewriting the parsing code, >> but

Re: [PATCH] auxdisplay: charlcd: fix x/y command parsing

Miguel Ojeda writes: > Hi Mans, > > [CC'ing a few people involved previously on this] > > On Wed, Dec 5, 2018 at 2:53 PM Mans Rullgard wrote: >> >> Commit b34050fadb86 ("auxdisplay: charlcd: Fix and clean up handling of >> x/y commands") fixed some problems by rewriting the parsing code, >> but

Re: [PATCH 1/8] perf: Allow to block process in syscall tracepoints

On Wed, Dec 05, 2018 at 12:35:03PM -0500, Steven Rostedt wrote: > On Wed, 5 Dec 2018 17:05:02 +0100 > Jiri Olsa wrote: > > > diff --git a/arch/x86/entry/common.c b/arch/x86/entry/common.c > > index 3b2490b81918..e55cf9169a03 100644 > > --- a/arch/x86/entry/common.c > > +++

Re: [PATCH 1/8] perf: Allow to block process in syscall tracepoints

On Wed, Dec 05, 2018 at 12:35:03PM -0500, Steven Rostedt wrote: > On Wed, 5 Dec 2018 17:05:02 +0100 > Jiri Olsa wrote: > > > diff --git a/arch/x86/entry/common.c b/arch/x86/entry/common.c > > index 3b2490b81918..e55cf9169a03 100644 > > --- a/arch/x86/entry/common.c > > +++

Re: [RFC PATCH 00/14] Heterogeneous Memory System (HMS) and hbind()

On Wed, Dec 05, 2018 at 09:27:09AM -0800, Dave Hansen wrote: > On 12/4/18 6:13 PM, Jerome Glisse wrote: > > On Tue, Dec 04, 2018 at 05:06:49PM -0800, Dave Hansen wrote: > >> OK, but there are 1024*1024 matrix cells on a systems with 1024 > >> proximity domains (ACPI term for NUMA node). So it

Re: [RFC PATCH 00/14] Heterogeneous Memory System (HMS) and hbind()

On Wed, Dec 05, 2018 at 09:27:09AM -0800, Dave Hansen wrote: > On 12/4/18 6:13 PM, Jerome Glisse wrote: > > On Tue, Dec 04, 2018 at 05:06:49PM -0800, Dave Hansen wrote: > >> OK, but there are 1024*1024 matrix cells on a systems with 1024 > >> proximity domains (ACPI term for NUMA node). So it

Re: [RFT PATCH v1 0/4] Unify CPU topology across ARM64 & RISC-V

On 11/29/2018 4:28 PM, Atish Patra wrote: The cpu-map DT entry in ARM64 can describe the CPU topology in much better way compared to other existing approaches. RISC-V can easily adopt this binding to represent it's own CPU topology. Thus, both cpu-map DT binding and topology parsing code can be

Re: [RFT PATCH v1 0/4] Unify CPU topology across ARM64 & RISC-V

On 11/29/2018 4:28 PM, Atish Patra wrote: The cpu-map DT entry in ARM64 can describe the CPU topology in much better way compared to other existing approaches. RISC-V can easily adopt this binding to represent it's own CPU topology. Thus, both cpu-map DT binding and topology parsing code can be

Re: [PATCH v2 2/2] soc: fsl: dpio: use a cpumask to identify which cpus are unused

On Tue, Dec 4, 2018 at 5:23 AM Ioana Ciornei wrote: > > The current implementation of the dpio driver uses a static next_cpu > variable to keep track of the index of the next cpu available. This > approach does not handle well unbinding and binding dpio devices in a > random order. For example,

Re: [PATCH v2 2/2] soc: fsl: dpio: use a cpumask to identify which cpus are unused

On Tue, Dec 4, 2018 at 5:23 AM Ioana Ciornei wrote: > > The current implementation of the dpio driver uses a static next_cpu > variable to keep track of the index of the next cpu available. This > approach does not handle well unbinding and binding dpio devices in a > random order. For example,

Re: [PATCH v2 1/2] soc: fsl: dpio: cleanup the cpu array on dpaa2_io_down

On Tue, Dec 4, 2018 at 5:21 AM Ioana Ciornei wrote: > > The dpio_by_cpu array should not contain a reference to a freed dpaa2_io > object. This patch adds the necessary cleanup in dpaa2_io_down. Applied. Thanks. > > Signed-off-by: Ioana Ciornei > --- > Changes in v2: > - none > >

Re: [PATCH v2 1/2] soc: fsl: dpio: cleanup the cpu array on dpaa2_io_down

On Tue, Dec 4, 2018 at 5:21 AM Ioana Ciornei wrote: > > The dpio_by_cpu array should not contain a reference to a freed dpaa2_io > object. This patch adds the necessary cleanup in dpaa2_io_down. Applied. Thanks. > > Signed-off-by: Ioana Ciornei > --- > Changes in v2: > - none > >

Re: [PATCH 2/2] ASoC: DA7219: Implement error check on reg read and write

On Wed, Dec 5, 2018 at 4:28 AM Mark Brown wrote: > > On Wed, Dec 05, 2018 at 10:21:04AM +, Adam Thomson wrote: > > > If the previous I2C access failed, how can we be sure that the write back > > to HW > > of 0xFF even succeeds? More importantly these error returns won't > > necessarily > >

Re: [PATCH 2/9] ACPI/IORT: Use helper functions to access dev->iommu_fwspec

On 04/12/2018 16:29, Joerg Roedel wrote: From: Joerg Roedel Use the new helpers dev_iommu_fwspec_get()/set() to access the dev->iommu_fwspec pointer. This makes it easier to move that pointer later into another struct. Cc: Lorenzo Pieralisi Signed-off-by: Joerg Roedel ---

Re: [PATCH 2/2] ASoC: DA7219: Implement error check on reg read and write

On Wed, Dec 5, 2018 at 4:28 AM Mark Brown wrote: > > On Wed, Dec 05, 2018 at 10:21:04AM +, Adam Thomson wrote: > > > If the previous I2C access failed, how can we be sure that the write back > > to HW > > of 0xFF even succeeds? More importantly these error returns won't > > necessarily > >

Re: [PATCH 2/9] ACPI/IORT: Use helper functions to access dev->iommu_fwspec

On 04/12/2018 16:29, Joerg Roedel wrote: From: Joerg Roedel Use the new helpers dev_iommu_fwspec_get()/set() to access the dev->iommu_fwspec pointer. This makes it easier to move that pointer later into another struct. Cc: Lorenzo Pieralisi Signed-off-by: Joerg Roedel ---

Re: [PATCH v1 3/5] perf cs-etm: Support for NO_SYNC packet

On Tue, 4 Dec 2018 at 20:31, wrote: > > On Mon, Nov 19, 2018 at 11:27:59AM -0700, Mathieu Poirier wrote: > > On Sun, Nov 11, 2018 at 12:59:41PM +0800, Leo Yan wrote: > > > As described in OpenCSD (CoreSight decoder lib), in the decoding stream > > > it includes one trace element with type

Re: [PATCH v1 3/5] perf cs-etm: Support for NO_SYNC packet

On Tue, 4 Dec 2018 at 20:31, wrote: > > On Mon, Nov 19, 2018 at 11:27:59AM -0700, Mathieu Poirier wrote: > > On Sun, Nov 11, 2018 at 12:59:41PM +0800, Leo Yan wrote: > > > As described in OpenCSD (CoreSight decoder lib), in the decoding stream > > > it includes one trace element with type

Re: [PATCH 1/2] ARM: Remove '-p' from LDFLAGS

On Tue, Dec 4, 2018 at 5:42 PM Nathan Chancellor wrote: > > This option is not supported by lld: > > ld.lld: error: unknown argument: -p > > This has been a no-op in binutils since 2004 (see commit dea514f51da1 in > that tree). Given that the lowest officially supported of binutils for > the

Re: [PATCH 1/2] ARM: Remove '-p' from LDFLAGS

On Tue, Dec 4, 2018 at 5:42 PM Nathan Chancellor wrote: > > This option is not supported by lld: > > ld.lld: error: unknown argument: -p > > This has been a no-op in binutils since 2004 (see commit dea514f51da1 in > that tree). Given that the lowest officially supported of binutils for > the

Re: rcu_preempt caused oom

On Wed, Dec 05, 2018 at 08:42:54AM +, He, Bo wrote: > I double checked the .config, we don't enable CONFIG_NO_HZ_FULL . > Our previous logs can dump all the task backtrace, and kthread (the > rcu_preempt, rcu_sched, and rcu_bh tasks) are all in "I" state not in "R" > state, my understandings

Re: rcu_preempt caused oom

On Wed, Dec 05, 2018 at 08:42:54AM +, He, Bo wrote: > I double checked the .config, we don't enable CONFIG_NO_HZ_FULL . > Our previous logs can dump all the task backtrace, and kthread (the > rcu_preempt, rcu_sched, and rcu_bh tasks) are all in "I" state not in "R" > state, my understandings

Re: [PATCH 14/14] power: supply: axp288: use the BIT() macro

Hi, On Mon, Nov 26, 2018 at 05:27:55PM +0200, Priit Laes wrote: > From: Olliver Schinagl > > Make use of the recommended BIT() macro for bit defines. > > Signed-off-by: Olliver Schinagl > Signed-off-by: Priit Laes > --- Thanks, queued to power-supply-next. -- Sebastian >

Re: [PATCH 14/14] power: supply: axp288: use the BIT() macro

Hi, On Mon, Nov 26, 2018 at 05:27:55PM +0200, Priit Laes wrote: > From: Olliver Schinagl > > Make use of the recommended BIT() macro for bit defines. > > Signed-off-by: Olliver Schinagl > Signed-off-by: Priit Laes > --- Thanks, queued to power-supply-next. -- Sebastian >

Re: [PATCH 13/14] power: supply: axp20x: add missing include bitops.h

Hi, On Mon, Nov 26, 2018 at 05:27:54PM +0200, Priit Laes wrote: > From: Olliver Schinagl > > The axp20x_usb_power driver uses BIT() operations but lacks the include > for it. Include the bitops.h header file. > > Signed-off-by: Olliver Schinagl > Signed-off-by: Priit Laes > --- >

Re: [PATCH 13/14] power: supply: axp20x: add missing include bitops.h

Hi, On Mon, Nov 26, 2018 at 05:27:54PM +0200, Priit Laes wrote: > From: Olliver Schinagl > > The axp20x_usb_power driver uses BIT() operations but lacks the include > for it. Include the bitops.h header file. > > Signed-off-by: Olliver Schinagl > Signed-off-by: Priit Laes > --- >

Re: [RFC PATCH 02/14] mm/hms: heterogenenous memory system (HMS) documentation

On 2018-12-04 7:31 p.m., Jerome Glisse wrote: > How can i express multiple link, or memory that is only accessible > by a subset of the devices/CPUs. In today model they are back in > assumption like everyone can access all the node which do not hold > in what i am trying to do. Well multiple

Re: [RFC PATCH 02/14] mm/hms: heterogenenous memory system (HMS) documentation

On 2018-12-04 7:31 p.m., Jerome Glisse wrote: > How can i express multiple link, or memory that is only accessible > by a subset of the devices/CPUs. In today model they are back in > assumption like everyone can access all the node which do not hold > in what i am trying to do. Well multiple

Re: [PATCH v2 1/2] perf cs-etm: Set branch instruction flags in packet

On Tue, 4 Dec 2018 at 23:26, wrote: > > On Mon, Nov 19, 2018 at 03:26:17PM -0700, Mathieu Poirier wrote: > > On Sun, Nov 11, 2018 at 01:07:55PM +0800, Leo Yan wrote: > > > The perf sample data contains flags to indicate the hardware trace data > > > is belonging to which type branch instruction,

Re: [PATCH v2 1/2] perf cs-etm: Set branch instruction flags in packet

On Tue, 4 Dec 2018 at 23:26, wrote: > > On Mon, Nov 19, 2018 at 03:26:17PM -0700, Mathieu Poirier wrote: > > On Sun, Nov 11, 2018 at 01:07:55PM +0800, Leo Yan wrote: > > > The perf sample data contains flags to indicate the hardware trace data > > > is belonging to which type branch instruction,

Re: [PATCH] firmware: qcom: scm: fix compilation error when disabled

+ linux-arm-msm On Wed 21 Nov 18:32 PST 2018, Jonathan Marek wrote: > This fixes the case when CONFIG_QCOM_SCM is not enabled, and linux/errno.h > has not been included previously. > > Signed-off-by: Jonathan Marek Reviewed-by: Bjorn Andersson Regards, Bjorn > --- > drm/msm includes

Re: [PATCH] firmware: qcom: scm: fix compilation error when disabled

+ linux-arm-msm On Wed 21 Nov 18:32 PST 2018, Jonathan Marek wrote: > This fixes the case when CONFIG_QCOM_SCM is not enabled, and linux/errno.h > has not been included previously. > > Signed-off-by: Jonathan Marek Reviewed-by: Bjorn Andersson Regards, Bjorn > --- > drm/msm includes

Re: [PATCH 10/12] staging: rtl8188eu: correct indentation in update_wireless_mode()

On Wed, 2018-12-05 at 18:02 +0100, Michael Straube wrote: > Correct indentation in update_wireless_mode() to clear a checkpatch > warning. WARNING: Statements should start on a tabstop [] > diff --git a/drivers/staging/rtl8188eu/core/rtw_wlan_util.c >

Re: [PATCH 10/12] staging: rtl8188eu: correct indentation in update_wireless_mode()

On Wed, 2018-12-05 at 18:02 +0100, Michael Straube wrote: > Correct indentation in update_wireless_mode() to clear a checkpatch > warning. WARNING: Statements should start on a tabstop [] > diff --git a/drivers/staging/rtl8188eu/core/rtw_wlan_util.c >

Re: [PATCH 1/8] perf: Allow to block process in syscall tracepoints

On Wed, 5 Dec 2018 17:05:02 +0100 Jiri Olsa wrote: > diff --git a/arch/x86/entry/common.c b/arch/x86/entry/common.c > index 3b2490b81918..e55cf9169a03 100644 > --- a/arch/x86/entry/common.c > +++ b/arch/x86/entry/common.c > @@ -60,6 +60,32 @@ static void do_audit_syscall_entry(struct pt_regs

Re: [PATCH 1/8] perf: Allow to block process in syscall tracepoints

On Wed, 5 Dec 2018 17:05:02 +0100 Jiri Olsa wrote: > diff --git a/arch/x86/entry/common.c b/arch/x86/entry/common.c > index 3b2490b81918..e55cf9169a03 100644 > --- a/arch/x86/entry/common.c > +++ b/arch/x86/entry/common.c > @@ -60,6 +60,32 @@ static void do_audit_syscall_entry(struct pt_regs

Re: [PATCH] perf, tools: Support srccode output

On Wed, Dec 05, 2018 at 01:28:38PM +0100, Jiri Olsa wrote: > On Mon, Dec 03, 2018 at 04:18:48PM -0800, Andi Kleen wrote: > > From: Andi Kleen > > > > When looking at PT or brstackinsn traces with perf script > > it can be very useful to see the source code. This adds a simple > > facility to

Re: [PATCH] perf, tools: Support srccode output

On Wed, Dec 05, 2018 at 01:28:38PM +0100, Jiri Olsa wrote: > On Mon, Dec 03, 2018 at 04:18:48PM -0800, Andi Kleen wrote: > > From: Andi Kleen > > > > When looking at PT or brstackinsn traces with perf script > > it can be very useful to see the source code. This adds a simple > > facility to

Re: [RFC PATCH 02/14] mm/hms: heterogenenous memory system (HMS) documentation

On 2018-12-04 7:37 p.m., Jerome Glisse wrote: >> >> This came up before for apis even better defined than HMS as well as >> more limited scope, i.e. experimental ABI availability only for -rc >> kernels. Linus said this: >> >> "There are no loopholes. No "but it's been only one release". No,

Re: [RFC PATCH 02/14] mm/hms: heterogenenous memory system (HMS) documentation

On 2018-12-04 7:37 p.m., Jerome Glisse wrote: >> >> This came up before for apis even better defined than HMS as well as >> more limited scope, i.e. experimental ABI availability only for -rc >> kernels. Linus said this: >> >> "There are no loopholes. No "but it's been only one release". No,

Re: [PATCH 4.19 000/139] 4.19.7-stable review

On Wed, Dec 05, 2018 at 02:44:59PM -0200, Rafael David Tinoco wrote: > On 12/4/18 8:48 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.19.7 release. > > There are 139 patches in this series, all will be posted as a response > > to this one. If anyone has

Re: [PATCH 4.19 000/139] 4.19.7-stable review

On Wed, Dec 05, 2018 at 02:44:59PM -0200, Rafael David Tinoco wrote: > On 12/4/18 8:48 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.19.7 release. > > There are 139 patches in this series, all will be posted as a response > > to this one. If anyone has

Re: [PATCH v3] signal: add procfd_send_signal() syscall

Hi Christian, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on linus/master] [also build test WARNING on v4.20-rc5] [cannot apply to next-20181205] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url

Re: [PATCH v3] signal: add procfd_send_signal() syscall

Hi Christian, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on linus/master] [also build test WARNING on v4.20-rc5] [cannot apply to next-20181205] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url

Re: [PATCH V2 5/5] PM / Domains: Propagate performance state updates

On Wed, 5 Dec 2018 at 07:42, Stephen Boyd wrote: > > Quoting Ulf Hansson (2018-12-03 05:38:35) > > + Stephen, Mike, Graham > > > > On Fri, 30 Nov 2018 at 12:06, Viresh Kumar wrote: > > > > > > On 30-11-18, 11:18, Ulf Hansson wrote: > > There is one a big difference while comparing with clocks,

Re: [PATCH V2 5/5] PM / Domains: Propagate performance state updates

On Wed, 5 Dec 2018 at 07:42, Stephen Boyd wrote: > > Quoting Ulf Hansson (2018-12-03 05:38:35) > > + Stephen, Mike, Graham > > > > On Fri, 30 Nov 2018 at 12:06, Viresh Kumar wrote: > > > > > > On 30-11-18, 11:18, Ulf Hansson wrote: > > There is one a big difference while comparing with clocks,

Re: [PATCH] power: supply: cpcap-battery: make array cpcap_battery_irqs static, shrinks object size

Hi, On Thu, Nov 29, 2018 at 11:03:42PM +, Colin King wrote: > From: Colin Ian King > > Don't populate the array cpcap_battery_irqs on the stack but instead > make it static. Makes the object code smaller by 99 bytes: > > Before: >text data bss dec hex filename >

Re: [PATCH] power: supply: cpcap-battery: make array cpcap_battery_irqs static, shrinks object size

Hi, On Thu, Nov 29, 2018 at 11:03:42PM +, Colin King wrote: > From: Colin Ian King > > Don't populate the array cpcap_battery_irqs on the stack but instead > make it static. Makes the object code smaller by 99 bytes: > > Before: >text data bss dec hex filename >

[PATCH] ARM: dts: omap5: Fix dual-role mode on Super-Speed port

OMAP5's Super-Speed USB port has a software mailbox register that needs to be fed with VBUS and ID events from an external VBUS/ID comparator. Without this, Host role will not work correctly. Fixes: 656c1a65ab55 ("ARM: dts: omap5: enable OTG role for DWC3 controller") Reported-by: H. Nikolaus

[PATCH] ARM: dts: omap5: Fix dual-role mode on Super-Speed port

OMAP5's Super-Speed USB port has a software mailbox register that needs to be fed with VBUS and ID events from an external VBUS/ID comparator. Without this, Host role will not work correctly. Fixes: 656c1a65ab55 ("ARM: dts: omap5: enable OTG role for DWC3 controller") Reported-by: H. Nikolaus

Re: [RFC PATCH 00/14] Heterogeneous Memory System (HMS) and hbind()

On 12/4/18 6:13 PM, Jerome Glisse wrote: > On Tue, Dec 04, 2018 at 05:06:49PM -0800, Dave Hansen wrote: >> OK, but there are 1024*1024 matrix cells on a systems with 1024 >> proximity domains (ACPI term for NUMA node). So it sounds like you are >> proposing a million-directory approach. > > No,

Re: [RFC PATCH 00/14] Heterogeneous Memory System (HMS) and hbind()

On 12/4/18 6:13 PM, Jerome Glisse wrote: > On Tue, Dec 04, 2018 at 05:06:49PM -0800, Dave Hansen wrote: >> OK, but there are 1024*1024 matrix cells on a systems with 1024 >> proximity domains (ACPI term for NUMA node). So it sounds like you are >> proposing a million-directory approach. > > No,

<    5   6   7   8   9   10   11   12   13   14   >