Linux PCI subsystem development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Mario Limonciello" <mario.limonciello@amd.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 3/3] drm/radeon: Match VFCT using initial PCI bus number
Date: Tue, 20 Oct 2026 14:12:38 +0000	[thread overview]
Message-ID: <sashiko-outbox-179093@kernel.org> (raw)
In-Reply-To: <20261020-vfct-regression-v2-3-d2394d11450a@amd.com>

> VFCT records the PCI bus number from BIOS POST. The current bus number
> can change after PCI core renumbers the bus, while accepting a mismatch
> based only on device identity can select the wrong VFCT image when
> matching devices are present. Compare against the bus number captured
> from the firmware bus assignment before bridge renumbering.
> 
> Fixes: 4059e2f02c8a ("drm/radeon: Fix VFCT bus number matching with soft filter")
> 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/20261020-vfct-regression-v2-0-d2394d11450a@amd.com?part=3


      reply	other threads:[~2026-10-20 14:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-20 14:04 [PATCH v2 0/3] Fix amdgpu detection of pci=realloc Mario Limonciello
2026-10-20 14:04 ` [PATCH v2 1/3] PCI: Preserve the initial bus number in pci_dev Mario Limonciello
2026-10-20 14:17   ` sashiko-bot
2026-10-20 14:04 ` [PATCH v2 2/3] drm/amdgpu: Match VFCT using initial PCI bus number Mario Limonciello
2026-10-20 14:10   ` sashiko-bot
2026-10-20 14:04 ` [PATCH v2 3/3] drm/radeon: " Mario Limonciello
2026-10-20 14:12   ` sashiko-bot [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=sashiko-outbox-179093@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