From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: accel/amdxdna: Import AMD_PMF namespace
Date: Tue, 03 Mar 2026 14:05:57 +1000 [thread overview]
Message-ID: <review-overall-20260301005028.367618-1-superm1@kernel.org> (raw)
In-Reply-To: <20260301005028.367618-1-superm1@kernel.org>
Overall Series Review
Subject: accel/amdxdna: Import AMD_PMF namespace
Author: "Mario Limonciello (AMD)" <superm1@kernel.org>
Patches: 2
Reviewed: 2026-03-03T14:05:57.418611
---
This is a single, trivially small patch that adds `MODULE_IMPORT_NS("AMD_PMF")` to the amdxdna accelerator driver. The stated purpose is to allow the driver to call `amd_pmf_get_npu_data()`, which is exported in the `AMD_PMF` namespace from `drivers/platform/x86/amd/pmf/core.c`.
The patch is **correct in form** — adding a `MODULE_IMPORT_NS()` is the right way to consume a symbol exported with `EXPORT_SYMBOL_NS_GPL()`. However, there is a significant concern: **the current amdxdna driver on drm-next has no reference to `amd_pmf_get_npu_data()` or any `amd_pmf` API at all**. This means the namespace import is being added ahead of the code that actually uses it, or depends on another patch (or series) that hasn't landed yet.
This is fine if this patch is intended to be applied on top of another series that adds the actual `amd_pmf_get_npu_data()` call, but the commit message should state this dependency explicitly (e.g., referencing the other series or commit). Without that context, the patch appears to add a namespace import for a symbol that is never used, which would be dead code.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-03-03 4:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-01 0:50 [PATCH] accel/amdxdna: Import AMD_PMF namespace Mario Limonciello (AMD)
2026-03-02 18:00 ` Lizhi Hou
2026-03-03 4:05 ` Claude Code Review Bot [this message]
2026-03-03 4:05 ` Claude review: " 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-overall-20260301005028.367618-1-superm1@kernel.org \
--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