From: computersforpeace@gmail.com (Brian Norris)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: footbridge: enable dc21285 mtd map in defconfig
Date: Thu, 28 May 2015 12:55:58 -0700 [thread overview]
Message-ID: <20150528195558.GR27753@ld-irv-0074> (raw)
In-Reply-To: <1432842380-4187-1-git-send-email-u.kleine-koenig@pengutronix.de>
On Thu, May 28, 2015 at 09:46:20PM +0200, Uwe Kleine-K?nig wrote:
> This driver fails to build since release 3.2. Improve compile coverage
> by enabling this driver in the footbridge defconfig
Actually, it did build, but it just had alarming warnings. I don't think
those warnings actually affected anything at runtime, except for lock
debugging (if enabled).
But anyway, the change looks good, and I'm doing this in my local build
tests now, so:
> Signed-off-by: Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>
Acked-by: Brian Norris <computersforpeace@gmail.com>
> ---
> arch/arm/configs/footbridge_defconfig | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/arm/configs/footbridge_defconfig b/arch/arm/configs/footbridge_defconfig
> index 87e020f303ab..9aebf4b910ca 100644
> --- a/arch/arm/configs/footbridge_defconfig
> +++ b/arch/arm/configs/footbridge_defconfig
> @@ -37,6 +37,10 @@ CONFIG_IRDA_CACHE_LAST_LSAP=y
> CONFIG_IRDA_FAST_RR=y
> CONFIG_IRDA_DEBUG=y
> CONFIG_WINBOND_FIR=m
> +CONFIG_MTD=m
> +CONFIG_MTD_CFI=m
> +CONFIG_MTD_COMPLEX_MAPPINGS=y
> +CONFIG_MTD_DC21285=m
> CONFIG_PARPORT=y
> CONFIG_PARPORT_PC=y
> CONFIG_PARPORT_PC_FIFO=y
next prev parent reply other threads:[~2015-05-28 19:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150528192238.GQ27753@ld-irv-0074>
2015-05-28 19:46 ` [PATCH] ARM: footbridge: enable dc21285 mtd map in defconfig Uwe Kleine-König
2015-05-28 19:55 ` Brian Norris [this message]
2015-05-28 21:05 ` Russell King - ARM Linux
2015-05-29 6:49 ` Uwe Kleine-König
2015-05-29 8:42 ` Russell King - ARM Linux
2015-05-30 1:18 ` 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=20150528195558.GR27753@ld-irv-0074 \
--to=computersforpeace@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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