From: Arnd Bergmann <arnd@arndb.de>
To: Philip Rakity <prakity@marvell.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Mark Brown <markb@marvell.com>, Chris Ball <cjb@laptop.org>
Subject: Re: [PATCH 2/4] arm: configs: update mmp2 defconfig for brownstone and SoC Selection
Date: Mon, 14 Feb 2011 15:05:39 +0100 [thread overview]
Message-ID: <201102141505.39981.arnd@arndb.de> (raw)
In-Reply-To: <04A50A49-CBBC-4E5D-B19E-391B4DF77DF3@marvell.com>
On Monday 14 February 2011, Philip Rakity wrote:
> took old mmp2_defconfig --
> did make menuconfig
> changed to CPU_MMP2
> added brownstone as supported board
>
> Signed-off-by: Philip Rakity <prakity@marvell.com>
You should not use full .config files as defconfig any more these days.
Please use 'make defconfig' as a final step to create the minimum
list of config symbols. This applies to the other two as well.
Arnd
next prev parent reply other threads:[~2011-02-14 14:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 6:44 [PATCH 2/4] arm: configs: update mmp2 defconfig for brownstone and SoC Selection Philip Rakity
2011-02-14 14:05 ` Arnd Bergmann [this message]
2011-02-14 18:26 ` Nicolas Pitre
2011-02-15 21:50 ` [PATCH 2/4] arm: V2 " Philip Rakity
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=201102141505.39981.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=cjb@laptop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=markb@marvell.com \
--cc=prakity@marvell.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