From: sashiko-bot@kernel.org
To: "Mario Limonciello" <mario.limonciello@amd.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH v4 1/3] PCI: Preserve the initial bus number in pci_bus
Date: Tue, 27 Oct 2026 16:34:07 +0000 [thread overview]
Message-ID: <sashiko-outbox-186927@kernel.org> (raw)
In-Reply-To: <20261027-vfct-regression-v4-1-0e7190e39c2c@amd.com>
> Bridge scans are split into two passes when bus numbers need reassigning.
> Save the firmware secondary bus number on the bridge in pass 0, before it
> is disabled. Use it to initialize number_initial when the child bus is
> created in pass 1, before bus registration callbacks run.
>
> Keep the saved secondary number on the bridge so a later rescan does not
> replace the child's initial number with its reassigned runtime number.
>
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261027-vfct-regression-v4-1-0e7190e39c2c@amd.com?part=1
next prev parent reply other threads:[~2026-10-27 16:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 16:22 [PATCH v4 0/3] Fix amdgpu detection of pci=realloc Mario Limonciello
2026-10-27 16:22 ` [PATCH v4 1/3] PCI: Preserve the initial bus number in pci_bus Mario Limonciello
2026-10-27 16:34 ` sashiko-bot [this message]
2026-10-27 22:41 ` Bjorn Helgaas
2026-10-27 16:22 ` [PATCH v4 2/3] drm/amdgpu: Match VFCT using initial PCI bus number Mario Limonciello
2026-10-27 16:29 ` sashiko-bot
2026-10-27 16:22 ` [PATCH v4 3/3] drm/radeon: " Mario Limonciello
2026-10-27 16:26 ` sashiko-bot
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=sashiko-outbox-186927@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=sashiko-reviews@lists.linux.dev \
/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