From: Florian Fainelli <f.fainelli@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: bcm-kernel-feedback-list@broadcom.com,
Florian Fainelli <f.fainelli@gmail.com>,
Jens Axboe <axboe@kernel.dk>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"open list:LIBATA SUBSYSTEM Serial and Parallel ATA drivers"
<linux-ide@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>
Subject: [PATCH v2 0/4] AHCI support for BCM63138
Date: Mon, 1 Oct 2018 10:32:58 -0700 [thread overview]
Message-ID: <20181001173302.25398-1-f.fainelli@gmail.com> (raw)
Hi Jens,
This is a resend of the previous series posted here:
https://lkml.org/lkml/2018/9/20/1060
With a few minor changes:
- rebased against your for-4.20/libata branch
- added Rob's Reviewed-by to patch
- fixed the use of the reset controller API
Thank you!
Florian Fainelli (4):
dt-bindings: ata: Document BCM63138 compatible string
ata: ahci_brcm: Allow optional reset controller to be used
ata: ahci_brcm: Match BCM63138 compatible strings
ata: ahci_brcm: Allow using driver or DSL SoCs
Documentation/devicetree/bindings/ata/brcm,sata-brcm.txt | 1 +
drivers/ata/Kconfig | 3 ++-
drivers/ata/ahci_brcm.c | 8 ++++++++
3 files changed, 11 insertions(+), 1 deletion(-)
--
2.17.1
next reply other threads:[~2018-10-01 17:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 17:32 Florian Fainelli [this message]
2018-10-01 17:32 ` [PATCH v2 1/4] dt-bindings: ata: Document BCM63138 compatible string Florian Fainelli
2018-10-01 17:33 ` [PATCH v2 2/4] ata: ahci_brcm: Allow optional reset controller to be used Florian Fainelli
2018-10-01 17:33 ` [PATCH v2 3/4] ata: ahci_brcm: Match BCM63138 compatible strings Florian Fainelli
2018-10-01 17:33 ` [PATCH v2 4/4] ata: ahci_brcm: Allow using driver or DSL SoCs Florian Fainelli
2018-10-01 22:39 ` [PATCH v2 0/4] AHCI support for BCM63138 Jens Axboe
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=20181001173302.25398-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=axboe@kernel.dk \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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).