From: Tejun Heo <tj@kernel.org>
To: sashiko-bot@kernel.org
Cc: sched-ext@lists.linux.dev
Subject: Re: [PATCH sched_ext/for-7.3] tools/sched_ext/include: Regenerate enum_defs.autogen.h
Date: Mon, 27 Jul 2026 10:02:53 -1000 [thread overview]
Message-ID: <e111bf08e6f123ae25b9281cc5a03fa5@kernel.org> (raw)
In-Reply-To: <20260726220016.D958B1F000E9@smtp.kernel.org>
On Sun, Jul 26, 2026 at 10:00:16PM +0000, sashiko-bot@kernel.org wrote:
> [Severity: Medium]
> Is the SCX_REENQ_LOCAL_MAX_REPEAT to SCX_REENQ_MAX_REPEAT rename actually
> present in this tree?
>
> Looking at kernel/sched/ext/types.h, the old enum name is still present:
The rename is in 7706d6e4f2e3 ("sched_ext: Bound per-task reenqueues and
eject the owning scheduler"), the commit right below this one on
sched_ext/for-7.3. The review base is missing it.
> [Severity: Medium]
> Will this cause build failures for BPF schedulers that check for
> HAVE_SCX_REENQ_MAX_REPEAT?
No. With the above commit in the tree, vmlinux.h carries the renamed enum.
Thanks.
--
tejun
next prev parent reply other threads:[~2026-07-27 20:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-26 19:49 [PATCH v3 sched_ext/for-7.3] sched_ext: Bound per-task reenqueues and eject the owning scheduler Tejun Heo
2026-07-26 20:20 ` Andrea Righi
2026-07-26 21:48 ` [PATCH sched_ext/for-7.3] tools/sched_ext/include: Regenerate enum_defs.autogen.h Tejun Heo
2026-07-26 22:00 ` sashiko-bot
2026-07-27 20:02 ` Tejun Heo [this message]
2026-07-26 21:48 ` [PATCH v3 sched_ext/for-7.3] sched_ext: Bound per-task reenqueues and eject the owning scheduler Tejun Heo
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=e111bf08e6f123ae25b9281cc5a03fa5@kernel.org \
--to=tj@kernel.org \
--cc=sashiko-bot@kernel.org \
--cc=sched-ext@lists.linux.dev \
/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