The thing is, every new kernel project should start small and should aim for constant stability.
Dropping a large amount of code on upstream with a large amount of open problems means the project has been done wrong from the get go.
If a project starts small in the upstream kernel, it is not a problem at all to have a constant flow of updates - as long as they are stabilized and are merged in the merge window only. That's how the kernel evolves, gradually.
A project that is in a constant state of breakage makes little sense.
Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds