On Thu, May 03, 2018 at 05:02:36AM -0700, Greg KH wrote:
> On Wed, May 02, 2018 at 11:39:51PM +0000, Sasha Levin wrote:
> > On Wed, May 02, 2018 at 04:36:49PM -0700, Greg KH wrote:
> > >On Wed, May 02, 2018 at 04:19:25PM -0700, Greg KH wrote:
> > >> On Fri, Apr 27, 2018 at 02:00:53AM +0000, Sasha Levin wrote:
> > >> > Hi Greg,
> > >> >
> > >> > Pleae pull commits for Linux 4.14 .
> > >> >
> > >> > I've sent a review request for all commits over a week ago and all
> > >> > comments were addressed.
> > >>
> > >> Are you running these through 0-day?  I have a bunch of warnings, and
> > >> some build breakages to fix up now that it reports :(
> > 
> > I thought 0-day runs through all the branches on git.kernel.org... I
> > haven't seen a mail from the bot for a while, but I thought it's because
> > I do allyesconfig/allmodconfig for x86 and arm on my end.
> 
> You can ask them to send you a "the build is finished" email when they
> are finished with a tree/branch so you _know_ that they really did run
> and test your branch.  I do that for my branches, otherwise you just
> guess.
> 
> And it really looks like these were not tested by 0-day, as 0-day is
> throwing up a bunch of errors/warnings at me.
> 
> And, 'allmodconfig' on x86 gives me warnings for 4.4 and 4.9, so are you
> sure you tested there?

As an example, here is the build log for allmodconfig on 4.4 with these
patches applied.  Grep for 'warning' :(