From: Michael Ellerman <mpe@ellerman.id.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>, linux-kernel@vger.kernel.org
Subject: Re: Build regressions/improvements in v4.20-rc2
Date: Thu, 15 Nov 2018 15:34:26 +1100 [thread overview]
Message-ID: <87bm6ruffx.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20181112213555.22941-1-geert@linux-m68k.org>
Geert Uytterhoeven <geert@linux-m68k.org> writes:
> Below is the list of build error/warning regressions/improvements in
> v4.20-rc2[1] compared to v4.19[2].
>
> Summarized:
> - build errors: +3/-0
> - build warnings: +123/-12803
>
> JFYI, when comparing v4.20-rc2[1] to v4.20-rc1[3], the summaries are:
> - build errors: +0/-0
> - build warnings: +61/-10479
>
> Happy fixing! ;-)
>
> Thanks to the linux-next team for providing the build service.
>
> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/ccda4af0f4b92f7b4c308d3acc262f4a7e3affad/ (all 240 configs)
> [2] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/84df9525b0c27f3ebc2ebb1864fa62a97fdedb7d/ (all 240 configs)
> [3] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/651022382c7f8da46cb4872a545ee1da6d097d2a/ (all 240 configs)
>
>
> *** ERRORS ***
>
> 3 error regressions:
> + /kisskb/src/arch/s390/kernel/nospec-branch.c: error: macro "memcpy" passed 6 arguments, but takes just 3: => 130:61
> + /kisskb/src/sound/pci/hda/patch_ca0132.c: error: implicit declaration of function 'pci_iomap' [-Werror=implicit-function-declaration]: => 8799:3
> + {standard input}: Error: Unrecognized opcode: `slbfee.': => 89, 37
I have a fix queued for this one.
cheers
prev parent reply other threads:[~2018-11-15 4:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 21:35 Geert Uytterhoeven
2018-11-15 4:34 ` Michael Ellerman [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=87bm6ruffx.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=geert@linux-m68k.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®