Behold, a Linux maintainer openly admitting to attempting to sabotage the entire Rust for Linux project:

https://lwn.net/ml/all/[email protected]/

The good news is this doesn’t affect drm/asahi, our GPU driver. The bad news is it does affect all the other drivers we’re (re)writing in Rust, two so far with a third one coming.

Another choice quote, calling R4L “cancer”: https://lore.kernel.org/lkml/[email protected]/

Personally, I would consider this grounds for removal of Christoph from the Linux project on Code of Conduct violation grounds, but sadly I doubt much will happen other than draining a lot of people’s energy and will to continue the project until Linus says “fuck you” or something.

As for how to move forward, if I were one of the Rust maintainers, I would just merge the patch (which does not touch code formally maintained by the dissenter). Either Linus takes the pull, and whatever Christoph says is irrelevant, or he doesn’t, and R4L dies. Everything else is a waste of everyone’s time and energy.

Edit: Sent in my 2 cents: https://lore.kernel.org/rust-for-linux/[email protected]/T/#m1944b6d485070970e359bbc7baa71b04c86a30af

  • BatmanAoD@programming.dev
    link
    fedilink
    arrow-up
    4
    ·
    1 day ago

    But…that’s exactly what’s happening. Rust is already in the kernel, with both Linus’s and GKH’s approval. CH is trying to singlehandedly reject any use of Rust in any part of the kernel where he has maintainer status. That’s pretty specific to R4L.

    • Lvxferre [he/him]@mander.xyz
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      19 hours ago

      But…that’s exactly what’s happening

      Well, then based on what you guys (specially you) are saying, it’s old man screaming at cloud. Torvalds and/or Kroah-Hartman* will likely need to intervene, since as you said they approved it; this drama Martin is doing in social media is pretty much pointless.

      And if there’s a violation in the CoC it has zero to do with what he says (calling the R4L project “cancer”); it’s about obstructing other developers.

      I also just catch something from the post I didn’t notice before:

      As for how to move forward, if I were one of the Rust maintainers, I would just merge the patch

      Martin isn’t even relevant! He’s just for the popcorn, like the rest of us! Free kernel development popcorn!

      *speaking on Kroah-Hartman, do those changes proposed by the project affect the stable branch now?