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: MAINTAINERS: serdev: Add self for serdev
Date: Thu, 04 Jun 2026 15:07:55 +1000	[thread overview]
Message-ID: <review-patch3-20260531-rust_serdev-v11-3-dee8e0d830f1@posteo.de> (raw)
In-Reply-To: <20260531-rust_serdev-v11-3-dee8e0d830f1@posteo.de>

Patch Review

Straightforward MAINTAINERS change replacing Rob Herring with Markus Probst as the serdev maintainer. Rob indicated he needs someone else to maintain serdev, and the linked lore messages confirm Markus volunteered. No issues.

**Summary:** The series is well-constructed with good attention to safety invariants. The key fixes are: (1) the typo "partiy" → "parity", and (2) the broken rustdoc link `[ Device::wait_until_sent`]`. The probe error-path handling looks correct after the v11 fixes. The mutex-guarded `active` flag is a clean solution for the receive-buf-after-drop race.

---
Generated by Claude Code Patch Reviewer

  reply	other threads:[~2026-06-04  5:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-30 22:51 [PATCH v11 0/3] rust: add basic serial device bus abstractions Markus Probst via B4 Relay
2026-05-30 22:51 ` [PATCH v11 1/3] " Markus Probst via B4 Relay
2026-05-30 23:51   ` Danilo Krummrich
2026-05-31  6:58     ` Onur Özkan
2026-05-31  7:01       ` Onur Özkan
2026-05-31 16:37       ` Markus Probst
2026-05-31 17:57         ` Danilo Krummrich
2026-05-31 19:42     ` Markus Probst
2026-05-31 21:49       ` Danilo Krummrich
2026-05-31 22:00         ` Markus Probst
2026-05-31 22:32           ` Danilo Krummrich
2026-06-01  0:13             ` Markus Probst
2026-06-04  5:07   ` Claude review: " Claude Code Review Bot
2026-05-30 22:51 ` [PATCH v11 2/3] samples: rust: add Rust serial device bus sample device driver Markus Probst via B4 Relay
2026-06-04  5:07   ` Claude review: " Claude Code Review Bot
2026-05-30 22:51 ` [PATCH v11 3/3] MAINTAINERS: serdev: Add self for serdev Markus Probst via B4 Relay
2026-06-04  5:07   ` Claude Code Review Bot [this message]
2026-06-04  5:07 ` Claude review: rust: add basic serial device bus abstractions Claude Code Review Bot
  -- strict thread matches above, loose matches on Subject: below --
2026-06-03 15:56 [PATCH v12 0/3] " Markus Probst via B4 Relay
2026-06-03 15:56 ` [PATCH v12 3/3] MAINTAINERS: serdev: Add self for serdev Markus Probst via B4 Relay
2026-06-04  1:33   ` Claude review: " Claude Code Review Bot
2026-05-30 19:25 [PATCH v10 0/5] rust: add basic serial device bus abstractions Markus Probst
2026-05-30 19:25 ` [PATCH v10 5/5] MAINTAINERS: serdev: Add self for serdev Markus Probst
2026-06-04  5:18   ` Claude review: " Claude Code Review Bot
2026-05-30 17:36 [PATCH v9 0/3] rust: add basic serial device bus abstractions Markus Probst
2026-05-30 17:36 ` [PATCH v9 3/3] MAINTAINERS: serdev: Add self for serdev Markus Probst
2026-06-04  5:28   ` Claude review: " Claude Code Review Bot
2026-05-30  1:13 [PATCH v8 0/5] rust: add basic serial device bus abstractions Markus Probst via B4 Relay
2026-05-30  1:13 ` [PATCH v8 5/5] MAINTAINERS: serdev: Add self for serdev Markus Probst via B4 Relay
2026-06-04  5:57   ` 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-patch3-20260531-rust_serdev-v11-3-dee8e0d830f1@posteo.de \
    --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