Message ID | 20200120100957.GA11113@black.fi.intel.com |
---|---|
State | New |
Headers | show |
Series | [GIT,PULL] intel-pinctrl for 5.6-1 | expand |
On Mon, Jan 20, 2020 at 11:10 AM Andy Shevchenko <andriy.shevchenko@linux.intel.com> wrote: > Intel pin control drivers update for v5.6 (next release cycle). > > Thanks, > > With Best Regards, > Andy Shevchenko > > The following changes since commit b9a19bdbc843abd659e8ec6b1b3c32ae3a2455eb: > > pinctrl: cherryview: Pass irqchip when adding gpiochip (2019-12-09 12:55:53 +0200) > > are available in the Git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/pinctrl/intel.git tags/intel-pinctrl-v5.6-1 > > for you to fetch changes up to cd0a32371db73d0b50536a7ca4f036abddff0d1d: Thanks Andy! Pulled this into my "devel" branch for v5.6. Yours, Linus Walleij
On Thu, Jan 23, 2020 at 03:45:14PM +0100, Linus Walleij wrote: > On Mon, Jan 20, 2020 at 11:10 AM Andy Shevchenko > <andriy.shevchenko@linux.intel.com> wrote: > > Intel pin control drivers update for v5.6 (next release cycle). ... > Pulled this into my "devel" branch for v5.6. Thanks! How long usually does it take to see in linux-next?
On Fri, Jan 24, 2020 at 11:57 AM Andy Shevchenko <andriy.shevchenko@linux.intel.com> 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... Yours, Linus Walleij
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@linux.intel.com> 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...
On Fri, Jan 24, 2020 at 2:21 PM Andy Shevchenko <andriy.shevchenko@linux.intel.com> 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@linux.intel.com> 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