From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-kernel@vger.kernel.org
Cc: linux-parisc@vger.kernel.org, sparclinux@vger.kernel.org,
linux-parport@lists.infradead.org, linux-sh@vger.kernel.org
Subject: Re: Build regressions/improvements in v6.6-rc3
Date: Mon, 25 Sep 2023 13:43:08 +0200 (CEST) [thread overview]
Message-ID: <687a5a25-65c4-f571-6626-2fdf9e843415@linux-m68k.org> (raw)
In-Reply-To: <20230925113220.3627083-1-geert@linux-m68k.org>
On Mon, 25 Sep 2023, Geert Uytterhoeven wrote:
> JFYI, when comparing v6.6-rc3[1] to v6.6-rc2[3], the summaries are:
> - build errors: +11/-4
+ error: modpost: ".L872" [drivers/mtd/nand/raw/nand.ko] undefined!: => N/A
parisc-gcc13/parisc-allmodconfig (seen before)
+ error: modpost: "ebus_dma_enable" [drivers/parport/parport_pc.ko] undefined!: => N/A
+ error: modpost: "ebus_dma_irq_enable" [drivers/parport/parport_pc.ko] undefined!: => N/A
+ error: modpost: "ebus_dma_prepare" [drivers/parport/parport_pc.ko] undefined!: => N/A
+ error: modpost: "ebus_dma_register" [drivers/parport/parport_pc.ko] undefined!: => N/A
+ error: modpost: "ebus_dma_request" [drivers/parport/parport_pc.ko] undefined!: => N/A
+ error: modpost: "ebus_dma_residue" [drivers/parport/parport_pc.ko] undefined!: => N/A
+ error: modpost: "ebus_dma_unregister" [drivers/parport/parport_pc.ko] undefined!: => N/A
+ error: modpost: "ns87303_lock" [drivers/parport/parport_pc.ko] undefined!: => N/A
sparc64-gcc{5,11,12,13}/sparc-allmodconfig (seen before)
+ {standard input}: Error: expected comma after name `xpcs_co' in .size directive: => 1100
sh4-gcc1[12]/sh-all{mod,yes}config (ICE)
+ {standard input}: Error: pcrel too far: => 932, 940, 939
sh4-gcc1[12]/sh-allyesconfig (ICE)
> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/6465e260f48790807eef06b583b38ca9789b6072/ (all 239 configs)
> [3] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/ce9ecca0238b140b88f43859b211c9fdfd8e5b70/ (237 out of 239 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
parent reply other threads:[~2023-09-25 11:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230925113220.3627083-1-geert@linux-m68k.org>]
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=687a5a25-65c4-f571-6626-2fdf9e843415@linux-m68k.org \
--to=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-parport@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=sparclinux@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).