From: Miguel Ojeda <ojeda@kernel.org>
To: gregkh@linuxfoundation.org
Cc: akpm@linux-foundation.org, jslaby@suse.cz,
linux-kernel@vger.kernel.org, lwn@lwn.net,
stable@vger.kernel.org, torvalds@linux-foundation.org,
Huacai Chen <chenhuacai@kernel.org>,
WANG Xuerui <kernel@xen0n.name>,
loongarch@lists.linux.dev
Subject: Re: Linux 6.12.18
Date: Fri, 7 Mar 2025 22:49:43 +0100 [thread overview]
Message-ID: <20250307214943.372210-1-ojeda@kernel.org> (raw)
In-Reply-To: <2025030745-flaxseed-unsubtly-c5e3@gregkh>
On Fri, 07 Mar 2025 18:52:44 +0100 Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>
> I'm announcing the release of the 6.12.18 kernel.
>
> All users of the 6.12 kernel series must upgrade.
While testing another backport, I found an unrelated build failure for
loongarch in v6.12.18 that I did not see in v6.12.17 -- I cannot find it
reported from a quick look, so I am doing so here:
CC arch/loongarch/kernel/asm-offsets.s - due to target missing
In file included from arch/loongarch/kernel/asm-offsets.c:8:
In file included from ./include/linux/sched.h:12:
In file included from ./arch/loongarch/include/generated/asm/current.h:1:
In file included from ./include/asm-generic/current.h:6:
./include/linux/thread_info.h:249:6: error: call to undeclared function 'annotate_reachable'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
249 | if (WARN_ON_ONCE(bytes > INT_MAX))
| ^
./include/asm-generic/bug.h:113:3: note: expanded from macro 'WARN_ON_ONCE'
113 | __WARN_FLAGS(BUGFLAG_ONCE | \
| ^
./arch/loongarch/include/asm/bug.h:47:2: note: expanded from macro '__WARN_FLAGS'
47 | annotate_reachable(); \
| ^
As well as warnings:
In file included from arch/loongarch/kernel/asm-offsets.c:9:
In file included from ./include/linux/mm.h:1120:
In file included from ./include/linux/huge_mm.h:8:
In file included from ./include/linux/fs.h:33:
In file included from ./include/linux/percpu-rwsem.h:7:
In file included from ./include/linux/rcuwait.h:6:
In file included from ./include/linux/sched/signal.h:6:
./include/linux/signal.h:114:27: warning: array index 3 is past the end of the array (that has type 'const unsigned long[1]') [-Warray-bounds]
114 | return (set1->sig[3] == set2->sig[3]) &&
| ^ ~
./include/uapi/asm-generic/signal.h:62:2: note: array 'sig' declared here
62 | unsigned long sig[_NSIG_WORDS];
| ^
I hope that helps.
Cheers,
Miguel
next prev parent reply other threads:[~2025-03-07 21:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 17:52 Linux 6.12.18 Greg Kroah-Hartman
2025-03-07 17:52 ` Greg Kroah-Hartman
2025-03-07 21:49 ` Miguel Ojeda [this message]
2025-03-08 5:28 ` Huacai Chen
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=20250307214943.372210-1-ojeda@kernel.org \
--to=ojeda@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=chenhuacai@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--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 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.