From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-kernel@vger.kernel.org
Cc: linux-rdma@vger.kernel.org, linux-um@lists.infradead.org,
linux-sh@vger.kernel.org
Subject: Re: Build regressions/improvements in v5.19-rc7
Date: Mon, 18 Jul 2022 09:51:03 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2207180949260.949449@ramsan.of.borg> (raw)
In-Reply-To: <20220718074308.3801763-1-geert@linux-m68k.org>
On Mon, 18 Jul 2022, Geert Uytterhoeven wrote:
> JFYI, when comparing v5.19-rc7[1] to v5.19-rc6[3], the summaries are:
> - build errors: +11/-6
+ /kisskb/src/drivers/infiniband/hw/qib/qib_wc_x86_64.c: error: 'X86_VENDOR_AMD' undeclared (first use in this function): => 149:37
+ /kisskb/src/drivers/infiniband/hw/qib/qib_wc_x86_64.c: error: 'struct cpuinfo_um' has no member named 'x86_vendor': => 149:22
+ /kisskb/src/drivers/infiniband/hw/qib/qib_wc_x86_64.c: error: control reaches end of non-void function [-Werror=return-type]: => 150:1
+ /kisskb/src/drivers/infiniband/sw/rdmavt/qp.c: error: 'struct cpuinfo_um' has no member named 'x86_cache_size': => 88:22
+ /kisskb/src/drivers/infiniband/sw/rdmavt/qp.c: error: control reaches end of non-void function [-Werror=return-type]: => 89:1
+ /kisskb/src/drivers/infiniband/sw/rdmavt/qp.c: error: implicit declaration of function '__copy_user_nocache' [-Werror=implicit-function-declaration]: => 100:2
um-x86_64/um-all{mod,yes}config
(seen before in v5.18)
+ {standard input}: Error: displacement to undefined symbol .L271 overflows 12-bit field: => 1625
+ {standard input}: Error: displacement to undefined symbol .L271 overflows 8-bit field : => 1634
+ {standard input}: Error: displacement to undefined symbol .L318 overflows 8-bit field : => 1665, 1681, 1711, 1693
+ {standard input}: Error: pcrel too far: => 1657, 1667, 1629, 1685, 1649, 1655, 1635, 1698, 1618, 1644, 1695, 1705, 1676, 1673, 1670, 1660, 1686, 1656, 1702, 1672, 1700, 1609, 1632, 1684
+ {standard input}: Error: unknown opcode: => 1713
sh4-gcc11/sh-allyesconfig
> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/ff6992735ade75aae3e35d16b17da1008d753d28/ (all 135 configs)
> [3] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/32346491ddf24599decca06190ebca03ff9de7f8/ (all 135 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
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
parent reply other threads:[~2022-07-18 7:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220718074308.3801763-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=alpine.DEB.2.22.394.2207180949260.949449@ramsan.of.borg \
--to=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-um@lists.infradead.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 NNTP newsgroup(s).