From: Brian Norris <computersforpeace@gmail.com>
To: <linux-mtd@lists.infradead.org>
Cc: linuxppc-dev@lists.ozlabs.org,
Brian Norris <computersforpeace@gmail.com>,
Scott Wood <scottwood@freescale.com>
Subject: [PATCH] mtd: nand: add FSL_SOC dependency to drivers using FSL_LBC
Date: Thu, 7 Jan 2016 11:21:41 -0800 [thread overview]
Message-ID: <1452194501-115280-1-git-send-email-computersforpeace@gmail.com> (raw)
I've managed to construct .config files (for ppc64) that come across
this Kconfig warning:
warning: (MPC836x_RDK && MTD_NAND_FSL_ELBC && MTD_NAND_FSL_UPM) selects FSL_LBC which has unmet direct dependencies (FSL_SOC)
Let's add the FSL_SOC dependency to the NAND drivers. AFAICT, they are
only supported on PPC32 FSL SoCs anyway.
Signed-off-by: Brian Norris <computersforpeace@gmail.com>
Cc: Scott Wood <scottwood@freescale.com>
---
drivers/mtd/nand/Kconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/mtd/nand/Kconfig b/drivers/mtd/nand/Kconfig
index 289664089cf3..13bbceec6b5f 100644
--- a/drivers/mtd/nand/Kconfig
+++ b/drivers/mtd/nand/Kconfig
@@ -427,6 +427,7 @@ config MTD_NAND_ORION
config MTD_NAND_FSL_ELBC
tristate "NAND support for Freescale eLBC controllers"
depends on PPC
+ depends on FSL_SOC
select FSL_LBC
help
Various Freescale chips, including the 8313, include a NAND Flash
@@ -448,6 +449,7 @@ config MTD_NAND_FSL_IFC
config MTD_NAND_FSL_UPM
tristate "Support for NAND on Freescale UPM"
depends on PPC_83xx || PPC_85xx
+ depends on FSL_SOC
select FSL_LBC
help
Enables support for NAND Flash chips wired onto Freescale PowerPC
--
2.6.0.rc2.230.g3dd15c0
next reply other threads:[~2016-01-07 19:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 19:21 Brian Norris [this message]
2016-01-07 19:47 ` [PATCH] mtd: nand: add FSL_SOC dependency to drivers using FSL_LBC Scott Wood
2016-01-07 20:34 ` Brian Norris
2016-01-07 20:40 ` Scott Wood
2016-01-07 20:45 ` Brian Norris
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=1452194501-115280-1-git-send-email-computersforpeace@gmail.com \
--to=computersforpeace@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.