This change affects all in-house drivers that people have written,
it's not limited to drivers shipped with the kernel.
Now, you talk about making "bad decisions". What exactly do you mean
by that? Is your intention that you want people to see the breakage,
look in the sources and figure out what flush() is used for and
determine whether they need to implement it? If so, I don't think
you'll get that effect. I think most driver writers will think "oh,
another optional VFS method: I'll just put NULL here".
Also, where is this new method documented (what it does and why you
need it)?
People with binary-only drivers will have breakage either way with
this change.
People with source code access will now have to edit their drivers
rather than just recompiling. They have to recompile anyway. But why
must they edit their source?
I don't see what the "benefit" to this intentional breakage is. I
don't see a situation where it improves anything.
Regards,
Richard....
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html