Look, I am entitled to think differently than you. I've been
listening. It seems to me people haven't listened to my points.
What I don't understand is *why* this flush() method is termed
mandatory (hence the intentional source breakage), and yet in *every*
driver in the 2.1.118 patch it is set to NULL.
So what is the difference between breaking all source and then
inserting NULLs, or appending the new method and taking advantage of
automatic structure initialisation. The only difference I've seen is
that one approach breaks things and requires lots of effort.
Again, if there is some other hidden assumption going on here, I'd
like to know. But *nobody* has explained how the breakage has helped
anything.
It would have been a different matter is a significant proportion of
drivers were modified by the patch to now have real flush()
methods. But that isn't the case: they're all set to NULL. The only
conclusion I can make from this is that flush() is optional for almost
every driver.
No, David, it's not a case of me not listening. It's a case of people
not explaining things clearly. If I'm wrong in flush() being optional,
then there is some hidden assumption.
Maybe the inner circle *does* know some deep dark secret, but *I*
don't know it and it hasn't been made public. In light of this, my
questions are entirely reasonable. Instead of flaming me for pursuing
this, why not come forth with some clearer explanations?
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