From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: drm/doc/rfc: Remove i915_scheduler item.
Date: Thu, 23 Apr 2026 10:10:54 +1000 [thread overview]
Message-ID: <review-patch4-20260420083318.92038-10-dev@lankhorst.se> (raw)
In-Reply-To: <20260420083318.92038-10-dev@lankhorst.se>
Patch Review
**Reviewed-by worthy**: Yes.
The commit message notes no updates since `e5e32171a2cf ("drm/i915/guc: Connect UAPI to GuC multi-lrc interface")`. The RFC described the plan for GuC submission and DRM scheduler integration in i915. GuC submission has landed, and the xe driver has taken over for future GPU submission work. The remaining TODO items (DRM scheduler integration for execlists, priority inheritance porting, etc.) are unlikely to ever be completed for i915.
No issues.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-04-23 0:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 8:33 [PATCH 0/4] drm/doc: Remove obsolete RFC docs related to i915 Maarten Lankhorst
2026-04-20 8:33 ` [PATCH 1/4] drm/doc/rfc: Remove i915_gem_lmem.rst Maarten Lankhorst
2026-04-23 0:10 ` Claude review: " Claude Code Review Bot
2026-04-20 8:33 ` [PATCH 2/4] drm/doc/rfc: Remove i915_vm_bind Maarten Lankhorst
2026-04-23 0:10 ` Claude review: " Claude Code Review Bot
2026-04-20 8:33 ` [PATCH 3/4] drm/doc/rfc: Remove i915_small_bar rfc Maarten Lankhorst
2026-04-23 0:10 ` Claude review: " Claude Code Review Bot
2026-04-20 8:33 ` [PATCH 4/4] drm/doc/rfc: Remove i915_scheduler item Maarten Lankhorst
2026-04-23 0:10 ` Claude Code Review Bot [this message]
2026-04-20 18:52 ` [PATCH 0/4] drm/doc: Remove obsolete RFC docs related to i915 Rodrigo Vivi
2026-04-23 0:10 ` 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-patch4-20260420083318.92038-10-dev@lankhorst.se \
--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