Do that, and we will stagnate.
> Does it mean, no userland ABI changes, but API changes affecting onto
> the kernel are ok?
That sounds acceptable to me.
But maybe I'm just biased, as I'm looking to start backporting some of
the USB 2.5 changes to 2.4 to fix real bugs that are in 2.4. This will
require changing kernel apis. And in doing so, fixing up all of the
in-kernel usages of that api will happen.
In doing this, it just enforces the fact that it really matters if you
have a in-kernel driver or not. If you want to keep a driver or any
other kernel code outside of the main tree, it is costly, both in time
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/