upvote
As a long time desktop and server user, why do I look at changelogs...

New filesystems and major changes to existing ones (large performance improvements, new features like adding better compression standards which I now know I can use, fixes to long-standing bugs which open new use cases).

New protocols like wireguard when it was new and exciting (still is now that I think of it). When that was mainlined, I knew I had some network rearchitecting to do.

New device drivers like amdgpu when it was massive news. Less so these days since most hardware is well supported, and I don't buy the absolute latest.

New kernel APIs which I can use in my programs — like landlock, when it was merged I knew it was time to improve sandboxing in some of my stuff.

Though LWN and kernel newbies do it best, already linked by others.

reply
It's a well-formatted changelog of the most salient features of the release. Linus doesn't provide one apart from a list of added commits and merged branches, which isn't very useful unless you are a kernel developer.
reply
This isn't quite right.

This is a well-formatted changelog of the changes that Igalia has contributed to the release, AFAICT.

KernelNewbies publishes a much more general summary of changes (it is much longer than this one).

https://kernelnewbies.org/LinuxChanges

https://kernelnewbies.org/LinuxVersions

reply
What great resource thank you !

This new thing is pretty cool :

    =USB4STREAM for streaming data with USB4=

    In addition to Thunderbolt networking, which was already supported, this release adds support for streaming data directly over a cable as well (USB4STREAM). It is very simple and basically just transfers raw packets from one host to another. The driver exposes /dev/tbstreamX devices on each side of the link that can be used to transfer data using regular filesystem operations such as read(2) and write(2):

    host1 # cat /dev/tbstream0
    host2 # echo hello > /dev/tbstream0

    This can be useful in cases where network tooling is not available or just for existing applications like dd and cat that do not support sockets. This feature can be used at the same time with thunderbolt_net so they don't rule each other out, and it allows multiple streams to be created.
reply
It only covers changes made by Igalia devs. For a more general changelog I’d recommend the LWN articles:

https://lwn.net/Articles/1078068/ https://lwn.net/Articles/1078539/

reply
deleted
reply
ty for the context. I was not aware of the Linux dev ecosystem.
reply
I think it is mostly "marketing" for Igalia's services. If you want to pay people to do "stuff" in Linux and adjacent projects like Mesa, Igalia seems very competent.
reply
hi audience, we know about this stuff you use on a daily basis, you may be interested in our executive summary of the latest release of the stuff
reply
I don't think there is much too it, it's a consulting firm. Would you hire a consulting firm with an empty tech blog portifolio? It's ticking a box, it's stating it's a consulting firm in tech, that it's target audience are companies with Linux machines etc...
reply
ty. so very narrow audicence it seems.

Per @sph, as Linus provide no changelog, seems like the firm is putting it together for others

reply
I for one am excited about HDMI 2.1 support on AMD.
reply
It's more than that: free and open support for HDMI 2.1 in general. Previously it was only proprietary implementations that didn't leak the spec which were allowed. AMD is just the only one that has really good open source drivers which can benefit from it, and didn't work around the problem by converting HDMI to DisplayPort in a proprietary on-board GPU chip.
reply
OK, now this is what I wanted to know as well. I was not aware that changelogs show all this inf.

ty for sharing

reply
deleted
reply