[PATCH 10/15] ata: pata_pxa: remove the dmaengine compat need

As the pxa architecture switched towards the dmaengine slave map, the old compatibility mechanism to acquire the dma requestor line number and priority are not needed anymore. This patch simplifies the dma resource acquisition, using the more generic function dma_request_slave_channel().

[PATCH 11/15] dmaengine: pxa: document pxad_param

Add some documentation for the pxad_param structure, and describe the contract behind the minimal required priority of a DMA channel. Signed-off-by: Robert Jarzmik --- include/linux/dma/pxa-dma.h | 9 + 1 file changed, 9 insertions(+) diff --git a/include/linux/dma/pxa-dma.h

[PATCH] checkpatch: relax check for revert commit

For revert commit, it might has two double quotation marks in its commit log. Relax the check condition for revert commit to avoid checkpatch errors. Signed-off-by: Jia He --- scripts/checkpatch.pl | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-)

[PATCH] checkpatch: relax check for revert commit

For revert commit, it might has two double quotation marks in its commit log. Relax the check condition for revert commit to avoid checkpatch errors. Signed-off-by: Jia He --- scripts/checkpatch.pl | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git

[PATCH] relax check regex for revert commit

For revert commit, it might has two double quotation marks in its commit log. Relax the check condition for revert commit to avoid checkpatch errors. Without this patch, checkpatch.pl will report errors: ERROR: Please use git commit description style ... Attached testcases here: [test case 1]

[PATCH 15/15] ARM: pxa: change SSP DMA channels allocation

Now the dma_slave_map is available for PXA architecture, switch the SSP device to it. This specifically means that : - for platform data based machines, the DMA requestor channels are extracted from platform data and passed further to the SSP user, ie. usually the pxa-pcm-audio driver - for

[PATCH] relax check regex for revert commit

For revert commit, it might has two double quotation marks in its commit log. Relax the check condition for revert commit to avoid checkpatch errors. Without this patch, checkpatch.pl will report errors: ERROR: Please use git commit description style ... Attached testcases here: [test case 1]

[PATCH 15/15] ARM: pxa: change SSP DMA channels allocation

Now the dma_slave_map is available for PXA architecture, switch the SSP device to it. This specifically means that : - for platform data based machines, the DMA requestor channels are extracted from platform data and passed further to the SSP user, ie. usually the pxa-pcm-audio driver - for

[PATCH 12/15] dmaengine: pxa: make the filter function internal

As the pxa architecture and all its related drivers do not rely anymore on the filter function, thanks to the slave map conversion, make pxad_filter_fn() static, and remove it from the global namespace. Signed-off-by: Robert Jarzmik --- drivers/dma/pxa_dma.c | 5

[PATCH 12/15] dmaengine: pxa: make the filter function internal

As the pxa architecture and all its related drivers do not rely anymore on the filter function, thanks to the slave map conversion, make pxad_filter_fn() static, and remove it from the global namespace. Signed-off-by: Robert Jarzmik --- drivers/dma/pxa_dma.c | 5 ++---

[PATCH 14/15] ARM: pxa: change SSP devices allocation

In order to prepare for the dma_slave_map change for SSP DMA channels allocation, the SSP platform devices will now include a platform data structure which in turn selects which dma channel has to be used for data transfers, especially the PCM ones. Signed-off-by: Robert Jarzmik

[PATCH 14/15] ARM: pxa: change SSP devices allocation

In order to prepare for the dma_slave_map change for SSP DMA channels allocation, the SSP platform devices will now include a platform data structure which in turn selects which dma channel has to be used for data transfers, especially the PCM ones. Signed-off-by: Robert Jarzmik ---

[PATCH 13/15] ARM: pxa: remove the DMA IO resources

As the last driver using the former mechanism to acquire the DMA requestor line has be converted to the dma_slave_map, remove all these resources from the PXA devices. Signed-off-by: Robert Jarzmik --- arch/arm/mach-pxa/devices.c | 136

[PATCH 13/15] ARM: pxa: remove the DMA IO resources

As the last driver using the former mechanism to acquire the DMA requestor line has be converted to the dma_slave_map, remove all these resources from the PXA devices. Signed-off-by: Robert Jarzmik --- arch/arm/mach-pxa/devices.c | 136 1 file

[PATCH 07/15] net: smc91x: remove the dmaengine compat need

From: Robert Jarzmik As the pxa architecture switched towards the dmaengine slave map, the old compatibility mechanism to acquire the dma requestor line number and priority are not needed anymore. This patch simplifies the dma resource acquisition, using the more

[PATCH 01/15] dmaengine: pxa: use a dma slave map

In order to remove the specific knowledge of the dma mapping from PXA drivers, add a default slave map for pxa architectures. This won't impact MMP architecture, but is aimed only at all PXA boards. This is the first step, and once all drivers are converted, pxad_filter_fn() will be made static,

[PATCH 07/15] net: smc91x: remove the dmaengine compat need

From: Robert Jarzmik As the pxa architecture switched towards the dmaengine slave map, the old compatibility mechanism to acquire the dma requestor line number and priority are not needed anymore. This patch simplifies the dma resource acquisition, using the more generic function

[PATCH 01/15] dmaengine: pxa: use a dma slave map

In order to remove the specific knowledge of the dma mapping from PXA drivers, add a default slave map for pxa architectures. This won't impact MMP architecture, but is aimed only at all PXA boards. This is the first step, and once all drivers are converted, pxad_filter_fn() will be made static,

[PATCH 03/15] mmc: pxamci: remove the dmaengine compat need

As the pxa architecture switched towards the dmaengine slave map, the old compatibility mechanism to acquire the dma requestor line number and priority are not needed anymore. This patch simplifies the dma resource acquisition, using the more generic function dma_request_slave_channel().

[PATCH 05/15] mtd: nand: pxa3xx: remove the dmaengine compat need

From: Robert Jarzmik As the pxa architecture switched towards the dmaengine slave map, the old compatibility mechanism to acquire the dma requestor line number and priority are not needed anymore. This patch simplifies the dma resource acquisition, using the more

[PATCH 06/15] net: smc911x: remove the dmaengine compat need

From: Robert Jarzmik As the pxa architecture switched towards the dmaengine slave map, the old compatibility mechanism to acquire the dma requestor line number and priority are not needed anymore. This patch simplifies the dma resource acquisition, using the more

[PATCH 03/15] mmc: pxamci: remove the dmaengine compat need

As the pxa architecture switched towards the dmaengine slave map, the old compatibility mechanism to acquire the dma requestor line number and priority are not needed anymore. This patch simplifies the dma resource acquisition, using the more generic function dma_request_slave_channel().

[PATCH 05/15] mtd: nand: pxa3xx: remove the dmaengine compat need

From: Robert Jarzmik As the pxa architecture switched towards the dmaengine slave map, the old compatibility mechanism to acquire the dma requestor line number and priority are not needed anymore. This patch simplifies the dma resource acquisition, using the more generic function

[PATCH 06/15] net: smc911x: remove the dmaengine compat need

From: Robert Jarzmik As the pxa architecture switched towards the dmaengine slave map, the old compatibility mechanism to acquire the dma requestor line number and priority are not needed anymore. This patch simplifies the dma resource acquisition, using the more generic function

[PATCH 00/15] ARM: pxa: switch to DMA slave maps

Hi, This serie is aimed at removing the dmaengine slave compat use, and transfer knowledge of the DMA requestors into architecture code. This was discussed/advised by Arnd a couple of years back, it's almost time. The serie is divided in 3 phasees : - phase 1 : patch 1/15 and patch 2/15 =>

[PATCH 00/15] ARM: pxa: switch to DMA slave maps

Hi, This serie is aimed at removing the dmaengine slave compat use, and transfer knowledge of the DMA requestors into architecture code. This was discussed/advised by Arnd a couple of years back, it's almost time. The serie is divided in 3 phasees : - phase 1 : patch 1/15 and patch 2/15 =>

[PULL] Documentation for 4.17

The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2: Linux 4.16-rc1 (2018-02-11 15:04:29 -0800) are available in the Git repository at: git://git.lwn.net/linux.git tags/docs-4.17 for you to fetch changes up to 86afad7d87f535ebb1a0e978bc32a8c58ac99268:

[PULL] Documentation for 4.17

The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2: Linux 4.16-rc1 (2018-02-11 15:04:29 -0800) are available in the Git repository at: git://git.lwn.net/linux.git tags/docs-4.17 for you to fetch changes up to 86afad7d87f535ebb1a0e978bc32a8c58ac99268:

Re: [PATCH 2/2] perf: add arm64 smmuv3 pmu driver

On 2018/4/2 14:37, Yisheng Xie wrote: > Hi Neil, > > On 2018/4/1 13:44, Neil Leeder wrote: >> Hi Yisheng Xie, >> >> On 3/29/2018 03:03 AM, Yisheng Xie wrote: >>> >>> Hi Neil, >>> >>> On 2017/8/5 3:59, Neil Leeder wrote: +mem_resource_0 = platform_get_resource(pdev, IORESOURCE_MEM, 0);

Re: [PATCH 2/2] perf: add arm64 smmuv3 pmu driver

On 2018/4/2 14:37, Yisheng Xie wrote: > Hi Neil, > > On 2018/4/1 13:44, Neil Leeder wrote: >> Hi Yisheng Xie, >> >> On 3/29/2018 03:03 AM, Yisheng Xie wrote: >>> >>> Hi Neil, >>> >>> On 2017/8/5 3:59, Neil Leeder wrote: +mem_resource_0 = platform_get_resource(pdev, IORESOURCE_MEM, 0);

Re: [PATCH v1] PCI/DPC: Rename from pcie-dpc.c to dpc.c.

On Sat, Mar 31, 2018 at 05:34:26PM -0500, Bjorn Helgaas wrote: > From: Bjorn Helgaas > > Rename from pcie-dpc.c to dpc.c. The path "drivers/pci/pcie/pcie-dpc.c" > has more occurrences of "pci" than necessary. > > Signed-off-by: Bjorn Helgaas Looks

Re: [PATCH v1] PCI/DPC: Rename from pcie-dpc.c to dpc.c.

On Sat, Mar 31, 2018 at 05:34:26PM -0500, Bjorn Helgaas wrote: > From: Bjorn Helgaas > > Rename from pcie-dpc.c to dpc.c. The path "drivers/pci/pcie/pcie-dpc.c" > has more occurrences of "pci" than necessary. > > Signed-off-by: Bjorn Helgaas Looks good. Acked-by: Keith Busch

Re: [PATCH] nvmet: fix nvmet_execute_write_zeroes function

On Mon, Apr 02, 2018 at 10:47:10AM -0300, Rodrigo Rosatti Galvao wrote: > One thing that I just forgot to explain previously, but I think its > relevant: > > 1. The command is failing with 4k logical block size, but works with 512B > > 2. With the patch, the command is working for both 512B and

Re: [PATCH] nvmet: fix nvmet_execute_write_zeroes function

On Mon, Apr 02, 2018 at 10:47:10AM -0300, Rodrigo Rosatti Galvao wrote: > One thing that I just forgot to explain previously, but I think its > relevant: > > 1. The command is failing with 4k logical block size, but works with 512B > > 2. With the patch, the command is working for both 512B and

Re: [PATCH 1/2] lib: vsprintf: Implement %pCOW

On Sun, 2018-04-01 at 10:56 +0200, Richard Weinberger wrote: > Add a new format string to print in cowsay format. > Apparently NAK b/c missed test cases! > Signed-off-by: Richard Weinberger > --- > lib/vsprintf.c | 52 > > 1

Re: [PATCH 1/2] lib: vsprintf: Implement %pCOW

On Sun, 2018-04-01 at 10:56 +0200, Richard Weinberger wrote: > Add a new format string to print in cowsay format. > Apparently NAK b/c missed test cases! > Signed-off-by: Richard Weinberger > --- > lib/vsprintf.c | 52 > > 1 file changed,

Re: [PATCH v3] vsprintf: Prevent crash when dereferencing invalid pointers

On Thu, 2018-03-29 at 16:53 +0200, Petr Mladek wrote: > On Fri 2018-03-16 20:19:35, Andy Shevchenko wrote: > > On Thu, 2018-03-15 at 16:26 +0100, Petr Mladek wrote: > > > On Thu 2018-03-15 15:09:03, Andy Shevchenko wrote: > > > > I still think that printing a hex value of the error code is > > >

Re: [PATCH v3] vsprintf: Prevent crash when dereferencing invalid pointers

On Thu, 2018-03-29 at 16:53 +0200, Petr Mladek wrote: > On Fri 2018-03-16 20:19:35, Andy Shevchenko wrote: > > On Thu, 2018-03-15 at 16:26 +0100, Petr Mladek wrote: > > > On Thu 2018-03-15 15:09:03, Andy Shevchenko wrote: > > > > I still think that printing a hex value of the error code is > > >

[PATCH] locking/hung_task: Show all hung tasks before panic

When we get a hung task it can often be valuable to see _all_ the hung tasks on the system before calling panic(). Quoting from https://syzkaller.appspot.com/text?tag=CrashReport=5412451675799552 INFO: task syz-executor3:13421 blocked for more than 120

[PATCH] locking/hung_task: Show all hung tasks before panic

When we get a hung task it can often be valuable to see _all_ the hung tasks on the system before calling panic(). Quoting from https://syzkaller.appspot.com/text?tag=CrashReport=5412451675799552 INFO: task syz-executor3:13421 blocked for more than 120

Signal handling in a page fault handler

Souptick and I have been auditing the various page fault handler routines and we've noticed that graphics drivers assume that a signal should be able to interrupt a page fault. In contrast, the page cache takes great care to allow only fatal signals to interrupt a page fault. I believe (but

Signal handling in a page fault handler

Souptick and I have been auditing the various page fault handler routines and we've noticed that graphics drivers assume that a signal should be able to interrupt a page fault. In contrast, the page cache takes great care to allow only fatal signals to interrupt a page fault. I believe (but

Re: [PATCH v5 03/14] PCI: Add pcie_bandwidth_capable() to compute max supported link bandwidth

On Mon, Apr 02, 2018 at 10:34:58AM +0300, Tal Gilboa wrote: > On 4/2/2018 3:40 AM, Bjorn Helgaas wrote: > > On Sun, Apr 01, 2018 at 11:38:53PM +0300, Tal Gilboa wrote: > > > On 3/31/2018 12:05 AM, Bjorn Helgaas wrote: > > > > From: Tal Gilboa > > > > > > > > Add

Re: [PATCH v5 03/14] PCI: Add pcie_bandwidth_capable() to compute max supported link bandwidth

On Mon, Apr 02, 2018 at 10:34:58AM +0300, Tal Gilboa wrote: > On 4/2/2018 3:40 AM, Bjorn Helgaas wrote: > > On Sun, Apr 01, 2018 at 11:38:53PM +0300, Tal Gilboa wrote: > > > On 3/31/2018 12:05 AM, Bjorn Helgaas wrote: > > > > From: Tal Gilboa > > > > > > > > Add pcie_bandwidth_capable() to

[PATCH] Input: synaptics-rmi4 - Fix an unchecked out of memory error path

When extending the rmi_spi buffers, we must check that no out of memory error occurs, otherwise we may access data above the currently allocated memory. Propagate the error code returned by 'rmi_spi_manage_pools()' instead. Signed-off-by: Christophe JAILLET ---

Re: [PATCH v2 1/3] locking: Document the semantics of spin_is_locked()

On Sun, 1 Apr 2018, Andrea Parri wrote: > There appeared to be a certain, recurrent uncertainty concerning the > semantics of spin_is_locked(), likely a consequence of the fact that > this semantics remains undocumented or that it has been historically > linked to the (likewise unclear) semantics

[PATCH] Input: synaptics-rmi4 - Fix an unchecked out of memory error path

When extending the rmi_spi buffers, we must check that no out of memory error occurs, otherwise we may access data above the currently allocated memory. Propagate the error code returned by 'rmi_spi_manage_pools()' instead. Signed-off-by: Christophe JAILLET --- drivers/input/rmi4/rmi_spi.c | 7

Re: [PATCH v2 1/3] locking: Document the semantics of spin_is_locked()

On Sun, 1 Apr 2018, Andrea Parri wrote: > There appeared to be a certain, recurrent uncertainty concerning the > semantics of spin_is_locked(), likely a consequence of the fact that > this semantics remains undocumented or that it has been historically > linked to the (likewise unclear) semantics

Re: [PATCH v2] serial: 8250: omap: Provide ability to enable/disable UART as wakeup source

On Mon, Apr 2, 2018 at 5:01 PM, Andy Shevchenko wrote: > On Mon, Apr 2, 2018 at 3:20 PM, Vignesh R wrote: >> + if (!device_may_wakeup(dev)) >> + priv->wer = 0; > > Can it be > > priv->wer = device_may_wakeup(dev); > > ? Answering

Re: [PATCH v2] serial: 8250: omap: Provide ability to enable/disable UART as wakeup source

On Mon, Apr 2, 2018 at 5:01 PM, Andy Shevchenko wrote: > On Mon, Apr 2, 2018 at 3:20 PM, Vignesh R wrote: >> + if (!device_may_wakeup(dev)) >> + priv->wer = 0; > > Can it be > > priv->wer = device_may_wakeup(dev); > > ? Answering to myself, missed that this value is used as

Re: [PATCH v2] serial: 8250: omap: Provide ability to enable/disable UART as wakeup source

On Mon, Apr 2, 2018 at 3:20 PM, Vignesh R wrote: > + pm_runtime_get_sync(dev); > + if (!device_may_wakeup(dev)) > + priv->wer = 0; Can it be priv->wer = device_may_wakeup(dev); ? > + serial_out(up, UART_OMAP_WER, priv->wer); > +

Re: [PATCH v2] serial: 8250: omap: Provide ability to enable/disable UART as wakeup source

On Mon, Apr 2, 2018 at 3:20 PM, Vignesh R wrote: > + pm_runtime_get_sync(dev); > + if (!device_may_wakeup(dev)) > + priv->wer = 0; Can it be priv->wer = device_may_wakeup(dev); ? > + serial_out(up, UART_OMAP_WER, priv->wer); > +

What is the universal (world wide) understanding behind degaussing harddisks?

Good evening from Singapore! The foremost question which I want to ask is, what is the universal (world wide) understanding behind degaussing hard drives? I work for No Secrets Agency (NSA) Pte Ltd (fictitious company name used). My sales manager Edward Joseph Snowden (fictitious individual name

What is the universal (world wide) understanding behind degaussing harddisks?

Good evening from Singapore! The foremost question which I want to ask is, what is the universal (world wide) understanding behind degaussing hard drives? I work for No Secrets Agency (NSA) Pte Ltd (fictitious company name used). My sales manager Edward Joseph Snowden (fictitious individual name

Re: [PATCH] scsi: hosts: remove redundant assingment of shost->use_blk_mq

On Mon, 2018-04-02 at 11:37 +0200, Johannes Thumshirn wrote: > Coverity reports that we're assigning shost->use_blk_mq twice. This > looks like the result of a bad merge of commit 2f31115e940c ("scsi: > core: introduce force_blk_mq") > > Signed-off-by: Johannes Thumshirn >

Re: [PATCH] scsi: hosts: remove redundant assingment of shost->use_blk_mq

On Mon, 2018-04-02 at 11:37 +0200, Johannes Thumshirn wrote: > Coverity reports that we're assigning shost->use_blk_mq twice. This > looks like the result of a bad merge of commit 2f31115e940c ("scsi: > core: introduce force_blk_mq") > > Signed-off-by: Johannes Thumshirn > --- >

Re: [PATCH] drm/amd/display: fix spelling mistake: "Usupported" -> "Unsupported"

On 2018-03-30 12:00 PM, Colin King wrote: > From: Colin Ian King > > Trivial fix to spelling mistake in DRM_ERROR error message text > > Signed-off-by: Colin Ian King Reviewed-by: Harry Wentland Harry > --- >

Re: [BISECTED][REGRESSION] Hang while booting EeePC 900

On Sun, 2018-04-01 at 15:35 +0100, Sitsofe Wheeler wrote: > While trying to boot an EeePC 900 on the latest git mainline kernel a > hang is encountered while systemd is starting services but this did > not happen with 4.15. A bisection narrowed it down to the commit >

Re: [PATCH] drm/amd/display: fix spelling mistake: "Usupported" -> "Unsupported"

On 2018-03-30 12:00 PM, Colin King wrote: > From: Colin Ian King > > Trivial fix to spelling mistake in DRM_ERROR error message text > > Signed-off-by: Colin Ian King Reviewed-by: Harry Wentland Harry > --- > drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 4 ++-- > 1 file changed, 2

Re: [BISECTED][REGRESSION] Hang while booting EeePC 900

On Sun, 2018-04-01 at 15:35 +0100, Sitsofe Wheeler wrote: > While trying to boot an EeePC 900 on the latest git mainline kernel a > hang is encountered while systemd is starting services but this did > not happen with 4.15. A bisection narrowed it down to the commit >

Re: [PATCH] nvmet: fix nvmet_execute_write_zeroes function

One thing that I just forgot to explain previously, but I think its relevant: 1. The command is failing with 4k logical block size, but works with 512B 2. With the patch, the command is working for both 512B and 4K. Here are some extra information I could get when executing the command with

Re: [PATCH] nvmet: fix nvmet_execute_write_zeroes function

One thing that I just forgot to explain previously, but I think its relevant: 1. The command is failing with 4k logical block size, but works with 512B 2. With the patch, the command is working for both 512B and 4K. Here are some extra information I could get when executing the command with

RE: [PATCH v3 4/4] bus: fsl-mc: add bus rescan attribute

> > Introduce the rescan attribute as a bus attribute to synchronize the > > fsl-mc bus objects and the MC firmware. > > > > To rescan the fsl-mc bus, e.g., > > echo 1 > /sys/bus/fsl-mc/rescan > > > > Signed-off-by: Ioana Ciornei > > --- > > Changes in v2: > > - added

RE: [PATCH v3 4/4] bus: fsl-mc: add bus rescan attribute

> > Introduce the rescan attribute as a bus attribute to synchronize the > > fsl-mc bus objects and the MC firmware. > > > > To rescan the fsl-mc bus, e.g., > > echo 1 > /sys/bus/fsl-mc/rescan > > > > Signed-off-by: Ioana Ciornei > > --- > > Changes in v2: > > - added proper documentation in

Re: [PATCH] nvmet: fix nvmet_execute_write_zeroes function

On Fri, Mar 30, 2018 at 06:18:50PM -0300, Rodrigo R. Galvao wrote: > sector = le64_to_cpu(write_zeroes->slba) << > (req->ns->blksize_shift - 9); > nr_sector = (((sector_t)le16_to_cpu(write_zeroes->length)) << > - (req->ns->blksize_shift - 9)) + 1; > +

Re: [PATCH] nvmet: fix nvmet_execute_write_zeroes function

On Fri, Mar 30, 2018 at 06:18:50PM -0300, Rodrigo R. Galvao wrote: > sector = le64_to_cpu(write_zeroes->slba) << > (req->ns->blksize_shift - 9); > nr_sector = (((sector_t)le16_to_cpu(write_zeroes->length)) << > - (req->ns->blksize_shift - 9)) + 1; > +

Re: [PATCH v3 2/4] bus: fsl-mc: add restool userspace support

Hi Ioana > The commands listed above are for creating/destroying DPAA2 objects > in Management Complex and not for runtime configuration where > standard userspace tools are used. Please can you explain why this is not just plumbing inside a switchdev driver? The hardware has a number of

Re: [PATCH v3 2/4] bus: fsl-mc: add restool userspace support

Hi Ioana > The commands listed above are for creating/destroying DPAA2 objects > in Management Complex and not for runtime configuration where > standard userspace tools are used. Please can you explain why this is not just plumbing inside a switchdev driver? The hardware has a number of

Re: INFO: task hung in perf_trace_event_unreg

On Mon, 02 Apr 2018 02:20:02 -0700 syzbot wrote: > Hello, > > syzbot hit the following crash on upstream commit > 0adb32858b0bddf4ada5f364a84ed60b196dbcda (Sun Apr 1 21:20:27 2018 +) > Linux 4.16 > syzbot dashboard link: >

Re: INFO: task hung in perf_trace_event_unreg

On Mon, 02 Apr 2018 02:20:02 -0700 syzbot wrote: > Hello, > > syzbot hit the following crash on upstream commit > 0adb32858b0bddf4ada5f364a84ed60b196dbcda (Sun Apr 1 21:20:27 2018 +) > Linux 4.16 > syzbot dashboard link: > https://syzkaller.appspot.com/bug?extid=2dbc55da20fa246378fd > >

Re: [PATCH v6 1/3] dt-bindings: display: bridge: Document THC63LVD1024 LVDS decoder

Hi Vladimir, On Tuesday, 27 March 2018 14:03:25 EEST Vladimir Zapolskiy wrote: > On 03/27/2018 01:10 PM, jacopo mondi wrote: > > On Tue, Mar 27, 2018 at 12:37:31PM +0300, Vladimir Zapolskiy wrote: > >> On 03/27/2018 11:57 AM, jacopo mondi wrote: > >>> On Tue, Mar 27, 2018 at 11:30:29AM +0300,

Re: [PATCH v6 1/3] dt-bindings: display: bridge: Document THC63LVD1024 LVDS decoder

Hi Vladimir, On Tuesday, 27 March 2018 14:03:25 EEST Vladimir Zapolskiy wrote: > On 03/27/2018 01:10 PM, jacopo mondi wrote: > > On Tue, Mar 27, 2018 at 12:37:31PM +0300, Vladimir Zapolskiy wrote: > >> On 03/27/2018 11:57 AM, jacopo mondi wrote: > >>> On Tue, Mar 27, 2018 at 11:30:29AM +0300,

[git pull] m68k updates for 4.17

Hi Linus, The following changes since commit 0c8efd610b58cb23cefdfa12015799079aef94ae: Linux 4.16-rc5 (2018-03-11 17:25:09 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git tags/m68k-for-v4.17-tag1 for you to fetch

[git pull] m68k updates for 4.17

Hi Linus, The following changes since commit 0c8efd610b58cb23cefdfa12015799079aef94ae: Linux 4.16-rc5 (2018-03-11 17:25:09 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git tags/m68k-for-v4.17-tag1 for you to fetch

Re: [Question] MFD driver that handles clocks/resets and populates child nodes

On Mon, Apr 02, 2018 at 10:21:01PM +0900, Masahiro Yamada wrote: > 2018-04-02 21:04 GMT+09:00 Andrew Lunn : > >> The maintainer of DWC3, Felipe Balbi, requested to > >> split the glue layer driver into small parts such as > >> reset, regulator, phy, etc. > > > > What exactly did

Re: [Question] MFD driver that handles clocks/resets and populates child nodes

On Mon, Apr 02, 2018 at 10:21:01PM +0900, Masahiro Yamada wrote: > 2018-04-02 21:04 GMT+09:00 Andrew Lunn : > >> The maintainer of DWC3, Felipe Balbi, requested to > >> split the glue layer driver into small parts such as > >> reset, regulator, phy, etc. > > > > What exactly did Felipe ask for?

[PATCH] PCI: endpoint: Create configfs entry for each pci_epf_device_id table entry

In order to be able to provide correct driver_data for pci_epf device, a separate configfs entry for each pci_epf_device_id table entry in pci_epf_driver is required. Add support to create configfs entry for each pci_epf_device_id table entry here. Signed-off-by: Kishon Vijay Abraham I

[PATCH] PCI: endpoint: Create configfs entry for each pci_epf_device_id table entry

In order to be able to provide correct driver_data for pci_epf device, a separate configfs entry for each pci_epf_device_id table entry in pci_epf_driver is required. Add support to create configfs entry for each pci_epf_device_id table entry here. Signed-off-by: Kishon Vijay Abraham I ---

RE: [PATCH v3 2/4] bus: fsl-mc: add restool userspace support

> > > I'm still not convinced either way (high-level or low-level > > interface), but I think this needs to be discussed with the networking > > maintainers. Given the examples on the github page you linked to, the > > high-level user space commands based on these ioctls > > > >ls-addni #

RE: [PATCH v3 2/4] bus: fsl-mc: add restool userspace support

> > > I'm still not convinced either way (high-level or low-level > > interface), but I think this needs to be discussed with the networking > > maintainers. Given the examples on the github page you linked to, the > > high-level user space commands based on these ioctls > > > >ls-addni #

Re: [PATCH v3 3/8] efi: Decode IA32/X64 Processor Error Info Structure

On 2 April 2018 at 15:21, Ghannam, Yazen wrote: >> -Original Message- >> From: Ard Biesheuvel >> Sent: Friday, March 30, 2018 7:25 AM >> To: Ghannam, Yazen >> Cc: Borislav Petkov ;

Re: [PATCH v3 3/8] efi: Decode IA32/X64 Processor Error Info Structure

On 2 April 2018 at 15:21, Ghannam, Yazen wrote: >> -Original Message- >> From: Ard Biesheuvel >> Sent: Friday, March 30, 2018 7:25 AM >> To: Ghannam, Yazen >> Cc: Borislav Petkov ; linux-...@vger.kernel.org; linux- >> ker...@vger.kernel.org; x...@kernel.org; tony.l...@intel.com >>

RE: [PATCH v3 3/8] efi: Decode IA32/X64 Processor Error Info Structure

> -Original Message- > From: Ard Biesheuvel > Sent: Friday, March 30, 2018 7:25 AM > To: Ghannam, Yazen > Cc: Borislav Petkov ; linux-...@vger.kernel.org; linux- > ker...@vger.kernel.org; x...@kernel.org;

RE: [PATCH v3 3/8] efi: Decode IA32/X64 Processor Error Info Structure

> -Original Message- > From: Ard Biesheuvel > Sent: Friday, March 30, 2018 7:25 AM > To: Ghannam, Yazen > Cc: Borislav Petkov ; linux-...@vger.kernel.org; linux- > ker...@vger.kernel.org; x...@kernel.org; tony.l...@intel.com > Subject: Re: [PATCH v3 3/8] efi: Decode IA32/X64 Processor

Re: [Question] MFD driver that handles clocks/resets and populates child nodes

2018-04-02 21:04 GMT+09:00 Andrew Lunn : >> The maintainer of DWC3, Felipe Balbi, requested to >> split the glue layer driver into small parts such as >> reset, regulator, phy, etc. > > What exactly did Felipe ask for? Did he ask that the patch be split > up, one patch per reset,

Re: [Question] MFD driver that handles clocks/resets and populates child nodes

2018-04-02 21:04 GMT+09:00 Andrew Lunn : >> The maintainer of DWC3, Felipe Balbi, requested to >> split the glue layer driver into small parts such as >> reset, regulator, phy, etc. > > What exactly did Felipe ask for? Did he ask that the patch be split > up, one patch per reset, regulator, phy

Re: [PATCH v2] locks: change POSIX lock ownership on execve when files_struct is displaced

On Thu, 2018-03-22 at 00:36 -0500, Eric W. Biederman wrote: > ebied...@xmission.com (Eric W. Biederman) writes: > > > Jeff Layton writes: > > > > > From: Jeff Layton > > > > > > POSIX mandates that open fds and their associated file locks should be > >

Re: [PATCH v2] locks: change POSIX lock ownership on execve when files_struct is displaced

On Thu, 2018-03-22 at 00:36 -0500, Eric W. Biederman wrote: > ebied...@xmission.com (Eric W. Biederman) writes: > > > Jeff Layton writes: > > > > > From: Jeff Layton > > > > > > POSIX mandates that open fds and their associated file locks should be > > > preserved across an execve. This

[PATCH 2/2] Documentation: devices.txt: remove the mk712 touchscreen device from the list

The input/touchscreen/mk712.c driver has been rewritten for the common input event system. in 2005. There shouldn't a special device node be created anymore. Signed-off-by: Martin Kepplinger --- Please review this by looking at the driver too. Thanks,

[PATCH 2/2] Documentation: devices.txt: remove the mk712 touchscreen device from the list

The input/touchscreen/mk712.c driver has been rewritten for the common input event system. in 2005. There shouldn't a special device node be created anymore. Signed-off-by: Martin Kepplinger --- Please review this by looking at the driver too. Thanks, martin

[PATCH 1/2] Input: mk712: update documentation web link

At the mentioned address there's nothing found. By searching information on the controller chip still can be found, so update the link to the resulting page. Signed-off-by: Martin Kepplinger --- drivers/input/touchscreen/mk712.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH 1/2] Input: mk712: update documentation web link

At the mentioned address there's nothing found. By searching information on the controller chip still can be found, so update the link to the resulting page. Signed-off-by: Martin Kepplinger --- drivers/input/touchscreen/mk712.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH v2] i2c: i801: blacklist Host Notify on HP EliteBook G3 850

The HP EliteBook G3 850 has a weird bug where a subsequent cold boot hangs while plugged in if Linux enables the Host Notify features of i2c-i801. The cold boot hang depends on how the system boots. It does not hang on UEFI Grub text boot or legacy Grub text boot. But it does hang on legacy

[PATCH v2] i2c: i801: blacklist Host Notify on HP EliteBook G3 850

The HP EliteBook G3 850 has a weird bug where a subsequent cold boot hangs while plugged in if Linux enables the Host Notify features of i2c-i801. The cold boot hang depends on how the system boots. It does not hang on UEFI Grub text boot or legacy Grub text boot. But it does hang on legacy

Re: [PATCH v2 0/2] perf: riscv: Preliminary Perf Event Support on RISC-V

Sorry for the lack of version prefix in the title. This patchset should be version 2. On Mon, Apr 02, 2018 at 08:31:22PM +0800, Alan Kao wrote: > This implements the baseline PMU for RISC-V platforms. > > To ease future PMU portings, a guide is also written, containing > perf concepts, arch

Re: [PATCH v2 0/2] perf: riscv: Preliminary Perf Event Support on RISC-V

Sorry for the lack of version prefix in the title. This patchset should be version 2. On Mon, Apr 02, 2018 at 08:31:22PM +0800, Alan Kao wrote: > This implements the baseline PMU for RISC-V platforms. > > To ease future PMU portings, a guide is also written, containing > perf concepts, arch

Re: [PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware dump in second kernel

On Monday, April 04/02/18, 2018 at 14:41:43 +0530, Jiri Pirko wrote: > Fri, Mar 30, 2018 at 08:42:00PM CEST, ebied...@xmission.com wrote: > >Rahul Lakkireddy writes: > > > >> On Friday, March 03/30/18, 2018 at 16:09:07 +0530, Jiri Pirko wrote: > >>> Sat, Mar 24, 2018

Re: [PATCH v3 1/2] Documentation: Documentation for qcom, llcc

On Tue, Mar 27, 2018 at 1:52 PM, Rishabh Bhatnagar wrote: > Documentation for last level cache controller device tree bindings, > client bindings usage examples. > > Signed-off-by: Channagoud Kadabi > Signed-off-by: Rishabh Bhatnagar

Re: [PATCH net-next v2 1/2] fs/crashdd: add API to collect hardware dump in second kernel

On Monday, April 04/02/18, 2018 at 14:41:43 +0530, Jiri Pirko wrote: > Fri, Mar 30, 2018 at 08:42:00PM CEST, ebied...@xmission.com wrote: > >Rahul Lakkireddy writes: > > > >> On Friday, March 03/30/18, 2018 at 16:09:07 +0530, Jiri Pirko wrote: > >>> Sat, Mar 24, 2018 at 11:56:33AM CET,

Re: [PATCH v3 1/2] Documentation: Documentation for qcom, llcc

On Tue, Mar 27, 2018 at 1:52 PM, Rishabh Bhatnagar wrote: > Documentation for last level cache controller device tree bindings, > client bindings usage examples. > > Signed-off-by: Channagoud Kadabi > Signed-off-by: Rishabh Bhatnagar > --- > .../devicetree/bindings/arm/msm/qcom,llcc.txt |

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