From: arno@natisbad.org (Arnaud Ebalard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv0 2/2] arm: mvebu: clarify (e)SATA ports info in NETGEAR ReadyNAS 102 .dts file
Date: Fri, 24 Oct 2014 23:41:29 +0200 [thread overview]
Message-ID: <87wq7pi1rq.fsf@natisbad.org> (raw)
In-Reply-To: <20141024212207.GC6436@lunn.ch> (Andrew Lunn's message of "Fri, 24 Oct 2014 23:22:07 +0200")
Andrew Lunn <andrew@lunn.ch> writes:
> On Fri, Oct 24, 2014 at 11:22:16PM +0200, Arnaud Ebalard wrote:
>>
>> On NETGEAR ReadyNAS 102, the two disks are connected to the external
>> Marvell 88SE9170 SATA Controller connected to the PCIe bus. The rear
>> eSATA port is connected to the native Armada 370 SATA controller.
>>
>> This patch updates the comments in .dts file wrt SATA interfaces and
>> reduces the number of ports for native Armada 370 interface from 1
>> to 2.
>
> Typ0.
>
> Jason, can you swap the 1 and 2 around when you commit?
> Save having a v2.
>
> Otherwise
>
> Acked-by: Andrew Lunn <andrew@lunn.ch>
Good catch. Thanks, Andrew.
Cheers,
a+
next prev parent reply other threads:[~2014-10-24 21: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 [this message]
2014-10-30 12:41 ` [PATCHv0 0/2] arm: mvebu: non-critical fixes for NETGEAR ReadyNAS 102 Gregory CLEMENT
2014-11-01 22:52 ` 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=87wq7pi1rq.fsf@natisbad.org \
--to=arno@natisbad.org \
--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).