From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "David E. Box" <david.e.box@linux.intel.com>,
Hans de Goede <hansg@kernel.org>, Lukas Wunner <lukas@wunner.de>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org,
Guangshuo Li <lgs201920130244@gmail.com>
Subject: Re: [PATCH] platform/x86/intel/vsec: reset state before re-enumerating
Date: Tue, 15 Sep 2026 16:19:06 +0300 [thread overview]
Message-ID: <178947834638.32141.10693851497877140431.b4-ty@b4> (raw)
In-Reply-To: <20260708032647.712412-1-lgs201920130244@gmail.com>
On Wed, 08 Jul 2026 11:26:47 +0800, Guangshuo Li wrote:
> The change referenced by the Fixes tag split the VSEC enumeration logic
> out of intel_vsec_pci_probe() and made PCIe error recovery call
> intel_vsec_pci_init() directly. This avoids another pcim_enable_device()
> devm action and another devm allocation during slot reset, but it also
> means that error recovery reuses the priv structure allocated by probe.
>
> On the initial probe, priv is zeroed by devm_kzalloc(), so state[],
> suppliers[] and found_caps start from their initial values. During slot
> reset, the existing aux devices are removed before re-enumerating, but
> the reused priv still records the old devices as registered and the old
> capabilities as found.
>
> [...]
Thank you for your contribution, it has been applied to my local
review-ilpo-next branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-next branch only once I've pushed my
local branch there, which might take a while.
FYI [if applicable to your patch], as per Linus' policy change, also
fixes are mostly routed through for-next unless the fix is for a
commit introduced in the most recent cycle or is clearly a regression
fix.
The list of commits applied:
[1/1] platform/x86/intel/vsec: reset state before re-enumerating
commit: 34744f72e1b83b8fc55f7321819c4bc8daab0a69
--
i.
prev parent reply other threads:[~2026-09-15 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 3:26 Guangshuo Li
2026-07-08 9:33 ` Lukas Wunner
2026-07-09 17:57 ` David Box
2026-08-13 20:10 ` Michael Bottini
2026-09-15 13:19 ` Ilpo Järvinen [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=178947834638.32141.10693851497877140431.b4-ty@b4 \
--to=ilpo.jarvinen@linux.intel.com \
--cc=david.e.box@linux.intel.com \
--cc=hansg@kernel.org \
--cc=lgs201920130244@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=platform-driver-x86@vger.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
all inboxes | Powered by JetHome®