From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Roger Quadros <rogerq@ti.com>
Cc: computersforpeace@gmail.com, fcooper@ti.com, tony@atomide.com,
linux-mtd@lists.infradead.org, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: nand: Allow MTD_NAND_OMAP2 to be usable on Keystone devices
Date: Fri, 26 Aug 2016 09:47:59 +0200 [thread overview]
Message-ID: <20160826094759.0130d6dd@bbrezillon> (raw)
In-Reply-To: <1472030700-16051-1-git-send-email-rogerq@ti.com>
On Wed, 24 Aug 2016 12:25:00 +0300
Roger Quadros <rogerq@ti.com> wrote:
> Some Keystone devices (e.g. K2G) include a OMAP NAND IP.
> Allow the NAND driver to be usable for both
> Keystone and OMAP devices.
>
> Signed-off-by: Roger Quadros <rogerq@ti.com>
Applied.
Thanks,
Boris
> ---
> drivers/mtd/nand/Kconfig | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/mtd/nand/Kconfig b/drivers/mtd/nand/Kconfig
> index 21ff580..e6260df 100644
> --- a/drivers/mtd/nand/Kconfig
> +++ b/drivers/mtd/nand/Kconfig
> @@ -88,11 +88,11 @@ config MTD_NAND_AMS_DELTA
> Support for NAND flash on Amstrad E3 (Delta).
>
> config MTD_NAND_OMAP2
> - tristate "NAND Flash device on OMAP2, OMAP3 and OMAP4"
> - depends on ARCH_OMAP2PLUS
> + tristate "NAND Flash device on OMAP2, OMAP3, OMAP4 and Keystone"
> + depends on (ARCH_OMAP2PLUS || ARCH_KEYSTONE)
> help
> - Support for NAND flash on Texas Instruments OMAP2, OMAP3 and OMAP4
> - platforms.
> + Support for NAND flash on Texas Instruments OMAP2, OMAP3, OMAP4
> + and Keystone platforms.
>
> config MTD_NAND_OMAP_BCH
> depends on MTD_NAND_OMAP2
prev parent reply other threads:[~2016-08-26 7:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 9:25 [PATCH] mtd: nand: Allow MTD_NAND_OMAP2 to be usable on Keystone devices Roger Quadros
2016-08-26 7:47 ` Boris Brezillon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160826094759.0130d6dd@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=fcooper@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=rogerq@ti.com \
--cc=tony@atomide.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).