From: eric@eukrea.com (Eric Bénard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/5] mx25: add defconfig
Date: Fri, 15 Oct 2010 10:19:58 +0200 [thread overview]
Message-ID: <4CB80EAE.9060103@eukrea.com> (raw)
In-Reply-To: <20101015072254.GG6747@pengutronix.de>
Hi Uwe,
Le 15/10/2010 09:22, Uwe Kleine-K?nig a ?crit :
> On Fri, Oct 15, 2010 at 01:00:02AM +0200, Eric B?nard wrote:
>> Signed-off-by: Eric B?nard<eric@eukrea.com>
> I'd like to see mx25 in a defconfig, too. In case RMK subjects
> that adding a defconfig isn't sensible, I think the best bet we have is
> merging mx3 and mx25 into mach-imx and working to allow compiling a
> kernel that supports these two in a single kernel. (mx3 and mx25 share
> PHYS_OFFSET, so this is easier than the other merges.)
>
I think we can go with this defconfig for the short time and have more time to
merge imx/mx25 and mx3.
Eric
next prev parent reply other threads:[~2010-10-15 8:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 23:00 [PATCH 1/5] mach-pcm037_eet: fix compile errors Eric Bénard
2010-10-14 23:00 ` [PATCH 2/5] mx25: add defconfig Eric Bénard
2010-10-15 7:22 ` Uwe Kleine-König
2010-10-15 8:19 ` Eric Bénard [this message]
2010-10-14 23:00 ` [PATCH 3/5] mx27: update defconfig Eric Bénard
2010-10-15 7:27 ` Uwe Kleine-König
2010-10-14 23:00 ` [PATCH 4/5] mx3: " Eric Bénard
2010-10-14 23:00 ` [PATCH 5/5] mx51: " Eric Bénard
2010-10-15 7:07 ` [PATCH 1/5] mach-pcm037_eet: fix compile errors Uwe Kleine-König
2010-10-15 10:15 ` [PATCH v2 " Eric Bénard
2010-10-15 10:15 ` [PATCH v2 2/5] mx25: add defconfig Eric Bénard
2010-10-16 18:33 ` Baruch Siach
2010-10-15 10:15 ` [PATCH v2 3/5] mx27: update defconfig Eric Bénard
2010-10-15 10:15 ` [PATCH v2 4/5] mx3: " Eric Bénard
2010-10-15 10:15 ` [PATCH v2 5/5] mx51: " Eric Bénard
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=4CB80EAE.9060103@eukrea.com \
--to=eric@eukrea.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;
as well as URLs for NNTP newsgroup(s).