From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: gpu: nova-core: require little endian
Date: Sun, 12 Apr 2026 14:47:44 +1000 [thread overview]
Message-ID: <review-overall-20260406-fix-kconfig-v1-1-8f634499f7f0@nvidia.com> (raw)
In-Reply-To: <20260406-fix-kconfig-v1-1-8f634499f7f0@nvidia.com>
Overall Series Review
Subject: gpu: nova-core: require little endian
Author: Eliot Courtney <ecourtney@nvidia.com>
Patches: 9
Reviewed: 2026-04-12T14:47:44.840568
---
This is a single-patch series adding `depends on !CPU_BIG_ENDIAN` to the nova-core Kconfig. The change is **correct in intent and low-risk**. The nova-core driver does assume little-endian byte order in multiple places — both via explicit `from_le_bytes()` calls (in `falcon.rs`, `vbios.rs`) and, more critically, via `FromBytes` / `from_bytes_copy_prefix()` patterns that reinterpret raw byte slices as structs without any endianness conversion (e.g., `PcirStruct`, `BitHeader`, `NpdeStruct`, `PmuLookupTableHeader` in `vbios.rs`). The GSP firmware command queue code also directly interprets byte buffers.
The commit message's claim that "RUST transitively depends on !CPU_BIG_ENDIAN" is practically true today but slightly imprecise — on arm64, `CPU_BIG_ENDIAN` depends on `BROKEN`, so it can't actually be selected, but it's not a hard Kconfig dependency of `RUST` itself. This makes the patch more of a "belt and suspenders" measure, which is fine — it makes the requirement explicit and future-proof in case the arm64 big-endian situation ever changes.
The patch is simple, correct, and harmless. **Recommend accepting.**
---
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-04-12 4:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 6:52 [PATCH] gpu: nova-core: require little endian Eliot Courtney
2026-04-06 16:30 ` Joel Fernandes
2026-04-07 10:56 ` Danilo Krummrich
2026-04-07 18:02 ` Timur Tabi
2026-04-07 18:30 ` Joel Fernandes
2026-04-06 16:34 ` Gary Guo
2026-04-06 19:37 ` John Hubbard
2026-04-06 19:46 ` Danilo Krummrich
2026-04-07 2:15 ` Eliot Courtney
2026-04-12 4:47 ` Claude Code Review Bot [this message]
2026-04-12 4:47 ` 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-20260406-fix-kconfig-v1-1-8f634499f7f0@nvidia.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