From: Jens Axboe <axboe@kernel.dk>
To: Florian Fainelli <f.fainelli@gmail.com>, linux-kernel@vger.kernel.org
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Hans de Goede <hdegoede@redhat.com>,
Philipp Zabel <p.zabel@pengutronix.de>, Tejun Heo <tj@kernel.org>,
Jaedon Shin <jaedon.shin@gmail.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>,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [PATCH v4 0/2] ata: ahci_brcm: Follow-up changes for BCM7216
Date: Fri, 17 Jan 2020 17:14:44 -0700 [thread overview]
Message-ID: <d171e5fa-7fcd-2176-12d4-5c2286bee46e@kernel.dk> (raw)
In-Reply-To: <20200117235313.14202-1-f.fainelli@gmail.com>
On 1/17/20 4:53 PM, Florian Fainelli wrote:
> Hi Jens,
>
> These three patches are a follow-up to my previous series titled: ata:
> ahci_brcm: Fixes and new device support.
>
> After submitting the BCM7216 RESCAL reset driver, Philipp the reset
> controller maintained indicated that the reset line should be self
> de-asserting and so reset_control_reset() should be used instead.
>
> These three patches update the driver in that regard. It would be great if
> you could apply those and get them queued up for 5.6 since they are
> directly related to the previous series.
Thanks, applied.
--
Jens Axboe
prev parent reply other threads:[~2020-01-18 0:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 23:53 [PATCH v4 0/2] ata: ahci_brcm: Follow-up changes for BCM7216 Florian Fainelli
2020-01-17 23:53 ` [PATCH v4 1/2] ata: ahci_brcm: Perform reset after obtaining resources Florian Fainelli
2020-01-17 23:53 ` [PATCH v4 2/2] ata: ahci_brcm: BCM7216 reset is self de-asserting Florian Fainelli
2020-01-18 0:14 ` Jens Axboe [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=d171e5fa-7fcd-2176-12d4-5c2286bee46e@kernel.dk \
--to=axboe@kernel.dk \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hdegoede@redhat.com \
--cc=jaedon.shin@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=tj@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).