[PATCH] Make AMBA a menuconfig to ease disabling it all

No need to get into the submenu to disable all AMBA-related config entries Signed-off-by: Vincent Legoll --- drivers/amba/Kconfig | 12 +++- 1 file changed, 3 insertions(+), 9 deletions(-) diff --git a/drivers/amba/Kconfig b/drivers/amba/Kconfig index

[PATCH] Make AMBA a menuconfig to ease disabling it all

No need to get into the submenu to disable all AMBA-related config entries Signed-off-by: Vincent Legoll --- drivers/amba/Kconfig | 12 +++- 1 file changed, 3 insertions(+), 9 deletions(-) diff --git a/drivers/amba/Kconfig b/drivers/amba/Kconfig index 294ba6f..3f8fcb8 100644 ---

Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory

On Thu, 2017-04-13 at 22:16 -0600, Jason Gunthorpe wrote: > > Any caller of pci_add_resource_offset() uses CPU addresses different from > > the PCI bus addresses (unless the offset is zero, of course).  All ACPI > > platforms also support this translation (see "translation_offset"), though > > in

Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory

On Thu, 2017-04-13 at 22:16 -0600, Jason Gunthorpe wrote: > > Any caller of pci_add_resource_offset() uses CPU addresses different from > > the PCI bus addresses (unless the offset is zero, of course).  All ACPI > > platforms also support this translation (see "translation_offset"), though > > in

Re: [RFC 2/3] sched/topology: fix sched groups on NUMA machines with mesh topology

On Thu, Apr 13, 2017 at 10:56:08AM -0300, Lauro Ramos Venancio wrote: > This patch constructs the sched groups from each CPU perspective. So, on > a 4 nodes machine with ring topology, while nodes 0 and 2 keep the same > groups as before [(3, 0, 1)(1, 2, 3)], nodes 1 and 3 have new groups > [(0,

Re: [RFC 2/3] sched/topology: fix sched groups on NUMA machines with mesh topology

On Thu, Apr 13, 2017 at 10:56:08AM -0300, Lauro Ramos Venancio wrote: > This patch constructs the sched groups from each CPU perspective. So, on > a 4 nodes machine with ring topology, while nodes 0 and 2 keep the same > groups as before [(3, 0, 1)(1, 2, 3)], nodes 1 and 3 have new groups > [(0,

Re: [PATCH 32/38] Annotate hardware config module parameters in drivers/video/

On Wednesday, April 05, 2017 06:01:34 PM David Howells wrote: > When the kernel is running in secure boot mode, we lock down the kernel to > prevent userspace from modifying the running kernel image. Whilst this > includes prohibiting access to things like /dev/mem, it must also prevent > access

Re: [PATCH 32/38] Annotate hardware config module parameters in drivers/video/

On Wednesday, April 05, 2017 06:01:34 PM David Howells wrote: > When the kernel is running in secure boot mode, we lock down the kernel to > prevent userspace from modifying the running kernel image. Whilst this > includes prohibiting access to things like /dev/mem, it must also prevent > access

[PATCH net-next] net: mvneta: fix failed to suspend if WOL is enabled

Recently, suspend/resume and WOL support are added into mvneta driver. If we enable WOL, then we get some error as below on Marvell BG4CT platforms during suspend: [ 184.149723] dpm_run_callback(): mdio_bus_suspend+0x0/0x50 returns -16 [ 184.149727] PM: Device f7b62004.mdio-mi:00 failed to

[PATCH net-next] net: mvneta: fix failed to suspend if WOL is enabled

Recently, suspend/resume and WOL support are added into mvneta driver. If we enable WOL, then we get some error as below on Marvell BG4CT platforms during suspend: [ 184.149723] dpm_run_callback(): mdio_bus_suspend+0x0/0x50 returns -16 [ 184.149727] PM: Device f7b62004.mdio-mi:00 failed to

Re: [RFC 2/3] sched/topology: fix sched groups on NUMA machines with mesh topology

On Thu, Apr 13, 2017 at 07:38:05PM -0400, Rik van Riel wrote: > What do the sched groups look like for these topologies, > before and after your patch series? > > > 4 nodes, ring topology > > node distances: > > node   0   1   2   3 > >   0:  10  20  30  20 > >   1:  20  10  20  30 > >   2:  30  

Re: [RFC 2/3] sched/topology: fix sched groups on NUMA machines with mesh topology

On Thu, Apr 13, 2017 at 07:38:05PM -0400, Rik van Riel wrote: > What do the sched groups look like for these topologies, > before and after your patch series? > > > 4 nodes, ring topology > > node distances: > > node   0   1   2   3 > >   0:  10  20  30  20 > >   1:  20  10  20  30 > >   2:  30  

Re: [PATCH 2/2] spi: atmel: add deepest PM support to SAMA5D2

On 14/04/2017 at 10:22:43 +0200, Quentin Schulz wrote: > This adds deepest (Backup+Self-Refresh) PM support to the ATMEL SAMA5D2 > SoC's SPI controller. > > When resuming from deepest state, it is required to restore MR register > as the registers are lost since VDD core has been shut down when >

Re: [PATCH 2/2] spi: atmel: add deepest PM support to SAMA5D2

On 14/04/2017 at 10:22:43 +0200, Quentin Schulz wrote: > This adds deepest (Backup+Self-Refresh) PM support to the ATMEL SAMA5D2 > SoC's SPI controller. > > When resuming from deepest state, it is required to restore MR register > as the registers are lost since VDD core has been shut down when >

Re: [PATCH 1/2] spi: atmel: factorize reusable code for SPI controller init

On 14/04/2017 at 10:22:42 +0200, Quentin Schulz wrote: > The SPI controller configuration during the init can be reused, for the > resume function for example. > > Let's move this configuration to a separate function. > > Signed-off-by: Quentin Schulz >

Re: [PATCH 1/2] spi: atmel: factorize reusable code for SPI controller init

On 14/04/2017 at 10:22:42 +0200, Quentin Schulz wrote: > The SPI controller configuration during the init can be reused, for the > resume function for example. > > Let's move this configuration to a separate function. > > Signed-off-by: Quentin Schulz > Acked-by: Nicolas Ferre Note that this

[PATCH] ARM32: Support mremap() for sigpage/vDSO

CRIU restores application mappings on the same place where they were before Checkpoint. That means, that we need to move vDSO and sigpage during restore on exactly the same place where they were before C/R. Make mremap() code update mm->context.{sigpage,vdso} pointers during VMA move. Sigpage is

[PATCH] ARM32: Support mremap() for sigpage/vDSO

CRIU restores application mappings on the same place where they were before Checkpoint. That means, that we need to move vDSO and sigpage during restore on exactly the same place where they were before C/R. Make mremap() code update mm->context.{sigpage,vdso} pointers during VMA move. Sigpage is

[PATCH] ARM/shmem: Drop page coloring align for non-VIPT CPUs

On ARMv6 CPUs with VIPT caches there are aliasing issues: if two different cache line indexes correspond to the same physical address, then changes made to one of the alias might be lost or they can overwrite each other. To overcome aliasing issues, the align for shared mappings was introduced

[PATCH] ARM/shmem: Drop page coloring align for non-VIPT CPUs

On ARMv6 CPUs with VIPT caches there are aliasing issues: if two different cache line indexes correspond to the same physical address, then changes made to one of the alias might be lost or they can overwrite each other. To overcome aliasing issues, the align for shared mappings was introduced

Re: [PATCH 2/6] drm: writeback: Add out-fences for writeback connectors

On Fri, 25 Nov 2016 16:49:00 + Brian Starkey wrote: > Add the OUT_FENCE_PTR property to writeback connectors, to enable > userspace to get a fence which will signal once the writeback is > complete. It is not allowed to request an out-fence without a > framebuffer

Re: [PATCH 2/6] drm: writeback: Add out-fences for writeback connectors

On Fri, 25 Nov 2016 16:49:00 + Brian Starkey wrote: > Add the OUT_FENCE_PTR property to writeback connectors, to enable > userspace to get a fence which will signal once the writeback is > complete. It is not allowed to request an out-fence without a > framebuffer attached to the connector.

Re: [PATCH] mm, page_alloc: re-enable softirq use of per-cpu page allocator

On Mon, 10 Apr 2017 14:26:16 -0700 Andrew Morton wrote: > On Mon, 10 Apr 2017 16:08:21 +0100 Mel Gorman > wrote: > > > IRQ context were excluded from using the Per-Cpu-Pages (PCP) lists caching > > of order-0 pages in commit 374ad05ab64d

Re: [PATCH] mm, page_alloc: re-enable softirq use of per-cpu page allocator

On Mon, 10 Apr 2017 14:26:16 -0700 Andrew Morton wrote: > On Mon, 10 Apr 2017 16:08:21 +0100 Mel Gorman > wrote: > > > IRQ context were excluded from using the Per-Cpu-Pages (PCP) lists caching > > of order-0 pages in commit 374ad05ab64d ("mm, page_alloc: only use per-cpu > > allocator for

Re: linux-next: build failure after merge of the rtc tree

On 11/04/2017 at 17:52:20 +1000, Stephen Rothwell wrote: > But it is a fix for a build failure caused by a commit in your tree ... > so you should probably get an ack from the x86 maintainers and add it > to your tree. Or do some other fix in your tree. > It is now in my tree. -- Alexandre

Re: linux-next: build failure after merge of the rtc tree

On 11/04/2017 at 17:52:20 +1000, Stephen Rothwell wrote: > But it is a fix for a build failure caused by a commit in your tree ... > so you should probably get an ack from the x86 maintainers and add it > to your tree. Or do some other fix in your tree. > It is now in my tree. -- Alexandre

Re: [PATCH 1/6] drm: Add writeback connector type

On Fri, 25 Nov 2016 16:48:59 + Brian Starkey wrote: > > diff --git a/drivers/gpu/drm/drm_connector.c b/drivers/gpu/drm/drm_connector.c > index b5c6a8e..6bbd93f 100644 > --- a/drivers/gpu/drm/drm_connector.c > +++ b/drivers/gpu/drm/drm_connector.c > @@ -86,6 +86,7 @@

Re: [PATCH 1/6] drm: Add writeback connector type

On Fri, 25 Nov 2016 16:48:59 + Brian Starkey wrote: > > diff --git a/drivers/gpu/drm/drm_connector.c b/drivers/gpu/drm/drm_connector.c > index b5c6a8e..6bbd93f 100644 > --- a/drivers/gpu/drm/drm_connector.c > +++ b/drivers/gpu/drm/drm_connector.c > @@ -86,6 +86,7 @@ struct

Re: [PATCH] ARM: dts: at91: use correct compatible for the gpio mux controller

On 13/04/2017 at 23:22:58 +0200, Peter Rosin wrote: > The compatible string for a gpio based mux controller is "gpio-mux", > and nothing else. > > Fixes: 29dd89418007 ("ARM: dts: at91: add envelope detector mux to the > Axentia TSE-850") > Signed-off-by: Peter Rosin > --- >

Re: [PATCH] ARM: dts: at91: use correct compatible for the gpio mux controller

On 13/04/2017 at 23:22:58 +0200, Peter Rosin wrote: > The compatible string for a gpio based mux controller is "gpio-mux", > and nothing else. > > Fixes: 29dd89418007 ("ARM: dts: at91: add envelope detector mux to the > Axentia TSE-850") > Signed-off-by: Peter Rosin > --- >

[PATCH] h8300: Remove stale definitions

Hi, By accident I noticed h8300 still defines smp_mb__{before,after}_clear_bit(). Those defines have been removed from the kernel since v3.16. Signed-off-by: Peter Zijlstra (Intel) --- arch/h8300/include/asm/bitops.h | 6 -- 1 file changed, 6 deletions(-) diff --git

[PATCH] h8300: Remove stale definitions

Hi, By accident I noticed h8300 still defines smp_mb__{before,after}_clear_bit(). Those defines have been removed from the kernel since v3.16. Signed-off-by: Peter Zijlstra (Intel) --- arch/h8300/include/asm/bitops.h | 6 -- 1 file changed, 6 deletions(-) diff --git

Re: [patch 02/13] workqueue: Provide work_on_cpu_safe()

On Fri, Apr 14, 2017 at 11:51:07AM +0200, Thomas Gleixner wrote: > On Fri, 14 Apr 2017, Peter Zijlstra wrote: > > > On Wed, Apr 12, 2017 at 10:07:28PM +0200, Thomas Gleixner wrote: > > > +long work_on_cpu_safe(int cpu, long (*fn)(void *), void *arg) > > > +{ > > > + long ret = -ENODEV; > > > + >

Re: [patch 02/13] workqueue: Provide work_on_cpu_safe()

On Fri, Apr 14, 2017 at 11:51:07AM +0200, Thomas Gleixner wrote: > On Fri, 14 Apr 2017, Peter Zijlstra wrote: > > > On Wed, Apr 12, 2017 at 10:07:28PM +0200, Thomas Gleixner wrote: > > > +long work_on_cpu_safe(int cpu, long (*fn)(void *), void *arg) > > > +{ > > > + long ret = -ENODEV; > > > + >

[tip:x86/urgent] ftrace/x86: Fix triple fault with graph tracing and suspend-to-ram

Commit-ID: 34a477e5297cbaa6ecc6e17c042a866e1cbe80d6 Gitweb: http://git.kernel.org/tip/34a477e5297cbaa6ecc6e17c042a866e1cbe80d6 Author: Josh Poimboeuf AuthorDate: Thu, 13 Apr 2017 17:53:55 -0500 Committer: Thomas Gleixner CommitDate: Fri, 14 Apr

[tip:x86/urgent] ftrace/x86: Fix triple fault with graph tracing and suspend-to-ram

Commit-ID: 34a477e5297cbaa6ecc6e17c042a866e1cbe80d6 Gitweb: http://git.kernel.org/tip/34a477e5297cbaa6ecc6e17c042a866e1cbe80d6 Author: Josh Poimboeuf AuthorDate: Thu, 13 Apr 2017 17:53:55 -0500 Committer: Thomas Gleixner CommitDate: Fri, 14 Apr 2017 11:48:51 +0200 ftrace/x86: Fix

Re: [patch 02/13] workqueue: Provide work_on_cpu_safe()

On Fri, 14 Apr 2017, Peter Zijlstra wrote: > On Wed, Apr 12, 2017 at 10:07:28PM +0200, Thomas Gleixner wrote: > > +long work_on_cpu_safe(int cpu, long (*fn)(void *), void *arg) > > +{ > > + long ret = -ENODEV; > > + > > + get_online_cpus(); > > + if (cpu_online(cpu)) > > + ret =

Re: [patch 02/13] workqueue: Provide work_on_cpu_safe()

On Fri, 14 Apr 2017, Peter Zijlstra wrote: > On Wed, Apr 12, 2017 at 10:07:28PM +0200, Thomas Gleixner wrote: > > +long work_on_cpu_safe(int cpu, long (*fn)(void *), void *arg) > > +{ > > + long ret = -ENODEV; > > + > > + get_online_cpus(); > > + if (cpu_online(cpu)) > > + ret =

Re: [PATCH v9 0/5] Extend virtio-balloon for fast (de)inflating & fast live migration

On Fri, Apr 14, 2017 at 04:50:48AM +0300, Michael S. Tsirkin wrote: > On Thu, Apr 13, 2017 at 01:44:11PM -0700, Matthew Wilcox wrote: > > On Thu, Apr 13, 2017 at 05:35:03PM +0800, Wei Wang wrote: > > > 2) transfer the guest unused pages to the host so that they > > > can be skipped to migrate in

Re: [PATCH v9 0/5] Extend virtio-balloon for fast (de)inflating & fast live migration

On Fri, Apr 14, 2017 at 04:50:48AM +0300, Michael S. Tsirkin wrote: > On Thu, Apr 13, 2017 at 01:44:11PM -0700, Matthew Wilcox wrote: > > On Thu, Apr 13, 2017 at 05:35:03PM +0800, Wei Wang wrote: > > > 2) transfer the guest unused pages to the host so that they > > > can be skipped to migrate in

Re: [PATCH 6/6] drm: mali-dp: Add writeback connector

On Fri, 25 Nov 2016 16:49:04 + Brian Starkey wrote: > +static int > +malidp_mw_encoder_atomic_check(struct drm_encoder *encoder, > +struct drm_crtc_state *crtc_state, > +struct drm_connector_state *conn_state) >

Re: [PATCH] arm: dma: fix sharing of coherent DMA memory without struct page

On Fri, Apr 14, 2017 at 09:56:07AM +0200, Marek Szyprowski wrote: > >>This would be however quite large task, especially taking into account > >>all current users of DMA-buf framework... > >Yeah it will be a large task. > > Maybe once scatterlist are switched to pfns, changing dmabuf internal >

[tip:x86/mm] x86/boot/e820: Remove a redundant self assignment

Commit-ID: ace2fb5a8b65d6aba530068ea9331f18e10ef565 Gitweb: http://git.kernel.org/tip/ace2fb5a8b65d6aba530068ea9331f18e10ef565 Author: Colin King AuthorDate: Thu, 13 Apr 2017 16:59:12 +0100 Committer: Thomas Gleixner CommitDate: Fri, 14 Apr

Re: [PATCH 6/6] drm: mali-dp: Add writeback connector

On Fri, 25 Nov 2016 16:49:04 + Brian Starkey wrote: > +static int > +malidp_mw_encoder_atomic_check(struct drm_encoder *encoder, > +struct drm_crtc_state *crtc_state, > +struct drm_connector_state *conn_state) > +{ > + struct

Re: [PATCH] arm: dma: fix sharing of coherent DMA memory without struct page

On Fri, Apr 14, 2017 at 09:56:07AM +0200, Marek Szyprowski wrote: > >>This would be however quite large task, especially taking into account > >>all current users of DMA-buf framework... > >Yeah it will be a large task. > > Maybe once scatterlist are switched to pfns, changing dmabuf internal >

[tip:x86/mm] x86/boot/e820: Remove a redundant self assignment

Commit-ID: ace2fb5a8b65d6aba530068ea9331f18e10ef565 Gitweb: http://git.kernel.org/tip/ace2fb5a8b65d6aba530068ea9331f18e10ef565 Author: Colin King AuthorDate: Thu, 13 Apr 2017 16:59:12 +0100 Committer: Thomas Gleixner CommitDate: Fri, 14 Apr 2017 11:43:21 +0200 x86/boot/e820: Remove a

FROM AISHA GADDAFI

for more details,contact me at my private email : agaddafi752(at)gmail. com Dr. Aisha Gaddafi, the daughter of late Libyan president, I need a partner or an investor that will help me in investing the sum of $87.5 million USD in his or her country, the funds is deposited here in Burkina Faso

FROM AISHA GADDAFI

for more details,contact me at my private email : agaddafi752(at)gmail. com Dr. Aisha Gaddafi, the daughter of late Libyan president, I need a partner or an investor that will help me in investing the sum of $87.5 million USD in his or her country, the funds is deposited here in Burkina Faso

Re: [PATCH] Make ANDROID a menuconfig to ease disabling it all

Hello, >> No need to get into the submenu to disable all ANDROID-related config entries > > I don't understand this, what exactly do you mean? This is intended for people using make menuconfig to tailor their kernel config to their need by disabling all options they don't need. In order to have

Re: [PATCH] Make ANDROID a menuconfig to ease disabling it all

Hello, >> No need to get into the submenu to disable all ANDROID-related config entries > > I don't understand this, what exactly do you mean? This is intended for people using make menuconfig to tailor their kernel config to their need by disabling all options they don't need. In order to have

[PATCH] f2fs: use rb-tree to track pending discard commands

Introduce rb-tree based discard cache infrastructure to speed up lookup and merge operation of discard entry. Signed-off-by: Chao Yu --- fs/f2fs/extent_cache.c | 6 +- fs/f2fs/f2fs.h | 47 ++- fs/f2fs/segment.c | 223

[PATCH] f2fs: use rb-tree to track pending discard commands

Introduce rb-tree based discard cache infrastructure to speed up lookup and merge operation of discard entry. Signed-off-by: Chao Yu --- fs/f2fs/extent_cache.c | 6 +- fs/f2fs/f2fs.h | 47 ++- fs/f2fs/segment.c | 223 - 3

Re: [GIT PULL] TTY/Serial driver fixes for 4.11-rc4

On 13 April 2017 at 20:34, Greg KH wrote: > On Thu, Apr 13, 2017 at 09:07:40AM -0700, Linus Torvalds wrote: >> On Thu, Apr 13, 2017 at 3:50 AM, Vegard Nossum >> wrote: >> > >> > I've bisected a syzkaller crash down to this commit >> >

Re: [GIT PULL] TTY/Serial driver fixes for 4.11-rc4

On 13 April 2017 at 20:34, Greg KH wrote: > On Thu, Apr 13, 2017 at 09:07:40AM -0700, Linus Torvalds wrote: >> On Thu, Apr 13, 2017 at 3:50 AM, Vegard Nossum >> wrote: >> > >> > I've bisected a syzkaller crash down to this commit >> > (5362544bebe85071188dd9e479b5a5040841c895). The crash is: >>

[PATCH] Make TI_ST a menuconfig to ease disabling it all

No need to get into the submenu to disable all TI_ST-related config entries Signed-off-by: Vincent Legoll --- drivers/misc/ti-st/Kconfig | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/drivers/misc/ti-st/Kconfig b/drivers/misc/ti-st/Kconfig

[PATCH] Make TI_ST a menuconfig to ease disabling it all

No need to get into the submenu to disable all TI_ST-related config entries Signed-off-by: Vincent Legoll --- drivers/misc/ti-st/Kconfig | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/drivers/misc/ti-st/Kconfig b/drivers/misc/ti-st/Kconfig index f34dcc5..9b297ca

Re: [PATCH] chipidea: Fix issue in reconnecing gadget without insmod/rmmod

On Wed, Apr 12, 2017 at 06:18:20PM +0530, Niranjan Dighe wrote: > > Hi Niranjan, > > > > When working with iAP device, there are two role-switch methods > > - Through OTG FSM, and using sysfs entries under > > /sys/bus/platform/devices/ci_hdrc.0/inputs > > but you may need to patch code to keep

Re: [PATCH] chipidea: Fix issue in reconnecing gadget without insmod/rmmod

On Wed, Apr 12, 2017 at 06:18:20PM +0530, Niranjan Dighe wrote: > > Hi Niranjan, > > > > When working with iAP device, there are two role-switch methods > > - Through OTG FSM, and using sysfs entries under > > /sys/bus/platform/devices/ci_hdrc.0/inputs > > but you may need to patch code to keep

[tip:perf/core] perf/x86: Fix spurious NMI with PEBS Load Latency event

Commit-ID: fd583ad1563bec5f00140e1f2444adbcd331caad Gitweb: http://git.kernel.org/tip/fd583ad1563bec5f00140e1f2444adbcd331caad Author: Kan Liang AuthorDate: Tue, 4 Apr 2017 15:14:06 -0400 Committer: Ingo Molnar CommitDate: Fri, 14 Apr 2017

[tip:perf/core] perf/x86: Fix spurious NMI with PEBS Load Latency event

Commit-ID: fd583ad1563bec5f00140e1f2444adbcd331caad Gitweb: http://git.kernel.org/tip/fd583ad1563bec5f00140e1f2444adbcd331caad Author: Kan Liang AuthorDate: Tue, 4 Apr 2017 15:14:06 -0400 Committer: Ingo Molnar CommitDate: Fri, 14 Apr 2017 10:31:39 +0200 perf/x86: Fix spurious NMI

Re: [RFC PATCH v3 0/6] Introduce writeback connectors

Hi Brian, On Fri, 25 Nov 2016 16:48:58 + Brian Starkey wrote: > Hi, > > This is v3 of my series introducing a new connector type: > DRM_MODE_CONNECTOR_WRITEBACK > See v1 and v2 here: [1] [2] > > Writeback connectors are used to expose the memory writeback engines >

Re: [RFC PATCH v3 0/6] Introduce writeback connectors

Hi Brian, On Fri, 25 Nov 2016 16:48:58 + Brian Starkey wrote: > Hi, > > This is v3 of my series introducing a new connector type: > DRM_MODE_CONNECTOR_WRITEBACK > See v1 and v2 here: [1] [2] > > Writeback connectors are used to expose the memory writeback engines > found in some display

Re: Question regarding Linux implementation of rbtrees

On Fri, Apr 14, 2017 at 10:51:32AM +0200, Peter Zijlstra wrote: > On Fri, Apr 14, 2017 at 12:24:55AM +0200, Alexandru Moise wrote: > > Seeing as RB_RED is defined to be 0 in include/linux/rbtree_augmented.h > > A call of this form: rb_set_parent_color(node, parent, RB_RED); > > as seen in

Re: Question regarding Linux implementation of rbtrees

On Fri, Apr 14, 2017 at 10:51:32AM +0200, Peter Zijlstra wrote: > On Fri, Apr 14, 2017 at 12:24:55AM +0200, Alexandru Moise wrote: > > Seeing as RB_RED is defined to be 0 in include/linux/rbtree_augmented.h > > A call of this form: rb_set_parent_color(node, parent, RB_RED); > > as seen in

Re: [RFC] Fix shared irq trigger-flags conflict when old irqaction uses IRQF_TRIGGER_NONE

On Mon, 10 Apr 2017, Hans de Goede wrote: > Where the new_action trigger_mask gets filled with the triger_mask > from the irq_data, which is a further hint that looking at > irqd_get_trigger_type(>irq_data) rather then at > (old->flags IRQF_TRIGGER_MASK) is probably the right fix. > > Note btw

Re: [RFC] Fix shared irq trigger-flags conflict when old irqaction uses IRQF_TRIGGER_NONE

On Mon, 10 Apr 2017, Hans de Goede wrote: > Where the new_action trigger_mask gets filled with the triger_mask > from the irq_data, which is a further hint that looking at > irqd_get_trigger_type(>irq_data) rather then at > (old->flags IRQF_TRIGGER_MASK) is probably the right fix. > > Note btw

[tip:x86/asm] x86/unwind: Read stack return address in update_stack_state()

Commit-ID: 6bcdf9d51b9892dd5c6892d50cf5e9628efb8062 Gitweb: http://git.kernel.org/tip/6bcdf9d51b9892dd5c6892d50cf5e9628efb8062 Author: Josh Poimboeuf AuthorDate: Wed, 12 Apr 2017 13:47:11 -0500 Committer: Ingo Molnar CommitDate: Fri, 14 Apr 2017

[tip:x86/asm] x86/unwind: Read stack return address in update_stack_state()

Commit-ID: 6bcdf9d51b9892dd5c6892d50cf5e9628efb8062 Gitweb: http://git.kernel.org/tip/6bcdf9d51b9892dd5c6892d50cf5e9628efb8062 Author: Josh Poimboeuf AuthorDate: Wed, 12 Apr 2017 13:47:11 -0500 Committer: Ingo Molnar CommitDate: Fri, 14 Apr 2017 10:19:59 +0200 x86/unwind: Read stack

[tip:locking/core] futex: Avoid freeing an active timer

Commit-ID: 97181f9bd57405b879403763284537e27d46963d Gitweb: http://git.kernel.org/tip/97181f9bd57405b879403763284537e27d46963d Author: Thomas Gleixner AuthorDate: Mon, 10 Apr 2017 18:03:36 +0200 Committer: Ingo Molnar CommitDate: Fri, 14 Apr 2017

[tip:x86/asm] x86/unwind: Move common code into update_stack_state()

Commit-ID: 5ed8d8bb38c5dcd78de540182cedb0fb19399aab Gitweb: http://git.kernel.org/tip/5ed8d8bb38c5dcd78de540182cedb0fb19399aab Author: Josh Poimboeuf AuthorDate: Wed, 12 Apr 2017 13:47:10 -0500 Committer: Ingo Molnar CommitDate: Fri, 14 Apr 2017

[tip:x86/asm] x86/unwind: Silence entry-related warnings

Commit-ID: a8b7a92318b6d7779f6d8e9aa6ba0e3de01a8943 Gitweb: http://git.kernel.org/tip/a8b7a92318b6d7779f6d8e9aa6ba0e3de01a8943 Author: Josh Poimboeuf AuthorDate: Wed, 12 Apr 2017 13:47:12 -0500 Committer: Ingo Molnar CommitDate: Fri, 14 Apr 2017

[tip:sched/core] sched/Documentation: Add 'sched-pelt' tool

Commit-ID: 76d034edcf658e3c74fd90b149882ab1464e4af9 Gitweb: http://git.kernel.org/tip/76d034edcf658e3c74fd90b149882ab1464e4af9 Author: Yuyang Du AuthorDate: Mon, 13 Feb 2017 05:44:22 +0800 Committer: Ingo Molnar CommitDate: Fri, 14 Apr 2017

[tip:locking/core] futex: Avoid freeing an active timer

Commit-ID: 97181f9bd57405b879403763284537e27d46963d Gitweb: http://git.kernel.org/tip/97181f9bd57405b879403763284537e27d46963d Author: Thomas Gleixner AuthorDate: Mon, 10 Apr 2017 18:03:36 +0200 Committer: Ingo Molnar CommitDate: Fri, 14 Apr 2017 10:29:53 +0200 futex: Avoid freeing an

[tip:x86/asm] x86/unwind: Move common code into update_stack_state()

Commit-ID: 5ed8d8bb38c5dcd78de540182cedb0fb19399aab Gitweb: http://git.kernel.org/tip/5ed8d8bb38c5dcd78de540182cedb0fb19399aab Author: Josh Poimboeuf AuthorDate: Wed, 12 Apr 2017 13:47:10 -0500 Committer: Ingo Molnar CommitDate: Fri, 14 Apr 2017 10:19:49 +0200 x86/unwind: Move common

[tip:x86/asm] x86/unwind: Silence entry-related warnings

Commit-ID: a8b7a92318b6d7779f6d8e9aa6ba0e3de01a8943 Gitweb: http://git.kernel.org/tip/a8b7a92318b6d7779f6d8e9aa6ba0e3de01a8943 Author: Josh Poimboeuf AuthorDate: Wed, 12 Apr 2017 13:47:12 -0500 Committer: Ingo Molnar CommitDate: Fri, 14 Apr 2017 10:20:06 +0200 x86/unwind: Silence

[tip:sched/core] sched/Documentation: Add 'sched-pelt' tool

Commit-ID: 76d034edcf658e3c74fd90b149882ab1464e4af9 Gitweb: http://git.kernel.org/tip/76d034edcf658e3c74fd90b149882ab1464e4af9 Author: Yuyang Du AuthorDate: Mon, 13 Feb 2017 05:44:22 +0800 Committer: Ingo Molnar CommitDate: Fri, 14 Apr 2017 10:26:35 +0200 sched/Documentation: Add

[tip:x86/asm] debug: Avoid setting BUGFLAG_WARNING twice

Commit-ID: f26dee15103f4040bfe21c910131db0cfe6624fc Gitweb: http://git.kernel.org/tip/f26dee15103f4040bfe21c910131db0cfe6624fc Author: Peter Zijlstra AuthorDate: Mon, 10 Apr 2017 10:49:39 +0200 Committer: Ingo Molnar CommitDate: Fri, 14 Apr 2017

[tip:x86/asm] debug: Avoid setting BUGFLAG_WARNING twice

Commit-ID: f26dee15103f4040bfe21c910131db0cfe6624fc Gitweb: http://git.kernel.org/tip/f26dee15103f4040bfe21c910131db0cfe6624fc Author: Peter Zijlstra AuthorDate: Mon, 10 Apr 2017 10:49:39 +0200 Committer: Ingo Molnar CommitDate: Fri, 14 Apr 2017 10:20:13 +0200 debug: Avoid setting

Re: [PATCH] Make ANDROID a menuconfig to ease disabling it all

On Fri, Apr 14, 2017 at 11:04:21AM +0200, Vincent Legoll wrote: > No need to get into the submenu to disable all ANDROID-related config entries I don't understand this, what exactly do you mean? > > Signed-off-by: Vincent Legoll > --- > drivers/android/Kconfig | 12

Re: [PATCH] Make ANDROID a menuconfig to ease disabling it all

On Fri, Apr 14, 2017 at 11:04:21AM +0200, Vincent Legoll wrote: > No need to get into the submenu to disable all ANDROID-related config entries I don't understand this, what exactly do you mean? > > Signed-off-by: Vincent Legoll > --- > drivers/android/Kconfig | 12 ++-- > 1 file

[PATCH 10/10] pinctrl: mxs: Use kcalloc() in mxs_dt_node_to_map()

From: Markus Elfring Date: Fri, 14 Apr 2017 10:32:29 +0200 A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus reuse the corresponding function "kcalloc". This issue was detected by

[PATCH 10/10] pinctrl: mxs: Use kcalloc() in mxs_dt_node_to_map()

From: Markus Elfring Date: Fri, 14 Apr 2017 10:32:29 +0200 A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus reuse the corresponding function "kcalloc". This issue was detected by using the Coccinelle software.

[PATCH 09/10] pinctrl: mxs: Use devm_kcalloc() in two functions

From: Markus Elfring Date: Thu, 13 Apr 2017 16:28:48 +0200 Multiplications for the size determination of memory allocations indicated that array data structures should be processed. Thus use the corresponding function "devm_kcalloc". This issue was detected by

[PATCH 09/10] pinctrl: mxs: Use devm_kcalloc() in two functions

From: Markus Elfring Date: Thu, 13 Apr 2017 16:28:48 +0200 Multiplications for the size determination of memory allocations indicated that array data structures should be processed. Thus use the corresponding function "devm_kcalloc". This issue was detected by using the Coccinelle software.

[PATCH 08/10] pinctrl: imx1-core: Use kmalloc_array() in imx_dt_node_to_map()

From: Markus Elfring Date: Thu, 13 Apr 2017 16:10:33 +0200 * A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus use the corresponding function "kmalloc_array". This issue was

[PATCH 08/10] pinctrl: imx1-core: Use kmalloc_array() in imx_dt_node_to_map()

From: Markus Elfring Date: Thu, 13 Apr 2017 16:10:33 +0200 * A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus use the corresponding function "kmalloc_array". This issue was detected by using the Coccinelle

[PATCH 07/10] pinctrl: imx: Use seq_puts() in imx_pinconf_dbg_show()

From: Markus Elfring Date: Thu, 13 Apr 2017 15:50:58 +0200 A string which did not contain a data format specification should be put into a sequence. Thus use the corresponding function "seq_puts". This issue was detected by using the Coccinelle software.

[PATCH 07/10] pinctrl: imx: Use seq_puts() in imx_pinconf_dbg_show()

From: Markus Elfring Date: Thu, 13 Apr 2017 15:50:58 +0200 A string which did not contain a data format specification should be put into a sequence. Thus use the corresponding function "seq_puts". This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

Greetings.

Good Day Dearest. My name is Sarah JOHNSON I am 18 years old, the only daughter of late Mr. Raymond JOHNSON from Burkina Faso, I am contacting you to help me relocate to your country to continue my university education in your country, before my father died he gave me a deposit slip document

Using ion memory for direct-io

Hi Currently, the ion mapped to userspace will be forced with VM_IO and VM_PFNMAP flags. When I use the ion memory to do the direct-io, it will fail when reaching the get_user_pages, Back to the VM_IO and VM_PFNMAP flag, there two flags are introduced by the remap_pfn_range called by the

Greetings.

Good Day Dearest. My name is Sarah JOHNSON I am 18 years old, the only daughter of late Mr. Raymond JOHNSON from Burkina Faso, I am contacting you to help me relocate to your country to continue my university education in your country, before my father died he gave me a deposit slip document

Using ion memory for direct-io

Hi Currently, the ion mapped to userspace will be forced with VM_IO and VM_PFNMAP flags. When I use the ion memory to do the direct-io, it will fail when reaching the get_user_pages, Back to the VM_IO and VM_PFNMAP flag, there two flags are introduced by the remap_pfn_range called by the

[PATCH 06/10] pinctrl: imx: Use seq_putc() in imx_pinconf_group_dbg_show()

From: Markus Elfring Date: Thu, 13 Apr 2017 15:43:55 +0200 A single character (line break) should be put into a sequence. Thus use the corresponding function "seq_putc". This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring

Re: [stable-4.9: PATCH] xen: revert commit 72a9b186292

On Thu, Apr 13, 2017 at 03:06:53PM +0200, Juergen Gross wrote: > Revert commit 72a9b186292 ("xen: Remove event channel notification > through Xen PCI platform device") as the original analysis was wrong > that all the removed code isn't in use any more. > > It is still necessary for old Xen

[PATCH 06/10] pinctrl: imx: Use seq_putc() in imx_pinconf_group_dbg_show()

From: Markus Elfring Date: Thu, 13 Apr 2017 15:43:55 +0200 A single character (line break) should be put into a sequence. Thus use the corresponding function "seq_putc". This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

Re: [stable-4.9: PATCH] xen: revert commit 72a9b186292

On Thu, Apr 13, 2017 at 03:06:53PM +0200, Juergen Gross wrote: > Revert commit 72a9b186292 ("xen: Remove event channel notification > through Xen PCI platform device") as the original analysis was wrong > that all the removed code isn't in use any more. > > It is still necessary for old Xen

[PATCH 05/10] pinctrl: imx: Use devm_kmalloc_array() in imx_pinctrl_probe()

From: Markus Elfring Date: Thu, 13 Apr 2017 15:35:27 +0200 A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus use the corresponding function "devm_kmalloc_array". This issue was

[PATCH 05/10] pinctrl: imx: Use devm_kmalloc_array() in imx_pinctrl_probe()

From: Markus Elfring Date: Thu, 13 Apr 2017 15:35:27 +0200 A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus use the corresponding function "devm_kmalloc_array". This issue was detected by using the Coccinelle

[PATCH 04/10] pinctrl: imx: Improve another size determination in imx_pinctrl_parse_functions()

From: Markus Elfring Date: Thu, 13 Apr 2017 15:20:43 +0200 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

[PATCH 04/10] pinctrl: imx: Improve another size determination in imx_pinctrl_parse_functions()

From: Markus Elfring Date: Thu, 13 Apr 2017 15:20:43 +0200 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style convention. Signed-off-by:

<    4   5   6   7   8   9   10   11   >