public inbox for soc@kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-soc@kernel.org
To: Arnd Bergmann <arnd@kernel.org>
Cc: soc@kernel.org
Subject: Re: [PATCH] [v2] ARM: dts: bcm4709: fix bus range assignment
Date: Mon, 20 Apr 2026 15:59:30 +0000	[thread overview]
Message-ID: <177670077004.1706382.3512415590482165274.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260414064754.3129667-1-arnd@kernel.org>

Hello:

This patch was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:

On Tue, 14 Apr 2026 08:47:46 +0200 you wrote:
> From: Arnd Bergmann <arnd@arndb.de>
> 
> The netgear r8000 dts file limits the bus range for the first host
> bridge to exclude bus 0, but the two devices on the first bus are
> explicitly assigned to bus 0, causing a build time warning:
> 
> /home/arnd/arm-soc/arch/arm/boot/dts/broadcom/bcm4709-netgear-r8000.dts:142.3-27: Warning (pci_device_bus_num): /axi@18000000/pcie@13000/pcie@0/pcie@0,0/pcie@1,0:bus-range: PCI bus number 0 out of range, expected (1 - 255)
> /home/arnd/arm-soc/arch/arm/boot/dts/broadcom/bcm4709-netgear-r8000.dts:142.3-27: Warning (pci_device_bus_num): /axi@18000000/pcie@13000/pcie@0/pcie@0,0/pcie@2,0:bus-range: PCI bus number 0 out of range, expected (1 - 255)
> 
> [...]

Here is the summary with links:
  - [v2] ARM: dts: bcm4709: fix bus range assignment
    https://git.kernel.org/soc/soc/c/b1bf0efcd9a5

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2026-04-20 16:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-14  6:47 [PATCH] [v2] ARM: dts: bcm4709: fix bus range assignment Arnd Bergmann
2026-04-20 15:59 ` patchwork-bot+linux-soc [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=177670077004.1706382.3512415590482165274.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-soc@kernel.org \
    --cc=arnd@kernel.org \
    --cc=soc@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