From: Jan Kara <jack@suse.cz>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Build regressions/improvements in v3.5-rc5
Date: Wed, 4 Jul 2012 15:34:55 +0200 [thread overview]
Message-ID: <20120704133455.GC29954@quack.suse.cz> (raw)
In-Reply-To: <1341342768-22221-1-git-send-email-geert@linux-m68k.org>
On Tue 03-07-12 21:12:48, Geert Uytterhoeven wrote:
> Below is the list of build error/warning regressions/improvements in
> v3.5-rc5[1] compared to v3.4[2].
>
> Too make this mail fit in the lkml limit, I deleted
> - all implicit function declaration error improvements
> - 245 lines about __mcount_loc on sparc64
> - all warning improvements
>
> Summarized:
> - build errors: +227/-575
> - build warnings: +644/-805
>
> JFYI, when comparing v3.5-rc5 to v3.5-rc4[3], the summaries are:
> - build errors: +20/-11
> - build warnings: +130/-533
>
> 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.5-rc5.summary.gz
>
> Happy fixing! ;-)
>
> Thanks to the linux-next team for providing the build service.
...
> + fs/quota/quota_tree.c: warning: format '%zd' expects argument of type 'signed size_t', but argument 4 has type 'ssize_t' [-Wformat]: => 372:4
> + fs/quota/quota_v2.c: warning: format '%zd' expects argument of type 'signed size_t', but argument 5 has type 'ssize_t' [-Wformat]: => 66:92
These really look like false positives (there are quite a few of this
kind). Can we possibly silence them?
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
prev parent reply other threads:[~2012-07-04 13:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 19:12 Build regressions/improvements in v3.5-rc5 Geert Uytterhoeven
2012-07-03 19:22 ` Geert Uytterhoeven
2012-07-04 6:05 ` Cong Wang
2012-07-04 13:34 ` Jan Kara [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=20120704133455.GC29954@quack.suse.cz \
--to=jack@suse.cz \
--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