On Fri, Jan 24, 2020 at 2:21 PM Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx> wrote: > On Fri, Jan 24, 2020 at 02:02:56PM +0100, Linus Walleij wrote: > > On Fri, Jan 24, 2020 at 11:57 AM Andy Shevchenko > > <andriy.shevchenko@xxxxxxxxxxxxxxx> wrote: > > > On Thu, Jan 23, 2020 at 03:45:14PM +0100, Linus Walleij wrote: > > > > > > Pulled this into my "devel" branch for v5.6. > > > > > > Thanks! > > > How long usually does it take to see in linux-next? > > > > What I need before I put it for-next is successful builds on a few > > archs. > > > > Zeroday has been smacky before so I could quickly cornfirm the branches > > build fine and that made things quicker in the past. But as of lately > > zeroday comes and goes a bit sporadically. > > > > I can do local builds of some archs but my computer isn't the most > > fantastic workhorse really. > > > > Lately I am investigating a cloud build service, it is quite promising, > > you see the branch "testmerge" in linux-gpio where I merge all > > the new stuff for GPIO and pin control and toss at the build server, > > so I am working on something here. > > > > Sometimes I just give up trying to build all stuff and submit it for > > next anyway but I'd rather not have to do that, it usually results > > in a patch storm of 4 different people fixing the same trivial > > issue in linux-next... > > Thank you for so detailed answer! I didn't mean to complain or so, > I was just wondering... Don't worry about that, it's a good question. I am looking a bit into automation and testing right now so these things are very much on my mind. Yours, Linus Walleij