From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/amdgpu: use ACK polling for page-write completion
Date: Thu, 04 Jun 2026 14:17:38 +1000 [thread overview]
Message-ID: <review-overall-20260601093226.1255621-1-kunal.devanandzodape@amd.com> (raw)
In-Reply-To: <20260601093226.1255621-1-kunal.devanandzodape@amd.com>
Overall Series Review
Subject: drm/amdgpu: use ACK polling for page-write completion
Author: Kunal Zodape <kunal.devanandzodape@amd.com>
Patches: 6
Reviewed: 2026-06-04T14:17:38.468071
---
This mbox contains two versions (v1 and v2) of the same single patch, replacing a fixed 10 ms `msleep()` after each EEPROM page write with ACK polling. The optimization is well-motivated: EEPROM internal write cycles are typically ~5 ms but the driver was always waiting the worst-case 10 ms. ACK polling is the standard technique described in EEPROM datasheets (AT24CM02 Section 7.4) and was even marked as a TODO in the existing code.
**v1** used an open-coded `ktime` + `do/while` loop. **v2** addressed review feedback (credited to Jani Nikula) by switching to `read_poll_timeout()`, which is the right kernel idiom.
v2 is a clean, correct patch. The approach, error handling, and use of `read_poll_timeout()` are all sound. I have one minor concern about variable reuse worth calling out, but no blocking issues.
---
---
Generated by Claude Code Patch Reviewer
prev parent reply other threads:[~2026-06-04 4:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 9:32 [PATCH] drm/amdgpu: use ACK polling for page-write completion Kunal Zodape
2026-06-01 9:57 ` Jani Nikula
2026-06-04 4:17 ` Claude review: " Claude Code Review Bot
2026-06-01 11:23 ` [PATCH v2] " Kunal Zodape
2026-06-01 13:05 ` Lazar, Lijo
2026-06-02 6:10 ` Devanand Zodape, Kunal
2026-06-02 6:31 ` Lazar, Lijo
2026-06-04 4:17 ` Claude review: " Claude Code Review Bot
2026-06-04 4:17 ` 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-20260601093226.1255621-1-kunal.devanandzodape@amd.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