From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
debian-powerpc <debian-powerpc@lists.debian.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
linux-stable <stable@vger.kernel.org>
Subject: Re: Kernel failing to build on 32-bit powerpc
Date: Fri, 17 Oct 2025 09:25:15 +0200 [thread overview]
Message-ID: <2025101758-appendage-postal-6d5e@gregkh> (raw)
In-Reply-To: <bd6fbf70-bf31-4b95-86db-68c0626a3338@csgroup.eu>
On Fri, Oct 17, 2025 at 08:49:06AM +0200, Christophe Leroy wrote:
> Hi,
>
> Le 16/10/2025 à 21:03, John Paul Adrian Glaubitz a écrit :
> > Hi,
> >
> > could someone investigate the following build failure on powerpc [1], please?
> >
> > In file included from /build/reproducible-path/linux-6.16.12/kernel/sched/build_policy.c:64:
> > /build/reproducible-path/linux-6.16.12/kernel/sched/ext_idle.c: In function ‘is_bpf_migration_disabled’:
> > /build/reproducible-path/linux-6.16.12/kernel/sched/ext_idle.c:893:14: error: ‘const struct task_struct’ has no member named ‘migration_disabled’
> > 893 | if (p->migration_disabled == 1)
> > | ^~
> > /build/reproducible-path/linux-6.16.12/kernel/sched/ext_idle.c:896:25: error: ‘const struct task_struct’ has no member named ‘migration_disabled’
> > 896 | return p->migration_disabled;
> > | ^~
> >
>
> I guess 6.16.12 is missing commit cac5cefbade9 ("sched/smp: Make SMP
> unconditional")
6.16 is now end-of-life, so not much we can do there, sorry.
greg k-h
prev parent reply other threads:[~2025-10-17 7:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 19:03 Kernel failing to build on 32-bit powerpc John Paul Adrian Glaubitz
2025-10-17 6:49 ` Christophe Leroy
2025-10-17 7:25 ` 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=2025101758-appendage-postal-6d5e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=christophe.leroy@csgroup.eu \
--cc=debian-powerpc@lists.debian.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.