public inbox for drm-ai-reviews@public-inbox.freedesktop.org
 help / color / mirror / Atom feed
From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: zorro: Improve handling of pointers in zorro_device_id::driver_data
Date: Wed, 27 May 2026 14:47:32 +1000	[thread overview]
Message-ID: <review-overall-cover.1779803053.git.u.kleine-koenig@baylibre.com> (raw)
In-Reply-To: <cover.1779803053.git.u.kleine-koenig@baylibre.com>

Overall Series Review

Subject: zorro: Improve handling of pointers in zorro_device_id::driver_data
Author: =?UTF-8?q?Uwe=20Kleine-K=C3=B6nig=20=28The=20Capable=20Hub=29?=
 <u.kleine-koenig@baylibre.com>
Patches: 6
Reviewed: 2026-05-27T14:47:32.957704

---

This is a well-structured cleanup series by Uwe Kleine-König targeting the `zorro_device_id` struct to improve type safety when storing pointers in `driver_data`. The mbox contains only 3 of 8 patches (5, 6, 8) — those relevant to the video/fbdev and the core header change. The remaining patches (1-4, 7) touch ata, scsi, net, and i2c subsystems and were filtered out.

The core idea (patch 6) is sound: replacing `kernel_ulong_t driver_data` with an anonymous union containing both `driver_data` and `const void *driver_data_ptr` eliminates unsafe `(unsigned long)` pointer casts. This is a standard pattern already used in other device ID structs in the kernel (e.g., `platform_device_id`). The motivation — CHERI compatibility — is legitimate, and the cleanup stands on its own merits regardless.

The patches are clean, mechanical, and correct. The anonymous union approach preserves backward compatibility with all existing users. No functional changes are introduced.

**Recommendation:** The series looks good. No correctness issues found.

---
Generated by Claude Code Patch Reviewer

      parent reply	other threads:[~2026-05-27  4:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-26 14:17 [PATCH v1 0/8] zorro: Improve handling of pointers in zorro_device_id::driver_data Uwe Kleine-König (The Capable Hub)
2026-05-26 14:17 ` [PATCH v1 5/8] video: fm2fb: Use named initializer for zorro_device_id array Uwe Kleine-König (The Capable Hub)
2026-05-27  4:47   ` Claude review: " Claude Code Review Bot
2026-05-26 14:17 ` [PATCH v1 6/8] zorro: Simplify storing pointers in device id struct Uwe Kleine-König (The Capable Hub)
2026-05-27  4:47   ` Claude review: " Claude Code Review Bot
2026-05-26 14:17 ` [PATCH v1 8/8] video: cirrusfb: Make use of struct zorro_device_id::driver_data_ptr Uwe Kleine-König (The Capable Hub)
2026-05-27  4:47   ` Claude review: " Claude Code Review Bot
2026-05-26 15:01 ` [PATCH v1 0/8] zorro: Improve handling of pointers in zorro_device_id::driver_data Geert Uytterhoeven
2026-05-26 16:38   ` Uwe Kleine-König (The Capable Hub)
2026-05-27  4:47 ` 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-cover.1779803053.git.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