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

On 15/04/17 04:17 PM, Benjamin Herrenschmidt wrote: > You can't. If the iommu is on, everything is remapped. Or do you mean > to have dma_map_* not do a remapping ? Well, yes, you'd have to change the code so that iomem pages do not get remapped and the raw BAR address is passed to the DMA

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

On 15/04/17 04:17 PM, Benjamin Herrenschmidt wrote: > You can't. If the iommu is on, everything is remapped. Or do you mean > to have dma_map_* not do a remapping ? Well, yes, you'd have to change the code so that iomem pages do not get remapped and the raw BAR address is passed to the DMA

Re: [PATCH RESEND] regulator: rn5t618: Fix out of bounds array access

On 2017-04-15 18:12, Axel Lin wrote: > 2017-04-16 0:53 GMT+08:00 Stefan Agner : >> On 2017-04-15 07:52, Axel Lin wrote: >>> The commit "regulator: rn5t618: Add RN5T567 PMIC support" added >>> RN5T618_DCDC4 to the enum, then RN5T618_REG_NUM is also changed. >>> So for rn5t618,

Re: [PATCH RESEND] regulator: rn5t618: Fix out of bounds array access

On 2017-04-15 18:12, Axel Lin wrote: > 2017-04-16 0:53 GMT+08:00 Stefan Agner : >> On 2017-04-15 07:52, Axel Lin wrote: >>> The commit "regulator: rn5t618: Add RN5T567 PMIC support" added >>> RN5T618_DCDC4 to the enum, then RN5T618_REG_NUM is also changed. >>> So for rn5t618, there is out of

[PATCH 2/8] Input: rotary-encoder - remove references to platform data from docs

The driver has been converted to use generic device properties, so stop referring to platform data. Signed-off-by: Dmitry Torokhov --- Documentation/input/rotary-encoder.rst | 85 ++ 1 file changed, 44 insertions(+), 41 deletions(-)

[PATCH 3/8] Input: fix "Game console" heading level in joystick documentation

The heading level should be the same as for other devices. Signed-off-by: Dmitry Torokhov --- Documentation/input/joystick.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/input/joystick.rst b/Documentation/input/joystick.rst index

[PATCH 2/8] Input: rotary-encoder - remove references to platform data from docs

The driver has been converted to use generic device properties, so stop referring to platform data. Signed-off-by: Dmitry Torokhov --- Documentation/input/rotary-encoder.rst | 85 ++ 1 file changed, 44 insertions(+), 41 deletions(-) diff --git

[PATCH 3/8] Input: fix "Game console" heading level in joystick documentation

The heading level should be the same as for other devices. Signed-off-by: Dmitry Torokhov --- Documentation/input/joystick.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/input/joystick.rst b/Documentation/input/joystick.rst index 202f5a090675..c9c175ffc2ff

[PATCH 6/8] Input: docs - note that MT-A protocol is obsolete

Everyone should be using multitouch protocol B (slotted) now. Signed-off-by: Dmitry Torokhov --- Documentation/input/multi-touch-protocol.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/input/multi-touch-protocol.rst

[PATCH 6/8] Input: docs - note that MT-A protocol is obsolete

Everyone should be using multitouch protocol B (slotted) now. Signed-off-by: Dmitry Torokhov --- Documentation/input/multi-touch-protocol.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Documentation/input/multi-touch-protocol.rst

[PATCH 7/8] Input: docs - split input docs into kernel- and user-facing

Split input documentation into several groups: kernel- and user-facing, and notes about individual device drivers. Move device drivers docs into a separate subdirectory. Signed-off-by: Dmitry Torokhov --- Documentation/input/{ => devices}/alps.rst | 2 +-

[PATCH 8/8] Input: docs - freshen up introduction

Stop saying that API is experimental and that only USB is supported, acknowledge that evdev is the preferred interface, and remove paragraph encouraging people sending snail mail to Vojtech :) along with his email. Signed-off-by: Dmitry Torokhov ---

[PATCH 7/8] Input: docs - split input docs into kernel- and user-facing

Split input documentation into several groups: kernel- and user-facing, and notes about individual device drivers. Move device drivers docs into a separate subdirectory. Signed-off-by: Dmitry Torokhov --- Documentation/input/{ => devices}/alps.rst | 2 +- Documentation/input/{ =>

[PATCH 8/8] Input: docs - freshen up introduction

Stop saying that API is experimental and that only USB is supported, acknowledge that evdev is the preferred interface, and remove paragraph encouraging people sending snail mail to Vojtech :) along with his email. Signed-off-by: Dmitry Torokhov --- Documentation/input/event-codes.rst |

[PATCH 1/8] Input: move documentation for Amiga CD32

Move the documentation for Amiga CD32 together with other parallel port joysticks. Signed-off-by: Dmitry Torokhov --- Documentation/input/cd32.rst | 24 - Documentation/input/index.rst| 1 -

[PATCH 4/8] Input: docs - remove disclaimer/GPL notice

This is just a part of kernel documentation, it does not require explicit license notice. Signed-off-by: Dmitry Torokhov --- Documentation/input/index.rst | 21 - 1 file changed, 21 deletions(-) diff --git a/Documentation/input/index.rst

[PATCH 5/8] Input: docs - update joystick documentation a bit

Consolidate use instructions and userspace API notes into the same chapter; remove completely obsolete references, move into a separate subdirectory. Signed-off-by: Dmitry Torokhov --- Documentation/input/index.rst | 6 +-

[PATCH 1/8] Input: move documentation for Amiga CD32

Move the documentation for Amiga CD32 together with other parallel port joysticks. Signed-off-by: Dmitry Torokhov --- Documentation/input/cd32.rst | 24 - Documentation/input/index.rst| 1 - Documentation/input/joystick-parport.rst | 37

[PATCH 4/8] Input: docs - remove disclaimer/GPL notice

This is just a part of kernel documentation, it does not require explicit license notice. Signed-off-by: Dmitry Torokhov --- Documentation/input/index.rst | 21 - 1 file changed, 21 deletions(-) diff --git a/Documentation/input/index.rst b/Documentation/input/index.rst

[PATCH 5/8] Input: docs - update joystick documentation a bit

Consolidate use instructions and userspace API notes into the same chapter; remove completely obsolete references, move into a separate subdirectory. Signed-off-by: Dmitry Torokhov --- Documentation/input/index.rst | 6 +- Documentation/input/joydev/index.rst |

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

On 15/04/17 09:01 PM, Benjamin Herrenschmidt wrote: > Are ZONE_DEVICE pages identifiable based on the struct page alone ? (a > flag ?) Well you can't use ZONE_DEVICE as an indicator. They may be regular RAM, (eg. pmem). It would need a separate flag indicating it is backed by iomem. Logan

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

On 15/04/17 09:01 PM, Benjamin Herrenschmidt wrote: > Are ZONE_DEVICE pages identifiable based on the struct page alone ? (a > flag ?) Well you can't use ZONE_DEVICE as an indicator. They may be regular RAM, (eg. pmem). It would need a separate flag indicating it is backed by iomem. Logan

Re: [PATCH v4 00/10] Add Basic SoC support for MT6797

Hi Stephen, Matthias gentle ping. :-) Thanks. On Sat, 2017-04-08 at 09:20 +0800, Mars Cheng wrote: > This patch set adds basic SoC support for mediatek's first 10-core > chip, X20, also known as MT6797. > > - based on 4.11-rc1 > - support common clk framework > - apply patches about intpol

Re: [PATCH v4 00/10] Add Basic SoC support for MT6797

Hi Stephen, Matthias gentle ping. :-) Thanks. On Sat, 2017-04-08 at 09:20 +0800, Mars Cheng wrote: > This patch set adds basic SoC support for mediatek's first 10-core > chip, X20, also known as MT6797. > > - based on 4.11-rc1 > - support common clk framework > - apply patches about intpol

Re: [PATCH RESEND] regulator: rn5t618: Fix out of bounds array access

2017-04-16 9:12 GMT+08:00 Axel Lin : > 2017-04-16 0:53 GMT+08:00 Stefan Agner : >> On 2017-04-15 07:52, Axel Lin wrote: >>> The commit "regulator: rn5t618: Add RN5T567 PMIC support" added >>> RN5T618_DCDC4 to the enum, then RN5T618_REG_NUM is also changed. >>>

Re: [PATCH RESEND] regulator: rn5t618: Fix out of bounds array access

2017-04-16 9:12 GMT+08:00 Axel Lin : > 2017-04-16 0:53 GMT+08:00 Stefan Agner : >> On 2017-04-15 07:52, Axel Lin wrote: >>> The commit "regulator: rn5t618: Add RN5T567 PMIC support" added >>> RN5T618_DCDC4 to the enum, then RN5T618_REG_NUM is also changed. >>> So for rn5t618, there is out of

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

On Sat, 2017-04-15 at 15:09 -0700, Dan Williams wrote: > I'm wondering, since this is limited to support behind a single > switch, if you could have a software-iommu hanging off that switch > device object that knows how to catch and translate the non-zero > offset bus address case. We have

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

On Sat, 2017-04-15 at 15:09 -0700, Dan Williams wrote: > I'm wondering, since this is limited to support behind a single > switch, if you could have a software-iommu hanging off that switch > device object that knows how to catch and translate the non-zero > offset bus address case. We have

Re: [PATCH] microblaze/timer: set ->min_delta_ticks and ->max_delta_ticks

Hello Daniel, On Fri, Apr 07 2017, Daniel Lezcano wrote: > On Thu, Mar 30, 2017 at 09:45:28PM +0200, Nicolai Stange wrote: >> diff --git a/arch/microblaze/kernel/timer.c b/arch/microblaze/kernel/timer.c >> index 999066192715..545ccd46edb3 100644 >> --- a/arch/microblaze/kernel/timer.c >> +++

Re: [PATCH] microblaze/timer: set ->min_delta_ticks and ->max_delta_ticks

Hello Daniel, On Fri, Apr 07 2017, Daniel Lezcano wrote: > On Thu, Mar 30, 2017 at 09:45:28PM +0200, Nicolai Stange wrote: >> diff --git a/arch/microblaze/kernel/timer.c b/arch/microblaze/kernel/timer.c >> index 999066192715..545ccd46edb3 100644 >> --- a/arch/microblaze/kernel/timer.c >> +++

Re: [PATCH] ARM: dts: omap4-droid4: add bluetooth

On Sat, Apr 15, 2017 at 5:18 PM, Sebastian Reichel wrote: > Droid 4 has wl1835 connected to the OMAP's UART4 port, which is > used for Bluetooth and most likely can also be used for controlling > the FM radio and GPS receivers. > > Signed-off-by: Sebastian Reichel

Re: [PATCH] ARM: dts: omap4-droid4: add bluetooth

On Sat, Apr 15, 2017 at 5:18 PM, Sebastian Reichel wrote: > Droid 4 has wl1835 connected to the OMAP's UART4 port, which is > used for Bluetooth and most likely can also be used for controlling > the FM radio and GPS receivers. > > Signed-off-by: Sebastian Reichel > --- > Hi, > > Thanks to the

arch/x86//kernel/ftrace.c:35:3: error: #error The following combination is not supported: ((compiler missing -mfentry) || (CONFIG_X86_32 and !CONFIG_DYNAMIC_FTRACE)) && CONFIG_FUNCTION_GRAPH_TRACER &

Hi Josh, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: d5ff0814fda50f0306e102f39640cf5bb76af08e commit: 3f135e57a4f76d24ae8d8a490314331f0ced40c5 x86/build: Mostly disable '-maccumulate-outgoing-args' date: 2

arch/x86//kernel/ftrace.c:35:3: error: #error The following combination is not supported: ((compiler missing -mfentry) || (CONFIG_X86_32 and !CONFIG_DYNAMIC_FTRACE)) && CONFIG_FUNCTION_GRAPH_TRACER &

Hi Josh, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: d5ff0814fda50f0306e102f39640cf5bb76af08e commit: 3f135e57a4f76d24ae8d8a490314331f0ced40c5 x86/build: Mostly disable '-maccumulate-outgoing-args' date: 2

Re: [PATCH RESEND] regulator: rn5t618: Fix out of bounds array access

2017-04-16 0:53 GMT+08:00 Stefan Agner : > On 2017-04-15 07:52, Axel Lin wrote: >> The commit "regulator: rn5t618: Add RN5T567 PMIC support" added >> RN5T618_DCDC4 to the enum, then RN5T618_REG_NUM is also changed. >> So for rn5t618, there is out of bounds array access when

Re: [PATCH RESEND] regulator: rn5t618: Fix out of bounds array access

2017-04-16 0:53 GMT+08:00 Stefan Agner : > On 2017-04-15 07:52, Axel Lin wrote: >> The commit "regulator: rn5t618: Add RN5T567 PMIC support" added >> RN5T618_DCDC4 to the enum, then RN5T618_REG_NUM is also changed. >> So for rn5t618, there is out of bounds array access when checking >>

[PATCH] Remove ARM errata Workarounds 458693 and 460075

According to ARM, these errata exist only in a version of Cortex-A8 (r2p0) which was never built. Therefore, I believe there are no platforms where this workaround should be enabled. link :http://infocenter.arm.com/help/index.jsp?topic= /com.arm.doc.faqs/ka15634.html Signed-off-by: Nisal Menuka

[PATCH] Remove ARM errata Workarounds 458693 and 460075

According to ARM, these errata exist only in a version of Cortex-A8 (r2p0) which was never built. Therefore, I believe there are no platforms where this workaround should be enabled. link :http://infocenter.arm.com/help/index.jsp?topic= /com.arm.doc.faqs/ka15634.html Signed-off-by: Nisal Menuka

Re: [PATCH] hugetlbfs: fix offset overflow in huegtlbfs mmap

On 04/13/2017 08:32 PM, Naoya Horiguchi wrote: > On Tue, Apr 11, 2017 at 03:51:58PM -0700, Mike Kravetz wrote: > ... >> diff --git a/fs/hugetlbfs/inode.c b/fs/hugetlbfs/inode.c >> index 7163fe0..dde8613 100644 >> --- a/fs/hugetlbfs/inode.c >> +++ b/fs/hugetlbfs/inode.c >> @@ -136,17 +136,26 @@

Re: [PATCH] hugetlbfs: fix offset overflow in huegtlbfs mmap

On 04/13/2017 08:32 PM, Naoya Horiguchi wrote: > On Tue, Apr 11, 2017 at 03:51:58PM -0700, Mike Kravetz wrote: > ... >> diff --git a/fs/hugetlbfs/inode.c b/fs/hugetlbfs/inode.c >> index 7163fe0..dde8613 100644 >> --- a/fs/hugetlbfs/inode.c >> +++ b/fs/hugetlbfs/inode.c >> @@ -136,17 +136,26 @@

Re: [patch 06/20] cpufreq: Use cpuhp_setup_state_nocalls_locked()

On Sat, Apr 15, 2017 at 7:01 PM, Thomas Gleixner wrote: > From: Sebastian Andrzej Siewior > > cpufreq holds get_online_cpus() while invoking cpuhp_setup_state_nocalls() > to make subsys_interface_register() and the registration of hotplug calls > atomic

Re: [patch 06/20] cpufreq: Use cpuhp_setup_state_nocalls_locked()

On Sat, Apr 15, 2017 at 7:01 PM, Thomas Gleixner wrote: > From: Sebastian Andrzej Siewior > > cpufreq holds get_online_cpus() while invoking cpuhp_setup_state_nocalls() > to make subsys_interface_register() and the registration of hotplug calls > atomic versus cpu hotplug. > >

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

On Sat, 2017-04-15 at 11:41 -0600, Logan Gunthorpe wrote: > Thanks, Benjamin, for the summary of some of the issues. > > On 14/04/17 04:07 PM, Benjamin Herrenschmidt wrote > > So I assume the p2p code provides a way to address that too via special > > dma_ops ? Or wrappers ? > > Not at this

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

On Sat, 2017-04-15 at 11:41 -0600, Logan Gunthorpe wrote: > Thanks, Benjamin, for the summary of some of the issues. > > On 14/04/17 04:07 PM, Benjamin Herrenschmidt wrote > > So I assume the p2p code provides a way to address that too via special > > dma_ops ? Or wrappers ? > > Not at this

[PATCH] ARM: dts: omap4-droid4: add bluetooth

Droid 4 has wl1835 connected to the OMAP's UART4 port, which is used for Bluetooth and most likely can also be used for controlling the FM radio and GPS receivers. Signed-off-by: Sebastian Reichel --- Hi, Thanks to the work of Rob adding Bluetooth support for Droid 4 was

[PATCH] ARM: dts: omap4-droid4: add bluetooth

Droid 4 has wl1835 connected to the OMAP's UART4 port, which is used for Bluetooth and most likely can also be used for controlling the FM radio and GPS receivers. Signed-off-by: Sebastian Reichel --- Hi, Thanks to the work of Rob adding Bluetooth support for Droid 4 was straight forward :) I

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

On Sat, Apr 15, 2017 at 10:41 AM, Logan Gunthorpe wrote: > Thanks, Benjamin, for the summary of some of the issues. > > On 14/04/17 04:07 PM, Benjamin Herrenschmidt wrote >> So I assume the p2p code provides a way to address that too via special >> dma_ops ? Or wrappers ? > >

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

On Sat, Apr 15, 2017 at 10:41 AM, Logan Gunthorpe wrote: > Thanks, Benjamin, for the summary of some of the issues. > > On 14/04/17 04:07 PM, Benjamin Herrenschmidt wrote >> So I assume the p2p code provides a way to address that too via special >> dma_ops ? Or wrappers ? > > Not at this time. We

Regression - Linux 4.9: ums_eneub6250 broken: transfer buffer not dma capable - Trace

Hello! Since Linux 4.9, ums_eneub6250 is broken. It's working fine if CONFIG_VMAP_STACK is disabled. I would be glad if it would be fixed. Thanks, kind regards, Andreas Apr 15 17:58:54 notebook2 kernel: usb 1-1.1: new high-speed USB device number 3 using ehci-pci Apr 15 17:58:54 notebook2

Regression - Linux 4.9: ums_eneub6250 broken: transfer buffer not dma capable - Trace

Hello! Since Linux 4.9, ums_eneub6250 is broken. It's working fine if CONFIG_VMAP_STACK is disabled. I would be glad if it would be fixed. Thanks, kind regards, Andreas Apr 15 17:58:54 notebook2 kernel: usb 1-1.1: new high-speed USB device number 3 using ehci-pci Apr 15 17:58:54 notebook2

[PATCH] Bluetooth: hci_ll: Fix NULL pointer deref on FW upload failure

Avoid NULL pointer dereference occurring due to freeing skb containing an error pointer. It can easily be triggered by using the driver with broken uart (i.e. due to misconfigured pinmuxing). Fixes: 371805522f87 ("bluetooth: hci_uart: add LL protocol serdev driver support") Signed-off-by:

[PATCH] Bluetooth: hci_ll: Fix NULL pointer deref on FW upload failure

Avoid NULL pointer dereference occurring due to freeing skb containing an error pointer. It can easily be triggered by using the driver with broken uart (i.e. due to misconfigured pinmuxing). Fixes: 371805522f87 ("bluetooth: hci_uart: add LL protocol serdev driver support") Signed-off-by:

Re: v4.10-rc8 (-rc6) boot regression on Intel desktop, does not boot after cold boots, boots after reboot

On Wed 2017-04-12 17:08:35, Frederic Weisbecker wrote: > On Mon, Apr 03, 2017 at 08:20:50PM +0200, Pavel Machek wrote: > > > > > > > ...1d.7: PCI fixup... pass 2 > > > > > > > ...1d.7: PCI fixup... pass 3 > > > > > > > ...1d.7: PCI fixup... pass 3 done > > > > > > > > > > > > > > ...followed by

Re: v4.10-rc8 (-rc6) boot regression on Intel desktop, does not boot after cold boots, boots after reboot

On Wed 2017-04-12 17:08:35, Frederic Weisbecker wrote: > On Mon, Apr 03, 2017 at 08:20:50PM +0200, Pavel Machek wrote: > > > > > > > ...1d.7: PCI fixup... pass 2 > > > > > > > ...1d.7: PCI fixup... pass 3 > > > > > > > ...1d.7: PCI fixup... pass 3 done > > > > > > > > > > > > > > ...followed by

[GIT PULL] ftrace: Fix removing of second function probe

Linus, While rewriting the function probe code, I stumbled over a long standing bug. This bug has been there since function tracing was added way back when. But my new development depends on this bug being fixed, and it should be fixed regardless as it causes ftrace to disable itself when

[GIT PULL] ftrace: Fix removing of second function probe

Linus, While rewriting the function probe code, I stumbled over a long standing bug. This bug has been there since function tracing was added way back when. But my new development depends on this bug being fixed, and it should be fixed regardless as it causes ftrace to disable itself when

Re: 4.10.9 nok with realtek wlan, atom

On 04/14/2017 03:26 PM, rupert THURNER wrote: On Thu, Feb 9, 2017 at 9:09 PM, Larry Finger wrote: On 02/09/2017 01:43 PM, Bjorn Helgaas wrote: [+cc rtl8192ce folks in case they've seen this] On Thu, Feb 09, 2017 at 03:45:01PM +0100, rupert THURNER wrote: hi,

Re: 4.10.9 nok with realtek wlan, atom

On 04/14/2017 03:26 PM, rupert THURNER wrote: On Thu, Feb 9, 2017 at 9:09 PM, Larry Finger wrote: On 02/09/2017 01:43 PM, Bjorn Helgaas wrote: [+cc rtl8192ce folks in case they've seen this] On Thu, Feb 09, 2017 at 03:45:01PM +0100, rupert THURNER wrote: hi, not technical expert enough,

[PATCH 1/3] mtd: sharpsl: add sharpslpart MTD partition parser

The Sharp SL Series (Zaurus) PXA handhelds have 16/64/128M of NAND flash and share the same layout of the first 7M partition, managed by Sharp FTL. The purpose of this self-contained patch is to add a common parser and remove the hardcoded sizes in the board files (these devices are not yet

[PATCH 1/3] mtd: sharpsl: add sharpslpart MTD partition parser

The Sharp SL Series (Zaurus) PXA handhelds have 16/64/128M of NAND flash and share the same layout of the first 7M partition, managed by Sharp FTL. The purpose of this self-contained patch is to add a common parser and remove the hardcoded sizes in the board files (these devices are not yet

[PATCH 0/3] mtd: sharpslpart partition parser

This patchset introduces a simple partition parser for the Sharp SL Series PXA handhelds. More details in the commit text. I have set in cc the ARM PXA maintainers because this is the MTD part of a planned wider patchset cleaning the Zaurus board files. Andrea Adami (3): mtd: sharpsl: add

[PATCH 2/3] mtd: nand: sharpsl.c: prefer sharpslpart MTD partition parser

This is the specific parser for Sharp SL Series (Zaurus). Signed-off-by: Andrea Adami --- drivers/mtd/nand/sharpsl.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/mtd/nand/sharpsl.c b/drivers/mtd/nand/sharpsl.c index 064ca17..2d1ba0e

[PATCH 3/3] mtd: nand: tmio_nand.c: prefer sharpslpart MTD partition parser

This is the specific parser for Sharp SL Series (Zaurus) Signed-off-by: Andrea Adami --- drivers/mtd/nand/tmio_nand.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/mtd/nand/tmio_nand.c b/drivers/mtd/nand/tmio_nand.c index fc5e773..f3612ac

[PATCH 2/3] mtd: nand: sharpsl.c: prefer sharpslpart MTD partition parser

This is the specific parser for Sharp SL Series (Zaurus). Signed-off-by: Andrea Adami --- drivers/mtd/nand/sharpsl.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/mtd/nand/sharpsl.c b/drivers/mtd/nand/sharpsl.c index 064ca17..2d1ba0e 100644 ---

[PATCH 3/3] mtd: nand: tmio_nand.c: prefer sharpslpart MTD partition parser

This is the specific parser for Sharp SL Series (Zaurus) Signed-off-by: Andrea Adami --- drivers/mtd/nand/tmio_nand.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/mtd/nand/tmio_nand.c b/drivers/mtd/nand/tmio_nand.c index fc5e773..f3612ac 100644 ---

[PATCH 0/3] mtd: sharpslpart partition parser

This patchset introduces a simple partition parser for the Sharp SL Series PXA handhelds. More details in the commit text. I have set in cc the ARM PXA maintainers because this is the MTD part of a planned wider patchset cleaning the Zaurus board files. Andrea Adami (3): mtd: sharpsl: add

Re: [PATCH] Revert "mm, page_alloc: only use per-cpu allocator for irq-safe requests"

On Sat, Apr 15, 2017 at 09:28:33PM +0200, Jesper Dangaard Brouer wrote: > On Sat, 15 Apr 2017 15:53:50 +0100 > Mel Gorman wrote: > > > This reverts commit 374ad05ab64d696303cec5cc8ec3a65d457b7b1c. While the > > patch worked great for userspace allocations, the fact

Re: [PATCH] Revert "mm, page_alloc: only use per-cpu allocator for irq-safe requests"

On Sat, Apr 15, 2017 at 09:28:33PM +0200, Jesper Dangaard Brouer wrote: > On Sat, 15 Apr 2017 15:53:50 +0100 > Mel Gorman wrote: > > > This reverts commit 374ad05ab64d696303cec5cc8ec3a65d457b7b1c. While the > > patch worked great for userspace allocations, the fact that softirq loses > > the

pinctrl: imx: Checking reuse of grouping functionality

Hello, A preprocessor symbol like “CONFIG_GENERIC_PINCTRL_GROUPS” was introduced by the commit c033a718f615b6b3ddc83ce3e0a217c30bd09cb5 (“pinctrl: stricten up generic group code”) on 2017-01-03. Some functions are only available then when this macro is defined. I have got the impression that the

pinctrl: imx: Checking reuse of grouping functionality

Hello, A preprocessor symbol like “CONFIG_GENERIC_PINCTRL_GROUPS” was introduced by the commit c033a718f615b6b3ddc83ce3e0a217c30bd09cb5 (“pinctrl: stricten up generic group code”) on 2017-01-03. Some functions are only available then when this macro is defined. I have got the impression that the

Re: [PATCH] Revert "mm, page_alloc: only use per-cpu allocator for irq-safe requests"

On Sat, 15 Apr 2017 15:53:50 +0100 Mel Gorman wrote: > This reverts commit 374ad05ab64d696303cec5cc8ec3a65d457b7b1c. While the > patch worked great for userspace allocations, the fact that softirq loses > the per-cpu allocator caused problems. It needs to be redone

Re: [PATCH] Revert "mm, page_alloc: only use per-cpu allocator for irq-safe requests"

On Sat, 15 Apr 2017 15:53:50 +0100 Mel Gorman wrote: > This reverts commit 374ad05ab64d696303cec5cc8ec3a65d457b7b1c. While the > patch worked great for userspace allocations, the fact that softirq loses > the per-cpu allocator caused problems. It needs to be redone taking into > account that a

[GIT PULL 07/19] lightnvm: don't check for failure from mempool_alloc()

From: NeilBrown mempool_alloc() cannot fail if the gfp flags allow it to sleep, and both GFP_KERNEL and GFP_NOIO allows for sleeping. So rrpc_move_valid_pages() and rrpc_make_rq() don't need to test the return value. Signed-off-by: NeilBrown Signed-off-by:

[GIT PULL 07/19] lightnvm: don't check for failure from mempool_alloc()

From: NeilBrown mempool_alloc() cannot fail if the gfp flags allow it to sleep, and both GFP_KERNEL and GFP_NOIO allows for sleeping. So rrpc_move_valid_pages() and rrpc_make_rq() don't need to test the return value. Signed-off-by: NeilBrown Signed-off-by: Matias Bjørling ---

[GIT PULL 06/19] lightnvm: enable nvme size compile asserts

The asserts in _nvme_nvm_check_size are not compiled due to the function not begin called. Make sure that it is called, and also fix the wrong sizes of asserts for nvme_nvm_addr_format, and nvme_nvm_bb_tbl, which checked for number of bits instead of bytes. Reported-by: Scott Bauer

[GIT PULL 10/19] lightnvm: bad type conversion for nvme control bits

From: Javier González The NVMe I/O command control bits are 16 bytes, but is interpreted as 32 bytes in the lightnvm user I/O data path. Signed-off-by: Javier González Signed-off-by: Matias Bjørling --- drivers/nvme/host/lightnvm.c

[GIT PULL 06/19] lightnvm: enable nvme size compile asserts

The asserts in _nvme_nvm_check_size are not compiled due to the function not begin called. Make sure that it is called, and also fix the wrong sizes of asserts for nvme_nvm_addr_format, and nvme_nvm_bb_tbl, which checked for number of bits instead of bytes. Reported-by: Scott Bauer

[GIT PULL 10/19] lightnvm: bad type conversion for nvme control bits

From: Javier González The NVMe I/O command control bits are 16 bytes, but is interpreted as 32 bytes in the lightnvm user I/O data path. Signed-off-by: Javier González Signed-off-by: Matias Bjørling --- drivers/nvme/host/lightnvm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[GIT PULL 02/19] nvme/lightnvm: Prevent small buffer overflow in nvme_nvm_identify

From: Scott Bauer There are two closely named structs in lightnvm: struct nvme_nvm_addr_format and struct nvme_addr_format. The first struct has 4 reserved bytes at the end, the second does not. (gdb) p sizeof(struct nvme_nvm_addr_format) $1 = 16 (gdb) p sizeof(struct

[GIT PULL 09/19] lightnvm: fix cleanup order of disk on init error

From: Javier González Reorder disk allocation such that the disk structure can be put safely. Signed-off-by: Javier González Signed-off-by: Matias Bjørling --- drivers/lightnvm/core.c | 14 +++--- 1 file changed, 7

[GIT PULL 02/19] nvme/lightnvm: Prevent small buffer overflow in nvme_nvm_identify

From: Scott Bauer There are two closely named structs in lightnvm: struct nvme_nvm_addr_format and struct nvme_addr_format. The first struct has 4 reserved bytes at the end, the second does not. (gdb) p sizeof(struct nvme_nvm_addr_format) $1 = 16 (gdb) p sizeof(struct nvm_addr_format) $2 = 12

[GIT PULL 09/19] lightnvm: fix cleanup order of disk on init error

From: Javier González Reorder disk allocation such that the disk structure can be put safely. Signed-off-by: Javier González Signed-off-by: Matias Bjørling --- drivers/lightnvm/core.c | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/drivers/lightnvm/core.c

[GIT PULL 03/19] lightnvm: submit erases using the I/O path

From: Javier González Until now erases have been submitted as synchronous commands through a dedicated erase function. In order to enable targets implementing asynchronous erases, refactor the erase path so that it uses the normal async I/O submission functions. If a target

[GIT PULL 03/19] lightnvm: submit erases using the I/O path

From: Javier González Until now erases have been submitted as synchronous commands through a dedicated erase function. In order to enable targets implementing asynchronous erases, refactor the erase path so that it uses the normal async I/O submission functions. If a target requires sync I/O, it

[GIT PULL 15/19] lightnvm: convert sprintf into strlcpy

From: Javier González Convert sprintf calls to strlcpy in order to make possible buffer overflow more obvious. Signed-off-by: Javier González Signed-off-by: Matias Bjørling --- drivers/lightnvm/core.c | 6 +++--- 1 file changed, 3

[GIT PULL 15/19] lightnvm: convert sprintf into strlcpy

From: Javier González Convert sprintf calls to strlcpy in order to make possible buffer overflow more obvious. Signed-off-by: Javier González Signed-off-by: Matias Bjørling --- drivers/lightnvm/core.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

[GIT PULL 14/19] lightnvm: fix type checks on rrpc

From: Javier González sector_t is always unsigned, therefore avoid < 0 checks on it. Signed-off-by: Javier González Signed-off-by: Matias Bjørling --- drivers/lightnvm/rrpc.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)

[GIT PULL 14/19] lightnvm: fix type checks on rrpc

From: Javier González sector_t is always unsigned, therefore avoid < 0 checks on it. Signed-off-by: Javier González Signed-off-by: Matias Bjørling --- drivers/lightnvm/rrpc.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/lightnvm/rrpc.c

[GIT PULL 08/19] lightnvm: double-clear of dev->lun_map on target init error

From: Javier González The dev->lun_map bits are cleared twice if an target init error occurs. First in the target clean routine, and then next in the nvm_tgt_create error function. Make sure that it is only cleared once by extending nvm_remove_tgt_devi() with a clear bit, such

[GIT PULL 08/19] lightnvm: double-clear of dev->lun_map on target init error

From: Javier González The dev->lun_map bits are cleared twice if an target init error occurs. First in the target clean routine, and then next in the nvm_tgt_create error function. Make sure that it is only cleared once by extending nvm_remove_tgt_devi() with a clear bit, such that clearing of

[GIT PULL 19/19] lightnvm: fix some error code in pblk-init.c

From: Dan Carpenter There were a bunch of places in pblk_lines_init() where we didn't set an error code. And in pblk_writer_init() we accidentally return 1 instead of a correct error code, which would result in a Oops later. Fixes: 11a5d6fdf919 ("lightnvm: physical

[GIT PULL 19/19] lightnvm: fix some error code in pblk-init.c

From: Dan Carpenter There were a bunch of places in pblk_lines_init() where we didn't set an error code. And in pblk_writer_init() we accidentally return 1 instead of a correct error code, which would result in a Oops later. Fixes: 11a5d6fdf919 ("lightnvm: physical block device (pblk) target")

[GIT PULL 17/19] lightnvm: pblk-gc: fix an error pointer dereference in init

From: Dan Carpenter These labels are reversed so we could end up dereferencing an error pointer or leaking. Fixes: 7f347ba6bb3a ("lightnvm: physical block device (pblk) target") Signed-off-by: Dan Carpenter Signed-off-by: Matias Bjørling

[GIT PULL 17/19] lightnvm: pblk-gc: fix an error pointer dereference in init

From: Dan Carpenter These labels are reversed so we could end up dereferencing an error pointer or leaking. Fixes: 7f347ba6bb3a ("lightnvm: physical block device (pblk) target") Signed-off-by: Dan Carpenter Signed-off-by: Matias Bjørling --- drivers/lightnvm/pblk-gc.c | 4 ++-- 1 file

[GIT PULL 18/19] lightnvm: fix some WARN() messages

From: Dan Carpenter WARN_ON() takes a condition, not an error message. I slightly tweaked some conditions so hopefully it's more clear. Signed-off-by: Dan Carpenter Signed-off-by: Matias Bjørling ---

[GIT PULL 18/19] lightnvm: fix some WARN() messages

From: Dan Carpenter WARN_ON() takes a condition, not an error message. I slightly tweaked some conditions so hopefully it's more clear. Signed-off-by: Dan Carpenter Signed-off-by: Matias Bjørling --- drivers/lightnvm/pblk-read.c | 12 ++-- drivers/lightnvm/pblk-recovery.c | 2

[GIT PULL 12/19] lightnvm: make nvm_free static

From: Javier González Prefix the nvm_free static function with a missing static keyword. Signed-off-by: Javier González Signed-off-by: Matias Bjørling --- drivers/lightnvm/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[GIT PULL 12/19] lightnvm: make nvm_free static

From: Javier González Prefix the nvm_free static function with a missing static keyword. Signed-off-by: Javier González Signed-off-by: Matias Bjørling --- drivers/lightnvm/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/lightnvm/core.c

[GIT PULL 13/19] lightnvm: clean unused variable

From: Javier González Clean unused variable on lightnvm core. Signed-off-by: Javier González Signed-off-by: Matias Bjørling --- drivers/lightnvm/core.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/drivers/lightnvm/core.c

[GIT PULL 11/19] lightnvm: allow to init targets on factory mode

From: Javier González Target initialization has two responsibilities: creating the target partition and instantiating the target. This patch enables to create a factory partition (e.g., do not trigger recovery on the given target). This is useful for target development and for

  1   2   3   4   >