Linus Torvalds On Linux 6.8 DRM: "Testing Is Seriously Lacking"

[phoronix]

Phoronix: Linus Torvalds On Linux 6.8 DRM: "Testing Is Seriously Lacking"

While the Direct Rendering Manager (DRM) kernel graphics/display driver updates for Linux 6.8 excitingly include the new Intel "Xe" DRM and PowerVR Imagination drivers, AMD color management properties in experimental form, Raspberry Pi 5 graphics support, and more, Linus Torvalds isn't happy with some of the new Intel Xe driver code...

https://www.phoronix.com/news/Torvalds-Unhappy-Linux-6.8-DRM

[bug77]

Linus is just nitpicking. Jeez, now code has to compile...

/s

[Hazel]

Linus is getting soft with the age.

Linus come on, you were the boss.

[Kjell]

Linux is used by largest corporations in the world yet it lacks automation..

I wonder when the main repository will migrate away from the ancient Mailing List and add proper CI/CD to evaluate performance metrics and build status?

Why delay the inevitable? It can't be like this forever. It's stubborn and a waste of time to hang on to the current setup.

[spicfoo]

Linux is used by largest corporations in the world yet it lacks automation..

I wonder when the main repository will migrate away from the ancient Mailing List and add proper CI/CD to evaluate performance metrics and build status?

Why delay the inevitable? It can't be like this forever. It's stubborn and a waste of time to hang on to the current setup.

Why don't you suggest this brilliant idea in their mailing list? They are friendly and welcoming to ideas like this and will totally not tell you: Talk is cheap. Show me the code

[blackshard]

Well, he's right... pushing non compiling code and an #include of .c file demonstrate rush in doing things. It is also quite irrespectful for the kernel maintainers that should review them because it wastes their time.

[skeevy420]

Linux is used by largest corporations in the world yet it lacks automation..

I wonder when the main repository will migrate away from the ancient Mailing List and add proper CI/CD to evaluate performance metrics and build status?

Why delay the inevitable? It can't be like this forever. It's stubborn and a waste of time to hang on to the current setup.

Well, the problem isn't that Linux lacks automation, it's that Intel seems to lack any automation or testing before they send their stuff out to Linus for review. Apparently, they couldn't even be bothered compile their patches before they sent them out. That's ignoring them not following the kernel's programming standards...Something, something, Rust would have caught that, Sieg Rust...

[Etherman]

Linux is used by largest corporations in the world yet it lacks automation..

Whatever.

[Mangogeddon]

The kernel does have a significant amount of automation around CI testing. Most of this tests stuff that's already in various kernel branches for regressions. However, subsystem maintainers are largely trusted with testing their own code prior to it getting merged into Linus' branch (where it would be tested by CI and Linus himself). AMD/Freedesktop has a CI farm of their own and support for this was merged into 6.6. The issue seems to be that Intel isn't testing their own contributions to the kernel, which is a REALLY bad look for them.

[Doomer]

Linux is used by largest corporations in the world yet it lacks automation..

I wonder when the main repository will migrate away from the ancient Mailing List and add proper CI/CD to evaluate performance metrics and build status?

Why delay the inevitable? It can't be like this forever. It's stubborn and a waste of time to hang on to the current setup.

some people are investing in it, see this for example : https://foundation.kernelci.org/ or this https://inria.hal.science/hal-02342130
both are very interesting and I'm sure there are more out there