From: Tejun Heo <tj@kernel.org>
To: jake@hillion.co.uk
Cc: David Vernet <void@manifault.com>,
Andrea Righi <arighi@nvidia.com>,
Changwoo Min <changwoo@igalia.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
sched-ext@lists.linux.dev, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH] sched_ext: Drop kfuncs marked for removal in 6.15
Date: Wed, 25 Jun 2025 13:15:05 -1000 [thread overview]
Message-ID: <aFyC-WVI1fkk0rPN@slm.duckdns.org> (raw)
In-Reply-To: <20250625-scx-kfunc-cleanup-v1-1-d93335286fd5@hillion.co.uk>
On Wed, Jun 25, 2025 at 06:05:46PM +0100, Jake Hillion via B4 Relay wrote:
> From: Jake Hillion <jake@hillion.co.uk>
>
> sched_ext performed a kfunc renaming pass in 6.13 and kept the old names
> around for compatibility with old binaries. These were scheduled for
> cleanup in 6.15 but were missed. Submitting for cleanup in for-next.
>
> Removed the kfuncs, their flags, and any references I could find to them
> in doc comments. Left the entries in include/scx/compat.bpf.h as they're
> still useful to make new binaries compatible with old kernels.
>
> Tested by applying to my kernel. It builds and a modern version of
> scx_lavd loads fine.
>
> Signed-off-by: Jake Hillion <jake@hillion.co.uk>
Applied to sched_ext/for-6.17.
Thanks.
--
tejun
prev parent reply other threads:[~2025-06-25 23:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 17:05 Jake Hillion via B4 Relay
2025-06-25 23:15 ` 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=aFyC-WVI1fkk0rPN@slm.duckdns.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=bpf@vger.kernel.org \
--cc=bsegall@google.com \
--cc=changwoo@igalia.com \
--cc=dietmar.eggemann@arm.com \
--cc=jake@hillion.co.uk \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sched-ext@lists.linux.dev \
--cc=vincent.guittot@linaro.org \
--cc=void@manifault.com \
--cc=vschneid@redhat.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
all inboxes | Powered by JetHome®