From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/8] ARM: mx5: use config to define boot related addresses
Date: Wed, 29 Dec 2010 10:25:26 +0100 [thread overview]
Message-ID: <20101229092526.GQ14221@pengutronix.de> (raw)
In-Reply-To: <1293607828-21213-1-git-send-email-richard.zhao@freescale.com>
On Wed, Dec 29, 2010 at 03:30:23PM +0800, Richard Zhao wrote:
> Signed-off-by: Richard Zhao <richard.zhao@freescale.com>
> ---
> Because common clock is change, I don't send out mx50 clock and board level code.
> But sure I tested the patch series using the clock/board code.
IMHO you can already add the board code and make it depend on BROKEN
with an accompanying comment about the missing clock support.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2010-12-29 9:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-29 7:30 [PATCH v2 1/8] ARM: mx5: use config to define boot related addresses Richard Zhao
2010-12-29 7:30 ` [PATCH v2 2/8] arm: plat-mxc: add full parameter macro to define gpio port Richard Zhao
2010-12-29 7:30 ` [PATCH v2 3/8] arm: mx51: define mx51's own MXC_GPIO_IRQS Richard Zhao
2010-12-29 7:30 ` [PATCH v2 4/8] arm: mx5: mx51/53 have different mxc_cpu_type definition Richard Zhao
2010-12-29 7:30 ` [PATCH v2 5/8] arm: mxc: move IOMUX_CONFIG_XXXX definitions to iomux-v3.h Richard Zhao
2010-12-29 7:30 ` [PATCH v2 6/8] arm: mx50: add core functions support except clock Richard Zhao
2010-12-29 8:26 ` Uwe Kleine-König
2010-12-29 9:03 ` Richard Zhao
2010-12-30 4:42 ` Richard Zhao
2010-12-29 8:13 ` [PATCH v2 5/8] arm: mxc: move IOMUX_CONFIG_XXXX definitions to iomux-v3.h Uwe Kleine-König
2010-12-29 8:52 ` Richard Zhao
2010-12-29 8:14 ` [PATCH v2 1/8] ARM: mx5: use config to define boot related addresses Uwe Kleine-König
2010-12-29 8:42 ` Richard Zhao
2010-12-29 9:25 ` Uwe Kleine-König [this message]
2010-12-29 9:33 ` Richard Zhao
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=20101229092526.GQ14221@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--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).