From: Paul Moore <paul@paul-moore.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>,
selinux@tycho.nsa.gov
Subject: Re: Build regressions/improvements in v3.9-rc8
Date: Wed, 24 Apr 2013 11:38:23 -0400 [thread overview]
Message-ID: <11026580.BGB2mffbp5@sifl> (raw)
In-Reply-To: <alpine.DEB.2.00.1304232131300.11127@ayla.of.borg>
On Tuesday, April 23, 2013 09:32:02 PM Geert Uytterhoeven wrote:
> Below is the list of build error/warning regressions/improvements in
> v3.9-rc8[1] compared to v3.8[2].
>
> Summarized:
> - build errors: +19/-58
> - build warnings: +223/-377
>
> JFYI, when comparing v3.9-rc8 to v3.9-rc7[3], the summaries are:
> - build errors: +9/-8
> - build warnings: +96/-145
>
> Note that there may be false regressions, as some logs are incomplete.
> Still, they're build errors/warnings.
>
> As I haven't mastered kup yet, there's no verbose summary at
> http://www.kernel.org/pub/linux/kernel/people/geert/linux-log/v3.9-rc8.summa
> ry.gz
>
> Happy fixing! ;-)
>
> Thanks to the linux-next team for providing the build service.
>
> [1] http://kisskb.ellerman.id.au/kisskb/head/6122/ (all 118 configs)
> [2] http://kisskb.ellerman.id.au/kisskb/head/5896/ (117 out of 118 configs)
> [3] http://kisskb.ellerman.id.au/kisskb/head/6094/ (all 118 configs)
...
> => 93:1 + security/selinux/netnode.c: warning: 'idx' may be used
> uninitialized in this function [-Wuninitialized]: 174:27 => 174:2, 174:27 +
FYI: A fix for this was (re)sent to the SELinux list on April 4th.
* http://marc.info/?l=selinux&m=136508710131898&w=2
--
paul moore
www.paul-moore.com
prev parent reply other threads:[~2013-04-24 15:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 19:32 Build regressions/improvements in v3.9-rc8 Geert Uytterhoeven
2013-04-23 19:35 ` Geert Uytterhoeven
2013-04-23 20:47 ` Randy Dunlap
2013-04-23 21:31 ` Linus Torvalds
2013-04-24 15:38 ` Paul Moore [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=11026580.BGB2mffbp5@sifl \
--to=paul@paul-moore.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=selinux@tycho.nsa.gov \
/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