One thing we typically cover at Kernel Summit is some of the activity
that's going on around testing upstream.  I think it'd be useful to have
some more of those discussions, both in terms of making people aware of
what's available and in terms of helping the people doing testing figure
out what would be useful.  A lot of this is probably well suited to a
workshop session between the interested people but I do think some
element in the core day beyond just a readout will be useful.

The main things I'm aware of that are happening at the minute are
kselftest development, the 0day tester, plus kernelci.org and the other
build and boot/test bots that are running against various trees.

In terms of discussion topics some of the issues I'm seeing are:

 - Can we pool resources to share the workload of running things and
   interpreting results, ideally also providing some central way for
   people to discover what results are out there for them to look at
   for a given kernel in the different systems?

 - Should we start carrying config fragments upstream designed to
   support testing, things like the distro config fragments that keep
   getting discussed are one example here but there's other things like
   collections of debug options we could be looking at.  Should we be
   more generally slimming defconfigs and moving things into fragments?

and there's always the the perennial ones about what people would like
to see testing for.