From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Libo Chen <libo.chen@oracle.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"lwn@lwn.net" <lwn@lwn.net>, "jslaby@suse.cz" <jslaby@suse.cz>,
Tejun Heo <htejun@meta.com>
Subject: Re: Linux 6.12.11
Date: Tue, 11 Feb 2025 09:57:03 +0100 [thread overview]
Message-ID: <2025021127-lapped-untwist-fef3@gregkh> (raw)
In-Reply-To: <1E4095C7-59A5-4421-AD2E-6EFF28F8A850@oracle.com>
On Mon, Feb 10, 2025 at 07:43:03PM +0000, Libo Chen wrote:
> > On Jan 23, 2025, at 09:12, Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> > Ihor Solodrai (1):
> > selftests/sched_ext: fix build after renames in sched_ext API
>
> Hi Greg,
>
> I think the commit "selftests/sched_ext: fix build after renames in sched_ext API” was wrongly pulled into the stable 6.12.y
> without the sched_ext API changes introduced by Tejun’s series: https://lore.kernel.org/all/20241110200308.103681-1-tj@kernel.org.
> As a result, the sched_ext selftests compilation fails starting from v6.12.11:
>
> exit.bpf.c:36:2: error: call to undeclared function 'scx_bpf_dsq_insert'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
> 36 | scx_bpf_dsq_insert(p, DSQ_ID, SCX_SLICE_DFL, enq_flags);
> | ^
> exit.bpf.c:44:2: error: call to undeclared function 'scx_bpf_dsq_move_to_local'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
> 44 | scx_bpf_dsq_move_to_local(DSQ_ID);
> | ^
> 2 errors generated.
> ...
Thanks for catching this (nit, can you trim your reply, it's hard to
find it in a huge email like this.)
Can you send a revert to fix this up?
thanks,
greg k-h
prev parent reply other threads:[~2025-02-11 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 17:12 Linux 6.12.11 Greg Kroah-Hartman
2025-01-23 17:12 ` Greg Kroah-Hartman
2025-02-10 19:43 ` Libo Chen
2025-02-11 8:57 ` Greg Kroah-Hartman [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=2025021127-lapped-untwist-fef3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=htejun@meta.com \
--cc=jslaby@suse.cz \
--cc=libo.chen@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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