From: Tejun Heo <tj@kernel.org>
To: David Vernet <void@manifault.com>
Cc: Andrea Righi <arighi@nvidia.com>,
Changwoo Min <changwoo@igalia.com>,
sched-ext@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH sched_ext/for-6.19] sched_ext/tools: Restore backward compat with v6.12 kernels
Date: Wed, 29 Oct 2025 10:46:09 -1000 [thread overview]
Message-ID: <0bac90274a876d04c27cdd366c336768@kernel.org> (raw)
In-Reply-To: <33d319a7063f59638ae1be709f4e10e9@kernel.org>
Applied to sched_ext/for-6.19 with the following comment lines removed as
they were from earlier and no longer apply:
* Build error is triggered if old names are used. New binaries work with both
* new and old names. The compat macros will be removed on v6.15 release.
Thanks.
--
tejun
prev parent reply other threads:[~2025-10-29 20:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 18:35 [PATCH sched_ext/for-6.19] sched_ext/tools: Restore backward compat with v6.12 kernels Tejun Heo
2025-10-29 20:09 ` Andrea Righi
2025-10-29 20:46 ` 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=0bac90274a876d04c27cdd366c336768@kernel.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sched-ext@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox