From: Florian Fainelli <f.fainelli@gmail.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
linux-pci@vger.kernel.org, james.quinlan@broadcom.com,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
bcm-kernel-feedback-list@broadcom.com,
Jim Quinlan <jim2101024@gmail.com>,
Bjorn Helgaas <helgaas@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
"moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
"moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE"
<linux-rpi-kernel@lists.infradead.org>,
Jim Quinlan <jquinlan@broadcom.com>,
Hans de Goede <hdegoede@redhat.com>, Jens Axboe <axboe@kernel.dk>,
"open list:LIBATA SUBSYSTEM Serial and Parallel ATA drivers"
<linux-ide@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 0/2] ata: ahci_brcm: Fix use of BCM7216 reset controller
Date: Tue, 6 Apr 2021 09:38:46 -0700 [thread overview]
Message-ID: <be8892ed-cba6-e8c3-6e1d-5a9940af9440@gmail.com> (raw)
In-Reply-To: <161772368880.12349.1551046998078695154.b4-ty@arm.com>
On 4/6/2021 8:42 AM, Lorenzo Pieralisi wrote:
> On Fri, 12 Mar 2021 15:45:53 -0500, Jim Quinlan wrote:
>> v5 -- Improved (I hope) commit description (Bjorn).
>> -- Rnamed error labels (Krzyszt).
>> -- Fixed typos.
>>
>> v4 -- does not rely on a pending commit, unlike v3.
>>
>> v3 -- discard commit from v2; instead rely on the new function
>> reset_control_rearm provided in a recent commit [1] applied
>> to reset/next.
>> -- New commit to correct pcie-brcmstb.c usage of a reset controller
>> to use reset/rearm verses deassert/assert.
>>
>> [...]
>
> Applied to pci/brcmstb, thanks!
>
> [1/2] ata: ahci_brcm: Fix use of BCM7216 reset controller
> https://git.kernel.org/lpieralisi/pci/c/92b9cb55a9
> [2/2] PCI: brcmstb: Use reset/rearm instead of deassert/assert
> https://git.kernel.org/lpieralisi/pci/c/a24fd1d646
Thanks a lot!
--
Florian
next prev parent reply other threads:[~2021-04-06 16:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 20:45 [PATCH v5 0/2] ata: ahci_brcm: Fix use of BCM7216 reset controller Jim Quinlan
2021-03-12 20:45 ` [PATCH v5 1/2] " Jim Quinlan
2021-04-06 15:16 ` Lorenzo Pieralisi
2021-04-06 15:26 ` Jens Axboe
2021-03-12 20:45 ` [PATCH v5 2/2] PCI: brcmstb: Use reset/rearm instead of deassert/assert Jim Quinlan
2021-03-29 16:06 ` Lorenzo Pieralisi
2021-03-29 16:10 ` Lorenzo Pieralisi
2021-03-29 16:50 ` Florian Fainelli
2021-03-29 16:58 ` Lorenzo Pieralisi
2021-03-29 17:01 ` Florian Fainelli
2021-04-06 15:42 ` [PATCH v5 0/2] ata: ahci_brcm: Fix use of BCM7216 reset controller Lorenzo Pieralisi
2021-04-06 16:38 ` Florian Fainelli [this message]
[not found] <CA+-6iNyN4UB3Sb14RJ9Jb2rXn_u-iwHzny1LYXEq3=VddWWxPg@mail.gmail.com>
2021-04-28 20:53 ` Bjorn Helgaas
2021-04-28 21:03 ` Florian Fainelli
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=be8892ed-cba6-e8c3-6e1d-5a9940af9440@gmail.com \
--to=f.fainelli@gmail.com \
--cc=axboe@kernel.dk \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=hdegoede@redhat.com \
--cc=helgaas@kernel.org \
--cc=james.quinlan@broadcom.com \
--cc=jim2101024@gmail.com \
--cc=jquinlan@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=nsaenzjulienne@suse.de \
--cc=robh@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).