From: Jonathan Corbet <corbet@lwn.net>
To: Shashank Balaji <shashank.mahadasyam@sony.com>,
Juri Lelli <juri.lelli@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Shinya Takumi <shinya.takumi@sony.com>,
Shashank Balaji <shashank.mahadasyam@sony.com>
Subject: Re: [PATCH v2 0/2] sched_deadline, docs: update rt-app examples, add cgroup v2 cpuset HOWTO
Date: Mon, 09 Jun 2025 15:02:36 -0600 [thread overview]
Message-ID: <87h60oaas3.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250527-sched-deadline-cpu-affinity-v2-0-b8b40a4feefa@sony.com>
Shashank Balaji <shashank.mahadasyam@sony.com> writes:
> The main goal of this patchset is to add the cgroup v2 cpuset controller HOWTO.
> In v1 of this series, Juri commented that rt-app no longer takes command-line
> options. So I ended up converting the rt-app examples to either use chrt instead
> or use config.json.
>
> Signed-off-by: Shashank Balaji <shashank.mahadasyam@sony.com>
> ---
> Changes in v2:
> - update rt-app examples to either use a chrt example or use config.json
> - Link to v1: https://lore.kernel.org/r/20250522-sched-deadline-cpu-affinity-v1-1-2172c683acac@sony.com
>
Applied, thanks.
jon
prev parent reply other threads:[~2025-06-09 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 14:55 [PATCH v2 0/2] sched_deadline, docs: update rt-app examples, add cgroup v2 cpuset HOWTO Shashank Balaji
2025-05-27 14:55 ` [PATCH v2 1/2] sched_deadline, docs: replace rt-app examples with chrt or use config.json Shashank Balaji
2025-05-27 14:55 ` [PATCH v2 2/2] sched_deadline, docs: add affinity setting with cgroup2 cpuset controller Shashank Balaji
2025-05-27 15:23 ` [PATCH v2 0/2] sched_deadline, docs: update rt-app examples, add cgroup v2 cpuset HOWTO Juri Lelli
2025-06-09 21:02 ` Jonathan Corbet [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=87h60oaas3.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=juri.lelli@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=shashank.mahadasyam@sony.com \
--cc=shinya.takumi@sony.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