From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-pci@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"open list:MIPS" <linux-mips@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>,
"Jim Quinlan" <jim2101024@gmail.com>
Subject: Re: [PATCH 0/2] Enable PCIE_BRCMSTB on MIPS
Date: Wed, 10 Nov 2021 09:51:29 +0100 [thread overview]
Message-ID: <20211110085129.GB5976@alpha.franken.de> (raw)
In-Reply-To: <20211108192432.1589507-1-f.fainelli@gmail.com>
On Mon, Nov 08, 2021 at 11:24:30AM -0800, Florian Fainelli wrote:
> This patch series allows building the PCIE_BRCMSTB driver for
> BMIPS_GENERIC. This is preliminary work to actually adding support for
> PCIe host bridge changes to the 7425/29/35 MIPS-based SoCs.
>
> The two patches are largely independent, though it might make more sense
> to merge them via the PCI drivers tree?
>
> Florian Fainelli (2):
> MIPS: BMIPS: Enable PCI Kconfig
> PCI: brcmstb: Allow building for BMIPS_GENERIC
>
> arch/mips/Kconfig | 2 ++
> drivers/pci/controller/Kconfig | 3 ++-
> 2 files changed, 4 insertions(+), 1 deletion(-)
series applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2021-11-10 8:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 19:24 [PATCH 0/2] Enable PCIE_BRCMSTB on MIPS Florian Fainelli
2021-11-08 19:24 ` [PATCH 1/2] MIPS: BMIPS: Enable PCI Kconfig Florian Fainelli
2021-11-08 19:24 ` [PATCH 2/2] PCI: brcmstb: Allow building for BMIPS_GENERIC Florian Fainelli
2021-11-10 8:51 ` Thomas Bogendoerfer [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=20211110085129.GB5976@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=f.fainelli@gmail.com \
--cc=jim2101024@gmail.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--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).