From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: "Tejun Heo" <tj@kernel.org>,
"Antoine Ténart" <antoine.tenart@free-electrons.com>
Cc: kishon@ti.com, alexandre.belloni@free-electrons.com,
thomas.petazzoni@free-electrons.com, zmxu@marvell.com,
jszhang@marvell.com, linux-arm-kernel@lists.infradead.org,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v13 0/8] ARM: berlin: add AHCI support
Date: Wed, 30 Jul 2014 20:23:43 +0200 [thread overview]
Message-ID: <53D9382F.3040206@gmail.com> (raw)
In-Reply-To: <20140730170923.GE23734@htj.dyndns.org>
On 07/30/2014 07:09 PM, Tejun Heo wrote:
> Applied 3-5 to libata/for-3.17. I suppose 6-8 are gonna routed
> through a different tree?
Tejun,
IMHO you should also take 6
("Documentation: bindings: document the sub-nodes AHCI bindings").
Sebastian
prev parent reply other threads:[~2014-07-30 18:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-30 17:04 [PATCH v13 0/8] ARM: berlin: add AHCI support Antoine Ténart
2014-07-30 17:04 ` [PATCH v13 1/8] phy: add a driver for the Berlin SATA PHY Antoine Ténart
2014-07-30 17:04 ` [PATCH v13 2/8] Documentation: bindings: add " Antoine Ténart
2014-07-30 17:04 ` [PATCH v13 3/8] ata: libahci_platform: move port_map parameters into the AHCI structure Antoine Ténart
2014-07-30 17:04 ` [PATCH v13 4/8] ata: libahci: allow to use multiple PHYs Antoine Ténart
2014-07-30 17:04 ` [PATCH v13 5/8] ata: ahci_platform: add a generic AHCI compatible Antoine Ténart
2014-07-30 17:05 ` [PATCH v13 6/8] Documentation: bindings: document the sub-nodes AHCI bindings Antoine Ténart
2014-07-30 17:05 ` [PATCH v13 7/8] ARM: berlin: add the AHCI node for the BG2Q Antoine Ténart
2014-07-30 17:05 ` [PATCH v13 8/8] ARM: berlin: enable the eSATA interface on the BG2Q DMP Antoine Ténart
2014-07-30 17:09 ` [PATCH v13 0/8] ARM: berlin: add AHCI support Tejun Heo
2014-07-30 17:18 ` Tejun Heo
2014-07-30 17:29 ` Antoine Ténart
2014-07-30 18:23 ` Sebastian Hesselbarth [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=53D9382F.3040206@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=antoine.tenart@free-electrons.com \
--cc=jszhang@marvell.com \
--cc=kishon@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.petazzoni@free-electrons.com \
--cc=tj@kernel.org \
--cc=zmxu@marvell.com \
/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).