On 05/11/2018 09:38 PM, Stephen Rothwell wrote:
Hi all,
On Wed, 9 May 2018 20:47:27 +1000 Stephen Rothwell <s...@canb.auug.org.au>
wrote:
On Wed, 9 May 2018 18:03:46 +0900 Mark Brown <broo...@kernel.org> wrote:
On Wed, May 09, 2018 at 10:47:57AM +0200, Daniel Vetter wrote:
On Wed, May 9, 2018 at 10:44 AM, Mark Brown <broo...@kernel.org> wrote:
I think this is an excellent idea, copying in Stephen for his input.
I'm currently on holiday but unless someone convinces me it's a terrible
idea I'm willing to at least give it a go on a trial basis once I'm back
home.
Since Stephen merges all -fixes branches first, before merging all the
-next branches, he already generates that as part of linux-next. All
he'd need to do is push that intermediate state out to some
linux-fixes branch for consumption by test bots.
Good idea ... I will see what I can do.
See my announcement of a pending-fixes branch in linux-next (on LKML
and others)
Excellent.
Build/test results match mainline.
For v4.17-rc4-241-ga1b6c55:
Build results:
total: 132 pass: 130 fail: 2
Failed builds:
m68k:allmodconfig
xtensa:allmodconfig
Qemu test results:
total: 138 pass: 138 fail: 0
Guenter