Slashdot Mirror


How New, Polite Linus Torvalds Points Out Bad Kernel Code (phoronix.com)

Linus Torvalds "has shown already for the new Linux 4.20~5.0 cycle he isn't relaxing his standards but is communicating better when it comes to bringing up coding," reports Phoronix, adding "So far it looks like Linus' brief retreat is paying off with still addressing code quality issues -- and not blatantly accepting new code into the kernel as some feared -- but in doing so in a professional manner compared to his past manner of exclaiming himself over capitalized sentences and profanity that at time put him at odds with some in the Linux kernel community."

AmiMoJo quotes their report: Last Saturday he took issue with the HID pull request and its introduction of the BigBen game controller driver that was introduced: the developer enabled this new driver by default. Linus Torvalds has always frowned upon random new drivers being enabled by default in the kernel configuration driver. [H]e still voiced his opinion over this driver's default "Y" build configuration, but did so in a more professional manner than he has done in the past:

We do *not* enable new random drivers by default. And we most *definitely* don't do it when they are odd-ball ones that most people have never heard of.

Yet the new "BigBen Interactive" driver that was added this merge window did exactly that.

Just don't do it.

Yes, yes, every developer always thinks that _their_ driver is so special and so magically important that it should be enabled by default. But no. When we have thousands of drivers, we don't randomly pick one new driver to be enabled by default just because some developer thinks it is special. It's not.... Please don't do things like this.

Phoronix also describes another "kernel oops" testing Torvalds' patience, in which Linus responded tactfully that "What makes me *very* unhappy about this is that if I'm right, I think it means that code was literally not tested at all by anybody who didn't have one of the entries in that list."

6 of 370 comments (clear)

  1. #savelinus by NicknameUnavailable · · Score: 5, Funny

    I miss the old Linus.

    1. Re:#savelinus by Bruce+Perens · · Score: 5, Funny

      Fork him then. Create a web site with "old Linus" responses to every email he sends to the kernel list. Link them appropriately. Make a disclaimer that it's sarcasm. It should be quite a hoot :-)

    2. Re:#savelinus by Anonymous Coward · · Score: 0, Funny

      Google Translate, New Linus -> Old Linus

  2. Re: I can actually hear him gritting his teeth by greenfruitsalad · · Score: 4, Funny

    As the great Sean Connery once said when a book fell on his head: "I have only my shelf to blame."

  3. Re: Still not right by cerberusss · · Score: 3, Funny

    When he finally drops dead you can debate things with his successor all you like.

    Linus will not just "drop dead". He will turn into one of those nasty zombie processes that you can't even kill -9.

    --
    8 of 13 people found this answer helpful. Did you?
  4. Actual text by thegarbz · · Score: 4, Funny

    Oh fuck off. We do *not* enable new random drivers by default. And we most *definitely* don't do it when they are odd-ball ones that most people have never heard of.

    Yet the new "BigBen Interactive" driver that was added this merge window did exactly that.

    Just don't fucking do it.

    Yes, yes, you always thinks that your driver is so special and so magically important that it should be enabled by default. But no. When we have thousands of drivers, we don't randomly pick one new driver to be enabled by default just because some developer thinks they are special. You're not. Don't fucking do things like this.