Re: [PATCH for-4.4 1/2] mtd: spi-nor: fix Spansion regressions (aliased with Winbond)

Hi Cyrille, On Mon, Apr 04, 2016 at 05:33:30PM +0200, Cyrille Pitchen wrote: > Le 01/04/2016 22:27, Brian Norris a écrit : > > On Wed, Mar 30, 2016 at 02:47:48PM +0200, Cyrille Pitchen wrote: > >> Just a general remark: maybe reading the JEDEC ID is not a so reliable > >> mean to > >> discover

Re: [PATCH for-4.4 1/2] mtd: spi-nor: fix Spansion regressions (aliased with Winbond)

Hi Cyrille, On Mon, Apr 04, 2016 at 05:33:30PM +0200, Cyrille Pitchen wrote: > Le 01/04/2016 22:27, Brian Norris a écrit : > > On Wed, Mar 30, 2016 at 02:47:48PM +0200, Cyrille Pitchen wrote: > >> Just a general remark: maybe reading the JEDEC ID is not a so reliable > >> mean to > >> discover

Re: [PATCH 3/3] mtd: brcmnand: respect ECC algorithm set by NAND subsystem

On Fri, Apr 22, 2016 at 01:23:15PM +0200, Rafał Miłecki wrote: > It's more reliable than guessing based on ECC strength. It allows using > NAND on devices with BCH-1 (e.g. D-Link DIR-885L). > > Signed-off-by: Rafał Miłecki > --- > drivers/mtd/nand/brcmnand/brcmnand.c | 2 +- >

Re: [PATCH 3/3] mtd: brcmnand: respect ECC algorithm set by NAND subsystem

On Fri, Apr 22, 2016 at 01:23:15PM +0200, Rafał Miłecki wrote: > It's more reliable than guessing based on ECC strength. It allows using > NAND on devices with BCH-1 (e.g. D-Link DIR-885L). > > Signed-off-by: Rafał Miłecki > --- > drivers/mtd/nand/brcmnand/brcmnand.c | 2 +- > 1 file changed, 1

Re: [PATCH v7 05/15] i2c: octeon: Enable High-Level Controller

On Mon, Apr 25, 2016 at 11:44:29PM +0200, Wolfram Sang wrote: > On Mon, Apr 25, 2016 at 04:33:34PM +0200, Jan Glauber wrote: > > From: David Daney > > > > Use High-Level Controller (HLC) when possible. The HLC can read/write > > up to 8 bytes and is completely

Re: [PATCH v7 05/15] i2c: octeon: Enable High-Level Controller

On Mon, Apr 25, 2016 at 11:44:29PM +0200, Wolfram Sang wrote: > On Mon, Apr 25, 2016 at 04:33:34PM +0200, Jan Glauber wrote: > > From: David Daney > > > > Use High-Level Controller (HLC) when possible. The HLC can read/write > > up to 8 bytes and is completely optional. The most important

Re: [PATCH 1/2] clk: imx: do not sleep if IRQ's are still disabled

Hi Shawn, On Tue, Apr 26, 2016 at 9:23 AM, Shawn Guo wrote: > On Thu, Apr 21, 2016 at 11:45:20AM +0800, Dong Aisheng wrote: >> On Fri, Jan 29, 2016 at 02:49:23PM -0800, Stefan Agner wrote: >> > If a clock gets enabled early during boot time, it can lead to a PLL >> >

Re: [PATCH 1/2] clk: imx: do not sleep if IRQ's are still disabled

Hi Shawn, On Tue, Apr 26, 2016 at 9:23 AM, Shawn Guo wrote: > On Thu, Apr 21, 2016 at 11:45:20AM +0800, Dong Aisheng wrote: >> On Fri, Jan 29, 2016 at 02:49:23PM -0800, Stefan Agner wrote: >> > If a clock gets enabled early during boot time, it can lead to a PLL >> > startup. The wait_lock

Re: [RESEND PATCH v3 1/2] ARM: exynos_defconfig: Enable Samsung media platform drivers as modules

On 04/25/2016 06:51 PM, Javier Martinez Canillas wrote: > There are a bunch of media platform drivers under drivers/media/platform/ > that are for Samsung SoCs but are not being built with exynos_defconfig. > > This patch enables them as a module to improve build coverage for these > drivers and

Re: [RESEND PATCH v3 1/2] ARM: exynos_defconfig: Enable Samsung media platform drivers as modules

On 04/25/2016 06:51 PM, Javier Martinez Canillas wrote: > There are a bunch of media platform drivers under drivers/media/platform/ > that are for Samsung SoCs but are not being built with exynos_defconfig. > > This patch enables them as a module to improve build coverage for these > drivers and

Re: [RFC v6 04/10] PCI: Add support for enforcing all MMIO BARs to be page aligned

On 04/18/2016 08:56 PM, Yongji Xie wrote: When vfio passthrough a PCI device of which MMIO BARs are smaller than PAGE_SIZE, guest will not handle the mmio accesses to the BARs which leads to mmio emulations in host. This is because vfio will not allow to passthrough one BAR's mmio page which

Re: [RFC v6 04/10] PCI: Add support for enforcing all MMIO BARs to be page aligned

On 04/18/2016 08:56 PM, Yongji Xie wrote: When vfio passthrough a PCI device of which MMIO BARs are smaller than PAGE_SIZE, guest will not handle the mmio accesses to the BARs which leads to mmio emulations in host. This is because vfio will not allow to passthrough one BAR's mmio page which

Re: [PATCH v2] printk: Add kernel parameter to disable writes to /dev/kmsg

* Steven Rostedt wrote: > On Mon, 25 Apr 2016 12:28:30 -0700 > Linus Torvalds wrote: > > > On Mon, Apr 25, 2016 at 12:06 PM, Peter Zijlstra > > wrote: > > > > I think it should be a tristate with "yes/no/ratelimit",

Re: [PATCH v2] printk: Add kernel parameter to disable writes to /dev/kmsg

* Steven Rostedt wrote: > On Mon, 25 Apr 2016 12:28:30 -0700 > Linus Torvalds wrote: > > > On Mon, Apr 25, 2016 at 12:06 PM, Peter Zijlstra > > wrote: > > > > I think it should be a tristate with "yes/no/ratelimit", and let's > > default to ratelimit. > > > > Also note that ratelimit

Re: [PATCH v5 00/14] ACPI NUMA support for ARM64

Hi Will, David, On 2016/4/26 0:47, David Daney wrote: On 04/25/2016 04:13 AM, Will Deacon wrote: Hi David, On Tue, Apr 19, 2016 at 06:40:25PM -0700, David Daney wrote: From: David Daney Based on v16 of device-tree NUMA patch set for arm64 [1],this patch set

Re: [PATCH v5 00/14] ACPI NUMA support for ARM64

Hi Will, David, On 2016/4/26 0:47, David Daney wrote: On 04/25/2016 04:13 AM, Will Deacon wrote: Hi David, On Tue, Apr 19, 2016 at 06:40:25PM -0700, David Daney wrote: From: David Daney Based on v16 of device-tree NUMA patch set for arm64 [1],this patch set introduce the ACPI based

Re: [PATCH] watchdog: trivial fix of spelling mistake on "allocate"

On Mon, 2016-04-25 at 20:19 +0100, Colin King wrote: > fix spelling mistake, alloacate -> allocate [] > diff --git a/drivers/watchdog/jz4740_wdt.c b/drivers/watchdog/jz4740_wdt.c [] > @@ -161,7 +161,7 @@ static int jz4740_wdt_probe(struct platform_device *pdev) >   drvdata = devm_kzalloc(>dev,

Re: [PATCH] watchdog: trivial fix of spelling mistake on "allocate"

On Mon, 2016-04-25 at 20:19 +0100, Colin King wrote: > fix spelling mistake, alloacate -> allocate [] > diff --git a/drivers/watchdog/jz4740_wdt.c b/drivers/watchdog/jz4740_wdt.c [] > @@ -161,7 +161,7 @@ static int jz4740_wdt_probe(struct platform_device *pdev) >   drvdata = devm_kzalloc(>dev,

Re: [PATCH v5 04/14] acpi, numa: Move acpi_numa_arch_fixup() to ia64 only

On 2016/4/20 9:40, David Daney wrote: From: Robert Richter Since acpi_numa_arch_fixup() is only used in arch ia64, move it there to make a generic interface easier. This avoids empty function stubs or some complex kconfig options for x86 and arm64. Signed-off-by: Robert

Re: [PATCH v5 04/14] acpi, numa: Move acpi_numa_arch_fixup() to ia64 only

On 2016/4/20 9:40, David Daney wrote: From: Robert Richter Since acpi_numa_arch_fixup() is only used in arch ia64, move it there to make a generic interface easier. This avoids empty function stubs or some complex kconfig options for x86 and arm64. Signed-off-by: Robert Richter

Re: [PATCH] net: tsi108: use NULL for pointer-typed argument

From: Julia Lawall Date: Sat, 23 Apr 2016 11:07:02 +0200 > The first argument of pci_free_consistent has type struct pci_dev *, so use > NULL instead of 0. > > The semantic patch that performs this transformation is as follows: > (http://coccinelle.lip6.fr/) > > // > @@

RE: [PATCH v6 07/12] usb: otg: add OTG/dual-role core

Hi > -Original Message- > From: Peter Chen [mailto:hzpeterc...@gmail.com] > Sent: Tuesday, April 26, 2016 11:47 AM > To: Jun Li > Cc: Roger Quadros ; st...@rowland.harvard.edu; > ba...@kernel.org; gre...@linuxfoundation.org; peter.c...@freescale.com; >

Re: [PATCH] net: tsi108: use NULL for pointer-typed argument

From: Julia Lawall Date: Sat, 23 Apr 2016 11:07:02 +0200 > The first argument of pci_free_consistent has type struct pci_dev *, so use > NULL instead of 0. > > The semantic patch that performs this transformation is as follows: > (http://coccinelle.lip6.fr/) > > // > @@ > @@ >

RE: [PATCH v6 07/12] usb: otg: add OTG/dual-role core

Hi > -Original Message- > From: Peter Chen [mailto:hzpeterc...@gmail.com] > Sent: Tuesday, April 26, 2016 11:47 AM > To: Jun Li > Cc: Roger Quadros ; st...@rowland.harvard.edu; > ba...@kernel.org; gre...@linuxfoundation.org; peter.c...@freescale.com; > dan.j.willi...@intel.com;

[PATCH 1/1] firmware: correct test of wait_for_completion_interruptible_timeout return

Before this commit both code paths (hotplug and not-hotplug as determined by FW_OPT_UEVENT) would block on an interruptible completion, but the hotplugscenario also would wait until timeout and then abort. The non hotplugscenario (which dell-rbu followed) would block indefinitely until

[PATCH 1/1] firmware: correct test of wait_for_completion_interruptible_timeout return

Before this commit both code paths (hotplug and not-hotplug as determined by FW_OPT_UEVENT) would block on an interruptible completion, but the hotplugscenario also would wait until timeout and then abort. The non hotplugscenario (which dell-rbu followed) would block indefinitely until

linux-next: manual merge of the xen-tip tree with the arm64 tree

Hi all, Today's linux-next merge of the xen-tip tree got a conflict in: arch/arm64/kernel/setup.c between commit: 3194ac6e66cc ("arm64: Move unflatten_device_tree() call earlier.") from the arm64 tree and commit: 3915fea959b6 ("ARM: XEN: Move xen_early_init() before efi_init()") from

linux-next: manual merge of the xen-tip tree with the arm64 tree

Hi all, Today's linux-next merge of the xen-tip tree got a conflict in: arch/arm64/kernel/setup.c between commit: 3194ac6e66cc ("arm64: Move unflatten_device_tree() call earlier.") from the arm64 tree and commit: 3915fea959b6 ("ARM: XEN: Move xen_early_init() before efi_init()") from

Re: [PATCH 0/4] OMAP Mailbox legacy platform device support removal

On Wed, Apr 6, 2016 at 6:37 PM, Suman Anna wrote: > Hi Jassi, > > This series cleans up the OMAP Mailbox driver dropping the > support for legacy non-DT platform devices. The infrastructure > for creating any such devices has all been cleaned up from the > mach-omap2 layers. > >

Re: [PATCH 0/4] OMAP Mailbox legacy platform device support removal

On Wed, Apr 6, 2016 at 6:37 PM, Suman Anna wrote: > Hi Jassi, > > This series cleans up the OMAP Mailbox driver dropping the > support for legacy non-DT platform devices. The infrastructure > for creating any such devices has all been cleaned up from the > mach-omap2 layers. > > The removal from

Re: stable-security kernel updates

On Tue, Apr 26, 2016 at 01:14:13AM +0200, Ben Hutchings wrote: > On Thu, 2016-04-21 at 16:33 +0200, Willy Tarreau wrote: > > On Thu, Apr 21, 2016 at 10:27:46AM -0400, Sasha Levin wrote: > > > > > > This means that missing CVE fixes are quite common with stable > > > trees? > > Until someone

Re: stable-security kernel updates

On Tue, Apr 26, 2016 at 01:14:13AM +0200, Ben Hutchings wrote: > On Thu, 2016-04-21 at 16:33 +0200, Willy Tarreau wrote: > > On Thu, Apr 21, 2016 at 10:27:46AM -0400, Sasha Levin wrote: > > > > > > This means that missing CVE fixes are quite common with stable > > > trees? > > Until someone

Re: [PATCH 1/2] drm/dsi: Implement DCS get display mode

HI, I have not got response from maintainers. Did i miss anything? On Mon, Apr 18, 2016 at 2:52 PM, Vinay Simha BN wrote: > Provide a small convenience wrapper that transmits > a DCS get_display_mode command. > > Signed-off-by: Vinay Simha BN > --- >

Re: [PATCH 1/2] drm/dsi: Implement DCS get display mode

HI, I have not got response from maintainers. Did i miss anything? On Mon, Apr 18, 2016 at 2:52 PM, Vinay Simha BN wrote: > Provide a small convenience wrapper that transmits > a DCS get_display_mode command. > > Signed-off-by: Vinay Simha BN > --- > drivers/gpu/drm/drm_mipi_dsi.c | 24

Re: [PATCH 2/2] drm/dsi: Implement DCS get display self diagnostic

HI, I have not got response from maintainers. Did i miss anything? On Mon, Apr 18, 2016 at 2:52 PM, Vinay Simha BN wrote: > Provide a small convenience wrapper that transmits > a DCS get_diagnostic_result command. > > Signed-off-by: Vinay Simha BN > ---

Re: [PATCH 2/2] drm/dsi: Implement DCS get display self diagnostic

HI, I have not got response from maintainers. Did i miss anything? On Mon, Apr 18, 2016 at 2:52 PM, Vinay Simha BN wrote: > Provide a small convenience wrapper that transmits > a DCS get_diagnostic_result command. > > Signed-off-by: Vinay Simha BN > --- > drivers/gpu/drm/drm_mipi_dsi.c | 25

Re: [PATCH v2 5/5] dax: handle media errors in dax_do_io

On Mon, Apr 25, 2016 at 7:56 PM, Dave Chinner wrote: > On Mon, Apr 25, 2016 at 06:45:08PM -0700, Dan Williams wrote: [..] >> Otherwise, if an application wants to use DAX then it might >> need to be prepared to handle media errors itself same as the >> un-RAIDed disk case.

Re: [PATCH v2 5/5] dax: handle media errors in dax_do_io

On Mon, Apr 25, 2016 at 7:56 PM, Dave Chinner wrote: > On Mon, Apr 25, 2016 at 06:45:08PM -0700, Dan Williams wrote: [..] >> Otherwise, if an application wants to use DAX then it might >> need to be prepared to handle media errors itself same as the >> un-RAIDed disk case. Yes, at an

[PATCH] panic: lockdep: correct lock debugging state check

When kernel oops happens, lock debugging is turned off by debug_locks_off() in oops_enter() via calling __debug_locks_off() which set debug_locks to 0 via xchg(). But, calling to __debug_locks_off() to check lock debugging state in add_taint() called by oops_end() will always return false since

[PATCH] panic: lockdep: correct lock debugging state check

When kernel oops happens, lock debugging is turned off by debug_locks_off() in oops_enter() via calling __debug_locks_off() which set debug_locks to 0 via xchg(). But, calling to __debug_locks_off() to check lock debugging state in add_taint() called by oops_end() will always return false since

Re: [PATCH v6 07/12] usb: otg: add OTG/dual-role core

On Tue, Apr 26, 2016 at 02:07:56AM +, Jun Li wrote: > > +struct usb_otg *usb_otg_register(struct device *dev, > > +struct usb_otg_config *config) > > +{ > > + struct usb_otg *otg; > > + struct otg_wait_data *wait; > > + int ret = 0; > > + > > + if (!dev ||

Re: [PATCH v6 07/12] usb: otg: add OTG/dual-role core

On Tue, Apr 26, 2016 at 02:07:56AM +, Jun Li wrote: > > +struct usb_otg *usb_otg_register(struct device *dev, > > +struct usb_otg_config *config) > > +{ > > + struct usb_otg *otg; > > + struct otg_wait_data *wait; > > + int ret = 0; > > + > > + if (!dev ||

linux-next: build failure after merge of the block tree

Hi Nicolas, After merging the block tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: ERROR: ".blk_queue_write_cache" [drivers/block/virtio_blk.ko] undefined! ERROR: ".blk_queue_write_cache" [drivers/block/ps3disk.ko] undefined! ERROR: ".blk_queue_write_cache"

linux-next: build failure after merge of the block tree

Hi Nicolas, After merging the block tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: ERROR: ".blk_queue_write_cache" [drivers/block/virtio_blk.ko] undefined! ERROR: ".blk_queue_write_cache" [drivers/block/ps3disk.ko] undefined! ERROR: ".blk_queue_write_cache"

Re: [PATCH] scsi: fc: force inlining of wwn conversion functions

On Mon, 2016-04-25 at 22:40 -0400, Martin K. Petersen wrote: > > > > > > "Josh" == Josh Poimboeuf writes: > > Josh> Can you merge this patch for 4.6? > > I am really not a big fan of working around compiler bugs in a device > driver. Me neither > Are we sure there are no

Re: [PATCH] scsi: fc: force inlining of wwn conversion functions

On Mon, 2016-04-25 at 22:40 -0400, Martin K. Petersen wrote: > > > > > > "Josh" == Josh Poimboeuf writes: > > Josh> Can you merge this patch for 4.6? > > I am really not a big fan of working around compiler bugs in a device > driver. Me neither > Are we sure there are no other

Re: [PATCH V9 RESEND 13/14] arm64: tegra: add soctherm node for Tegra210

Hi Thierry, Do you know who can take these patch 13 and 14? The corresponding driver was merged to linux-next several weeks ago. Does I need to send these two patches again? Thanks. Wei. On 2016年04月12日 16:53, Wei Ni wrote: > Could anyone take a look this patch? > > On 2016年04月01日 15:01, Wei Ni

Re: [PATCH V9 RESEND 13/14] arm64: tegra: add soctherm node for Tegra210

Hi Thierry, Do you know who can take these patch 13 and 14? The corresponding driver was merged to linux-next several weeks ago. Does I need to send these two patches again? Thanks. Wei. On 2016年04月12日 16:53, Wei Ni wrote: > Could anyone take a look this patch? > > On 2016年04月01日 15:01, Wei Ni

Re: [PATCH v3 5/5] arm64: dts: marvell: add XOR node for Armada 3700 SoC

On Thu, Apr 14, 2016 at 06:53:38PM +0200, Gregory CLEMENT wrote: > From: Marcin Wojtas > > Armada 3700 SoC comprise one dual-channel XOR engine and this > patch adds its according representation. This need an ACK from ARM folks.. > > Signed-off-by: Marcin Wojtas

Re: [PATCH 0/6] drm/fsl-dcu: unload fixes

Applied patchset to my fsl-dcu tree. -- Stefan On 2016-04-16 22:25, Stefan Agner wrote: > Hi all, > > This patchset fixes several issues around unloading/unbinding > the driver. There is still one WARNING when unloading the driver > while vblank interrupts are enabled. I am not sure what/who >

Re: [PATCH v3 5/5] arm64: dts: marvell: add XOR node for Armada 3700 SoC

On Thu, Apr 14, 2016 at 06:53:38PM +0200, Gregory CLEMENT wrote: > From: Marcin Wojtas > > Armada 3700 SoC comprise one dual-channel XOR engine and this > patch adds its according representation. This need an ACK from ARM folks.. > > Signed-off-by: Marcin Wojtas > Signed-off-by: Gregory

Re: [PATCH 0/6] drm/fsl-dcu: unload fixes

Applied patchset to my fsl-dcu tree. -- Stefan On 2016-04-16 22:25, Stefan Agner wrote: > Hi all, > > This patchset fixes several issues around unloading/unbinding > the driver. There is still one WARNING when unloading the driver > while vblank interrupts are enabled. I am not sure what/who >

Re: [PATCH] dmaengine: pxa: handle bus errors

On Mon, Mar 28, 2016 at 11:32:24PM +0200, Robert Jarzmik wrote: > In the current state, upon bus error the driver will spin endlessly, > relaunching the last tx, which will fail again and again : > - a bus error happens > - pxad_chan_handler() is called > - as PXA_DCSR_STOPSTATE is true, the

RE: [PATCH 0/2] Add Opal unlock support to NVMe.

> -Original Message- > From: linux-block-ow...@vger.kernel.org [mailto:linux-block- > ow...@vger.kernel.org] On Behalf Of Christoph Hellwig > Sent: Monday, April 25, 2016 3:24 AM > To: Rafael Antognolli > Cc: linux-n...@lists.infradead.org;

Re: [PATCH] dmaengine: pxa: handle bus errors

On Mon, Mar 28, 2016 at 11:32:24PM +0200, Robert Jarzmik wrote: > In the current state, upon bus error the driver will spin endlessly, > relaunching the last tx, which will fail again and again : > - a bus error happens > - pxad_chan_handler() is called > - as PXA_DCSR_STOPSTATE is true, the

RE: [PATCH 0/2] Add Opal unlock support to NVMe.

> -Original Message- > From: linux-block-ow...@vger.kernel.org [mailto:linux-block- > ow...@vger.kernel.org] On Behalf Of Christoph Hellwig > Sent: Monday, April 25, 2016 3:24 AM > To: Rafael Antognolli > Cc: linux-n...@lists.infradead.org; linux-kernel@vger.kernel.org; >

RE: [v8, 6/7] MAINTAINERS: add entry for Freescale SoC specific driver

Hi Scott and Leo, > -Original Message- > From: linux-mmc-ow...@vger.kernel.org [mailto:linux-mmc- > ow...@vger.kernel.org] On Behalf Of Scott Wood > Sent: Saturday, April 23, 2016 7:23 AM > To: Yangbo Lu; linux-...@vger.kernel.org; linuxppc-...@lists.ozlabs.org; >

RE: [v8, 6/7] MAINTAINERS: add entry for Freescale SoC specific driver

Hi Scott and Leo, > -Original Message- > From: linux-mmc-ow...@vger.kernel.org [mailto:linux-mmc- > ow...@vger.kernel.org] On Behalf Of Scott Wood > Sent: Saturday, April 23, 2016 7:23 AM > To: Yangbo Lu; linux-...@vger.kernel.org; linuxppc-...@lists.ozlabs.org; >

Re: [PATCH 0/2 v3] fsl-mc binding and device tree updates

On Tue, Apr 19, 2016 at 04:43:27PM -0500, Stuart Yoder wrote: > Stuart Yoder (2): > Documentation: fsl-mc: binding updates for MSIs, ranges, PHYs > arm64: dts: ls2080a: fsl-mc dt node updates Applied both, thanks.

Re: [PATCH 0/2 v3] fsl-mc binding and device tree updates

On Tue, Apr 19, 2016 at 04:43:27PM -0500, Stuart Yoder wrote: > Stuart Yoder (2): > Documentation: fsl-mc: binding updates for MSIs, ranges, PHYs > arm64: dts: ls2080a: fsl-mc dt node updates Applied both, thanks.

Re: [PATCH V17 2/3] dmaengine: qcom_hidma: add debugfs hooks

On Mon, Apr 11, 2016 at 10:21:12AM -0400, Sinan Kaya wrote: > +static int hidma_chan_stats(struct seq_file *s, void *unused) > +{ > + struct hidma_chan *mchan = s->private; > + struct hidma_desc *mdesc; > + struct hidma_dev *dmadev = mchan->dmadev; > + > +

Re: [PATCH V17 2/3] dmaengine: qcom_hidma: add debugfs hooks

On Mon, Apr 11, 2016 at 10:21:12AM -0400, Sinan Kaya wrote: > +static int hidma_chan_stats(struct seq_file *s, void *unused) > +{ > + struct hidma_chan *mchan = s->private; > + struct hidma_desc *mdesc; > + struct hidma_dev *dmadev = mchan->dmadev; > + > +

Re: [PATCH V17 1/3] dmaengine: qcom_hidma: implement lower level hardware interface

On Mon, Apr 11, 2016 at 10:21:11AM -0400, Sinan Kaya wrote: > + * HIDMA is not aware of IOMMU presence since it follows the DMA API. All > + * IOMMU latency will be built into the data movement time. By the time > + * interrupt happens, IOMMU lookups + data movement has already taken place. Do

Re: [PATCH V17 1/3] dmaengine: qcom_hidma: implement lower level hardware interface

On Mon, Apr 11, 2016 at 10:21:11AM -0400, Sinan Kaya wrote: > + * HIDMA is not aware of IOMMU presence since it follows the DMA API. All > + * IOMMU latency will be built into the data movement time. By the time > + * interrupt happens, IOMMU lookups + data movement has already taken place. Do

RE: [PATCH kernel 1/2] mm: add the related functions to build the free page bitmap

> On Mon, Apr 25, 2016 at 03:11:05AM +, Li, Liang Z wrote: > > > On Fri, Apr 22, 2016 at 10:48:38AM +0100, Dr. David Alan Gilbert wrote: > > > > * Michael S. Tsirkin (m...@redhat.com) wrote: > > > > > On Tue, Apr 19, 2016 at 03:02:09PM +, Li, Liang Z wrote: > > > > > > > On Tue, 2016-04-19

RE: [PATCH kernel 1/2] mm: add the related functions to build the free page bitmap

> On Mon, Apr 25, 2016 at 03:11:05AM +, Li, Liang Z wrote: > > > On Fri, Apr 22, 2016 at 10:48:38AM +0100, Dr. David Alan Gilbert wrote: > > > > * Michael S. Tsirkin (m...@redhat.com) wrote: > > > > > On Tue, Apr 19, 2016 at 03:02:09PM +, Li, Liang Z wrote: > > > > > > > On Tue, 2016-04-19

[PATCH net-next V2] tuntap: calculate rps hash only when needed

There's no need to calculate rps hash if it was not enabled. So this patch export rps_needed and check it before trying to get rps hash. Tests (using pktgen to inject packets to guest) shows this can improve pps about 13% (when rps is disabled). Before: ~115 pps After: ~130 pps Cc:

[PATCH net-next V2] tuntap: calculate rps hash only when needed

There's no need to calculate rps hash if it was not enabled. So this patch export rps_needed and check it before trying to get rps hash. Tests (using pktgen to inject packets to guest) shows this can improve pps about 13% (when rps is disabled). Before: ~115 pps After: ~130 pps Cc:

Re: [PATCH net-next] tuntap: calculate rps hash only when needed

On 04/26/2016 09:55 AM, Jason Wang wrote: > There's no need to calculate rps hash if it was not enabled. So this > patch export rps_needed and check it before trying to get rps > hash. Tests (using pktgen to inject packets to guest) shows this can > improve pps about 13% (when rps is disabled).

Re: next: suspicious RCU usage message since commit 'rcu: Remove superfluous versions of rcu_read_lock_sched_held()'

On 04/25/2016 01:49 PM, Paul E. McKenney wrote: On Mon, Apr 25, 2016 at 01:25:10PM -0700, Guenter Roeck wrote: On Mon, Apr 25, 2016 at 10:12:39AM -0700, Paul E. McKenney wrote: On Sun, Apr 24, 2016 at 11:26:41PM -0700, Guenter Roeck wrote: On 04/24/2016 10:49 PM, Paul E. McKenney wrote: On

Re: [PATCH net-next] tuntap: calculate rps hash only when needed

On 04/26/2016 09:55 AM, Jason Wang wrote: > There's no need to calculate rps hash if it was not enabled. So this > patch export rps_needed and check it before trying to get rps > hash. Tests (using pktgen to inject packets to guest) shows this can > improve pps about 13% (when rps is disabled).

Re: next: suspicious RCU usage message since commit 'rcu: Remove superfluous versions of rcu_read_lock_sched_held()'

On 04/25/2016 01:49 PM, Paul E. McKenney wrote: On Mon, Apr 25, 2016 at 01:25:10PM -0700, Guenter Roeck wrote: On Mon, Apr 25, 2016 at 10:12:39AM -0700, Paul E. McKenney wrote: On Sun, Apr 24, 2016 at 11:26:41PM -0700, Guenter Roeck wrote: On 04/24/2016 10:49 PM, Paul E. McKenney wrote: On

Re: random(4) changes

On Sun, Apr 24, 2016 at 10:03:45AM +0200, Stephan Mueller wrote: > > I agree here. The only challenge with the current implementation is the time > the fast_pool is to be mixed into an entropy pool. This requires a lock and > quite some code afterwards. This only happens no more than once

Re: random(4) changes

On Sun, Apr 24, 2016 at 10:03:45AM +0200, Stephan Mueller wrote: > > I agree here. The only challenge with the current implementation is the time > the fast_pool is to be mixed into an entropy pool. This requires a lock and > quite some code afterwards. This only happens no more than once

Re: [PATCH v2 5/5] dax: handle media errors in dax_do_io

On Mon, Apr 25, 2016 at 06:45:08PM -0700, Dan Williams wrote: > On Mon, Apr 25, 2016 at 5:11 PM, Dave Chinner wrote: > > On Mon, Apr 25, 2016 at 04:43:14PM -0700, Dan Williams wrote: > [..] > >> Maybe I missed something, but all these assumptions are already > >> present for

Re: [PATCH v2 5/5] dax: handle media errors in dax_do_io

On Mon, Apr 25, 2016 at 06:45:08PM -0700, Dan Williams wrote: > On Mon, Apr 25, 2016 at 5:11 PM, Dave Chinner wrote: > > On Mon, Apr 25, 2016 at 04:43:14PM -0700, Dan Williams wrote: > [..] > >> Maybe I missed something, but all these assumptions are already > >> present for typical block

[PATCH] drivers/input: Macros with complex values should be enclosed in parentheses

The bitwise shift operator has lower priority than plus operator. So the values on macros should be enclosed in parentheses. For example, "(1 << 4 + 1)" means "(1 << (4 + 1))", but it is not expected by the macros. And also fix other two coding style problems reported by scripts/checkpatch.pl.

[PATCH] drivers/input: Macros with complex values should be enclosed in parentheses

The bitwise shift operator has lower priority than plus operator. So the values on macros should be enclosed in parentheses. For example, "(1 << 4 + 1)" means "(1 << (4 + 1))", but it is not expected by the macros. And also fix other two coding style problems reported by scripts/checkpatch.pl.

Re: [PATCH v2 7/7] f2fs: should check the remaining dentry bits

Change log from v1: o remove wron f2fs_bug_on() >From 545c0c9055b0d8dc5d134d9340b3cd80eeecdafa Mon Sep 17 00:00:00 2001 From: Jaegeuk Kim Date: Mon, 25 Apr 2016 14:24:44 -0700 Subject: [PATCH] f2fs: should check the remaining dentry bits Let's consider a race condition

Re: [PATCH v2 7/7] f2fs: should check the remaining dentry bits

Change log from v1: o remove wron f2fs_bug_on() >From 545c0c9055b0d8dc5d134d9340b3cd80eeecdafa Mon Sep 17 00:00:00 2001 From: Jaegeuk Kim Date: Mon, 25 Apr 2016 14:24:44 -0700 Subject: [PATCH] f2fs: should check the remaining dentry bits Let's consider a race condition between

RE: [v8, 1/7] Documentation: DT: update Freescale DCFG compatible

Hi Mark, > -Original Message- > From: Mark Rutland [mailto:mark.rutl...@arm.com] > Sent: Friday, April 22, 2016 9:12 PM > To: Yangbo Lu > Cc: linux-...@vger.kernel.org; linuxppc-...@lists.ozlabs.org; > devicet...@vger.kernel.org; linux-arm-ker...@lists.infradead.org; linux- >

RE: [v8, 1/7] Documentation: DT: update Freescale DCFG compatible

Hi Mark, > -Original Message- > From: Mark Rutland [mailto:mark.rutl...@arm.com] > Sent: Friday, April 22, 2016 9:12 PM > To: Yangbo Lu > Cc: linux-...@vger.kernel.org; linuxppc-...@lists.ozlabs.org; > devicet...@vger.kernel.org; linux-arm-ker...@lists.infradead.org; linux- >

Re: [PATCH 2/2] mountinfo: implement show_path for kernfs and cgroup

Quoting Serge E. Hallyn (se...@hallyn.com): > Quoting Serge E. Hallyn (se...@hallyn.com): > > Quoting Eric W. Biederman (ebied...@xmission.com): > > > "Serge E. Hallyn" writes: > > > > > > >> diff --git a/kernel/cgroup.c b/kernel/cgroup.c > > > >> index 671dc05..9a0d7b3

Re: [PATCH 2/2] mountinfo: implement show_path for kernfs and cgroup

Quoting Serge E. Hallyn (se...@hallyn.com): > Quoting Serge E. Hallyn (se...@hallyn.com): > > Quoting Eric W. Biederman (ebied...@xmission.com): > > > "Serge E. Hallyn" writes: > > > > > > >> diff --git a/kernel/cgroup.c b/kernel/cgroup.c > > > >> index 671dc05..9a0d7b3 100644 > > > >> ---

[PATCH v3 0/4] ARM64: dts: rockchip: add support for RK3399

Add dtsi file for RK3399 SoCs, and evb dts file for RK3399 evb. To make patch more easily to be reviewed, some nodes have been removed temporarily, after this base file been applied, more patches will be upstreamed independently. Jianqun Xu (3): ARM64: dts: rockchip: add core dtsi file for

Re: [PATCH] tmpfs: fix VM_MAYSHARE mappings for NOMMU

On Mon, 25 Apr 2016 20:47:45 -0400 Rich Felker wrote: > On Mon, Apr 25, 2016 at 08:41:24PM -0400, Rich Felker wrote: > > On Mon, Apr 25, 2016 at 05:09:09PM -0700, Andrew Morton wrote: > > > On Fri, 22 Apr 2016 18:19:44 -0400 Rich Felker wrote: > > > > > > >

[PATCH 3/4] Documentation: devicetree: rockchip: Document rk3399-evb

Use "rockchip,rk3399-evb" compatible string for Rockchip RK3399 evaluation board. Acked-by: Rob Herring Signed-off-by: Jianqun Xu --- changes in v3: - modify title (Rob) Documentation/devicetree/bindings/arm/rockchip.txt | 6 +- 1 file changed, 5

Re: [PATCH] scsi: fc: force inlining of wwn conversion functions

> "Josh" == Josh Poimboeuf writes: Josh> Can you merge this patch for 4.6? I am really not a big fan of working around compiler bugs in a device driver. Are we sure there are no other get_unaligned_be64() calls in the kernel that suffer the same fate? -- Martin K.

Re: [PATCH] scsi: fc: force inlining of wwn conversion functions

> "Josh" == Josh Poimboeuf writes: Josh> Can you merge this patch for 4.6? I am really not a big fan of working around compiler bugs in a device driver. Are we sure there are no other get_unaligned_be64() calls in the kernel that suffer the same fate? -- Martin K. Petersen Oracle

[PATCH v3 0/4] ARM64: dts: rockchip: add support for RK3399

Add dtsi file for RK3399 SoCs, and evb dts file for RK3399 evb. To make patch more easily to be reviewed, some nodes have been removed temporarily, after this base file been applied, more patches will be upstreamed independently. Jianqun Xu (3): ARM64: dts: rockchip: add core dtsi file for

Re: [PATCH] tmpfs: fix VM_MAYSHARE mappings for NOMMU

On Mon, 25 Apr 2016 20:47:45 -0400 Rich Felker wrote: > On Mon, Apr 25, 2016 at 08:41:24PM -0400, Rich Felker wrote: > > On Mon, Apr 25, 2016 at 05:09:09PM -0700, Andrew Morton wrote: > > > On Fri, 22 Apr 2016 18:19:44 -0400 Rich Felker wrote: > > > > > > > Subject: [PATCH] tmpfs: fix

[PATCH 3/4] Documentation: devicetree: rockchip: Document rk3399-evb

Use "rockchip,rk3399-evb" compatible string for Rockchip RK3399 evaluation board. Acked-by: Rob Herring Signed-off-by: Jianqun Xu --- changes in v3: - modify title (Rob) Documentation/devicetree/bindings/arm/rockchip.txt | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git

[PATCH 4/4] ARM64: dts: rockchip: add dts file for RK3399 evaluation board

This patch add rk3399-evb.dts for RK3399 evaluation board. Tested on RK3399 evb. Signed-off-by: Jianqun Xu --- changes in v3: - add more compatible (Doug) - add modle arch/arm64/boot/dts/rockchip/Makefile | 1 + arch/arm64/boot/dts/rockchip/rk3399-evb.dts | 125

[PATCH v3 2/4] ARM64: dts: rockchip: add core dtsi file for RK3399 SoCs

This patch adds core dtsi file for Rockchip RK3399 SoCs. The RK3399 has big/little architecture, which needs a separate node for the PMU of each microarchitecture, for now it missing the pmu node since the old one could not work well. Marc is working on it with:

[PATCH 4/4] ARM64: dts: rockchip: add dts file for RK3399 evaluation board

This patch add rk3399-evb.dts for RK3399 evaluation board. Tested on RK3399 evb. Signed-off-by: Jianqun Xu --- changes in v3: - add more compatible (Doug) - add modle arch/arm64/boot/dts/rockchip/Makefile | 1 + arch/arm64/boot/dts/rockchip/rk3399-evb.dts | 125

[PATCH v3 2/4] ARM64: dts: rockchip: add core dtsi file for RK3399 SoCs

This patch adds core dtsi file for Rockchip RK3399 SoCs. The RK3399 has big/little architecture, which needs a separate node for the PMU of each microarchitecture, for now it missing the pmu node since the old one could not work well. Marc is working on it with:

[PATCH v3 1/4] Documentation: rockchip-dw-mshc: add description for rk3399

From: Shawn Lin Add "rockchip,rk3399-dw-mshc", "rockchip,rk3288-dw-mshc" for dwmmc on rk3399 platform. Acked-by: Rob Herring Signed-off-by: Shawn Lin Signed-off-by: Jianqun Xu ---

[PATCH v3 1/4] Documentation: rockchip-dw-mshc: add description for rk3399

From: Shawn Lin Add "rockchip,rk3399-dw-mshc", "rockchip,rk3288-dw-mshc" for dwmmc on rk3399 platform. Acked-by: Rob Herring Signed-off-by: Shawn Lin Signed-off-by: Jianqun Xu --- Documentation/devicetree/bindings/mmc/rockchip-dw-mshc.txt | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH] ps3_gelic: fix memcpy parameter

The size allocated for target->hwinfo and the number of bytes copied in it should be consistent. Signed-off-by: Christophe JAILLET --- Untested drivers/net/ethernet/toshiba/ps3_gelic_wireless.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] ps3_gelic: fix memcpy parameter

The size allocated for target->hwinfo and the number of bytes copied in it should be consistent. Signed-off-by: Christophe JAILLET --- Untested drivers/net/ethernet/toshiba/ps3_gelic_wireless.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

  1   2   3   4   5   6   7   8   9   10   >