[lkml]   [1998]   [Aug]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.1.118 Tons of oopes
Richard Gooch wrote:
> David S. Miller writes:
> >
> > you talk too much and don't spend enough time listening to what people
> > are saying to you...
> 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.

Because Linus said so.

It is sort of like when a teenager asks their parent for permission
to do something, and the parent says "No". The teenager asks why not?
The answer is "Because I said so."

> 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.

Does it necessarily have to have a definite purpose?

Hold on here comes the conspiracy theories. The Linux version of
the X-Files. Brought to you by the Bud Lite Penguin.

> 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....

Terry L. Ridder
Blue Danube Software (Blaue Donau Software)
"We do not write software, we compose it."

When the toast is burnt
and all the milk has turned
and Captain Crunch is waving farewell
when the Big One finds you
may this song remind you that they
don't serve breakfast in hell

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:44    [W:0.129 / U:2.344 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site