From: arno@natisbad•org (Arnaud Ebalard)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCHv2 0/4] ARM: mvebu/kirkwood: NETGEAR ReadyNAS .dts files cleanup
Date: Mon, 02 Dec 2013 00:09:11 +0100 [thread overview]
Message-ID: <87eh5wmanc.fsf@natisbad.org> (raw)
In-Reply-To: <20131201221710.GB2879@titan.lakedaemon.net> (Jason Cooper's message of "Sun, 1 Dec 2013 17:17:10 -0500")
Jason Cooper <jason@lakedaemon•net> writes:
>> Arnaud Ebalard (4):
>> ARM: kirkwood: NETGEAR ReadyNAS Duo v2 .dts cleanup
>> ARM: mvebu: NETGEAR ReadyNAS 102 .dts cleanup
>> ARM: mvebu: NETGEAR ReadyNAS 104 .dts cleanup
>> ARM: Fix whitespaces in NETGEAR ReadyNAS .dts files
>>
>> arch/arm/boot/dts/armada-370-netgear-rn102.dts | 82 ++++++++++--------
>> arch/arm/boot/dts/armada-370-netgear-rn104.dts | 68 +++++++--------
>> .../boot/dts/kirkwood-netgear_readynas_duo_v2.dts | 99 +++++++++++++---------
>> 3 files changed, 141 insertions(+), 108 deletions(-)
>
> whole series applied to mvebu/dt. There was a small conflict with
> Sebastian's pinctrl work. Please double check and let me know if
> anything is amiss.
All three .dts files look as they should in your branch.
next prev parent reply other threads:[~2013-12-01 23:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 20:27 [PATCHv2 0/4] ARM: mvebu/kirkwood: NETGEAR ReadyNAS .dts files cleanup Arnaud Ebalard
2013-11-29 20:27 ` [PATCHv2 1/4] ARM: kirkwood: NETGEAR ReadyNAS Duo v2 .dts cleanup Arnaud Ebalard
2013-11-29 20:27 ` [PATCHv2 2/4] ARM: mvebu: NETGEAR ReadyNAS 102 " Arnaud Ebalard
2013-11-29 20:27 ` [PATCHv2 3/4] ARM: mvebu: NETGEAR ReadyNAS 104 " Arnaud Ebalard
2013-11-29 20:27 ` [PATCHv2 4/4] ARM: Fix whitespaces in NETGEAR ReadyNAS .dts files Arnaud Ebalard
2013-12-01 22:17 ` [PATCHv2 0/4] ARM: mvebu/kirkwood: NETGEAR ReadyNAS .dts files cleanup Jason Cooper
2013-12-01 23:09 ` Arnaud Ebalard [this message]
2013-12-01 23:34 ` Jason Cooper
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=87eh5wmanc.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