[Ksummit-2012-discuss] [ATTEND] stable kernel stuff and grumpy maintainers [bisection/rebase/-next]

[Glauber Costa]

On 06/19/2012 09:48 PM, Steven Rostedt wrote:
> On Tue, 2012-06-19 at 12:38 -0500, Jason Wessel wrote:
>
>> Are you saying that patchcheck can check a single patch for the scope
>> of what it changed and potentially output all the KCONFIG options that
>> affect any macro definition changes or ifdefs in the code and generate
>> a complete series of X number of kernels to compile to prove you
>> didn't break anything?
>
> Sorry, I didn't say that ;-)

The thing is, although there is of course value in ktest.pl, specially 
in very long series where it is easy to miss something in the middle, 
most of the breakages comes from setups which are outside of your config 
realm.

But the real question is, *even* if you came up with such a tool, that 
takes a lot of time to do all that over multiple configs considering the 
average boxes most of us have.

Automated tests on multiple configs are done in linux-next, but by the 
time they reach linux-next, it might be too late. There would be value 
in having a powerful box doing this in a rewindable tree.