From: ipaton0@gmail.com (Iain Paton)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] ARM: sun7i: add support for A20-OLinuXino-Lime2
Date: Fri, 10 Oct 2014 14:15:48 +0100 [thread overview]
Message-ID: <5437DC04.6070000@gmail.com> (raw)
In-Reply-To: <20141009195630.GJ19438@lukather>
On 09/10/14 20:56, Maxime Ripard wrote:
> Hi Iain,
>
> On Thu, Oct 09, 2014 at 11:27:50AM +0100, Iain Paton wrote:
>> This adds support for the Olimex A20-OLinuXino-Lime2
>> https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXIno-LIME2
>>
>> Differences to previous Lime boards are 1GB RAM and gigabit ethernet
>>
>> Signed-off-by: Iain Paton <ipaton0@gmail.com>
>
> Sorry for noticing this so late, but we sort the DT nodes by their
> base address. Could you respin this for another version?
Sure, no problem, on it's way shortly.
Is there any general rule for this sort of thing, or is this something
specific to sunxi?
Asking mainly as I've been asked to do them alphabetically previously
by a different maintainer and that's esentially why I did it the same
way here.
Everyone having different undocumented conventions seems likely to
become counter productive eventually.
Iain
next prev parent reply other threads:[~2014-10-10 13:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-28 13:18 [PATCH] ARM: sun7i: add support for A20-OLinuXino-Lime2 Iain Paton
2014-09-28 16:43 ` Maxime Ripard
2014-09-29 12:56 ` Iain Paton
2014-09-29 13:25 ` Maxime Ripard
2014-09-29 14:32 ` Iain Paton
2014-10-02 12:48 ` Maxime Ripard
2014-10-05 22:40 ` [PATCH v3 ] " Iain Paton
2014-10-06 9:20 ` Maxime Ripard
2014-10-09 10:27 ` [PATCH v4] " Iain Paton
2014-10-09 19:56 ` Maxime Ripard
2014-10-10 13:15 ` [PATCH v5] " Iain Paton
2014-10-10 13:55 ` Maxime Ripard
2014-10-10 13:15 ` Iain Paton [this message]
2014-10-10 13:56 ` [PATCH v4] " Maxime Ripard
2014-10-11 14:00 ` Andreas Färber
2014-10-06 8:56 ` [PATCH] " Javier Martinez Canillas
2014-10-06 9:11 ` Maxime Ripard
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=5437DC04.6070000@gmail.com \
--to=ipaton0@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).