You are not logged in.
Pages: 1
From today's edition of The Register:
------------------------------------------------------------------------------------------------------
Intel and AMD engineers rush to save Linux 6.13 after dodgy Microsoft tweak
'Let's not do this again please'... days before release date
------------------------------------------------------------------------------------------------------
By Richard Speed - Tue 14 Jan 2025 // 14:02 UTC
See https://www.theregister.com/2025/01/14/ … ge_pulled/
Microsoft is notable for dubious quality control standards regarding releases of its flagship operating system, Windows. That one of its engineers should drop some dodgy code into the Linux kernel is not hugely surprising, and the unfortunate individual is not the first and will not be the last to do so, regardless of their employer.
Seems that something went very (very) wrong ...
Best,
A.
Offline
Microcrap employee dumps garbage code into the linux kernel.......just wondering who did it, perhaps somebody with the initials L.P. ?
https://sourceforge.net/projects/vuu-do/ New Vuu-do isos uploaded January 2025!
Vuu-do GNU/Linux, minimal Devuan-based openbox systems to build on, maximal versions if you prefer your linux fully-loaded.
New Devuan-mate-mini isos too!
Please donate to support Devuan and init freedom! https://devuan.org/os/donate
Offline
perhaps somebody with the initials L.P. ?
Perhaps somebody with the initials L.T. ?
Offline
Here's the kernel thread :
https://lore.kernel.org/lkml/2024102316 … ernel.org/
Of the comments, Borislav Petkov reveals the underlying concern and emerging challenge :
I just love it how this went in without a single x86 maintainer Ack, it broke
a bunch of things and then it is still there instead of getting reverted.Let's not do this again please.
--
Regards/Gruss,
Boris.
We could do with a bit more of the old L.T. management style verbally smacking younglings doing dumb things. Boris was too kind.
Cheers,
--K
Offline
Hello:
... old L.T. management style verbally smacking younglings doing dumb things.
While I agree, it is not the solution.
What failed here was management.
-> Big -> Time -> Fail
... went in without a single x86 maintainer Ack ...
... still there instead of getting reverted.
Uncanny.
Coming from where it came from, I think this was a test to see what would happen if ...
The response must be swift and ruthless.
ie:
The 'unfortunate individual' should be banned from the Linux team.
Permanently.
There is far too much at risk to do anything else.
Of course, YMMV.
Best,
A.
Offline
They won't boot out a developer who works for one of the big paymasters...
https://www.linuxfoundation.org/about/members
Quality control was never that great however...
Offline
Pages: 1