From: Alison Wang <b18965@freescale.com>
To: <boris.brezillon@free-electrons.com>, <marek.vasut@gmail.com>,
<cyrille.pitchen@atmel.com>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mtd@lists.infradead.org>, <dwmw2@infradead.org>,
<computersforpeace@gmail.com>
Cc: <alison.wang@nxp.com>
Subject: [PATCH v2 2/2] mtd: nand: Update dependency of IFC for LS1021A
Date: Tue, 3 Jan 2017 10:41:06 +0800 [thread overview]
Message-ID: <1483411266-45875-2-git-send-email-b18965@freescale.com> (raw)
In-Reply-To: <1483411266-45875-1-git-send-email-b18965@freescale.com>
As NAND support for Freescale/NXP IFC controller is available on
LS1021A, the dependency for LS1021A is added.
Signed-off-by: Alison Wang <alison.wang@nxp.com>
---
Changes in v2:
- None
drivers/mtd/nand/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mtd/nand/Kconfig b/drivers/mtd/nand/Kconfig
index 353a9dd..85e3860 100644
--- a/drivers/mtd/nand/Kconfig
+++ b/drivers/mtd/nand/Kconfig
@@ -441,7 +441,7 @@ config MTD_NAND_FSL_ELBC
config MTD_NAND_FSL_IFC
tristate "NAND support for Freescale IFC controller"
- depends on FSL_SOC || ARCH_LAYERSCAPE
+ depends on FSL_SOC || ARCH_LAYERSCAPE || SOC_LS1021A
select FSL_IFC
select MEMORY
help
--
2.1.0.27.g96db324
next prev parent reply other threads:[~2017-01-03 2:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 2:41 [PATCH v2 1/2] mtd: ifc: Update dependency of IFC for LS1021A Alison Wang
2017-01-03 2:41 ` Alison Wang [this message]
2017-01-03 11:46 ` [PATCH v2 2/2] mtd: nand: " Marek Vasut
2017-01-04 1:46 ` Alison Wang
2017-01-04 1:50 ` Marek Vasut
2017-01-05 2:02 ` Alison Wang
2017-02-06 9:05 ` Boris Brezillon
2017-02-13 6:59 ` Alison Wang
2017-01-03 9:04 ` [PATCH v2 1/2] mtd: ifc: " Boris Brezillon
2017-01-03 9:19 ` Alison Wang
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=1483411266-45875-2-git-send-email-b18965@freescale.com \
--to=b18965@freescale.com \
--cc=alison.wang@nxp.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@atmel.com \
--cc=dwmw2@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.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).