From: festevam@gmail.com (Fabio Estevam)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: mx5: introduce SOC_IMX51
Date: Fri, 19 Nov 2010 18:34:14 -0200 [thread overview]
Message-ID: <AANLkTimxVg3o2U=gr5g-aaBFH+-FNzaCgJPC6ugqPcpi@mail.gmail.com> (raw)
In-Reply-To: <20101119192846.GW8942@pengutronix.de>
Hi Uwe,
2010/11/19 Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>:
...
>> ?config ARCH_MX51
>> ? ? ? bool
>> +
>> +config SOC_IMX51
>> + ? ? bool
>> ? ? ? default y
> Can you please remove this default y and let all MACH_XYZ select it?
Ok, will do as suggested and will send the v2 of this patch after your
patch series hits Sascha?s tree.
I noticed that arch/arm/mach-mx5/Kconfig will conflict later if I base
my patch on top of your tree.
Thanks,
Fabio Estevam
prev parent reply other threads:[~2010-11-19 20:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 19:06 [PATCH 1/2] ARM: mx5: introduce SOC_IMX51 Fabio Estevam
2010-11-19 19:06 ` [PATCH 2/2] ARM: mx5: dynamically allocate imx2-wdt devices Fabio Estevam
2010-11-19 19:28 ` [PATCH 1/2] ARM: mx5: introduce SOC_IMX51 Uwe Kleine-König
2010-11-19 20:34 ` Fabio Estevam [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='AANLkTimxVg3o2U=gr5g-aaBFH+-FNzaCgJPC6ugqPcpi@mail.gmail.com' \
--to=festevam@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;
as well as URLs for NNTP newsgroup(s).