From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Parisc List <linux-parisc@vger.kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: Build regressions/improvements in v4.6-rc4
Date: Tue, 19 Apr 2016 08:57:37 +0200 [thread overview]
Message-ID: <CAMuHMdUqJ0dj25oXhC4MgqSk0SaOHvT262ew+sBs7eV2SCwyUA@mail.gmail.com> (raw)
In-Reply-To: <1461048813-28712-1-git-send-email-geert@linux-m68k.org>
On Tue, Apr 19, 2016 at 8:53 AM, Geert Uytterhoeven
<geert@linux-m68k.org> wrote:
> Below is the list of build error/warning regressions/improvements in
> v4.6-rc4[1] compared to v4.5[2].
>
> Summarized:
> - build errors: +11/-7
> - build warnings: +16376/-165
Sorry for the delay, initially I didn't realize why my first report didn't make
it to the list. It was too big, due to 16211 warnings in parisc-allmodconfig
about "-ffunction-sections disabled; it makes profiling impossible [enabled by
default]".
> JFYI, when comparing v4.6-rc4[1] to v4.6-rc3[3], the summaries are:
> - build errors: +9/-9
+ /home/kisskb/slave/src/arch/powerpc/kernel/pci_dn.c: error:
'struct pci_dn' has no member named 'edev': => 272:8
+ /home/kisskb/slave/src/arch/powerpc/kernel/pci_dn.c: error:
dereferencing pointer to incomplete type: => 215:7
+ /home/kisskb/slave/src/arch/powerpc/kernel/pci_dn.c: error:
implicit declaration of function 'eeh_dev_init'
[-Werror=implicit-function-declaration]: => 212:3
powerpc-randconfig
+ /home/kisskb/slave/src/drivers/thermal/mtk_thermal.c: error:
implicit declaration of function 'device_reset'
[-Werror=implicit-function-declaration]: => 560:2
x86_64-randconfig (patch available)
> [1] http://kisskb.ellerman.id.au/kisskb/head/10194/ (all 262 configs)
> [3] http://kisskb.ellerman.id.au/kisskb/head/10162/ (all 262 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 prev parent reply other threads:[~2016-04-19 6:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 6:53 Build regressions/improvements in v4.6-rc4 Geert Uytterhoeven
2016-04-19 6:57 ` Geert Uytterhoeven [this message]
2016-04-19 13:31 ` Build regressions/improvements in v4.6-rc4 (parisc warnings) Helge Deller
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=CAMuHMdUqJ0dj25oXhC4MgqSk0SaOHvT262ew+sBs7eV2SCwyUA@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).