From: arno@natisbad•org (Arnaud Ebalard)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH, FIX] ARM: mvebu: add missing DT Mbus ranges and relocate PCIe DT nodes for RN102
Date: Thu, 03 Oct 2013 07:54:43 +0200 [thread overview]
Message-ID: <87vc1eucf0.fsf@natisbad.org> (raw)
In-Reply-To: <CAOesGMjs=_USrFR9EkzksBj=7=1CgyujqvNhDZhpfdgkTt6gJQ@mail.gmail.com> (Olof Johansson's message of "Wed, 2 Oct 2013 20:57:57 -0700")
Hi,
Olof Johansson <olof@lixom•net> writes:
> Hi,
>
> On Mon, Sep 30, 2013 at 3:19 PM, Arnaud Ebalard <arno@natisbad•org> wrote:
>>
>> When 5e12a613 and 0cd3754a were introduced, Netgear ReadyNAS 102 .dts
>> file was queued for inclusion and missed the update to have Mbus (and
>> then BootROM) ranges properties declared. It also missed the relocation
>> of Armada 370/XP PCIe DT nodes introduced by 14fd8ed0 after de1af8d4.
>> This patch fixes that which makes 3.12-rc3 bootable on the NAS.
>
> In the future please don't just quote the SHAs, give the patch subject
> as well. It makes it easier to follow the patch description without
> looking them up (besides, there's a chance that the 8-character SHAs
> will not be unique at some point in the future, which makes the lookup
> harder).
Dully noted. Will do it next time, olof.
Cheers,
a+
prev parent reply other threads:[~2013-10-03 5:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 22:19 [PATCH, FIX] ARM: mvebu: add missing DT Mbus ranges and relocate PCIe DT nodes for RN102 Arnaud Ebalard
2013-10-01 0:50 ` [PATCH,FIX] " Jason Cooper
2013-10-03 3:57 ` [PATCH, FIX] " Olof Johansson
2013-10-03 5:54 ` Arnaud Ebalard [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=87vc1eucf0.fsf@natisbad.org \
--to=arno@natisbad$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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