There have been a number of presentations over the years where various folks (including Greg) have advocated that people and companies should commit to aggressively tracking and moving forward to get the latest fixes and security updates.
The LTS story on kernel.org reflects that. Gone is the 6 year LTS. 6.12 is just 2 years of support. There is a long list of kernels going end of life in Dec of 2026. Companies are not at that point in time where they have to face that face that the time it takes to develop a product barely can get something out and shipping before an LTS would be end of life. It's reality. This especially impacts those shipping Linux in an embedded embodiment as compared to something disto based.
So unless a company can take on the engineering to track the kernel, test, re-qualify their kernel (and potentially other software change) and then ship, they're in a situation where they're going to have to hire someone else to pick up where the community left off. It is not an easy task.
Thankfully in like the Arm space companies like Linaro do this. (and do it well) Ok great, but is this good for the universe? Do we in the kernel community want to empower commercial LTS instead of having a solid community driven LTS?
I do wonder if within the community we should be thinking of a better way to maintain an LTS instead of how it's done today. Doing an LTS is hard, pulling together the patches, a lot of testing, etc it takes a team of smart people to do it well.
And yes I know about CIP, they are not a project I recommend due to the fact that they do not follow the same LTS conventions that kernel.org established. For instance they back port functionality. They are not a general purpose kernel. CIP also does not do extensive testing across a wide variety of hardware like LTS does. CIP has its place, it's just not a general purpose LTS solution.