From: Philipp Stanner <phasta@mailbox.org>
To: "Philipp Stanner" <phasta@kernel.org>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Jonathan Corbet" <corbet@lwn.net>,
"Christian König" <christian.koenig@amd.com>,
"Tvrtko Ursulin" <tvrtko.ursulin@igalia.com>,
"Matthew Brost" <matthew.brost@intel.com>
Cc: dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] drm/todo: Add section for GPU Scheduler
Date: Thu, 27 Nov 2025 13:49:53 +0100 [thread overview]
Message-ID: <c35026065b1d109b7f4b9e1d8dee8ea45f9a1dba.camel@mailbox.org> (raw)
In-Reply-To: <20251107135701.244659-2-phasta@kernel.org>
+Cc Matthew, Tvrtko, Christian
On Fri, 2025-11-07 at 14:56 +0100, Philipp Stanner wrote:
> Changes in v2:
> - Fix wrong list item index in patch 1.
>
> The GPU Scheduler has enough problems to be covered by the drm todo
> list. Let's add an entry.
>
> This series is the succesor of [1].
>
> [1] https://lore.kernel.org/dri-devel/20251023143031.149496-2-phasta@kernel.org/
>
> Philipp Stanner (2):
> drm/todo: Add section with task for GPU scheduler
> drm/todo: Add entry for unlocked drm/sched rq readers
Can someone give this series a review please?
Thx,
P.
next prev parent reply other threads:[~2025-11-27 12:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 13:56 [PATCH v2 0/2] drm/todo: Add section for GPU Scheduler Philipp Stanner
2025-11-07 13:57 ` [PATCH v2 1/2] drm/todo: Add section with task for GPU scheduler Philipp Stanner
2025-11-07 13:57 ` [PATCH v2 2/2] drm/todo: Add entry for unlocked drm/sched rq readers Philipp Stanner
2025-11-27 12:49 ` Philipp Stanner [this message]
2025-12-02 7:37 ` [PATCH v2 0/2] drm/todo: Add section for GPU Scheduler Dave Airlie
2025-12-02 9:42 ` Philipp Stanner
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=c35026065b1d109b7f4b9e1d8dee8ea45f9a1dba.camel@mailbox.org \
--to=phasta@mailbox.org \
--cc=airlied@gmail.com \
--cc=christian.koenig@amd.com \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.brost@intel.com \
--cc=mripard@kernel.org \
--cc=phasta@kernel.org \
--cc=simona@ffwll.ch \
--cc=tvrtko.ursulin@igalia.com \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).