Re: [PATCH for-4.4] mtd: nand: assign reasonable default name for NAND drivers

Hi Boris, On Mon, Jan 04, 2016 at 09:31:02PM +0100, Boris Brezillon wrote: > On Mon, 4 Jan 2016 11:11:03 -0800 > Brian Norris wrote: > > > Commits such as commit 853f1c58c4b2 ("mtd: nand: omap2: show parent > > device structure in sysfs") attempt to rely on the core MTD code to set > > the MTD

Re: [PATCH for-4.4] mtd: nand: assign reasonable default name for NAND drivers

Hi Boris, On Mon, Jan 04, 2016 at 09:31:02PM +0100, Boris Brezillon wrote: > On Mon, 4 Jan 2016 11:11:03 -0800 > Brian Norris wrote: > > > Commits such as commit 853f1c58c4b2 ("mtd: nand: omap2: show parent > > device structure in sysfs") attempt to rely on the

Re: [PATCH for-4.4] mtd: nand: assign reasonable default name for NAND drivers

Hello Brian, Am 04.01.2016 um 20:11 schrieb Brian Norris: Commits such as commit 853f1c58c4b2 ("mtd: nand: omap2: show parent device structure in sysfs") attempt to rely on the core MTD code to set the MTD name based on the parent device. However, nand_base tries to set a different default name

Re: [PATCH for-4.4] mtd: nand: assign reasonable default name for NAND drivers

Hi Brian, On Mon, 4 Jan 2016 11:11:03 -0800 Brian Norris wrote: > Commits such as commit 853f1c58c4b2 ("mtd: nand: omap2: show parent > device structure in sysfs") attempt to rely on the core MTD code to set > the MTD name based on the parent device. However, nand_base tries to set > a

[PATCH for-4.4] mtd: nand: assign reasonable default name for NAND drivers

Commits such as commit 853f1c58c4b2 ("mtd: nand: omap2: show parent device structure in sysfs") attempt to rely on the core MTD code to set the MTD name based on the parent device. However, nand_base tries to set a different default name according to the flash name (e.g., extracted from the ONFI

[PATCH for-4.4] mtd: nand: assign reasonable default name for NAND drivers

Commits such as commit 853f1c58c4b2 ("mtd: nand: omap2: show parent device structure in sysfs") attempt to rely on the core MTD code to set the MTD name based on the parent device. However, nand_base tries to set a different default name according to the flash name (e.g., extracted from the ONFI

Re: [PATCH for-4.4] mtd: nand: assign reasonable default name for NAND drivers

Hi Brian, On Mon, 4 Jan 2016 11:11:03 -0800 Brian Norris wrote: > Commits such as commit 853f1c58c4b2 ("mtd: nand: omap2: show parent > device structure in sysfs") attempt to rely on the core MTD code to set > the MTD name based on the parent device. However,

Re: [PATCH for-4.4] mtd: nand: assign reasonable default name for NAND drivers

Hello Brian, Am 04.01.2016 um 20:11 schrieb Brian Norris: Commits such as commit 853f1c58c4b2 ("mtd: nand: omap2: show parent device structure in sysfs") attempt to rely on the core MTD code to set the MTD name based on the parent device. However, nand_base tries to set a different default name