Re: [LTP] [PATCH] Create policy for testing unstable kernel features

[Petr Vorel <pvorel@suse.cz>]

Hi all,

...
> > +7 Testing pre-release kernel features
> > +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > +
> > +Tests for features not yet in a mainline kernel release are accepted.
> > However
> > +they must only be added to the +staging+ runtest file. Once a feature is
> > part
> > +of the stable kernel ABI the associated test must be moved out of staging.
> > +
> > +This is primarily to help test kernel RCs by avoiding the need to download
> > +separate LTP patchsets.
> > diff --git a/runtest/staging b/runtest/staging
...

FYI keyctl09 [1] patch is a candidate for merging under this policy.

Cyril wasn't sure [2] that we haven't agreed yet about how this should be
handled. Not sure what exactly is he missing.

I guess the description is quite open to allow testing both tests in next tree
or even in maintainer tree (before endup in next tree). From my point it should
be obvious that not *anything* out of mainline can be added, just tests which
sooner or later endup in mainline (and if not, they should be deleted).

Also procedure after release is pretty clear: just move everything out of
staging to expected runtest files (mostly syscalls).

=> I'd merge this.

Kind regards,
Petr

[1] https://patchwork.ozlabs.org/project/ltp/patch/20220223200731.1859670-1-yaelt@google.com/
[2] https://lore.kernel.org/ltp/YiC4Pj1sH8UIHY7k@yuki/

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp