From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: platform/x86/intel/vsec: Decouple add/link helpers from PCI
Date: Fri, 27 Feb 2026 14:12:36 +1000 [thread overview]
Message-ID: <review-patch3-20260224-upstream-pmt-acpi-v5-v5-3-8dd73bcf049c@linux.intel.com> (raw)
In-Reply-To: <20260224-upstream-pmt-acpi-v5-v5-3-8dd73bcf049c@linux.intel.com>
Patch Review
**Overall: Good refactor, clean separation.**
This removes the `struct pci_dev *pdev` parameter from `intel_vsec_add_aux()` and `intel_vsec_link_devices()`, replacing them with `struct device *parent`. The key safety addition is:
```c
if (!dev_is_pci(parent))
return 0;
```
in `intel_vsec_link_devices()`, which correctly short-circuits the dependency-tracking logic (which relies on PCI ID matching) for non-PCI devices. The dependency/linking machinery is only relevant to the VSEC PCI driver's own probe path, so returning 0 for non-PCI parents is correct.
The `vsec_tpmi.c` caller update from `vsec_dev->pcidev` to `&vsec_dev->pcidev->dev` is correct given that at this point in the series, `pcidev` still exists.
No issues found.
---
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-02-27 4:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 1:50 [PATCH v5 0/6] platform/x86/intel/vsec: Prep for ACPI PMT discovery David E. Box
2026-02-25 1:50 ` [PATCH v5 1/6] platform/x86/intel/vsec: Refactor base_addr handling David E. Box
2026-02-27 4:12 ` Claude review: " Claude Code Review Bot
2026-02-25 1:50 ` [PATCH v5 2/6] platform/x86/intel/vsec: Make driver_data info const David E. Box
2026-02-27 4:12 ` Claude review: " Claude Code Review Bot
2026-02-25 1:50 ` [PATCH v5 3/6] platform/x86/intel/vsec: Decouple add/link helpers from PCI David E. Box
2026-02-27 4:12 ` Claude Code Review Bot [this message]
2026-02-25 1:50 ` [PATCH v5 4/6] platform/x86/intel/vsec: Switch exported helpers from pci_dev to device David E. Box
2026-02-27 4:12 ` Claude review: " Claude Code Review Bot
2026-02-25 1:50 ` [PATCH v5 5/6] platform/x86/intel/vsec: Return real error codes from registration path David E. Box
2026-02-27 4:12 ` Claude review: " Claude Code Review Bot
2026-02-25 1:50 ` [PATCH v5 6/6] platform/x86/intel/vsec: Plumb ACPI PMT discovery tables through vsec David E. Box
2026-02-27 4:12 ` Claude review: " Claude Code Review Bot
2026-02-27 4:12 ` Claude review: platform/x86/intel/vsec: Prep for ACPI PMT discovery Claude Code Review 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=review-patch3-20260224-upstream-pmt-acpi-v5-v5-3-8dd73bcf049c@linux.intel.com \
--to=claude-review@example.com \
--cc=dri-devel-reviews@example.com \
/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