From patchwork Mon Apr 6 13:10:54 2009 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: mtd: fix Kconfig comment about 'armflash' Date: Mon, 06 Apr 2009 03:10:54 -0000 From: Paulius Zaleckas X-Patchwork-Id: 25634 Message-Id: <20090406131054.16163.11343.stgit@Programuotojas> To: linux-mtd@lists.infradead.org, trivial@kernel.org Cc: linux-kernel@vger.kernel.org The real 'armflash' map driver is selected by CONFIG_MTD_ARM_INTEGRATOR Signed-off-by: Paulius Zaleckas --- 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"