From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-kernel@vger.kernel.org
Cc: Kent Overstreet <kent.overstreet@linux.dev>,
Brian Foster <bfoster@redhat.com>,
linux-bcachefs@vger.kernel.org
Subject: Re: Build regressions/improvements in v6.9-rc5
Date: Mon, 22 Apr 2024 15:08:28 +0200 (CEST) [thread overview]
Message-ID: <34dec962-474b-353-a33f-de147cffa06c@linux-m68k.org> (raw)
In-Reply-To: <20240422124533.1363483-1-geert@linux-m68k.org>
On Mon, 22 Apr 2024, Geert Uytterhoeven wrote:
> JFYI, when comparing v6.9-rc5[1] to v6.9-rc4[3], the summaries are:
> - build errors: +6/-5
+ /kisskb/src/arch/sparc/kernel/setup_64.c: error: no previous prototype for 'alloc_irqstack_bootmem' [-Werror=missing-prototypes]: => 602:13
+ /kisskb/src/arch/sparc/vdso/vclock_gettime.c: error: no previous prototype for '__vdso_clock_gettime' [-Werror=missing-prototypes]: => 254:1
+ /kisskb/src/arch/sparc/vdso/vclock_gettime.c: error: no previous prototype for '__vdso_clock_gettime_stick' [-Werror=missing-prototypes]: => 282:1
+ /kisskb/src/arch/sparc/vdso/vclock_gettime.c: error: no previous prototype for '__vdso_gettimeofday' [-Werror=missing-prototypes]: => 307:1
+ /kisskb/src/arch/sparc/vdso/vclock_gettime.c: error: no previous prototype for '__vdso_gettimeofday_stick' [-Werror=missing-prototypes]: => 343:1
sparc64-gcc13/sparc64-allmodconfig (seen before in other configs)
+ /kisskb/src/fs/bcachefs/btree_io.c: error: format '%lu' expects argument of type 'long unsigned int', but argument 12 has type 'unsigned int' [-Werror=format=]: => 891:34, 891:6
m68k-gcc8/m68k-allmodconfig
m68k-gcc8/m68k-defconfig
m68k-gcc8/sun3_defconfig
m68k-gcc11/m68k-allmodconfig
m68k-gcc11/m68k-defconfig
m68k-gcc11/sun3_defconfig
m68k-gcc13/m68k-allmodconfig
m68k-gcc13/m68k-defconfig
m68k-gcc13/sun3_defconfig
mips-gcc8/mips-allmodconfig
mips-gcc13/mips-allmodconfig
parisc-gcc13/parisc-allmodconfig
powerpc-gcc5/ppc32_allmodconfig
powerpc-gcc13/ppc32_allmodconfig
sh4-gcc13/sh-allmodconfig
sh4-gcc13/sh-allyesconfig
sparc64-gcc5/sparc-allmodconfig
sparc64-gcc13/sparc-allmodconfig
xtensa-gcc13/xtensa-allmodconfig
(Multiple) fixes available
> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/ed30a4a51bb196781c8058073ea720133a65596f/ (all 138 configs)
> [3] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/0bbac3facb5d6cc0171c45c9873a2dc96bea9680/ (all 138 configs)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2024-04-22 13:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-21 19:53 Linux 6.9-rc5 Linus Torvalds
2024-04-22 12:45 ` Build regressions/improvements in v6.9-rc5 Geert Uytterhoeven
2024-04-22 13:08 ` Geert Uytterhoeven [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=34dec962-474b-353-a33f-de147cffa06c@linux-m68k.org \
--to=geert@linux-m68k.org \
--cc=bfoster@redhat.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@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 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®