From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: "Rob Herring" <robh@kernel.org>, "Rafał Miłecki" <zajec5@gmail.com>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Scott Branden <sbranden@broadcom.com>,
Florian Fainelli <f.fainelli@gmail.com>,
BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Abhishek Shah <abhishek.shah@broadcom.com>,
Srinath Mannam <srinath.mannam@broadcom.com>,
linux-pci@vger.kernel.org,
Jitendra Bhivare <jitendra.bhivare@broadcom.com>,
Roman Bacik <roman.bacik@broadcom.com>,
Bharat Gooty <bharat.gooty@broadcom.com>,
Ray Jui <ray.jui@broadcom.com>
Subject: Re: [PATCH 1/2] PCI: of: Don't fail devm_pci_alloc_host_bridge() on missing 'ranges'
Date: Wed, 4 Aug 2021 12:23:10 +0100 [thread overview]
Message-ID: <162807604073.10493.5773914111068469846.b4-ty@arm.com> (raw)
In-Reply-To: <20210803215656.3803204-1-robh@kernel.org>
On Tue, 3 Aug 2021 15:56:55 -0600, Rob Herring wrote:
> Commit 669cbc708122 ("PCI: Move DT resource setup into
> devm_pci_alloc_host_bridge()") made devm_pci_alloc_host_bridge() fail on
> any DT resource parsing errors, but Broadcom iProc uses
> devm_pci_alloc_host_bridge() on BCMA bus devices that don't have DT
> resources. In particular, there is no 'ranges' property. Fix iProc by
> making 'ranges' optional.
>
> [...]
Applied to pci/iproc, thanks!
[1/2] PCI: of: Don't fail devm_pci_alloc_host_bridge() on missing 'ranges'
https://git.kernel.org/lpieralisi/pci/c/d277f6e88c
[2/2] PCI: iproc: Fix BCMA probe resource handling
https://git.kernel.org/lpieralisi/pci/c/aeaea8969b
Thanks,
Lorenzo
prev parent reply other threads:[~2021-08-04 11:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 21:56 [PATCH 1/2] PCI: of: Don't fail devm_pci_alloc_host_bridge() on missing 'ranges' Rob Herring
2021-08-03 21:56 ` [PATCH 2/2] PCI: iproc: Fix BCMA probe resource handling Rob Herring
2021-08-04 6:49 ` Rafał Miłecki
2021-08-03 23:43 ` [PATCH 1/2] PCI: of: Don't fail devm_pci_alloc_host_bridge() on missing 'ranges' Bjorn Helgaas
2021-08-04 6:47 ` Rafał Miłecki
2021-08-04 11:23 ` 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=162807604073.10493.5773914111068469846.b4-ty@arm.com \
--to=lorenzo.pieralisi@arm.com \
--cc=abhishek.shah@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bharat.gooty@broadcom.com \
--cc=bhelgaas@google.com \
--cc=f.fainelli@gmail.com \
--cc=jitendra.bhivare@broadcom.com \
--cc=linux-pci@vger.kernel.org \
--cc=ray.jui@broadcom.com \
--cc=robh@kernel.org \
--cc=roman.bacik@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=srinath.mannam@broadcom.com \
--cc=zajec5@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.