From: Sudeep Holla <sudeep.holla@arm.com>
To: Liviu Dudau <liviu.dudau@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Sudeep Holla <sudeep.holla@arm.com>,
"Aneesh Kumar K.V (Arm)" <aneesh.kumar@kernel.org>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Subject: Re: [PATCH] arm64: dts: fvp: Update bus-range property
Date: Thu, 5 Dec 2024 14:27:24 +0000 [thread overview]
Message-ID: <Z1G4TCY9ekezAc8Y@bogus> (raw)
In-Reply-To: <Z1GxQHY1XkQcPFc0@e110455-lin.cambridge.arm.com>
On Thu, Dec 05, 2024 at 01:57:20PM +0000, Liviu Dudau wrote:
> On Thu, Dec 05, 2024 at 10:31:03AM +0000, Sudeep Holla wrote:
> > On Thu, 28 Nov 2024 20:55:43 +0530, Aneesh Kumar K.V (Arm) wrote:
> > > These days, the Fixed Virtual Platforms(FVP) Base RevC model supports
> > > more PCI devices. Update the max bus number so that Linux can enumerate
> > > them correctly. Without this, the kernel throws the below error while
> > > booting with the default hierarchy
> > >
> > > pci_bus 0000:01: busn_res: [bus 01] end is updated to 01
> > > pci_bus 0000:02: busn_res: can not insert [bus 02-01] under [bus 00-01] (conflicts with (null) [bus 00-01])
> > > pci_bus 0000:02: busn_res: [bus 02-01] end is updated to 02
> > > pci_bus 0000:02: busn_res: can not insert [bus 02] under [bus 00-01] (conflicts with (null) [bus 00-01])
> > > pci_bus 0000:03: busn_res: can not insert [bus 03-01] under [bus 00-01] (conflicts with (null) [bus 00-01])
> > > pci_bus 0000:03: busn_res: [bus 03-01] end is updated to 03
> > > pci_bus 0000:03: busn_res: can not insert [bus 03] under [bus 00-01] (conflicts with (null) [bus 00-01])
> > > pci_bus 0000:04: busn_res: can not insert [bus 04-01] under [bus 00-01] (conflicts with (null) [bus 00-01])
> > > pci_bus 0000:04: busn_res: [bus 04-01] end is updated to 04
> > > pci_bus 0000:04: busn_res: can not insert [bus 04] under [bus 00-01] (conflicts with (null) [bus 00-01])
> > > pci 0000:00:01.0: BAR 14: assigned [mem 0x50000000-0x500fffff]
> > >
> > > [...]
> >
> > Applied to sudeep.holla/linux (for-next/juno/fixes), thanks!
> >
> > [1/1] arm64: dts: fvp: Update bus-range property
> > https://git.kernel.org/sudeep.holla/c/4f776d81bf92
>
> Thanks for the quick response. TBH, I did not receive your initial review
> email, that's why I've messaged thinking it got lost.
No I hadn't responded on the list yet. I queue and wait for a day for the
kbuild bot or any other bots to report no failures before I officially respond
as applied as I wouldn't have tried all build configs in general but it
doesn't apply for DT files though 😉.
--
Regards,
Sudeep
prev parent reply other threads:[~2024-12-05 14:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 15:25 [PATCH] arm64: dts: fvp: Update bus-range property Aneesh Kumar K.V (Arm)
[not found] ` <Z1CwGaAh714XfILz@e110455-lin.cambridge.arm.com>
2024-12-05 9:59 ` Sudeep Holla
2024-12-05 10:31 ` Sudeep Holla
[not found] ` <Z1GxQHY1XkQcPFc0@e110455-lin.cambridge.arm.com>
2024-12-05 14:27 ` Sudeep Holla [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=Z1G4TCY9ekezAc8Y@bogus \
--to=sudeep.holla@arm.com \
--cc=aneesh.kumar@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=lpieralisi@kernel.org \
--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).