I didn't mention non-source drivers. To be clear: I'm talking about
drivers where the source is available to those who use it, yet not
shipped with the kernel. PCMCIA is just one example. There must be
many in-house drivers people have developed to work with some
specialised hardware they have built or bought. They have source code
access to these drivers of course.
> Perhaps you consider silent total failures acceptable.
Definately not! But if flush() was appended to the structure, then
people had only to recompile their drivers and all would be fine. So
there would be no silent failures in that scheme.
The other scenario is where people only have binary modules
available. These will break *either way* with structure changes.
So please explain where the benefit of placing flush() in the middle
is?
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