[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54AC3395.9080101@hurleysoftware.com>
Date: Tue, 06 Jan 2015 14:12:21 -0500
From: Peter Hurley <peter@...leysoftware.com>
To: Geert Uytterhoeven <geert@...ux-m68k.org>,
linux-kernel@...r.kernel.org
Subject: Re: Build regressions/improvements in v3.19-rc3
Hi Geert,
On 01/06/2015 04:36 AM, Geert Uytterhoeven wrote:
> Below is the list of build error/warning regressions/improvements in
> v3.19-rc3[1] compared to v3.18[2].
>
> Summarized:
> - build errors: +86/-19
> - build warnings: +242/-127
>
> JFYI, when comparing v3.19-rc3[1] to v3.19-rc2[3], the summaries are:
> - build errors: +64/-9
> - build warnings: +123/-75
>
> 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.19-rc3.summary.gz
>
> Happy fixing! ;-)
>
> Thanks to the linux-next team for providing the build service.
>
> [1] http://kisskb.ellerman.id.au/kisskb/head/8277/ (255 out of 262 configs)
> [2] http://kisskb.ellerman.id.au/kisskb/head/8168/ (all 262 configs)
> [3] http://kisskb.ellerman.id.au/kisskb/head/8257/ (all 262 configs)
[snip]
> + /home/kisskb/slave/src/drivers/tty/serial/8250/8250_core.c: warning: 'flags' may be used uninitialized in this function: => 3186:16
Is there some way of finding out what gcc + config produced this warning?
I know what commit produced this build regression but I'm not seeing a problem
with the code.
Regards,
Peter Hurley
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists