From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: fbdev: Consistently define pci_device_ids using named initializers
Date: Tue, 05 May 2026 10:30:11 +1000 [thread overview]
Message-ID: <review-overall-20260430111637.211336-2-u.kleine-koenig@baylibre.com> (raw)
In-Reply-To: <20260430111637.211336-2-u.kleine-koenig@baylibre.com>
Overall Series Review
Subject: fbdev: 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: 2
Reviewed: 2026-05-05T10:30:11.568532
---
This is a single, well-motivated mechanical cleanup patch across 21 fbdev drivers. It converts positional `struct pci_device_id` initializers to named initializers using `PCI_DEVICE()` / `PCI_VDEVICE()` helper macros. The stated motivation — preparing for an anonymous union on `driver_data` — is a legitimate kernel-wide effort, and this patch is a reasonable prerequisite since anonymous unions require designated initializers.
The conversions look correct throughout. The patch consistently replaces verbose `{vendor, device, PCI_ANY_ID, PCI_ANY_ID, 0, 0, driver_data}` patterns with readable macro-based forms, and replaces `{0, 0, 0, 0, 0, 0, 0}` terminators with `{ }`. The claim of no binary change to the compiled `pci_device_id` arrays is credible.
**Verdict: Looks good overall, with a couple of minor observations below.**
---
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-05-05 0:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 11:16 [PATCH] fbdev: Consistently define pci_device_ids using named initializers Uwe Kleine-König (The Capable Hub)
2026-04-30 11:59 ` Helge Deller
2026-05-05 0:30 ` Claude Code Review Bot [this message]
2026-05-05 0:30 ` 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-20260430111637.211336-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