From: tj@kernel.org (Tejun Heo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 2/5] ata: ahci_mvebu: new driver for Marvell Armada 380 AHCI interfaces
Date: Fri, 2 May 2014 11:22:37 -0400 [thread overview]
Message-ID: <20140502152237.GE10204@htj.dyndns.org> (raw)
In-Reply-To: <1397574006-5868-3-git-send-email-thomas.petazzoni@free-electrons.com>
On Tue, Apr 15, 2014 at 05:00:03PM +0200, Thomas Petazzoni wrote:
> The Marvell Armada 380 SoC includes two AHCI compatible
> interfaces. However, like all DMA-capable Marvell interface, they
> require special handling to configure MBus windows. Therefore, this
> commit adds a new ahci_mvebu driver, which relies on the
> libahci_platform.c code recently introduced.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
How should this be routed? Can I pick up just this one and apply it
to libata/for-3.16?
Thanks.
--
tejun
next prev parent reply other threads:[~2014-05-02 15:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-15 15:00 [PATCHv3 0/5] Support for Marvell AHCI interface on Armada 38x Thomas Petazzoni
2014-04-15 15:00 ` [PATCHv3 1/5] Documentation: dt-bindings: reformat and order list of ahci-platform compatibles Thomas Petazzoni
2014-04-26 0:23 ` Jason Cooper
2014-05-04 19:28 ` Tejun Heo
2014-04-15 15:00 ` [PATCHv3 2/5] ata: ahci_mvebu: new driver for Marvell Armada 380 AHCI interfaces Thomas Petazzoni
2014-04-26 0:23 ` Jason Cooper
2014-05-02 15:22 ` Tejun Heo [this message]
2014-05-02 15:33 ` Thomas Petazzoni
2014-05-04 19:29 ` Tejun Heo
2014-04-15 15:00 ` [PATCHv3 3/5] ARM: mvebu: add Device Tree description of AHCI interfaces on Armada 38x Thomas Petazzoni
2014-04-26 0:27 ` Jason Cooper
2014-04-15 15:00 ` [PATCHv3 4/5] ARM: configs: add ahci_mvebu to mvebu_v7_defconfig Thomas Petazzoni
2014-04-26 0:28 ` Jason Cooper
2014-04-15 15:00 ` [PATCHv3 5/5] ARM: configs: add ahci_mvebu to multi_v7_defconfig Thomas Petazzoni
2014-04-26 0:25 ` Jason Cooper
2014-05-05 21:51 ` Olof Johansson
2014-05-05 21:56 ` Thomas Petazzoni
2014-05-06 13:32 ` 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=20140502152237.GE10204@htj.dyndns.org \
--to=tj@kernel.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).