On Sun, Oct 25, 2015 at 06:33:18AM -0700, David Miller wrote:
> From: kbuild test robot <[email protected]>
> Date: Sat, 24 Oct 2015 23:11:00 +0800
>
> > TO: "David S. Miller" <[email protected]>
> > CC: [email protected]
> > CC: Jon Maloy <[email protected]>
> > CC: Ying Xue <[email protected]>
> > CC: [email protected]
> > CC: [email protected]
> >
> >
> > Signed-off-by: Fengguang Wu <[email protected]>
>
> Why doesn't the kbuild robot run on it's own changes? :-/
It does, however it detects only build failures (which indicates a
false sparse warning) to avoid sending bad make-it-static patch
and the false warning.
The build warning looks easier to be discovered and fixed in the
larger loop of
apply patch => git push => 0day build test
> CC [M] net/tipc/link.o
> net/tipc/link.c:176:12: warning: ‘tipc_link_is_active’ defined but not used
> [-Wunused-function]
If the robot detected the above warning, it'll still need to send the
report out. Otherwise we lose a chance to notice tipc_link_is_active()
is not used.
However it may be valuable to include possible new warnings inside
the patch changelog, so that maintainers can immediately see the
consequences of applying the patch.
Thanks,
Fengguang
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
