From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/amdgpu: Consistently define pci_device_ids using named initializers
Date: Tue, 05 May 2026 11:20:07 +1000 [thread overview]
Message-ID: <review-overall-20260429171644.8406-2-u.kleine-koenig@baylibre.com> (raw)
In-Reply-To: <20260429171644.8406-2-u.kleine-koenig@baylibre.com>
Overall Series Review
Subject: drm/amdgpu: Consistently define pci_device_ids using named initializers
Author: =?UTF-8?q?Uwe=20Kleine-K=C3=B6nig=20=28The=20Capable=20Hub=29?=
<u.kleine-koenig@baylibre.com>
Patches: 1
Reviewed: 2026-05-05T11:20:07.151228
---
This is a single-patch cleanup that converts the amdgpu PCI device ID table from raw positional struct initializers to `PCI_DEVICE()` macro + named `.driver_data` initializers. The transformation is mechanical and correct. The `PCI_DEVICE()` macro (defined at `include/linux/pci.h:1052`) expands to exactly the same fields that were previously specified positionally (`.vendor`, `.device`, `.subvendor = PCI_ANY_ID`, `.subdevice = PCI_ANY_ID`), while the old explicit `.class = 0, .class_mask = 0` values are dropped since zero is the default for uninitialized struct members in C. The author states the compiled output was verified identical on x86 and arm64.
The patch is well motivated: it improves readability, makes the table consistent with the entries that already used `PCI_DEVICE()` for the class-match CHIP_IP_DISCOVERY entries at the end of the table, and prepares for a future `driver_data` anonymous union change across the kernel.
**Verdict: Looks good to merge.** No functional concerns.
---
---
Generated by Claude Code Patch Reviewer
prev parent reply other threads:[~2026-05-05 1:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 17:16 [PATCH] drm/amdgpu: Consistently define pci_device_ids using named initializers Uwe Kleine-König (The Capable Hub)
2026-05-05 1:20 ` Claude review: " Claude Code Review Bot
2026-05-05 1:20 ` Claude Code Review 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=review-overall-20260429171644.8406-2-u.kleine-koenig@baylibre.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