From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: linux-mtd@lists.infradead.org, Han Xu <han.xu@nxp.com>,
Richard Weinberger <richard@nod.at>,
kernel@pengutronix.de
Subject: Re: [PATCH] mtd: nand: gpmi-nand: Remove wrong Kconfig help text
Date: Thu, 30 Nov 2017 22:34:56 +0100 [thread overview]
Message-ID: <20171130223456.1c5c0db6@bbrezillon> (raw)
In-Reply-To: <20171117110912.24305-1-s.hauer@pengutronix.de>
On Fri, 17 Nov 2017 12:09:12 +0100
Sascha Hauer <s.hauer@pengutronix.de> wrote:
> The GPMI nand Kconfig help texts mentions that the GPMI nand driver
> might conflict with SD cards. The only conflict there might really
> be is that both controllers use the same pins, but this is resolved
> by the pincontroller setup in the device tree. In any way the GPMI
> driver can safely be enabled, the text is just wrong. Remove it.
Applied.
Thanks,
Boris
>
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> ---
> drivers/mtd/nand/Kconfig | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/mtd/nand/Kconfig b/drivers/mtd/nand/Kconfig
> index 3f2036f31da4..8f4c288cf9f1 100644
> --- a/drivers/mtd/nand/Kconfig
> +++ b/drivers/mtd/nand/Kconfig
> @@ -373,9 +373,7 @@ config MTD_NAND_GPMI_NAND
> Enables NAND Flash support for IMX23, IMX28 or IMX6.
> The GPMI controller is very powerful, with the help of BCH
> module, it can do the hardware ECC. The GPMI supports several
> - NAND flashs at the same time. The GPMI may conflicts with other
> - block, such as SD card. So pay attention to it when you enable
> - the GPMI.
> + NAND flashs at the same time.
>
> config MTD_NAND_BRCMNAND
> tristate "Broadcom STB NAND controller"
prev parent reply other threads:[~2017-11-30 21:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 11:09 [PATCH] mtd: nand: gpmi-nand: Remove wrong Kconfig help text Sascha Hauer
2017-11-17 11:34 ` Fabio Estevam
2017-11-17 16:46 ` Han Xu
2017-11-30 21:34 ` 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=20171130223456.1c5c0db6@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=han.xu@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=s.hauer@pengutronix.de \
/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