The best of Linus Torvalds

I'm too lazy to bother to look in my lkml email archives, but whoever said "The simple version is just a static array of [NR_CPUS] cpumask_t's." and then implemented this piece of shit is a complete and utter moron. I'm sorry, but guys, I really expect people to have better taste than this, and also expect people to be able to _think_ better than this.

So just reverting it from stable, *WITHOUT LEARNING THE LESSON*, is not a no-op at all, it's a sign of being a f*cking moron. I'm stupider for just reading your email. Go away.

In short: just say NO TO DRUGS, and maybe you won't end up like the Hurd people.

Once you realize that documentation should be laughed at, peed upon, put on fire, and just ridiculed in general, THEN, and only then, have you reached the level where you can safely read it and try to use it to actually implement a driver.

I also claim that Slashdot people usually are smelly and eat their boogers, and have an IQ slightly lower than my daughters pet hamster (that's "hamster" without a "p", btw, for any slashdot posters out there. Try to follow me, ok?). [...] Finally, it's clear that I'm not only the smartest person around, I'm also incredibly good-looking, and that my infallible charm is also second only to my becoming modesty. So there. Just to clarify. Linus "bow down before me, you scum" Torvalds

Modern PCs are horrible. ACPI is a complete design disaster in every way. But we're kind of stuck with it. If any Intel people are listening to this and you had anything to do with ACPI, shoot yourself now, before you reproduce.

[on the GNOME usability mailing list] Please, just tell people to use KDE.

I like colorized diffs, but let's face it, those particular color choices will make most people decide to pick out their eyes with a fondue fork. And that's not good. Digging in your eye-sockets with a fondue fork is strictly considered to be bad for your health, and seven out of nine optometrists are dead set against the practice. So in order to avoid a lot of blind git users, please apply this patch.

Or just get rid of emacs. Your problem has nothing to do with git, and everything to do with emacs. And then you have the _gall_ to talk about "unix design" and not gumming programs together, when you yourself use the most gummed-up piece of absolute sh*t there is!

Standards are paper. I use paper to wipe my butt every day. That's how much that paper is worth.

[just click the link]

I mean, really? Anybody who writes code like that, or any compiler where that "control_dependency()" marker makes any difference what-so-ever for code generation should just be retroactively aborted.

Of course, I'd also suggest that whoever was the genius who thought it was a good idea to read things ONE F*CKING BYTE AT A TIME with system calls for each byte should be retroactively aborted. Who the f*ck does idiotic things like that? How did they noty die as babies, considering that they were likely too stupid to find a tit to suck on?

Christ, people. Learn C, instead of just stringing random characters together until it compiles (with warnings). This: static bool rate_control_cap_mask(struct ieee80211_sub_if_data *sdata, struct ieee80211_supported_band *sband, struct ieee80211_sta *sta, u32 *mask, u8 mcs_mask[IEEE80211_HT_MCS_MASK_LEN]) is horribly broken to begin with, because array arguments in C don't actually exist. Sadly, compilers accept it for various bad historical reasons, and silently turn it into just a pointer argument. There are arguments for them, but they are from weak minds. [...] Then it got moved and turned from "confused but happens to generate correct code" into "buggy pile of bovine manure".

I call BS. Let me be very clear. I'm not applying that shit-for-brains stupid patch, and will not be pulling it unless somebody tricks me into it. [...] This whole "I have mounted important filesystems" is just pure and utter garbage. Stop pushing this shit.

First off, I'd suggest printing out a copy of the GNU coding standards, and NOT read it. Burn them, it's a great symbolic gesture. [...] Tabs are 8 characters, and thus indentations are also 8 characters. There are heretic movements that try to make indentations 4 (or even 2!) characters deep, and that is akin to trying to define the value of PI to be 3. [...] Heretic people all over the world have claimed that this inconsistency is ... well ... inconsistent, but all right-thinking people know that (a) K&R are _right_ and (b) K&R are right. [...] To call a global function "foo" is a shooting offense. [...] Encoding the type of a function into the name (so-called Hungarian notation) is brain damaged - the compiler knows the types anyway and can check those, and it only confuses the programmer. No wonder MicroSoft makes buggy programs. [...] If you are afraid to mix up your local variable names, you have another problem, which is called the function-growth-hormone-imbalance syndrome. [...] (in fact, they are worse than random typing - an infinite number of monkeys typing into GNU emacs would never make a good program)