From: Tejun Heo <tj@kernel.org>
To: Andrea Righi <arighi@nvidia.com>
Cc: David Vernet <void@manifault.com>,
Changwoo Min <changwoo@igalia.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched_ext: Documentation: add task lifecycle summary
Date: Thu, 27 Feb 2025 06:28:33 -1000 [thread overview]
Message-ID: <Z8CSsWJhODjGlKF2@slm.duckdns.org> (raw)
In-Reply-To: <20250227155733.292672-1-arighi@nvidia.com>
On Thu, Feb 27, 2025 at 04:57:33PM +0100, Andrea Righi wrote:
> Understanding the lifecycle of a task in sched_ext can be not trivial,
> therefore add a section to the main documentation that summarizes the
> entire workflow of a task using pseudo-code.
>
> Signed-off-by: Andrea Righi <arighi@nvidia.com>
Applied to sched_ext/for-6.15.
Thanks.
--
tejun
prev parent reply other threads:[~2025-02-27 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 15:57 [PATCH] sched_ext: Documentation: add task lifecycle summary Andrea Righi
2025-02-27 16:28 ` Tejun Heo [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=Z8CSsWJhODjGlKF2@slm.duckdns.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=void@manifault.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 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.