Re: [PATCH v3 1/2] soc: qcom: smem: Rename "uncached" accessors

On 10/04, Bjorn Andersson wrote: > In preparation for adding accessors for "cached" entries rename the > "uncached" accessors. Also rename "first" cached entry to "last", as > the cached list grows backwards. > > Signed-off-by: Bjorn Andersson > --- Reviewed-by: Stephen Boyd -- Qualcomm

Re: [PATCH v3 2/2] soc: qcom: smem: Support getting cached entries

On 10/04, Bjorn Andersson wrote: > On msm8996 cached SMEM items are used for storing the GLINK FIFOs, so > for items not found in the uncached list we need to also search the > cased list for these items. > > Signed-off-by: Bjorn Andersson > --- Reviewed-by: Stephen Boyd -- Qualcomm

Re: [PATCH tip/core/rcu 1/3] membarrier: Provide register expedited private command

- On Oct 5, 2017, at 12:21 PM, Peter Zijlstra pet...@infradead.org wrote: > On Thu, Oct 05, 2017 at 04:02:06PM +, Mathieu Desnoyers wrote: >> - On Oct 5, 2017, at 8:12 AM, Peter Zijlstra pet...@infradead.org wrote: >> >> > On Wed, Oct 04, 2017 at 02:37:53PM -0700, Paul E. McKenney

Re: [PATCH tip/core/rcu 1/3] membarrier: Provide register expedited private command

- On Oct 5, 2017, at 12:21 PM, Peter Zijlstra pet...@infradead.org wrote: > On Thu, Oct 05, 2017 at 04:02:06PM +, Mathieu Desnoyers wrote: >> - On Oct 5, 2017, at 8:12 AM, Peter Zijlstra pet...@infradead.org wrote: >> >> > On Wed, Oct 04, 2017 at 02:37:53PM -0700, Paul E. McKenney

[RFC PATCH for 4.14 1/2] membarrier: Remove unused code for architectures without membarrier hooks

Architectures without membarrier hooks don't need to emit the empty membarrier_arch_switch_mm() static inline when CONFIG_MEMBARRIER=y. Adapt the CONFIG_MEMBARRIER=n counterpart to only emit the empty membarrier_arch_switch_mm() for architectures with membarrier hooks. Reported-by: Nicholas

[RFC PATCH for 4.14 1/2] membarrier: Remove unused code for architectures without membarrier hooks

Architectures without membarrier hooks don't need to emit the empty membarrier_arch_switch_mm() static inline when CONFIG_MEMBARRIER=y. Adapt the CONFIG_MEMBARRIER=n counterpart to only emit the empty membarrier_arch_switch_mm() for architectures with membarrier hooks. Reported-by: Nicholas

[RFC PATCH for 4.14 2/2] Fix: membarrier: Handle CLONE_VM + !CLONE_THREAD correctly on powerpc

Threads targeting the same VM but which belong to different thread groups is a tricky case. It has a few consequences: It turns out that we cannot rely on get_nr_threads(p) to count the number of threads using a VM. We can use (atomic_read(>mm_users) == 1 && get_nr_threads(p) == 1) instead to

[RFC PATCH for 4.14 2/2] Fix: membarrier: Handle CLONE_VM + !CLONE_THREAD correctly on powerpc

Threads targeting the same VM but which belong to different thread groups is a tricky case. It has a few consequences: It turns out that we cannot rely on get_nr_threads(p) to count the number of threads using a VM. We can use (atomic_read(>mm_users) == 1 && get_nr_threads(p) == 1) instead to

Re: Extreme time jitter with suspend/resume cycles

On Thu, 5 Oct 2017, Thomas Gleixner wrote: > On Thu, 5 Oct 2017, Gabriel Beddingfield wrote: > > > Hi Thomas, > > > > On Thu, Oct 5, 2017 at 11:01 AM, Thomas Gleixner wrote: > > >> > Which SoC/clocksource driver are you talking about? > > >> > > >> NXP i.MX 6SoloX > > >>

Re: Extreme time jitter with suspend/resume cycles

On Thu, 5 Oct 2017, Thomas Gleixner wrote: > On Thu, 5 Oct 2017, Gabriel Beddingfield wrote: > > > Hi Thomas, > > > > On Thu, Oct 5, 2017 at 11:01 AM, Thomas Gleixner wrote: > > >> > Which SoC/clocksource driver are you talking about? > > >> > > >> NXP i.MX 6SoloX > > >>

Re: [PATCH 1/3] arm/xen: don't inclide rwlock.h directly.1~B

On 2017-10-05 12:58:32 [-0700], Stefano Stabellini wrote: > Let me know if you want this patch to go via the xen tree. Yes, please. Sebastian

Re: [PATCH 1/3] arm/xen: don't inclide rwlock.h directly.1~B

On 2017-10-05 12:58:32 [-0700], Stefano Stabellini wrote: > Let me know if you want this patch to go via the xen tree. Yes, please. Sebastian

Re: Extreme time jitter with suspend/resume cycles

Gabriel, On Thu, 5 Oct 2017, Gabriel Beddingfield wrote: > Hi John, > > On Wed, Oct 4, 2017 at 5:16 PM, John Stultz wrote: > >> Please let me know what you think -- and what the right approach for > >> solving this would be. > > > > So I suspect the best solution for

Re: Extreme time jitter with suspend/resume cycles

Gabriel, On Thu, 5 Oct 2017, Gabriel Beddingfield wrote: > Hi John, > > On Wed, Oct 4, 2017 at 5:16 PM, John Stultz wrote: > >> Please let me know what you think -- and what the right approach for > >> solving this would be. > > > > So I suspect the best solution for you here is: provide some

Re: [PATCH v1 3/5] dt-bindings: Add DT bindings for NVIDIA Tegra AHB DMA controller

On 05.10.2017 23:33, Rob Herring wrote: > On Tue, Sep 26, 2017 at 02:22:04AM +0300, Dmitry Osipenko wrote: >> Document DT bindings for NVIDIA Tegra AHB DMA controller that presents >> on Tegra20/30 SoC's. >> >> Signed-off-by: Dmitry Osipenko >> --- >>

Re: [PATCH v1 3/5] dt-bindings: Add DT bindings for NVIDIA Tegra AHB DMA controller

On 05.10.2017 23:33, Rob Herring wrote: > On Tue, Sep 26, 2017 at 02:22:04AM +0300, Dmitry Osipenko wrote: >> Document DT bindings for NVIDIA Tegra AHB DMA controller that presents >> on Tegra20/30 SoC's. >> >> Signed-off-by: Dmitry Osipenko >> --- >> .../bindings/dma/nvidia,tegra20-ahbdma.txt

Re: [Intel-wired-lan] [PATCH] PCI: Check/Set ARI capability before setting numVFs

On Thu, Oct 5, 2017 at 2:07 PM, Bjorn Helgaas wrote: > On Wed, Oct 04, 2017 at 04:29:14PM -0700, Alexander Duyck wrote: >> On Wed, Oct 4, 2017 at 4:01 PM, Bjorn Helgaas wrote: >> > On Wed, Oct 04, 2017 at 08:52:58AM -0700, Tony Nguyen wrote: >> >> This

Re: [Intel-wired-lan] [PATCH] PCI: Check/Set ARI capability before setting numVFs

On Thu, Oct 5, 2017 at 2:07 PM, Bjorn Helgaas wrote: > On Wed, Oct 04, 2017 at 04:29:14PM -0700, Alexander Duyck wrote: >> On Wed, Oct 4, 2017 at 4:01 PM, Bjorn Helgaas wrote: >> > On Wed, Oct 04, 2017 at 08:52:58AM -0700, Tony Nguyen wrote: >> >> This fixes a bug that can occur if an AER error

Re: [PATCH 2/2] PCI: mvebu: Check DRAM window size

On Mon, Sep 25, 2017 at 06:56:58PM -0500, Bjorn Helgaas wrote: > On Mon, Aug 28, 2017 at 05:25:17PM +0200, Jan Luebbe wrote: > > The sum of the DRAM windows may exceed 4GB (at least on Armada XP). > > Return an error in that case. > > > > Signed-off-by: Jan Luebbe > >

Re: [PATCH 2/2] PCI: mvebu: Check DRAM window size

On Mon, Sep 25, 2017 at 06:56:58PM -0500, Bjorn Helgaas wrote: > On Mon, Aug 28, 2017 at 05:25:17PM +0200, Jan Luebbe wrote: > > The sum of the DRAM windows may exceed 4GB (at least on Armada XP). > > Return an error in that case. > > > > Signed-off-by: Jan Luebbe > > Looking for an ack from

[PATCH v10 00/10] complete deferred page initialization

Changelog: v10 - v9 - Addressed new comments from Michal Hocko. - Sent "mm: deferred_init_memmap improvements" as a separate patch as it is also fixing existing problem. - Merged "mm: stop zeroing memory during allocation in vmemmap" with "mm: zero struct pages during initialization". - Added

[PATCH v10 00/10] complete deferred page initialization

Changelog: v10 - v9 - Addressed new comments from Michal Hocko. - Sent "mm: deferred_init_memmap improvements" as a separate patch as it is also fixing existing problem. - Merged "mm: stop zeroing memory during allocation in vmemmap" with "mm: zero struct pages during initialization". - Added

Re: [PATCH RT] time/hrtimer: Use softirq based wakeups for non-RT threads

Sebastian Andrzej Siewior writes: > Normal wake ups (like clock_nanosleep()) which are performed by normal > users can easily lead to 2ms latency spikes if (enough) hrtimer wakeups > are synchronized. > This patch moves all hrtimers wakeups to the softirq queue unless the > caller has a RT

Re: [PREVIEW] Add x86 zstd kernel compression

Hi, On 10/05/2017 09:22 PM, Nick Terrell wrote: On 10/5/17, 1:18 AM, "René Rebe" wrote: Hi Nick, On Oct 5, 2017, at 1:29, Nick Terrell wrote: On 10/4/17, 3:01 AM, "linux-kernel-ow...@vger.kernel.org on behalf of René Rebe"

Re: [PATCH RT] time/hrtimer: Use softirq based wakeups for non-RT threads

Sebastian Andrzej Siewior writes: > Normal wake ups (like clock_nanosleep()) which are performed by normal > users can easily lead to 2ms latency spikes if (enough) hrtimer wakeups > are synchronized. > This patch moves all hrtimers wakeups to the softirq queue unless the > caller has a RT

Re: [PREVIEW] Add x86 zstd kernel compression

Hi, On 10/05/2017 09:22 PM, Nick Terrell wrote: On 10/5/17, 1:18 AM, "René Rebe" wrote: Hi Nick, On Oct 5, 2017, at 1:29, Nick Terrell wrote: On 10/4/17, 3:01 AM, "linux-kernel-ow...@vger.kernel.org on behalf of René Rebe" wrote: Hi, I noticed zstd compression was recently added for

RE: [PATCH v4 4/5] cramfs: add mmap support

On Thu, 5 Oct 2017, Chris Brandt wrote: > On Wednesday, October 04, 2017, Nicolas Pitre wrote: > > Anyway, here's a replacement for patch 4/5 below: > > > > - >8 > > Subject: cramfs: add mmap support > > > > When cramfs_physmem is used then we have the opportunity to map files > > directly

RE: [PATCH v4 4/5] cramfs: add mmap support

On Thu, 5 Oct 2017, Chris Brandt wrote: > On Wednesday, October 04, 2017, Nicolas Pitre wrote: > > Anyway, here's a replacement for patch 4/5 below: > > > > - >8 > > Subject: cramfs: add mmap support > > > > When cramfs_physmem is used then we have the opportunity to map files > > directly

[RELEASE] LTTng-modules 2.10.2 and 2.9.5 (Linux kernel tracer)

Hi, Those are two important bugfix releases coming shortly after 2.10.1 and 2.9.4, which introduced a NULL pointer dereference in the block layer instrumentation for kernels before 4.14. This issue has been caught by our CI at . All LTTng-modules users of versions 2.10.1 and

[RELEASE] LTTng-modules 2.10.2 and 2.9.5 (Linux kernel tracer)

Hi, Those are two important bugfix releases coming shortly after 2.10.1 and 2.9.4, which introduced a NULL pointer dereference in the block layer instrumentation for kernels before 4.14. This issue has been caught by our CI at . All LTTng-modules users of versions 2.10.1 and

Re: Extreme time jitter with suspend/resume cycles

On Thu, Oct 5, 2017 at 2:04 PM, Thomas Gleixner wrote: >> > So that clocksource driver looks correct. Do you have an idea in which >> > context this time jump happens? Does it happen when you exercise your high >> > frequency suspend/resume dance or is that happening just when

Re: Extreme time jitter with suspend/resume cycles

On Thu, Oct 5, 2017 at 2:04 PM, Thomas Gleixner wrote: >> > So that clocksource driver looks correct. Do you have an idea in which >> > context this time jump happens? Does it happen when you exercise your high >> > frequency suspend/resume dance or is that happening just when you let the >> >

[PATCH v10 07/10] x86/kasan: use kasan_map_populate()

To optimize the performance of struct page initialization, vmemmap_populate() will no longer zero memory. Therefore, we must use a new interface to allocate and map kasan shadow memory, that also zeroes memory for us. Signed-off-by: Pavel Tatashin ---

[PATCH v10 07/10] x86/kasan: use kasan_map_populate()

To optimize the performance of struct page initialization, vmemmap_populate() will no longer zero memory. Therefore, we must use a new interface to allocate and map kasan shadow memory, that also zeroes memory for us. Signed-off-by: Pavel Tatashin --- arch/x86/mm/kasan_init_64.c | 8

[PATCH v10 02/10] sparc64/mm: setting fields in deferred pages

Without deferred struct page feature (CONFIG_DEFERRED_STRUCT_PAGE_INIT), flags and other fields in "struct page"es are never changed prior to first initializing struct pages by going through __init_single_page(). With deferred struct page feature enabled there is a case where we set some fields

[PATCH v10 02/10] sparc64/mm: setting fields in deferred pages

Without deferred struct page feature (CONFIG_DEFERRED_STRUCT_PAGE_INIT), flags and other fields in "struct page"es are never changed prior to first initializing struct pages by going through __init_single_page(). With deferred struct page feature enabled there is a case where we set some fields

[PATCH v10 05/10] mm: zero reserved and unavailable struct pages

Some memory is reserved but unavailable: not present in memblock.memory (because not backed by physical pages), but present in memblock.reserved. Such memory has backing struct pages, but they are not initialized by going through __init_single_page(). In some cases these struct pages are accessed

[PATCH v10 06/10] mm/kasan: kasan specific map populate function

During early boot, kasan uses vmemmap_populate() to establish its shadow memory. But, that interface is intended for struct pages use. Because of the current project, vmemmap won't be zeroed during allocation, but kasan expects that memory to be zeroed. We are adding a new kasan_map_populate()

[PATCH v10 05/10] mm: zero reserved and unavailable struct pages

Some memory is reserved but unavailable: not present in memblock.memory (because not backed by physical pages), but present in memblock.reserved. Such memory has backing struct pages, but they are not initialized by going through __init_single_page(). In some cases these struct pages are accessed

[PATCH v10 06/10] mm/kasan: kasan specific map populate function

During early boot, kasan uses vmemmap_populate() to establish its shadow memory. But, that interface is intended for struct pages use. Because of the current project, vmemmap won't be zeroed during allocation, but kasan expects that memory to be zeroed. We are adding a new kasan_map_populate()

[PATCH v10 09/10] mm: stop zeroing memory during allocation in vmemmap

vmemmap_alloc_block() will no longer zero the block, so zero memory at its call sites for everything except struct pages. Struct page memory is zero'd by struct page initialization. Replace allocators in sprase-vmemmap to use the non-zeroing version. So, we will get the performance improvement

[PATCH v10 09/10] mm: stop zeroing memory during allocation in vmemmap

vmemmap_alloc_block() will no longer zero the block, so zero memory at its call sites for everything except struct pages. Struct page memory is zero'd by struct page initialization. Replace allocators in sprase-vmemmap to use the non-zeroing version. So, we will get the performance improvement

[PATCH v10 04/10] mm: defining memblock_virt_alloc_try_nid_raw

* A new variant of memblock_virt_alloc_* allocations: memblock_virt_alloc_try_nid_raw() - Does not zero the allocated memory - Does not panic if request cannot be satisfied * optimize early system hash allocations Clients can call alloc_large_system_hash() with flag: HASH_ZERO to specify

[PATCH v10 04/10] mm: defining memblock_virt_alloc_try_nid_raw

* A new variant of memblock_virt_alloc_* allocations: memblock_virt_alloc_try_nid_raw() - Does not zero the allocated memory - Does not panic if request cannot be satisfied * optimize early system hash allocations Clients can call alloc_large_system_hash() with flag: HASH_ZERO to specify

[PATCH v10 10/10] sparc64: optimized struct page zeroing

Add an optimized mm_zero_struct_page(), so struct page's are zeroed without calling memset(). We do eight to ten regular stores based on the size of struct page. Compiler optimizes out the conditions of switch() statement. SPARC-M6 with 15T of memory, single thread performance:

[PATCH v10 10/10] sparc64: optimized struct page zeroing

Add an optimized mm_zero_struct_page(), so struct page's are zeroed without calling memset(). We do eight to ten regular stores based on the size of struct page. Compiler optimizes out the conditions of switch() statement. SPARC-M6 with 15T of memory, single thread performance:

[PATCH v10 08/10] arm64/kasan: use kasan_map_populate()

To optimize the performance of struct page initialization, vmemmap_populate() will no longer zero memory. Therefore, we must use a new interface to allocate and map kasan shadow memory, that also zeroes memory for us. Signed-off-by: Pavel Tatashin ---

[PATCH v10 08/10] arm64/kasan: use kasan_map_populate()

To optimize the performance of struct page initialization, vmemmap_populate() will no longer zero memory. Therefore, we must use a new interface to allocate and map kasan shadow memory, that also zeroes memory for us. Signed-off-by: Pavel Tatashin --- arch/arm64/mm/kasan_init.c | 12

[PATCH v10 03/10] sparc64: simplify vmemmap_populate

Remove duplicating code by using common functions vmemmap_pud_populate and vmemmap_pgd_populate. Signed-off-by: Pavel Tatashin Reviewed-by: Steven Sistare Reviewed-by: Daniel Jordan Reviewed-by: Bob Picco

[PATCH v10 01/10] x86/mm: setting fields in deferred pages

Without deferred struct page feature (CONFIG_DEFERRED_STRUCT_PAGE_INIT), flags and other fields in "struct page"es are never changed prior to first initializing struct pages by going through __init_single_page(). With deferred struct page feature enabled, however, we set fields in

[PATCH v10 03/10] sparc64: simplify vmemmap_populate

Remove duplicating code by using common functions vmemmap_pud_populate and vmemmap_pgd_populate. Signed-off-by: Pavel Tatashin Reviewed-by: Steven Sistare Reviewed-by: Daniel Jordan Reviewed-by: Bob Picco Acked-by: David S. Miller Acked-by: Michal Hocko --- arch/sparc/mm/init_64.c | 23

[PATCH v10 01/10] x86/mm: setting fields in deferred pages

Without deferred struct page feature (CONFIG_DEFERRED_STRUCT_PAGE_INIT), flags and other fields in "struct page"es are never changed prior to first initializing struct pages by going through __init_single_page(). With deferred struct page feature enabled, however, we set fields in

Re: [PATCH] pci/ehp_hpc: Convert timers to use timer_setup()

On Wed, Oct 04, 2017 at 05:53:48PM -0700, Kees Cook wrote: > In preparation for unconditionally passing the struct timer_list pointer to > all timer callbacks, switch to using the new timer_setup() and from_timer() > to pass the timer pointer explicitly. This fixes what appears to be a bug > in

Re: [PATCH] pci/ehp_hpc: Convert timers to use timer_setup()

On Wed, Oct 04, 2017 at 05:53:48PM -0700, Kees Cook wrote: > In preparation for unconditionally passing the struct timer_list pointer to > all timer callbacks, switch to using the new timer_setup() and from_timer() > to pass the timer pointer explicitly. This fixes what appears to be a bug > in

Re: [PATCH] switchtec: make struct event_regs static

On Thu, Oct 05, 2017 at 11:01:45AM +0100, Colin King wrote: > From: Colin Ian King > > The structure event_regs is local to the source and does not need to > be in global scope, so make it static. > > Cleans up sparse warning: > symbol 'event_regs' was not declared.

Re: [PATCH] switchtec: make struct event_regs static

On Thu, Oct 05, 2017 at 11:01:45AM +0100, Colin King wrote: > From: Colin Ian King > > The structure event_regs is local to the source and does not need to > be in global scope, so make it static. > > Cleans up sparse warning: > symbol 'event_regs' was not declared. Should it be static > >

[PATCH V6 RESEND] sched/fair: Remove group imbalance from calculate_imbalance()

The group_imbalance path in calculate_imbalance() made sense when it was added back in 2007 with commit 908a7c1b9b80 ("sched: fix improper load balance across sched domain") because busiest->load_per_task factored into the amount of imbalance that was calculated. Beginning with commit dd5feea14a7d

[PATCH V6 RESEND] sched/fair: Remove group imbalance from calculate_imbalance()

The group_imbalance path in calculate_imbalance() made sense when it was added back in 2007 with commit 908a7c1b9b80 ("sched: fix improper load balance across sched domain") because busiest->load_per_task factored into the amount of imbalance that was calculated. Beginning with commit dd5feea14a7d

Re: [Intel-wired-lan] [PATCH] PCI: Check/Set ARI capability before setting numVFs

On Wed, Oct 04, 2017 at 04:29:14PM -0700, Alexander Duyck wrote: > On Wed, Oct 4, 2017 at 4:01 PM, Bjorn Helgaas wrote: > > On Wed, Oct 04, 2017 at 08:52:58AM -0700, Tony Nguyen wrote: > >> This fixes a bug that can occur if an AER error is encountered while SRIOV > >> devices

Re: [Intel-wired-lan] [PATCH] PCI: Check/Set ARI capability before setting numVFs

On Wed, Oct 04, 2017 at 04:29:14PM -0700, Alexander Duyck wrote: > On Wed, Oct 4, 2017 at 4:01 PM, Bjorn Helgaas wrote: > > On Wed, Oct 04, 2017 at 08:52:58AM -0700, Tony Nguyen wrote: > >> This fixes a bug that can occur if an AER error is encountered while SRIOV > >> devices are present. > >> >

Re: [PATCH v2] ACPI / LPIT: Add Low Power Idle Table (LPIT) support

On Thursday, October 5, 2017 10:43:33 PM CEST Srinivas Pandruvada wrote: > On Thu, 2017-10-05 at 21:39 +0300, Andy Shevchenko wrote: > > On Thu, Oct 5, 2017 at 9:16 PM, Srinivas Pandruvada > > wrote: > > > > > > Added functionality to read LPIT table, which

Re: [PATCH v2] ACPI / LPIT: Add Low Power Idle Table (LPIT) support

On Thursday, October 5, 2017 10:43:33 PM CEST Srinivas Pandruvada wrote: > On Thu, 2017-10-05 at 21:39 +0300, Andy Shevchenko wrote: > > On Thu, Oct 5, 2017 at 9:16 PM, Srinivas Pandruvada > > wrote: > > > > > > Added functionality to read LPIT table, which provides: > > > > > > - Sysfs

Re: Extreme time jitter with suspend/resume cycles

On Thu, 5 Oct 2017, Gabriel Beddingfield wrote: > Hi Thomas, > > On Thu, Oct 5, 2017 at 11:01 AM, Thomas Gleixner wrote: > >> > Which SoC/clocksource driver are you talking about? > >> > >> NXP i.MX 6SoloX > >> drivers/clocksource/timer-imx-gpt.c > > > > So that clocksource

Re: Extreme time jitter with suspend/resume cycles

On Thu, 5 Oct 2017, Gabriel Beddingfield wrote: > Hi Thomas, > > On Thu, Oct 5, 2017 at 11:01 AM, Thomas Gleixner wrote: > >> > Which SoC/clocksource driver are you talking about? > >> > >> NXP i.MX 6SoloX > >> drivers/clocksource/timer-imx-gpt.c > > > > So that clocksource driver looks

Re: [PATCH v6 01/11] dt-bindings: net: Restore sun8i dwmac binding

On Wed, Sep 27, 2017 at 09:34:04AM +0200, Corentin Labbe wrote: > This patch restore dt-bindings documentation about dwmac-sun8i > This reverts commit 8aa33ec2f481 ("dt-bindings: net: Revert sun8i dwmac > binding") What's missing here is why you are reverting? > > Signed-off-by: Corentin Labbe

Re: [PATCH v6 01/11] dt-bindings: net: Restore sun8i dwmac binding

On Wed, Sep 27, 2017 at 09:34:04AM +0200, Corentin Labbe wrote: > This patch restore dt-bindings documentation about dwmac-sun8i > This reverts commit 8aa33ec2f481 ("dt-bindings: net: Revert sun8i dwmac > binding") What's missing here is why you are reverting? > > Signed-off-by: Corentin Labbe

Applied "spi: spreadtrum adi: add hwspinlock dependency" to the spi tree

The patch spi: spreadtrum adi: add hwspinlock dependency has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Applied "spi: spreadtrum adi: add hwspinlock dependency" to the spi tree

The patch spi: spreadtrum adi: add hwspinlock dependency has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Re: [PATCH v4 12/14] platform/x86: wmi: create character devices when requested by drivers

On Thu, Oct 05, 2017 at 09:09:48PM +0200, Greg KH wrote: > On Thu, Oct 05, 2017 at 07:03:24PM +, mario.limoncie...@dell.com wrote: ... > > It's up to firmware to block the crazy stuff that you can put in a buffer. > > So userspace can pass any blob it wants to the firmware through this >

Re: [PATCH v4 12/14] platform/x86: wmi: create character devices when requested by drivers

On Thu, Oct 05, 2017 at 09:09:48PM +0200, Greg KH wrote: > On Thu, Oct 05, 2017 at 07:03:24PM +, mario.limoncie...@dell.com wrote: ... > > It's up to firmware to block the crazy stuff that you can put in a buffer. > > So userspace can pass any blob it wants to the firmware through this >

Re: [RFC PATCH 1/2] kbuild: Add a cache for generated variables

Hi, On Thu, Oct 5, 2017 at 12:26 AM, Masahiro Yamada wrote: > As far as I tested, I always see only one space after ":=" in v2. > > I did not consider this deeply, > but something is working nicely behind the scene. Try adding this to the end of the main Makefile:

Re: [RFC PATCH 1/2] kbuild: Add a cache for generated variables

Hi, On Thu, Oct 5, 2017 at 12:26 AM, Masahiro Yamada wrote: > As far as I tested, I always see only one space after ":=" in v2. > > I did not consider this deeply, > but something is working nicely behind the scene. Try adding this to the end of the main Makefile: +$(info LDFLAGS_BUILD_ID =

Re: [Part2 PATCH v5 11/31] crypto: ccp: Define SEV key management command id

On Wed, Oct 04, 2017 at 08:13:52AM -0500, Brijesh Singh wrote: > Define Secure Encrypted Virtualization (SEV) key management command id > and structure. The command definition is available in SEV KM [1] spec > 0.14. > > [1] http://support.amd.com/TechDocs/55766_SEV-KM API_Specification.pdf > >

Re: [Part2 PATCH v5 11/31] crypto: ccp: Define SEV key management command id

On Wed, Oct 04, 2017 at 08:13:52AM -0500, Brijesh Singh wrote: > Define Secure Encrypted Virtualization (SEV) key management command id > and structure. The command definition is available in SEV KM [1] spec > 0.14. > > [1] http://support.amd.com/TechDocs/55766_SEV-KM API_Specification.pdf > >

Re: [PATCH] vfs: fix statfs64() returning impossible EOVERFLOW for 64-bit f_files

On Thu, Oct 05, 2017 at 09:36:36PM +0300, Sergey Klyaus wrote: > compat_statfs64 structure has some 32-bit and some 64-bit fields, so > 64d2ab32e "vfs: fix put_compat_statfs64() does not handle errors" fixed > 32-bit overflow checks not being performed, but accidentally enabled > checks for

Re: [PATCH] vfs: fix statfs64() returning impossible EOVERFLOW for 64-bit f_files

On Thu, Oct 05, 2017 at 09:36:36PM +0300, Sergey Klyaus wrote: > compat_statfs64 structure has some 32-bit and some 64-bit fields, so > 64d2ab32e "vfs: fix put_compat_statfs64() does not handle errors" fixed > 32-bit overflow checks not being performed, but accidentally enabled > checks for

[PATCH 1/3] pinctrl: sunxi: Introduce the strict flag

Our pinctrl device should have had strict set all along. However, it wasn't the case, and most of our old device trees also have a pinctrl group in addition to the GPIOs properties, which mean that we can't really turn it on now. All our new SoCs don't have that group, so we should still enable

[PATCH 1/3] pinctrl: sunxi: Introduce the strict flag

Our pinctrl device should have had strict set all along. However, it wasn't the case, and most of our old device trees also have a pinctrl group in addition to the GPIOs properties, which mean that we can't really turn it on now. All our new SoCs don't have that group, so we should still enable

[PATCH 2/3] pinctrl: sunxi: Disable strict mode for old pinctrl drivers

Old pinctrl drivers will need to disable strict mode for various reasons, among which: - Some DT will still have a pinctrl group for each GPIO used, which will be rejected by pin_request. While we could remove those nodes, we still have to deal with old DTs. - Some GPIOs on these

[PATCH 2/3] pinctrl: sunxi: Disable strict mode for old pinctrl drivers

Old pinctrl drivers will need to disable strict mode for various reasons, among which: - Some DT will still have a pinctrl group for each GPIO used, which will be rejected by pin_request. While we could remove those nodes, we still have to deal with old DTs. - Some GPIOs on these

[PATCH 3/3] pinctrl: sunxi: Enforce the strict mode by default

The strict mode should always have been enabled on our driver, and leaving it unchecked just makes it harder to find a migration path as time passes. Let's enable it by default now so that hopefully the new SoCs should be safe. Signed-off-by: Maxime Ripard ---

[PATCH 0/3] pinctrl: sunxi: Start to enforce the strict mode

Hi, Here is an attempt to enable pinctrl's strict mode on our pinctrl drivers. Indeed, our controllers should have had that mode enabled since its introduction. However, there's a number of issues with old device trees that prevent from just enabling it for all the devices. There's basically two

[PATCH 3/3] pinctrl: sunxi: Enforce the strict mode by default

The strict mode should always have been enabled on our driver, and leaving it unchecked just makes it harder to find a migration path as time passes. Let's enable it by default now so that hopefully the new SoCs should be safe. Signed-off-by: Maxime Ripard ---

[PATCH 0/3] pinctrl: sunxi: Start to enforce the strict mode

Hi, Here is an attempt to enable pinctrl's strict mode on our pinctrl drivers. Indeed, our controllers should have had that mode enabled since its introduction. However, there's a number of issues with old device trees that prevent from just enabling it for all the devices. There's basically two

[PATCH 2/2] powermac: Improve a size determination in five functions

From: Markus Elfring Date: Thu, 5 Oct 2017 22:40:39 +0200 Replace the specification of data structures by pointer dereferences as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

[PATCH 2/2] powermac: Improve a size determination in five functions

From: Markus Elfring Date: Thu, 5 Oct 2017 22:40:39 +0200 Replace the specification of data structures by pointer dereferences as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style convention. This issue was

Re: [PATCH v4 12/14] platform/x86: wmi: create character devices when requested by drivers

On Thu, Oct 05, 2017 at 07:03:24PM +, mario.limoncie...@dell.com wrote: > > > > And how _exactly_ is this interface exposed in Windows? Is it ad-hoc > > with custom kernel drivers written by each vendor? Or does the OS > > provide a "sane" interface for it? > > On Windows it's a

[PATCH 1/2] powermac: Delete an error message for a failed memory allocation in kw_i2c_host_init()

From: Markus Elfring Date: Thu, 5 Oct 2017 22:30:29 +0200 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

Re: Extreme time jitter with suspend/resume cycles

Hi Thomas, On Thu, Oct 5, 2017 at 11:01 AM, Thomas Gleixner wrote: >> > Which SoC/clocksource driver are you talking about? >> >> NXP i.MX 6SoloX >> drivers/clocksource/timer-imx-gpt.c > > So that clocksource driver looks correct. Do you have an idea in which > context this

Re: [PATCH v4 12/14] platform/x86: wmi: create character devices when requested by drivers

On Thu, Oct 05, 2017 at 07:03:24PM +, mario.limoncie...@dell.com wrote: > > > > And how _exactly_ is this interface exposed in Windows? Is it ad-hoc > > with custom kernel drivers written by each vendor? Or does the OS > > provide a "sane" interface for it? > > On Windows it's a

[PATCH 1/2] powermac: Delete an error message for a failed memory allocation in kw_i2c_host_init()

From: Markus Elfring Date: Thu, 5 Oct 2017 22:30:29 +0200 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- arch/powerpc/platforms/powermac/low_i2c.c | 5 + 1 file changed, 1

Re: Extreme time jitter with suspend/resume cycles

Hi Thomas, On Thu, Oct 5, 2017 at 11:01 AM, Thomas Gleixner wrote: >> > Which SoC/clocksource driver are you talking about? >> >> NXP i.MX 6SoloX >> drivers/clocksource/timer-imx-gpt.c > > So that clocksource driver looks correct. Do you have an idea in which > context this time jump happens?

Re: [PATCH] Add Tecon Microprocessor Technologies, LLC vendor prefix

On Tue, Sep 26, 2017 at 05:49:37PM +0300, dun...@tecon.ru wrote: > From: Dmitry Dunaev > > Signed-off-by: Dmitry Dunaev > --- > Documentation/devicetree/bindings/vendor-prefixes.txt | 1 + > 1 file changed, 1 insertion(+) Applied.

Re: [PATCH] Add Tecon Microprocessor Technologies, LLC vendor prefix

On Tue, Sep 26, 2017 at 05:49:37PM +0300, dun...@tecon.ru wrote: > From: Dmitry Dunaev > > Signed-off-by: Dmitry Dunaev > --- > Documentation/devicetree/bindings/vendor-prefixes.txt | 1 + > 1 file changed, 1 insertion(+) Applied.

[PATCH 0/2] Power Mac: Adjustments for five function implementations

From: Markus Elfring Date: Thu, 5 Oct 2017 22:48:22 +0200 Two update suggestions were taken into account from static source code analysis. Markus Elfring (2): Delete an error message for a failed memory allocation in kw_i2c_host_init() Improve a size

Re: [PATCH v2 01/10] pinctrl: move gpio-axp209 to pinctrl

On Tue, Sep 26, 2017 at 02:17:11PM +0200, Quentin Schulz wrote: > To prepare the driver for the upcoming pinctrl features, move the GPIO > driver AXP209 from GPIO to pinctrl subsystem. > > Signed-off-by: Quentin Schulz > --- >

[PATCH 0/2] Power Mac: Adjustments for five function implementations

From: Markus Elfring Date: Thu, 5 Oct 2017 22:48:22 +0200 Two update suggestions were taken into account from static source code analysis. Markus Elfring (2): Delete an error message for a failed memory allocation in kw_i2c_host_init() Improve a size determination in five functions

Re: [PATCH v2 01/10] pinctrl: move gpio-axp209 to pinctrl

On Tue, Sep 26, 2017 at 02:17:11PM +0200, Quentin Schulz wrote: > To prepare the driver for the upcoming pinctrl features, move the GPIO > driver AXP209 from GPIO to pinctrl subsystem. > > Signed-off-by: Quentin Schulz > --- > Documentation/devicetree/bindings/gpio/gpio-axp209.txt | 30

Re: [PATCH v4] Input: add support for the Samsung S6SY761 touchscreen

On Tue, Sep 26, 2017 at 03:31:35PM +0900, Andi Shyti wrote: > The S6SY761 touchscreen is a capicitive multi-touch controller > for mobile use. It's connected with i2c at the address 0x48. > > This commit provides a basic version of the driver which can > handle only initialization, touch events

Re: [PATCH v4] Input: add support for the Samsung S6SY761 touchscreen

On Tue, Sep 26, 2017 at 03:31:35PM +0900, Andi Shyti wrote: > The S6SY761 touchscreen is a capicitive multi-touch controller > for mobile use. It's connected with i2c at the address 0x48. > > This commit provides a basic version of the driver which can > handle only initialization, touch events

<    1   2   3   4   5   6   7   8   9   10   >