From: Florian Fainelli <florian.fainelli@broadcom.com>
To: linux-arm-kernel@lists.infradead.org
Cc: "Hauke Mehrtens" <hauke@hauke-m.de>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] ARM: dts: BCM5301X: Fix PCIe controller warnings
Date: Fri, 31 May 2024 14:33:16 -0700 [thread overview]
Message-ID: <a6bb8da7-569f-45ea-88ff-06f96ab5e2a4@broadcom.com> (raw)
In-Reply-To: <20240430230714.3923578-1-florian.fainelli@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]
On 4/30/24 16:07, Florian Fainelli wrote:
> Hi Rafal,
>
> Here is a counter proposal to your patch series:
>
> https://lore.kernel.org/all/20240423110238.32148-1-zajec5@gmail.com/
>
> which is a little bit smaller in terms of lines changed. Note that with
> either my patches or yours, we still have the following warnings show
> up:
>
> arch/arm/boot/dts/broadcom/bcm4709-netgear-r8000.dts:133.15-145.4:
> Warning (pci_device_reg): /axi@18000000/pcie@18012000/bridge@0,0,0: PCI
> unit address format error, expected "0,0"
> arch/arm/boot/dts/broadcom/bcm4709-netgear-r8000.dts:152.15-191.4:
> Warning (pci_device_reg): /axi@18000000/pcie@18013000/bridge@1,0,0: PCI
> unit address format error, expected "0,0"
Rafal, any chance you could test those patches? Thanks
>
> Thanks!
>
> Florian Fainelli (1):
> ARM: dts: BCM5301X: Relocate PCIe nodes to top-level
>
> Rafał Miłecki (1):
> ARM: dts: BCM5301X: Describe PCIe controllers fully
>
> arch/arm/boot/dts/broadcom/bcm-ns.dtsi | 97 +++++++++++++++-----------
> 1 file changed, 58 insertions(+), 39 deletions(-)
>
--
Florian
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4221 bytes --]
prev parent reply other threads:[~2024-05-31 21:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 23:07 Florian Fainelli
2024-04-30 23:07 ` [PATCH 1/2] ARM: dts: BCM5301X: Relocate PCIe nodes to top-level Florian Fainelli
2024-04-30 23:07 ` [PATCH 2/2] ARM: dts: BCM5301X: Describe PCIe controllers fully Florian Fainelli
2024-05-31 21:33 ` Florian Fainelli [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=a6bb8da7-569f-45ea-88ff-06f96ab5e2a4@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hauke@hauke-m.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®