From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Parisc List <linux-parisc@vger.kernel.org>,
linux-rdma <linux-rdma@vger.kernel.org>,
Greentime Hu <green.hu@gmail.com>,
Vincent Chen <deanbo422@gmail.com>
Subject: Re: Build regressions/improvements in v5.3-rc5
Date: Mon, 19 Aug 2019 11:07:49 +0200 [thread overview]
Message-ID: <CAMuHMdV11Km7yF3gk5uTrPS1mVhjMdkbg28QRymcYyBPiAMBMw@mail.gmail.com> (raw)
In-Reply-To: <20190819081157.9736-1-geert@linux-m68k.org>
On Mon, Aug 19, 2019 at 10:47 AM Geert Uytterhoeven
<geert@linux-m68k.org> wrote:
> JFYI, when comparing v5.3-rc5[1] to v5.3-rc4[3], the summaries are:
> - build errors: +7/-0
+ /kisskb/src/include/asm-generic/5level-fixup.h: error: unknown
type name 'pgd_t'; did you mean 'pid_t'?: => 14:18
+ /kisskb/src/include/asm-generic/pgtable.h: error: implicit
declaration of function 'p4d_bad'; did you mean 'pgd_bad'?
[-Werror=implicit-function-declaration]: => 580:15
+ /kisskb/src/include/asm-generic/pgtable.h: error: implicit
declaration of function 'p4d_bad'; did you mean 'pud_bad'?
[-Werror=implicit-function-declaration]: => 580:15
+ /kisskb/src/include/asm-generic/pgtable.h: error: implicit
declaration of function 'p4d_none'; did you mean 'pgd_none'?
[-Werror=implicit-function-declaration]: => 578:6
+ /kisskb/src/include/asm-generic/pgtable.h: error: implicit
declaration of function 'p4d_none'; did you mean 'pud_none'?
[-Werror=implicit-function-declaration]: => 578:6
parisc-defconfig
parisc-allmodconfig
parisc-allnoconfig
a500_defconfig
+ error: "can_do_mlock" [drivers/infiniband/sw/siw/siw.ko] undefined!: => N/A
sh-allmodconfig
sh-allyesconfig
Note that these are NOMMU!
+ error: rk3399_gru_sound.c: relocation truncated to fit:
R_NDS32_WORD_9_PCREL_RELA against `.text': => (.text+0x624)
nds32-allyesconfig
> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/d1abaeb3be7b5fa6d7a1fbbd2e14e3310005c4c1/ (all 242 configs)
> [3] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/d45331b00ddb179e291766617259261c112db872/ (all 242 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
next parent reply other threads:[~2019-08-19 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190819081157.9736-1-geert@linux-m68k.org>
2019-08-19 9:07 ` Geert Uytterhoeven [this message]
2019-08-21 21:39 ` Build regressions/improvements in v5.3-rc5 Aaro Koskinen
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=CAMuHMdV11Km7yF3gk5uTrPS1mVhjMdkbg28QRymcYyBPiAMBMw@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=deanbo422@gmail.com \
--cc=green.hu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-rdma@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 NNTP newsgroup(s).