From: Danilo Krummrich <dakr@kernel.org>
To: 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, 6 Mar 2025 15:28:38 +0100 [thread overview]
Message-ID: <Z8mxFslgK-XE3EEX@cassiopeiae> (raw)
In-Reply-To: <20250305130551.136682-2-phasta@kernel.org>
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>
next prev parent reply other threads:[~2025-03-06 14:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 13:05 [PATCH v7 0/3] drm/sched: Documentation and refcount improvements 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 ` Danilo Krummrich [this message]
2025-03-06 15:44 ` [PATCH v7 0/3] drm/sched: Documentation and refcount improvements 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=Z8mxFslgK-XE3EEX@cassiopeiae \
--to=dakr@kernel.org \
--cc=airlied@gmail.com \
--cc=ckoenig.leichtzumerken@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.