From: sshtylyov@mvista.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [patch 1/1] iMX: Fix build for iMX53
Date: Fri, 05 Aug 2011 15:04:49 +0400 [thread overview]
Message-ID: <4E3BCE51.9010405@ru.mvista.com> (raw)
In-Reply-To: <20110805073253.599604130@rtp-net.org>
Hello.
On 05-08-2011 11:32, Arnaud Patard (Rtp) wrote:
> Commit fad107086d5a869c1c07e5bb35b7b57a10ecf578 fixed the wrong test for MX51
Please specify that commit's summary in parens.
> as the MX51 addresses are wrong for MX50 and MX53 but now it's MX51 only,
> UART_PADDR is not defined anymore when building for MX50/MX53.
> Signed-off-by: Arnaud Patard <arnaud.patard@rtp-net.org>
> Tested-by: Steev Klimaszewski <steev@genesi-usa.com>
WBR, Sergei
prev parent reply other threads:[~2011-08-05 11:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110805073240.162681115@rtp-net.org>
2011-08-05 7:32 ` [patch 1/1] iMX: Fix build for iMX53 Arnaud Patard (Rtp)
2011-08-05 7:54 ` Uwe Kleine-König
2011-08-05 11:04 ` Sergei Shtylyov [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=4E3BCE51.9010405@ru.mvista.com \
--to=sshtylyov@mvista.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).