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: Re: [PATCH v3] staging: fbtft: replace empty macro args with identity converter
Date: Mon, 13 Apr 2026 18:50:47 +1000	[thread overview]
Message-ID: <review-overall-CAHp75VcdWMvvM-oKTqRACSXSUiVsEh1Ep_82MsJxfbrG4thUdA@mail.gmail.com> (raw)
In-Reply-To: <CAHp75VcdWMvvM-oKTqRACSXSUiVsEh1Ep_82MsJxfbrG4thUdA@mail.gmail.com>

Overall Series Review

Subject: Re: [PATCH v3] staging: fbtft: replace empty macro args with identity converter
Author: Andy Shevchenko <andy.shevchenko@gmail.com>
Patches: 5
Reviewed: 2026-04-13T18:50:47.485308

---

This mbox contains two patches addressing the same issue in `drivers/staging/fbtft/fbtft-bus.c`: the `define_fbtft_write_reg` macro is invoked with an empty 4th argument for the no-conversion cases. Patch 1 is a broken v1 that removes the argument entirely, while Patch 2 (labeled v3) is the corrected approach that introduces an identity macro. Only Patch 2 should be considered for merging.

The series has formatting/process issues: Patch 1 is a standalone `[PATCH]` (not a cover letter) that contains a full diff of a broken approach, and Patch 2 is `[PATCH v3]` sent as a reply. This is confusing — v3 should have been sent as its own top-level thread, with a note that it supersedes the prior versions.

Patch 2 is functionally correct but its commit message makes an inaccurate claim about undefined behavior.

---
Generated by Claude Code Patch Reviewer

      parent reply	other threads:[~2026-04-13  8:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-12 17:33 [PATCH] staging: fbtft: fix coding style issue in fbtft-bus.c Baker
2026-04-12 17:33 ` [PATCH v3] staging: fbtft: replace empty macro args with identity converter Baker
2026-04-13  5:58   ` Andy Shevchenko
2026-04-13  6:03     ` Greg KH
2026-04-13  6:08       ` Andy Shevchenko
2026-04-13  8:50       ` Claude review: " Claude Code Review Bot
2026-04-13  8:50     ` Claude Code Review Bot
2026-04-13  8:50     ` 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-CAHp75VcdWMvvM-oKTqRACSXSUiVsEh1Ep_82MsJxfbrG4thUdA@mail.gmail.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