Re: merging new drivers (was Re: 2.6.18 -mm merge plans)

[Andi Kleen <ak@suse.de>]

Chris Wright <chrisw@sous-sol.org> writes:

> * Arjan van de Ven (arjan@infradead.org) wrote:
> > On Mon, 2006-06-05 at 11:32 +0100, Alan Cox wrote:
> > > It isn't just drivers. Xen has the same problem.
> > 
> > Xen has many problems. This is not nearly their biggest ;)
> 
> What is the biggest, or even top 3 or 5?  I've a todo list of some

I would say the biggest is that things haven't gotten submitted
for so long and aren't not resubmitted quickly.

e.g. Xen code needs a lot of arch/* cleanups in small patches that should
be just submitted, fixed, resubmitted quickly.  Many of them
could be already merged.

For example Jan Beulich has been sending many of the cleanups he 
needed for x86-64/i386 Xen immediately and at least for x86-64 
I merged most of them. If the other things were submitted
earlier a lot of it could be already merged too.

Then Xen net/block/char etc. drivers should be submitted to the
respective maintainers independently (they are useful even without the
rest of Xen in HVM guests)

> 140-odd entries which are being worked on.  It's slow and tedious,
> but in progress. 

What I would do is to concentrate on the small cleanup patches first
and post them as soon as you fix them. I think a lot of them were
actually ok without changes. Then bigger stuff piece by piece. You
don't need to wait to fix everything first.

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/