[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140925164446.GD28201@nazgul.tnic>
Date: Thu, 25 Sep 2014 18:44:46 +0200
From: Borislav Petkov <bp@...en8.de>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
"Rustad, Mark D" <mark.d.rustad@...el.com>,
"sparse@...isli.org" <sparse@...isli.org>,
"linux-sparse@...r.kernel.org" <linux-sparse@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/7] Silence even more W=2 warnings
On Thu, Sep 25, 2014 at 09:45:29AM +0200, Geert Uytterhoeven wrote:
> Instead of grepping, you can feed the build log to linux-log-summary.
> Or when changing a driver, feed the before and after build logs to
> linux-log-diff. That way you won't miss the single new warning you've
> just introduced.
>
> https://github.com/geertu/linux-scripts
Yep, nice stuff: linux-log-summary does nicely summarize it all like
this here:
...
include/linux/kernel.h:120:19: warning: cast from function call of type ‘void *’ to non-matching type ‘long unsigned int’ [-Wbad-function-cast]: 40 warnings in 1 logs
include/linux/kernel.h:67:27: warning: conversion to ‘int’ from ‘long unsigned int’ may alter its value [-Wconversion]: 2 warnings in 1 logs
include/linux/kernel.h:67:33: warning: conversion to ‘long unsigned int’ from ‘int’ may change the sign of the result [-Wsign-conversion]: 3 warnings in 1 logs
...
which I ran on a file built with W=123.
So I'd say everything needed is there to massage those build logs.
Thanks.
--
Regards/Gruss,
Boris.
--
--
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