From: Lorenzo Pieralisi <lpieralisi@kernel.org>
To: bcm-kernel-feedback-list@broadcom.com, linux-pci@vger.kernel.org,
Nicolas Saenz Julienne <nsaenz@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Cyril Brulebois <kibi@debian.org>,
Jim Quinlan <jim2101024@gmail.com>,
james.quinlan@broadcom.com
Cc: "open list" <linux-kernel@vger.kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"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>
Subject: Re: [PATCH v2 0/5] PCI: brcmstb: Add Multi-MSI and some improvements
Date: Fri, 11 Nov 2022 11:43:19 +0100 [thread overview]
Message-ID: <166816337015.202749.4605725952437837970.b4-ty@kernel.org> (raw)
In-Reply-To: <20221011184211.18128-1-jim2101024@gmail.com>
On Tue, 11 Oct 2022 14:42:05 -0400, Jim Quinlan wrote:
> v2 -- Commit "PCI: brcmstb: Set RCB_{MPS,64B}_MODE bits"
> - s/read compeletion boudnary/Read Completion Boundary/ (Bjorn)
>
> v1 -- original
>
> Jim Quinlan (5):
> PCI: brcmstb: Enable Multi-MSI
> PCI: brcmstb: Wait for 100ms following PERST# deassert
> PCI: brcmstb: Replace status loops with read_poll_timeout_atomic()
> PCI: brcmstb: Functions needlessly specified as "inline"
> PCI: brcmstb: Set RCB_{MPS,64B}_MODE bits
>
> [...]
Applied to pci/brcmstb, thanks!
[1/5] PCI: brcmstb: Enable Multi-MSI
https://git.kernel.org/lpieralisi/pci/c/198acab1772f
[2/5] PCI: brcmstb: Wait for 100ms following PERST# deassert
https://git.kernel.org/lpieralisi/pci/c/3ae140ad827b
[3/5] PCI: brcmstb: Replace status loops with read_poll_timeout_atomic()
https://git.kernel.org/lpieralisi/pci/c/ca5dcc76314d
[4/5] PCI: brcmstb: Functions needlessly specified as "inline"
https://git.kernel.org/lpieralisi/pci/c/137b57413f56
[5/5] PCI: brcmstb: Set RCB_{MPS,64B}_MODE bits
https://git.kernel.org/lpieralisi/pci/c/602fb860945f
Thanks,
Lorenzo
prev parent reply other threads:[~2022-11-11 10:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 18:42 [PATCH v2 0/5] PCI: brcmstb: Add Multi-MSI and some improvements Jim Quinlan
2022-10-11 18:42 ` [PATCH v2 1/5] PCI: brcmstb: Enable Multi-MSI Jim Quinlan
2022-10-11 18:42 ` [PATCH v2 2/5] PCI: brcmstb: Wait for 100ms following PERST# deassert Jim Quinlan
2022-10-11 18:42 ` [PATCH v2 3/5] PCI: brcmstb: Replace status loops with read_poll_timeout_atomic() Jim Quinlan
2022-10-11 18:42 ` [PATCH v2 4/5] PCI: brcmstb: Functions needlessly specified as "inline" Jim Quinlan
2022-10-13 14:11 ` Bjorn Helgaas
2022-10-11 18:42 ` [PATCH v2 5/5] PCI: brcmstb: Set RCB_{MPS,64B}_MODE bits Jim Quinlan
2022-10-13 14:12 ` Bjorn Helgaas
2022-10-14 19:16 ` Jim Quinlan
2022-10-14 19:27 ` Bjorn Helgaas
2022-11-03 18:48 ` Florian Fainelli
2022-11-03 19:43 ` Jim Quinlan
2022-11-11 10:26 ` Lorenzo Pieralisi
2022-11-11 10:43 ` Lorenzo Pieralisi [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=166816337015.202749.4605725952437837970.b4-ty@kernel.org \
--to=lpieralisi@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=james.quinlan@broadcom.com \
--cc=jim2101024@gmail.com \
--cc=kibi@debian.org \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=nsaenz@kernel.org \
--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).