From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: "Bjorn Helgaas" <bhelgaas@google.com>,
"Gregory Clement" <gregory.clement@bootlin.com>,
"Rob Herring" <robh@kernel.org>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Pali Rohár" <pali@kernel.org>
Cc: "Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
linux-pci@vger.kernel.org, "Marc Zyngier" <maz@kernel.org>,
"Marek Behún" <kabel@kernel.org>,
linux-arm-kernel@lists.infradead.org,
"Tomasz Maciej Nowak" <tmn505@gmail.com>,
"Remi Pommarel" <repk@triplefau.lt>,
linux-kernel@vger.kernel.org, Xogium <contact@xogium.me>
Subject: Re: [PATCH 0/2] PCI: aardvark: Resource fixes
Date: Fri, 20 Aug 2021 13:41:21 +0100 [thread overview]
Message-ID: <162946326563.4746.9940152798050527363.b4-ty@arm.com> (raw)
In-Reply-To: <20210624215546.4015-1-pali@kernel.org>
On Thu, 24 Jun 2021 23:55:44 +0200, Pali Rohár wrote:
> This patch series fixes configuring PCIe resources (IO and MEM) in
> aardvark controller driver. It is required to initialize BARs on systems
> with more cards, e.g. NVMe disks and WiFi AX cards.
>
> Pali Rohár (2):
> PCI: aardvark: Configure PCIe resources from 'ranges' DT property
> arm64: dts: marvell: armada-37xx: Extend PCIe MEM space
>
> [...]
Applied to pci/aardvark, thanks!
[1/1] PCI: aardvark: Configure PCIe resources from 'ranges' DT property
https://git.kernel.org/lpieralisi/pci/c/64f160e19e
Thanks,
Lorenzo
prev parent reply other threads:[~2021-08-20 12:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 21:55 [PATCH 0/2] PCI: aardvark: Resource fixes Pali Rohár
2021-06-24 21:55 ` [PATCH 1/2] PCI: aardvark: Configure PCIe resources from 'ranges' DT property Pali Rohár
2021-06-24 21:55 ` [PATCH 2/2] arm64: dts: marvell: armada-37xx: Extend PCIe MEM space Pali Rohár
2021-07-23 12:52 ` Gregory CLEMENT
2021-07-23 14:12 ` Pali Rohár
2021-07-23 15:52 ` Lorenzo Pieralisi
2021-07-23 16:45 ` Pali Rohár
2021-08-07 11:35 ` Pali Rohár
2021-08-15 20:30 ` Pali Rohár
2021-08-17 16:39 ` Gregory CLEMENT
2021-08-20 12:41 ` 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=162946326563.4746.9940152798050527363.b4-ty@arm.com \
--to=lorenzo.pieralisi@arm.com \
--cc=bhelgaas@google.com \
--cc=contact@xogium.me \
--cc=gregory.clement@bootlin.com \
--cc=kabel@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=maz@kernel.org \
--cc=pali@kernel.org \
--cc=repk@triplefau.lt \
--cc=robh@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=tmn505@gmail.com \
/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).