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: vfs: change inode->i_ino from unsigned long to u64
Date: Fri, 27 Feb 2026 11:50:53 +1000	[thread overview]
Message-ID: <review-overall-20260226-iino-u64-v1-0-ccceff366db9@kernel.org> (raw)
In-Reply-To: <20260226-iino-u64-v1-0-ccceff366db9@kernel.org>

Overall Series Review

Subject: vfs: change inode->i_ino from unsigned long to u64
Author: Jeff Layton <jlayton@kernel.org>
Patches: 3
Reviewed: 2026-02-27T11:50:53.889328

---

This is a 61-patch series from Jeff Layton that changes `inode->i_ino` from `unsigned long` to `u64` across the kernel. The mbox has been filtered to show only the 3 messages relevant to DRM/dma-buf subsystems: the cover letter (patch 0/61), patch 52/61 (drm/amdgpu), and patch 56/61 (dma-buf).

The overall goal is well-motivated: `unsigned long` is 32 bits on 32-bit architectures, forcing filesystems to hash 64-bit identifiers into 32 bits. Changing to `u64` eliminates those hacks and provides a universal 64-bit inode identifier. The two patches touching DRM/dma-buf code are straightforward mechanical format string updates and are clearly correct.

**Recommendation: Acked-by for both drm/amdgpu and dma-buf patches.** These are trivially correct format string changes that follow directly from the type change in patch 2 of the series.

---

---
Generated by Claude Code Patch Reviewer

  parent reply	other threads:[~2026-02-27  1:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-26 15:55 [PATCH 00/61] vfs: change inode->i_ino from unsigned long to u64 Jeff Layton
2026-02-26 15:55 ` [PATCH 52/61] drm/amdgpu: update for u64 i_ino Jeff Layton
2026-02-27  1:50   ` Claude review: " Claude Code Review Bot
2026-02-26 15:55 ` [PATCH 56/61] dma-buf: update format string " Jeff Layton
2026-02-27  1:50   ` Claude review: " Claude Code Review Bot
2026-02-27  1:50 ` Claude Code Review Bot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-03-02 20:23 [PATCH v2 000/110] vfs: change inode->i_ino from unsigned long to u64 Jeff Layton
2026-03-03 22:15 ` 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-20260226-iino-u64-v1-0-ccceff366db9@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