From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Jim Quinlan <jim2101024@gmail.com>
Cc: linux-pci@vger.kernel.org, linux-mips@vger.kernel.org,
"Nicolas Saenz Julienne" <nsaenz@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Kevin Cernekee" <cernekee@gmail.com>,
bcm-kernel-feedback-list@broadcom.com,
james.quinlan@broadcom.com,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
"open list" <linux-kernel@vger.kernel.org>,
"moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE"
<linux-rpi-kernel@lists.infradead.org>,
"Rob Herring" <robh@kernel.org>,
"Saenz Julienne" <nsaenzjulienne@suse.de>
Subject: Re: [PATCH v1 0/4] PCI: brcmstb: Augment driver for MIPs SOCs
Date: Wed, 5 Jan 2022 11:42:02 +0100 [thread overview]
Message-ID: <20220105104202.GD7009@alpha.franken.de> (raw)
In-Reply-To: <20211209204726.6676-1-jim2101024@gmail.com>
On Thu, Dec 09, 2021 at 03:47:21PM -0500, Jim Quinlan wrote:
> With this patchset, the Broadcom STB PCIe controller driver
> supports Arm, Arm64, and now MIPs.
>
> Jim Quinlan (4):
> dt-bindings: PCI: Add compatible string for Brcmstb 74[23]5 MIPs SOCs
> MIPS: bmips: Add support PCIe controller device nodes
> MIPS: bmips: Remove obsolete DMA mapping support
> PCI: brcmstb: Augment driver for MIPs SOCs
>
> .../bindings/pci/brcm,stb-pcie.yaml | 2 +
> arch/mips/Kconfig | 1 -
> arch/mips/bmips/dma.c | 106 +-----------------
> arch/mips/boot/dts/brcm/bcm7425.dtsi | 30 +++++
> arch/mips/boot/dts/brcm/bcm7435.dtsi | 30 +++++
> arch/mips/boot/dts/brcm/bcm97425svmb.dts | 9 ++
> arch/mips/boot/dts/brcm/bcm97435svmb.dts | 9 ++
> drivers/pci/controller/Kconfig | 2 +-
> drivers/pci/controller/pcie-brcmstb.c | 82 +++++++++++++-
> 9 files changed, 161 insertions(+), 110 deletions(-)
if nobody objects I'd like to add this series to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2022-01-05 10:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 20:47 [PATCH v1 0/4] PCI: brcmstb: Augment driver for MIPs SOCs Jim Quinlan
2021-12-09 20:47 ` [PATCH v1 1/4] dt-bindings: PCI: Add compatible string for Brcmstb 74[23]5 " Jim Quinlan
2021-12-09 21:29 ` Florian Fainelli
2021-12-15 19:50 ` Rob Herring
2021-12-09 20:47 ` [PATCH v1 2/4] MIPS: bmips: Add support PCIe controller device nodes Jim Quinlan
2021-12-09 21:30 ` Florian Fainelli
2021-12-09 20:47 ` [PATCH v1 3/4] MIPS: bmips: Remove obsolete DMA mapping support Jim Quinlan
2021-12-09 21:31 ` Florian Fainelli
2021-12-13 8:28 ` Christoph Hellwig
2022-02-08 10:34 ` nicolas saenz julienne
2021-12-09 20:47 ` [PATCH v1 4/4] PCI: brcmstb: Augment driver for MIPs SOCs Jim Quinlan
2021-12-09 21:32 ` Florian Fainelli
2022-07-06 21:42 ` Bjorn Helgaas
2022-07-08 13:37 ` Jim Quinlan
2022-01-05 10:42 ` Thomas Bogendoerfer [this message]
2022-01-07 22:36 ` [PATCH v1 0/4] " Jim Quinlan
2022-01-11 15:18 ` Thomas Bogendoerfer
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=20220105104202.GD7009@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=cernekee@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=james.quinlan@broadcom.com \
--cc=jim2101024@gmail.com \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=nsaenz@kernel.org \
--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).