From: Tao Cui <cui.tao@linux.dev>
To: tj@kernel.org, corbet@lwn.net
Cc: rdunlap@infradead.org, skhan@linuxfoundation.org,
arighi@nvidia.com, yphbchou0911@gmail.com, jpiecuch@google.com,
ihor.solodrai@linux.dev, suzhidao@xiaomi.com,
luoliang@kylinos.cn, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, cui.tao@linux.dev,
Tao Cui <cuitao@kylinos.cn>
Subject: [PATCH v2 0/2] sched_ext: minor doc and comment fixes
Date: Fri, 14 Aug 2026 07:01:21 +0800 [thread overview]
Message-ID: <20260813230123.2069719-1-cui.tao@linux.dev> (raw)
From: Tao Cui <cuitao@kylinos.cn>
Two small doc and comment fixes noticed while
reading the code. No functional changes.
Changes in v2 (per Tejun's review):
- show_state example: aborting prints as False (drgn bools)
- inlines.h: use scx_bpf_sub_dispatch(), not scx_bpf_dsq_insert()
- internal.h: name %SCX_DEQ_SCHED_CHANGE instead of dropping the
never-defined %SCX_DEQ_SAVE
- internal.h: reword @name to cover sub-schedulers
- rebase onto sched_ext/for-7.3
Tao Cui (2):
Documentation: sched_ext: fix events sysfs path and show_state example
sched_ext: fix stale references in doc comments
Documentation/scheduler/sched-ext.rst | 9 +++++----
kernel/sched/ext/inlines.h | 2 +-
kernel/sched/ext/internal.h | 7 ++++---
3 files changed, 10 insertions(+), 8 deletions(-)
--
2.43.0
next reply other threads:[~2026-08-13 23:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 23:01 Tao Cui [this message]
2026-08-13 23:01 ` [PATCH v2 1/2] Documentation: sched_ext: fix events sysfs path and show_state example Tao Cui
2026-08-13 23:01 ` [PATCH v2 2/2] sched_ext: fix stale references in doc comments Tao Cui
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=20260813230123.2069719-1-cui.tao@linux.dev \
--to=cui.tao@linux.dev \
--cc=arighi@nvidia.com \
--cc=corbet@lwn.net \
--cc=cuitao@kylinos.cn \
--cc=ihor.solodrai@linux.dev \
--cc=jpiecuch@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luoliang@kylinos.cn \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=suzhidao@xiaomi.com \
--cc=tj@kernel.org \
--cc=yphbchou0911@gmail.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