Re: [PATCH 3/4] nvmet-fc: Don't use the count returned by the dma_map_sg call

On 3/29/2018 9:07 AM, Logan Gunthorpe wrote: When allocating an SGL, the fibre channel target uses the number of entities mapped as the number of entities in a given scatter gather list. This is incorrect. The DMA-API-HOWTO document gives this note: The 'nents' argument to the dma_unmap_sg

Re: [PATCH 3/4] nvmet-fc: Don't use the count returned by the dma_map_sg call

On 3/29/2018 9:07 AM, Logan Gunthorpe wrote: When allocating an SGL, the fibre channel target uses the number of entities mapped as the number of entities in a given scatter gather list. This is incorrect. The DMA-API-HOWTO document gives this note: The 'nents' argument to the dma_unmap_sg

Re: [PATCH v2 04/19] powerpc/kvm: Prefer fault_in_pages_readable function

Mathieu Malaterre a écrit : Directly use fault_in_pages_readable instead of manual __get_user code. Fix warning treated as error with W=1: arch/powerpc/kernel/kvm.c:675:6: error: variable ‘tmp’ set but not used [-Werror=unused-but-set-variable] Suggested-by: Christophe

Re: [PATCH v2 04/19] powerpc/kvm: Prefer fault_in_pages_readable function

Mathieu Malaterre a écrit : Directly use fault_in_pages_readable instead of manual __get_user code. Fix warning treated as error with W=1: arch/powerpc/kernel/kvm.c:675:6: error: variable ‘tmp’ set but not used [-Werror=unused-but-set-variable] Suggested-by: Christophe Leroy

Re: [PATCH v2 05/19] powerpc/chrp/setup: Add attribute unused and make some functions static

The subject of the patch should be updated as well Christophe Mathieu Malaterre a écrit : Remove variable declaration idu_size and associated code since not used. These functions can all be static, make it so. Fix warnings treated as errors with W=1:

Re: [PATCH v2 05/19] powerpc/chrp/setup: Add attribute unused and make some functions static

The subject of the patch should be updated as well Christophe Mathieu Malaterre a écrit : Remove variable declaration idu_size and associated code since not used. These functions can all be static, make it so. Fix warnings treated as errors with W=1:

Re: [PATCH v6 2/6] dt-bindings: input: Add common keyboard document bindings

On Wed, Oct 25, 2017 at 09:16:00PM +0800, Chen Zhong wrote: > This patch adds the device tree binding documentation for common > keyboard. > > Acked-by: Rob Herring > Signed-off-by: Chen Zhong Acked-by: Dmitry Torokhov >

Re: [PATCH v6 2/6] dt-bindings: input: Add common keyboard document bindings

On Wed, Oct 25, 2017 at 09:16:00PM +0800, Chen Zhong wrote: > This patch adds the device tree binding documentation for common > keyboard. > > Acked-by: Rob Herring > Signed-off-by: Chen Zhong Acked-by: Dmitry Torokhov > --- > Documentation/devicetree/bindings/input/keys.txt |8

Re: [PATCH v6 3/6] dt-bindings: input: Add document bindings for mtk-pmic-keys

On Wed, Oct 25, 2017 at 09:16:01PM +0800, Chen Zhong wrote: > This patch adds the device tree binding documentation for the MediaTek > pmic keys found on PMIC MT6397/MT6323. > > Acked-by: Rob Herring > Signed-off-by: Chen Zhong Acked-by: Dmitry

Re: [PATCH v6 3/6] dt-bindings: input: Add document bindings for mtk-pmic-keys

On Wed, Oct 25, 2017 at 09:16:01PM +0800, Chen Zhong wrote: > This patch adds the device tree binding documentation for the MediaTek > pmic keys found on PMIC MT6397/MT6323. > > Acked-by: Rob Herring > Signed-off-by: Chen Zhong Acked-by: Dmitry Torokhov > --- >

Re: [PATCH 3/4] nvmet-fc: Don't use the count returned by the dma_map_sg call

On 29/03/18 10:14 AM, Bart Van Assche wrote: > On Thu, 2018-03-29 at 10:07 -0600, Logan Gunthorpe wrote: >> +ret = fc_dma_map_sg(fod->tgtport->dev, sg, nent, >> +((fod->io_dir == NVMET_FCP_WRITE) ? >> +DMA_FROM_DEVICE : DMA_TO_DEVICE));

Re: [PATCH 3/4] nvmet-fc: Don't use the count returned by the dma_map_sg call

On 29/03/18 10:14 AM, Bart Van Assche wrote: > On Thu, 2018-03-29 at 10:07 -0600, Logan Gunthorpe wrote: >> +ret = fc_dma_map_sg(fod->tgtport->dev, sg, nent, >> +((fod->io_dir == NVMET_FCP_WRITE) ? >> +DMA_FROM_DEVICE : DMA_TO_DEVICE));

Re: [PATCH v6 0/6] Add MediaTek PMIC keys support

On Thu, Mar 29, 2018 at 02:04:02PM +0100, Lee Jones wrote: > On Thu, 29 Mar 2018, Chen Zhong wrote: > > > On Wed, 2018-03-28 at 11:26 +0100, Lee Jones wrote: > > > On Tue, 27 Mar 2018, Matthias Brugger wrote: > > > > > > > > > > > > > > > On 03/27/2018 10:05 AM, Lee Jones wrote: > > > > > On

Re: [PATCH v6 0/6] Add MediaTek PMIC keys support

On Thu, Mar 29, 2018 at 02:04:02PM +0100, Lee Jones wrote: > On Thu, 29 Mar 2018, Chen Zhong wrote: > > > On Wed, 2018-03-28 at 11:26 +0100, Lee Jones wrote: > > > On Tue, 27 Mar 2018, Matthias Brugger wrote: > > > > > > > > > > > > > > > On 03/27/2018 10:05 AM, Lee Jones wrote: > > > > > On

Re: [PATCH 3/4] nvmet-fc: Don't use the count returned by the dma_map_sg call

On Thu, 2018-03-29 at 10:07 -0600, Logan Gunthorpe wrote: > + ret = fc_dma_map_sg(fod->tgtport->dev, sg, nent, > + ((fod->io_dir == NVMET_FCP_WRITE) ? > + DMA_FROM_DEVICE : DMA_TO_DEVICE)); > + /* note: write from

Re: [PATCH 3/4] nvmet-fc: Don't use the count returned by the dma_map_sg call

On Thu, 2018-03-29 at 10:07 -0600, Logan Gunthorpe wrote: > + ret = fc_dma_map_sg(fod->tgtport->dev, sg, nent, > + ((fod->io_dir == NVMET_FCP_WRITE) ? > + DMA_FROM_DEVICE : DMA_TO_DEVICE)); > + /* note: write from

Re: [PATCH v2 03/19] powerpc: Mark variables as unused

Mathieu Malaterre a écrit : Add gcc attribute unused for two variables. Fix warnings treated as errors with W=1: arch/powerpc/kernel/prom_init.c:1388:8: error: variable ‘path’ set but not used [-Werror=unused-but-set-variable] Suggested-by: Christophe Leroy

Re: [PATCH v2 03/19] powerpc: Mark variables as unused

Mathieu Malaterre a écrit : Add gcc attribute unused for two variables. Fix warnings treated as errors with W=1: arch/powerpc/kernel/prom_init.c:1388:8: error: variable ‘path’ set but not used [-Werror=unused-but-set-variable] Suggested-by: Christophe Leroy Signed-off-by: Mathieu

Re: [PATCH 4.4 014/134] perf tools: Make perf_event__synthesize_mmap_events() scale

On Mon, 2018-03-19 at 19:04 +0100, Greg Kroah-Hartman wrote: > 4.4-stable review patch.  If anyone has any objections, please let me know. > > -- > > From: Stephane Eranian > > > [ Upstream commit 88b897a30c525c2eee6e7f16e1e8d0f18830845e ] > > This patch

Re: [PATCH 4.4 014/134] perf tools: Make perf_event__synthesize_mmap_events() scale

On Mon, 2018-03-19 at 19:04 +0100, Greg Kroah-Hartman wrote: > 4.4-stable review patch.  If anyone has any objections, please let me know. > > -- > > From: Stephane Eranian > > > [ Upstream commit 88b897a30c525c2eee6e7f16e1e8d0f18830845e ] > > This patch significantly

Re: [PATCH] vsprintf: Make "null" pointer dereference more robust

On Thu, 2018-03-29 at 17:13 +0200, Petr Mladek wrote: > The original simple patch grew into something bigger. I have it > almost ready. It looks the following way at the moment: [] > vsprintf: Factor out %p[iI] handler as ip_addr_string() > vsprintf: Factor out %pV handler as va_format() >

Re: [PATCH] vsprintf: Make "null" pointer dereference more robust

On Thu, 2018-03-29 at 17:13 +0200, Petr Mladek wrote: > The original simple patch grew into something bigger. I have it > almost ready. It looks the following way at the moment: [] > vsprintf: Factor out %p[iI] handler as ip_addr_string() > vsprintf: Factor out %pV handler as va_format() >

Re: [PATCH 2/8] PCI: Add pci_find_common_upstream_dev()

Am 29.03.2018 um 17:45 schrieb Logan Gunthorpe: On 29/03/18 05:44 AM, Christian König wrote: Am 28.03.2018 um 21:53 schrieb Logan Gunthorpe: On 28/03/18 01:44 PM, Christian König wrote: Well, isn't that exactly what dma_map_resource() is good for? As far as I can see it makes sure IOMMU is

Re: [PATCH 2/8] PCI: Add pci_find_common_upstream_dev()

Am 29.03.2018 um 17:45 schrieb Logan Gunthorpe: On 29/03/18 05:44 AM, Christian König wrote: Am 28.03.2018 um 21:53 schrieb Logan Gunthorpe: On 28/03/18 01:44 PM, Christian König wrote: Well, isn't that exactly what dma_map_resource() is good for? As far as I can see it makes sure IOMMU is

Re: [PATCH v2 02/19] powerpc/powermac: Mark variable x as unused

Mathieu Malaterre a écrit : Since the value of x is never intended to be read, remove it. Fix warning treated as error with W=1: arch/powerpc/platforms/powermac/udbg_scc.c:76:9: error: variable ‘x’ set but not used [-Werror=unused-but-set-variable] Suggested-by:

Re: [PATCH v2 02/19] powerpc/powermac: Mark variable x as unused

Mathieu Malaterre a écrit : Since the value of x is never intended to be read, remove it. Fix warning treated as error with W=1: arch/powerpc/platforms/powermac/udbg_scc.c:76:9: error: variable ‘x’ set but not used [-Werror=unused-but-set-variable] Suggested-by: Christophe Leroy

Re: [PATCH v3] x86,sched: allow topologies where NUMA nodes share an LLC

On Thu, Mar 29, 2018 at 07:34:58AM -0700, Dave Hansen wrote: > What should we say, though? > > /* > * false means 'c' does not share the LLC of 'o'. > * Note: this decision gets reflected all the way > * out to userspace > */ >

Re: [PATCH v3] x86,sched: allow topologies where NUMA nodes share an LLC

On Thu, Mar 29, 2018 at 07:34:58AM -0700, Dave Hansen wrote: > What should we say, though? > > /* > * false means 'c' does not share the LLC of 'o'. > * Note: this decision gets reflected all the way > * out to userspace > */ >

Re: [PATCH 1/1] xen-netback: process malformed sk_buff correctly to avoid BUG_ON()

From: Dongli Zhang Date: Wed, 28 Mar 2018 07:42:16 +0800 > The "BUG_ON(!frag_iter)" in function xenvif_rx_next_chunk() is triggered if > the received sk_buff is malformed, that is, when the sk_buff has pattern > (skb->data_len && !skb_shinfo(skb)->nr_frags). Below is a

Re: [PATCH 1/1] xen-netback: process malformed sk_buff correctly to avoid BUG_ON()

From: Dongli Zhang Date: Wed, 28 Mar 2018 07:42:16 +0800 > The "BUG_ON(!frag_iter)" in function xenvif_rx_next_chunk() is triggered if > the received sk_buff is malformed, that is, when the sk_buff has pattern > (skb->data_len && !skb_shinfo(skb)->nr_frags). Below is a sample call > stack: We

[PATCH 1/4] nvmet: Introduce helper functions to allocate and free request SGLs

Add helpers to allocate and free the SGL in a struct nvmet_req: int nvmet_req_alloc_sgl(struct nvmet_req *req, struct nvmet_sq *sq) void nvmet_req_free_sgl(struct nvmet_req *req) This will be expanded in a future patch to implement peer-to-peer memory and should be common with all target

Re: omap4-droid4: voice call support was Re: [PATCHv5,5/5] ARM: dts: omap4-droid4: add soundcard

Hi! > @@ -510,17 +510,17 @@ > 07f4: > 07f8: > 07fc: > -0800: 0065 > -0804: > -0808: 0040 > +0800: 0025 # CPCAP_REG_VAUDIOC VAUDIO Control > +0804: 60cf # CPCAP_REG_CC Codec Control, moto cpcap.c:1337 sets > 0x0093? > +0808: ae0a # CPCAP_REG_CDI

[PATCH 1/4] nvmet: Introduce helper functions to allocate and free request SGLs

Add helpers to allocate and free the SGL in a struct nvmet_req: int nvmet_req_alloc_sgl(struct nvmet_req *req, struct nvmet_sq *sq) void nvmet_req_free_sgl(struct nvmet_req *req) This will be expanded in a future patch to implement peer-to-peer memory and should be common with all target

Re: omap4-droid4: voice call support was Re: [PATCHv5,5/5] ARM: dts: omap4-droid4: add soundcard

Hi! > @@ -510,17 +510,17 @@ > 07f4: > 07f8: > 07fc: > -0800: 0065 > -0804: > -0808: 0040 > +0800: 0025 # CPCAP_REG_VAUDIOC VAUDIO Control > +0804: 60cf # CPCAP_REG_CC Codec Control, moto cpcap.c:1337 sets > 0x0093? > +0808: ae0a # CPCAP_REG_CDI

[PATCH 4/4] nvmet-fc: Use new SGL alloc/free helper for requests

Use the new helpers introduced earlier to allocate the SGLs for the request. To do this, we drop the appearantly redundant data_sg and data_sg_cnt members as they are identical to the existing req.sg and req.sg_cnt. Signed-off-by: Logan Gunthorpe Cc: James Smart

[PATCH 4/4] nvmet-fc: Use new SGL alloc/free helper for requests

Use the new helpers introduced earlier to allocate the SGLs for the request. To do this, we drop the appearantly redundant data_sg and data_sg_cnt members as they are identical to the existing req.sg and req.sg_cnt. Signed-off-by: Logan Gunthorpe Cc: James Smart Cc: Christoph Hellwig Cc: Sagi

Re: [PATCH v2 01/19] powerpc/powermac: Mark variable x as unused

Mathieu Malaterre a écrit : Since the value of x is never intended to be read, declare it with gcc attribute as unused. Fix warning treated as error with W=1: arch/powerpc/platforms/powermac/bootx_init.c:471:21: error: variable ‘x’ set but not used

Re: [PATCH v2 01/19] powerpc/powermac: Mark variable x as unused

Mathieu Malaterre a écrit : Since the value of x is never intended to be read, declare it with gcc attribute as unused. Fix warning treated as error with W=1: arch/powerpc/platforms/powermac/bootx_init.c:471:21: error: variable ‘x’ set but not used [-Werror=unused-but-set-variable]

[PATCH 0/4] SGL alloc and free helper functions for requests

Hey, These patches are going to be part of the P2PDMA patchset I'm working on. The change was suggested by Christoph. I just wanted to get the NVMe community's initial feedback on them seperate from our main patchset. That is, except for patch 0003 which I'm pretty sure is a valid bug fix but it

[PATCH 3/4] nvmet-fc: Don't use the count returned by the dma_map_sg call

When allocating an SGL, the fibre channel target uses the number of entities mapped as the number of entities in a given scatter gather list. This is incorrect. The DMA-API-HOWTO document gives this note: The 'nents' argument to the dma_unmap_sg call must be the _same_ one you passed into

[PATCH 0/4] SGL alloc and free helper functions for requests

Hey, These patches are going to be part of the P2PDMA patchset I'm working on. The change was suggested by Christoph. I just wanted to get the NVMe community's initial feedback on them seperate from our main patchset. That is, except for patch 0003 which I'm pretty sure is a valid bug fix but it

[PATCH 3/4] nvmet-fc: Don't use the count returned by the dma_map_sg call

When allocating an SGL, the fibre channel target uses the number of entities mapped as the number of entities in a given scatter gather list. This is incorrect. The DMA-API-HOWTO document gives this note: The 'nents' argument to the dma_unmap_sg call must be the _same_ one you passed into

[PATCH 2/4] nvmet-rdma: Use new SGL alloc/free helper for requests

Use the new helpers introduced in the previous patch to allocate the SGLs for the request. Seeing we use req.transfer_len as the length of the SGL it is set earlier and cleared on any error. It also seems to be unnecessary to accumulate the length as the map_sgl functions should only ever be

[PATCH 2/4] nvmet-rdma: Use new SGL alloc/free helper for requests

Use the new helpers introduced in the previous patch to allocate the SGLs for the request. Seeing we use req.transfer_len as the length of the SGL it is set earlier and cleared on any error. It also seems to be unnecessary to accumulate the length as the map_sgl functions should only ever be

Re: omap4-droid4: voice call support was Re: [PATCHv5,5/5] ARM: dts: omap4-droid4: add soundcard

* Sebastian Reichel [180329 15:47]: > Hi, > > On Thu, Mar 29, 2018 at 06:59:04AM -0700, Tony Lindgren wrote: > > > I think cpcap is always the clock and frame master, but I think > > > mdm6600 is the remote side and OMAP is not involved at all. > > > > OK. So

Re: [PATCH net-next 0/2] net: bgmac: Couple of small bgmac changes

From: Florian Fainelli Date: Tue, 27 Mar 2018 16:20:00 -0700 > This patch series addresses two minor issues with the bgmac driver: > > - provides the interface name through /proc/interrupts rather than "bgmac" > - makes sure the interrupts are masked during probe, in case

Re: omap4-droid4: voice call support was Re: [PATCHv5,5/5] ARM: dts: omap4-droid4: add soundcard

* Sebastian Reichel [180329 15:47]: > Hi, > > On Thu, Mar 29, 2018 at 06:59:04AM -0700, Tony Lindgren wrote: > > > I think cpcap is always the clock and frame master, but I think > > > mdm6600 is the remote side and OMAP is not involved at all. > > > > OK. So could it be just an alsamixer

Re: [PATCH net-next 0/2] net: bgmac: Couple of small bgmac changes

From: Florian Fainelli Date: Tue, 27 Mar 2018 16:20:00 -0700 > This patch series addresses two minor issues with the bgmac driver: > > - provides the interface name through /proc/interrupts rather than "bgmac" > - makes sure the interrupts are masked during probe, in case the block was > not

Re: [PATCH v1] kernel/trace:check the val against the available mem

On Thu, 29 Mar 2018 18:41:44 +0800 Zhaoyang Huang wrote: > It is reported that some user app would like to echo a huge > number to "/sys/kernel/debug/tracing/buffer_size_kb" regardless > of the available memory, which will cause the coinstantaneous > page allocation

Re: [PATCH v1] kernel/trace:check the val against the available mem

On Thu, 29 Mar 2018 18:41:44 +0800 Zhaoyang Huang wrote: > It is reported that some user app would like to echo a huge > number to "/sys/kernel/debug/tracing/buffer_size_kb" regardless > of the available memory, which will cause the coinstantaneous > page allocation failed and introduce OOM.

Re: [PATCH v7 0/5] Add Intel IOMMU debugfs support

On Thu, 29 Mar 2018 10:48:24 +0200 Joerg Roedel wrote: > [ Adding Gary from AMD to Cc ] > > On Mon, Mar 19, 2018 at 09:37:14AM -0700, Jacob Pan wrote: > > On Thu, 15 Mar 2018 14:18:54 +0100 > > Joerg Roedel wrote: > > > > > On Thu, Feb 15, 2018 at

Re: [PATCH v7 0/5] Add Intel IOMMU debugfs support

On Thu, 29 Mar 2018 10:48:24 +0200 Joerg Roedel wrote: > [ Adding Gary from AMD to Cc ] > > On Mon, Mar 19, 2018 at 09:37:14AM -0700, Jacob Pan wrote: > > On Thu, 15 Mar 2018 14:18:54 +0100 > > Joerg Roedel wrote: > > > > > On Thu, Feb 15, 2018 at 08:38:11AM -0800, Jacob Pan wrote: > > >

Re: [PATCH 15/19] powerpc: Add missing prototype

Mathieu Malaterre a écrit : On Fri, Mar 23, 2018 at 1:20 PM, christophe leroy wrote: Le 22/03/2018 à 21:20, Mathieu Malaterre a écrit : Add one missing prototype for function rh_dump_blk. Fix warning treated as error in W=1:

Re: [PATCH 15/19] powerpc: Add missing prototype

Mathieu Malaterre a écrit : On Fri, Mar 23, 2018 at 1:20 PM, christophe leroy wrote: Le 22/03/2018 à 21:20, Mathieu Malaterre a écrit : Add one missing prototype for function rh_dump_blk. Fix warning treated as error in W=1: arch/powerpc/lib/rheap.c:740:6: error: no previous

Re: [PATCH net-next 0/3] rxrpc: Tracing updates

From: David Howells Date: Tue, 27 Mar 2018 23:57:50 +0100 > Here are some patches that update tracing in AF_RXRPC and AFS: > > (1) Add a tracepoint for tracking resend events. > > (2) Use debug_ids in traces rather than pointers (as pointers are now hashed) > and

Re: [PATCH net-next 0/3] rxrpc: Tracing updates

From: David Howells Date: Tue, 27 Mar 2018 23:57:50 +0100 > Here are some patches that update tracing in AF_RXRPC and AFS: > > (1) Add a tracepoint for tracking resend events. > > (2) Use debug_ids in traces rather than pointers (as pointers are now hashed) > and allow use of the same

Re: [PATCH v7 07/14] fs, dax: use page->mapping to warn if truncate collides with a busy page

On Wed 21-03-18 15:57:48, Dan Williams wrote: > Catch cases where extent unmap operations encounter pages that are > pinned / busy. Typically this is pinned pages that are under active dma. > This warning is a canary for potential data corruption as truncated > blocks could be allocated to a new

Re: [PATCH v7 07/14] fs, dax: use page->mapping to warn if truncate collides with a busy page

On Wed 21-03-18 15:57:48, Dan Williams wrote: > Catch cases where extent unmap operations encounter pages that are > pinned / busy. Typically this is pinned pages that are under active dma. > This warning is a canary for potential data corruption as truncated > blocks could be allocated to a new

Re: [PATCH 1/1] hugetlbfs: fix bug in pgoff overflow checking

Hi Mike, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on linus/master] [also build test WARNING on v4.16-rc7 next-20180329] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci

Re: [PATCH 1/1] hugetlbfs: fix bug in pgoff overflow checking

Hi Mike, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on linus/master] [also build test WARNING on v4.16-rc7 next-20180329] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci

general protection fault in try_to_wake_up

Hello, syzbot hit the following crash on upstream commit bcfc1f4554662d8f2429ac8bd96064a59c149754 (Sat Mar 24 16:50:12 2018 +) Merge tag 'pinctrl-v4.16-3' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl syzbot dashboard link:

general protection fault in try_to_wake_up

Hello, syzbot hit the following crash on upstream commit bcfc1f4554662d8f2429ac8bd96064a59c149754 (Sat Mar 24 16:50:12 2018 +) Merge tag 'pinctrl-v4.16-3' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl syzbot dashboard link:

Re: [PATCH net-next 0/6] rxrpc: Fixes

From: David Howells Date: Tue, 27 Mar 2018 23:44:05 +0100 > The patches are tagged here: > > git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git > rxrpc-fixes-20180327 David, this GIT URL has tons of unrelated changes. It seems to bring in the

Re: [PATCH net-next 0/6] rxrpc: Fixes

From: David Howells Date: Tue, 27 Mar 2018 23:44:05 +0100 > The patches are tagged here: > > git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git > rxrpc-fixes-20180327 David, this GIT URL has tons of unrelated changes. It seems to bring in the parts of Linus's tree

Re: [PATCH v4 4/8] dt-bindings: Add doc for the Ingenic TCU drivers

Hi Rob, Le mer. 28 mars 2018 à 18:28, Rob Herring a écrit : On Wed, Mar 28, 2018 at 10:33 AM, Paul Cercueil wrote: Le 2018-03-27 16:46, Rob Herring a écrit : On Sun, Mar 18, 2018 at 12:28:57AM +0100, Paul Cercueil wrote: Add documentation about

Re: [PATCH v4 4/8] dt-bindings: Add doc for the Ingenic TCU drivers

Hi Rob, Le mer. 28 mars 2018 à 18:28, Rob Herring a écrit : On Wed, Mar 28, 2018 at 10:33 AM, Paul Cercueil wrote: Le 2018-03-27 16:46, Rob Herring a écrit : On Sun, Mar 18, 2018 at 12:28:57AM +0100, Paul Cercueil wrote: Add documentation about how to properly use the Ingenic TCU

Reduce init time of `lp_init()` and `ppdev_init()`

Dear Linux folks, I am trying to reduce the start-up time of the Linux kernel on an old Lenovo X60. Looking through the time stamps of Linux 4.16-rc7+, the modules `lp` and `ppdev` both take more than ten milliseconds to initialize according to `initcall_debug`. ``` [8.337692] calling

Reduce init time of `lp_init()` and `ppdev_init()`

Dear Linux folks, I am trying to reduce the start-up time of the Linux kernel on an old Lenovo X60. Looking through the time stamps of Linux 4.16-rc7+, the modules `lp` and `ppdev` both take more than ten milliseconds to initialize according to `initcall_debug`. ``` [8.337692] calling

Re: [PATCH v7 0/5] Add Intel IOMMU debugfs support

On 03/29/2018 03:48 AM, Joerg Roedel wrote: [ Adding Gary from AMD to Cc ] On Mon, Mar 19, 2018 at 09:37:14AM -0700, Jacob Pan wrote: On Thu, 15 Mar 2018 14:18:54 +0100 Joerg Roedel wrote: On Thu, Feb 15, 2018 at 08:38:11AM -0800, Jacob Pan wrote: Just wondering if your

Re: [PATCH v7 0/5] Add Intel IOMMU debugfs support

On 03/29/2018 03:48 AM, Joerg Roedel wrote: [ Adding Gary from AMD to Cc ] On Mon, Mar 19, 2018 at 09:37:14AM -0700, Jacob Pan wrote: On Thu, 15 Mar 2018 14:18:54 +0100 Joerg Roedel wrote: On Thu, Feb 15, 2018 at 08:38:11AM -0800, Jacob Pan wrote: Just wondering if your concern is on the

Re: [PATCH v6 2/2] net: ethernet: nixge: Add support for National Instruments XGE netdev

From: Moritz Fischer Date: Tue, 27 Mar 2018 14:43:15 -0700 > Add support for the National Instruments XGE 1/10G network device. > > It uses the EEPROM on the board via NVMEM. > > Signed-off-by: Moritz Fischer Applied.

Re: [PATCH v6 2/2] net: ethernet: nixge: Add support for National Instruments XGE netdev

From: Moritz Fischer Date: Tue, 27 Mar 2018 14:43:15 -0700 > Add support for the National Instruments XGE 1/10G network device. > > It uses the EEPROM on the board via NVMEM. > > Signed-off-by: Moritz Fischer Applied.

Re: [PATCH 11/19] powerpc/powermac: Move pmac_pfunc_base_install prototype to header file

Mathieu Malaterre a écrit : On Fri, Mar 23, 2018 at 1:13 PM, christophe leroy wrote: Le 22/03/2018 à 21:19, Mathieu Malaterre a écrit : The pmac_pfunc_base_install prototype was declared in powermac/smp.c since function was used there, move it

Re: [PATCH v6 1/2] dt-bindings: net: Add bindings for National Instruments XGE netdev

From: Moritz Fischer Date: Tue, 27 Mar 2018 14:43:14 -0700 > This adds bindings for the NI XGE 1G/10G network device. > > Reviewed-by: Rob Herring > Signed-off-by: Moritz Fischer Applied.

Re: [PATCH v6 1/2] dt-bindings: net: Add bindings for National Instruments XGE netdev

From: Moritz Fischer Date: Tue, 27 Mar 2018 14:43:14 -0700 > This adds bindings for the NI XGE 1G/10G network device. > > Reviewed-by: Rob Herring > Signed-off-by: Moritz Fischer Applied.

Re: [PATCH 11/19] powerpc/powermac: Move pmac_pfunc_base_install prototype to header file

Mathieu Malaterre a écrit : On Fri, Mar 23, 2018 at 1:13 PM, christophe leroy wrote: Le 22/03/2018 à 21:19, Mathieu Malaterre a écrit : The pmac_pfunc_base_install prototype was declared in powermac/smp.c since function was used there, move it to pmac_pfunc.h header to be visible in

Re: omap4-droid4: voice call support was Re: [PATCHv5,5/5] ARM: dts: omap4-droid4: add soundcard

Hi, On Thu, Mar 29, 2018 at 06:59:04AM -0700, Tony Lindgren wrote: > > I think cpcap is always the clock and frame master, but I think > > mdm6600 is the remote side and OMAP is not involved at all. > > OK. So could it be just an alsamixer on/off toggle then for > "Modem" or something similar?

Re: omap4-droid4: voice call support was Re: [PATCHv5,5/5] ARM: dts: omap4-droid4: add soundcard

Hi, On Thu, Mar 29, 2018 at 06:59:04AM -0700, Tony Lindgren wrote: > > I think cpcap is always the clock and frame master, but I think > > mdm6600 is the remote side and OMAP is not involved at all. > > OK. So could it be just an alsamixer on/off toggle then for > "Modem" or something similar?

Re: [PATCH 2/8] PCI: Add pci_find_common_upstream_dev()

On 29/03/18 05:44 AM, Christian König wrote: > Am 28.03.2018 um 21:53 schrieb Logan Gunthorpe: >> >> On 28/03/18 01:44 PM, Christian König wrote: >>> Well, isn't that exactly what dma_map_resource() is good for? As far as >>> I can see it makes sure IOMMU is aware of the access route and >>>

Re: [PATCH 2/8] PCI: Add pci_find_common_upstream_dev()

On 29/03/18 05:44 AM, Christian König wrote: > Am 28.03.2018 um 21:53 schrieb Logan Gunthorpe: >> >> On 28/03/18 01:44 PM, Christian König wrote: >>> Well, isn't that exactly what dma_map_resource() is good for? As far as >>> I can see it makes sure IOMMU is aware of the access route and >>>

Re: [PATCH v7 06/14] ext2, dax: introduce ext2_dax_aops

On Wed 21-03-18 15:57:43, Dan Williams wrote: > In preparation for the dax implementation to start associating dax pages > to inodes via page->mapping, we need to provide a 'struct > address_space_operations' instance for dax. Otherwise, direct-I/O > triggers incorrect page cache assumptions and

Re: [PATCH v7 06/14] ext2, dax: introduce ext2_dax_aops

On Wed 21-03-18 15:57:43, Dan Williams wrote: > In preparation for the dax implementation to start associating dax pages > to inodes via page->mapping, we need to provide a 'struct > address_space_operations' instance for dax. Otherwise, direct-I/O > triggers incorrect page cache assumptions and

[PATCH 0/6] FPGA Manager Patches for 4.17

Hi Greg, can you please take the following patches for 4.17. Alan's changes are mostly refactoring in preparation for non-dt based FPGA regions. Anatolij's changes fix a small issue with altera-ps-spi FPGAs, where the FPGA is being reset unnessesarily on driver load. All patches have been

[PATCH 0/6] FPGA Manager Patches for 4.17

Hi Greg, can you please take the following patches for 4.17. Alan's changes are mostly refactoring in preparation for non-dt based FPGA regions. Anatolij's changes fix a small issue with altera-ps-spi FPGAs, where the FPGA is being reset unnessesarily on driver load. All patches have been

[PATCH 1/6] fpga: region: don't use drvdata in common fpga code

From: Alan Tull Part of patchset that changes the following fpga_*_register functions to not set drvdata: * fpga_region_register. * fpga_mgr_register * fpga_bridge_register The rationale is that setting drvdata is fine for DT based devices that will have one manager, bridge,

[PATCH 1/6] fpga: region: don't use drvdata in common fpga code

From: Alan Tull Part of patchset that changes the following fpga_*_register functions to not set drvdata: * fpga_region_register. * fpga_mgr_register * fpga_bridge_register The rationale is that setting drvdata is fine for DT based devices that will have one manager, bridge, or region per

[PATCH 3/6] fpga: bridge: don't use drvdata in common fpga code

From: Alan Tull Change fpga_bridge_register to not set drvdata. Change the register/unregister functions parameters to take the bridge struct: * int fpga_bridge_register(struct fpga_bridge *bridge); * void fpga_bridge_unregister(struct fpga_bridge *bridge); Change the drivers

[PATCH 3/6] fpga: bridge: don't use drvdata in common fpga code

From: Alan Tull Change fpga_bridge_register to not set drvdata. Change the register/unregister functions parameters to take the bridge struct: * int fpga_bridge_register(struct fpga_bridge *bridge); * void fpga_bridge_unregister(struct fpga_bridge *bridge); Change the drivers that call

[PATCH 2/6] fpga: manager: don't use drvdata in common fpga code

From: Alan Tull Change fpga_mgr_register to not set or use drvdata. Change the register/unregister function parameters to take the mgr struct: * int fpga_mgr_register(struct fpga_manager *mgr); * void fpga_mgr_unregister(struct fpga_manager *mgr); Change the drivers that call

[PATCH 2/6] fpga: manager: don't use drvdata in common fpga code

From: Alan Tull Change fpga_mgr_register to not set or use drvdata. Change the register/unregister function parameters to take the mgr struct: * int fpga_mgr_register(struct fpga_manager *mgr); * void fpga_mgr_unregister(struct fpga_manager *mgr); Change the drivers that call fpga_mgr_register

[PATCH 5/6] fpga: fpga-region: comment on fpga_region_program_fpga locking

From: Alan Tull Add a comment to the header of fpga_region_program_fpga() regarding locking of the bridges. Signed-off-by: Alan Tull Signed-off-by: Moritz Fischer --- drivers/fpga/fpga-region.c | 5 + 1 file changed, 5 insertions(+)

[PATCH 5/6] fpga: fpga-region: comment on fpga_region_program_fpga locking

From: Alan Tull Add a comment to the header of fpga_region_program_fpga() regarding locking of the bridges. Signed-off-by: Alan Tull Signed-off-by: Moritz Fischer --- drivers/fpga/fpga-region.c | 5 + 1 file changed, 5 insertions(+) diff --git a/drivers/fpga/fpga-region.c

Re: [PATCH v4 1/3] perf/core: store context switch out type into Perf trace

Hi, On Thu, Mar 29, 2018 at 06:02:48PM +0300, Alexey Budankov wrote: > diff --git a/include/uapi/linux/perf_event.h b/include/uapi/linux/perf_event.h > index 912b85b52344..cd6ad7e13824 100644 > --- a/include/uapi/linux/perf_event.h > +++ b/include/uapi/linux/perf_event.h > @@ -655,6 +655,10 @@

Re: [PATCH v4 1/3] perf/core: store context switch out type into Perf trace

Hi, On Thu, Mar 29, 2018 at 06:02:48PM +0300, Alexey Budankov wrote: > diff --git a/include/uapi/linux/perf_event.h b/include/uapi/linux/perf_event.h > index 912b85b52344..cd6ad7e13824 100644 > --- a/include/uapi/linux/perf_event.h > +++ b/include/uapi/linux/perf_event.h > @@ -655,6 +655,10 @@

[PATCH 6/6] fpga-manager: altera-ps-spi: preserve nCONFIG state

From: Anatolij Gustschin If the driver module is loaded when FPGA is configured, the FPGA is reset because nconfig is pulled low (low-active gpio inited with GPIOD_OUT_HIGH activates the signal which means setting its value to low). Init nconfig with GPIOD_OUT_LOW to prevent this.

[PATCH 6/6] fpga-manager: altera-ps-spi: preserve nCONFIG state

From: Anatolij Gustschin If the driver module is loaded when FPGA is configured, the FPGA is reset because nconfig is pulled low (low-active gpio inited with GPIOD_OUT_HIGH activates the signal which means setting its value to low). Init nconfig with GPIOD_OUT_LOW to prevent this.

[PATCH 4/6] fpga: region: change fpga_region_register to have one param

From: Alan Tull Change fpga_region_register to only take one parameter: int fpga_region_register(struct fpga_region *region) The parent dev is added to struct fpga_region. This make it similar to fpga_bridge_register and fpga_mgr_register which also just take their

[PATCH 4/6] fpga: region: change fpga_region_register to have one param

From: Alan Tull Change fpga_region_register to only take one parameter: int fpga_region_register(struct fpga_region *region) The parent dev is added to struct fpga_region. This make it similar to fpga_bridge_register and fpga_mgr_register which also just take their respective struct. The

[PATCH v2] kbuild: use -fmacro-prefix-map to make __FILE__ a relative path

The __FILE__ macro is used everywhere in the kernel to locate the file path printing the log message. The biggest users of this macro are WARN_ON() and friends. If the kernel is built out of tree, this could be a long absolute path, like this: WARNING: CPU: 1 PID: 1 at

[PATCH v2] kbuild: use -fmacro-prefix-map to make __FILE__ a relative path

The __FILE__ macro is used everywhere in the kernel to locate the file path printing the log message. The biggest users of this macro are WARN_ON() and friends. If the kernel is built out of tree, this could be a long absolute path, like this: WARNING: CPU: 1 PID: 1 at

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