On Tue, May 05, 2015 at 02:12:01PM -0600, Jens Axboe wrote: > We can't merge the NVMe bits until the proposal is included/finalized. But > this is a problem. I don't want to add this to the Facebook kernel until we > know the API is stable, while I have no problem adding experimental NVMe > changes since those can be easily updated without impacting applications. > The latter is not true for the user interface. They might never be finalized, and even if they are mere mortals might never get this hardware. Merging infrastructure without any users is a bad idea in general, and merging infrastructure with no user that exposes untestable user interface and bloats core data structures is even worse. I don't think this has any merit at all at this point. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
