Subject: Re: linux-next: left over things in linux-next after 2.6.28-c1

From: Sam Ravnborg <[email-masked]>
Date: Sat, 25 Oct 2008 23:52:45 +0200

On Sat, Oct 25, 2008 at 02:16:51PM -0700, Greg KH wrote:
> On Sat, Oct 25, 2008 at 04:37:15PM +0200, Sam Ravnborg wrote:
> > > tests
> > > 
> > > 	Ananth N Mavinakayanahalli (7):
> > > 	      Add tests/ directory
> > > 	      Move locking selftests to tests/
> > > 	      Move rcutorture to tests/
> > > 	      Move rtmutex tester to tests/
> > > 	      Move lkdtm to tests/
> > > 	      Move kprobes smoke tests to tests/
> > > 	      Move backtrace selftests to tests/
> > 
> > I have almost given up on this.
> > Three merge attemps failed for different reasons,
> > and I will not even have time for my maintainership
> > duties the next months.
> > 
> > Anyone that can bring it forward?
> 
> What are the reasons this is failing?  Is it just moving different files
> around into the tests/ directory?  Or is it new functionality here?
> 
> If just moving stuff, is that really needed?

The incentive was to have a common place to add small tests that
could be used to verify that the kernel works as expected.
>>From inkernel modules (like rcutorture) to small userspace
utilities such as something massaging the epoll interface or
similar.

The above was just to get it started.

Having a set of tests to run when introducing a new syscall
would make it much easier for an arch maintainer to verify
that the implemented syscall works as expected.

And forcing the developer to use the interface from user-space
will hopefully catch a few issues earlier.

	Sam