From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: calxeda: Correct memory map syntax
Date: Fri, 29 Aug 2014 08:59:30 +0900 [thread overview]
Message-ID: <20140828235930.GF16165@verge.net.au> (raw)
In-Reply-To: <CAL_Jsq+7iCz7rs=msnbJM1Q=Okw3S7GBB1FNabPb5-Gw9C6rcw@mail.gmail.com>
On Wed, Aug 27, 2014 at 07:09:39AM -0500, Rob Herring wrote:
> On Tue, Aug 26, 2014 at 11:18 PM, Simon Horman
> <horms+renesas@verge.net.au> wrote:
> > Correct a syntax error by using two comma-delimited 32 bit values
> > rather than a single 64 bit value.
> >
> > This is a documentation fix and should have no run-time affect.
> >
> > This problem was introduced by 7d6ab9b8620bbca6
> > ("ARM: dts: Add Calxeda ECX-2000 support") in v3.7.
> >
> > Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
>
> Acked-by: Rob Herring <robh@kernel.org>
I would like to withdraw this patch.
The latest information I have is that the syntax used is already correct.
prev parent reply other threads:[~2014-08-28 23:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 4:18 [PATCH] ARM: dts: calxeda: Correct memory map syntax Simon Horman
2014-08-27 12:09 ` Rob Herring
2014-08-28 23:59 ` Simon Horman [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=20140828235930.GF16165@verge.net.au \
--to=horms@verge.net.au \
--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).