From: Philipp Stanner <phasta@mailbox.org>
To: Danilo Krummrich <dakr@kernel.org>, Philipp Stanner <phasta@kernel.org>
Cc: "Matthew Brost" <matthew.brost@intel.com>,
"Christian König" <ckoenig.leichtzumerken@gmail.com>,
"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>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 0/3] drm/sched: Documentation and refcount improvements
Date: Thu, 06 Mar 2025 16:44:21 +0100 [thread overview]
Message-ID: <748519f2ce93d2692c1f32a6ca0950304a3000fa.camel@mailbox.org> (raw)
In-Reply-To: <Z8mxFslgK-XE3EEX@cassiopeiae>
On Thu, 2025-03-06 at 15:28 +0100, Danilo Krummrich wrote:
> On Wed, Mar 05, 2025 at 02:05:49PM +0100, Philipp Stanner wrote:
> > Philipp Stanner (3):
> > drm/sched: Adjust outdated docu for run_job()
> > drm/sched: Document run_job() refcount hazard
> > drm/sched: Update timedout_job()'s documentation
>
> Acked-by: Danilo Krummrich <dakr@kernel.org>
Applied to drm-misc-next.
Thanks
prev parent reply other threads:[~2025-03-06 15:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 13:05 Philipp Stanner
2025-03-05 13:05 ` [PATCH v7 1/3] drm/sched: Adjust outdated docu for run_job() Philipp Stanner
2025-03-05 13:45 ` Bagas Sanjaya
2025-03-05 14:24 ` Philipp Stanner
2025-03-07 18:09 ` Maíra Canal
2025-03-07 18:17 ` Philipp Stanner
2025-03-05 13:05 ` [PATCH v7 2/3] drm/sched: Document run_job() refcount hazard Philipp Stanner
2025-03-05 13:05 ` [PATCH v7 3/3] drm/sched: Update timedout_job()'s documentation Philipp Stanner
2025-03-06 20:57 ` Matthew Brost
2025-03-07 9:37 ` Philipp Stanner
2025-03-07 17:07 ` Matthew Brost
2025-03-07 17:35 ` Matthew Brost
2025-03-06 14:28 ` [PATCH v7 0/3] drm/sched: Documentation and refcount improvements Danilo Krummrich
2025-03-06 15:44 ` Philipp Stanner [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=748519f2ce93d2692c1f32a6ca0950304a3000fa.camel@mailbox.org \
--to=phasta@mailbox.org \
--cc=airlied@gmail.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.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=sumit.semwal@linaro.org \
--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
all inboxes | Powered by JetHome®