2009-04-06 13:11:17

by Paulius Zaleckas

Subject: [PATCH] mtd: fix Kconfig comment about 'armflash'

The real 'armflash' map driver is selected by CONFIG_MTD_ARM_INTEGRATOR

Signed-off-by: Paulius Zaleckas <[email protected]>
---

drivers/mtd/Kconfig | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)


diff --git a/drivers/mtd/Kconfig b/drivers/mtd/Kconfig
index 7d04fb9..b8e35a0 100644
--- a/drivers/mtd/Kconfig
+++ b/drivers/mtd/Kconfig
@@ -154,7 +154,8 @@ config MTD_AFS_PARTS

You will still need the parsing functions to be called by the driver
for your particular device. It won't happen automatically. The
- 'armflash' map driver (CONFIG_MTD_ARMFLASH) does this, for example.
+ 'armflash' map driver (CONFIG_MTD_ARM_INTEGRATOR) does this, for
+ example.

config MTD_OF_PARTS
tristate "Flash partition map based on OF description"

2009-04-15 09:58:22

by Jiri Kosina

Subject: Re: [PATCH] mtd: fix Kconfig comment about 'armflash'

On Mon, 6 Apr 2009, Paulius Zaleckas wrote:

> The real 'armflash' map driver is selected by CONFIG_MTD_ARM_INTEGRATOR
>
> Signed-off-by: Paulius Zaleckas <[email protected]>
> ---
>
> drivers/mtd/Kconfig | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
>
> diff --git a/drivers/mtd/Kconfig b/drivers/mtd/Kconfig
> index 7d04fb9..b8e35a0 100644
> --- a/drivers/mtd/Kconfig
> +++ b/drivers/mtd/Kconfig
> @@ -154,7 +154,8 @@ config MTD_AFS_PARTS
>
> You will still need the parsing functions to be called by the driver
> for your particular device. It won't happen automatically. The
> - 'armflash' map driver (CONFIG_MTD_ARMFLASH) does this, for example.
> + 'armflash' map driver (CONFIG_MTD_ARM_INTEGRATOR) does this, for
> + example.
>
> config MTD_OF_PARTS
> tristate "Flash partition map based on OF description"

Applied to trivial tree, thanks.

--
Jiri Kosina
SUSE Labs