From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: richard@nod.at, dwmw2@infradead.org, computersforpeace@gmail.com,
marek.vasut@gmail.com, cyrille.pitchen@atmel.com,
linux-mtd@lists.infradead.org, john@phrozen.org,
stable@vger.kernel.org
Subject: Re: [PATCH V2 1/2] mtd: nand: xway: disable module support
Date: Tue, 3 Jan 2017 09:19:15 +0100 [thread overview]
Message-ID: <20170103091915.50673027@bbrezillon> (raw)
In-Reply-To: <20161205211437.29489-1-hauke@hauke-m.de>
On Mon, 5 Dec 2016 22:14:36 +0100
Hauke Mehrtens <hauke@hauke-m.de> wrote:
> The xway_nand driver accesses the ltq_ebu_membase symbol which is not
> exported. This also should not get exported and we should handle the
> EBU interface in a better way later. This quick fix just deactivated
> support for building as module.
>
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
Applied both to nand/fixes. They should appear in one of the next -rc
(probably not -rc3 though).
Thanks,
Boris
> ---
> 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 7b7a887..b254090 100644
> --- a/drivers/mtd/nand/Kconfig
> +++ b/drivers/mtd/nand/Kconfig
> @@ -537,7 +537,7 @@ config MTD_NAND_FSMC
> Flexible Static Memory Controller (FSMC)
>
> config MTD_NAND_XWAY
> - tristate "Support for NAND on Lantiq XWAY SoC"
> + bool "Support for NAND on Lantiq XWAY SoC"
> depends on LANTIQ && SOC_TYPE_XWAY
> help
> Enables support for NAND Flash chips on Lantiq XWAY SoCs. NAND is attached
prev parent reply other threads:[~2017-01-03 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 21:14 [PATCH V2 1/2] mtd: nand: xway: disable module support Hauke Mehrtens
2016-12-05 21:14 ` [PATCH V2 2/2] mtd: nand: xway: fix build because of module functions Hauke Mehrtens
2017-01-03 8:19 ` 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=20170103091915.50673027@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@atmel.com \
--cc=dwmw2@infradead.org \
--cc=hauke@hauke-m.de \
--cc=john@phrozen.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
--cc=stable@vger.kernel.org \
/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