From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv0 0/2] arm: mvebu: non-critical fixes for NETGEAR ReadyNAS 102
Date: Thu, 30 Oct 2014 13:41:01 +0100 [thread overview]
Message-ID: <545231DD.7090500@free-electrons.com> (raw)
In-Reply-To: <cover.1414185031.git.arno@natisbad.org>
Hi Arnaud,
On 24/10/2014 23:21, Arnaud Ebalard wrote:
> Hi,
>
> This two patches are non-critical and respectively fix the following
> in RN102 .dts file:
> - the color for LEDs labels (they are blue, and not green)
> - eSATA/SATA ports info
>
> Arnaud Ebalard (2):
> arm: mvebu: fix LED color in NETGEAR ReadyNAS 102 .dts file
> arm: mvebu: clarify (e)SATA ports info in NETGEAR ReadyNAS 102 .dts file
>
> arch/arm/boot/dts/armada-370-netgear-rn102.dts | 17 +++++++++--------
> 1 file changed, 9 insertions(+), 8 deletions(-)
>
For both patches:
Acked-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
Thanks,
Gregory
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2014-10-30 12:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 21:21 [PATCHv0 0/2] arm: mvebu: non-critical fixes for NETGEAR ReadyNAS 102 Arnaud Ebalard
2014-10-24 21:22 ` [PATCHv0 1/2] arm: mvebu: fix LED color in NETGEAR ReadyNAS 102 .dts file Arnaud Ebalard
2014-10-24 21:20 ` Andrew Lunn
2014-10-24 21:22 ` [PATCHv0 2/2] arm: mvebu: clarify (e)SATA ports info " Arnaud Ebalard
2014-10-24 21:22 ` Andrew Lunn
2014-10-24 21:41 ` Arnaud Ebalard
2014-10-30 12:41 ` Gregory CLEMENT [this message]
2014-11-01 22:52 ` [PATCHv0 0/2] arm: mvebu: non-critical fixes for NETGEAR ReadyNAS 102 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=545231DD.7090500@free-electrons.com \
--to=gregory.clement@free-electrons.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).