Message ID | 20090406131054.16163.11343.stgit@Programuotojas |
---|---|
State | Superseded |
Headers | show |
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 <paulius.zaleckas@teltonika.lt> > --- > > 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.
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"
The real 'armflash' map driver is selected by CONFIG_MTD_ARM_INTEGRATOR Signed-off-by: Paulius Zaleckas <paulius.zaleckas@teltonika.lt> --- drivers/mtd/Kconfig | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-)