|
|
Subscribe / Log in / New account

The imminent stable-version apocalypse

The imminent stable-version apocalypse

Posted Feb 5, 2021 16:44 UTC (Fri) by willy (subscriber, #9762)
Parent article: The imminent stable-version apocalypse

I suggest saturating at KERNEL_VERSION at xxxxFF.

Code which needs to care about versions after 255 can check LINUX_VERSION_SUBLEVEL directly.


to post comments

The imminent stable-version apocalypse

Posted Feb 5, 2021 17:52 UTC (Fri) by mchehab (subscriber, #41156) [Link] (1 responses)

> I suggest saturating at KERNEL_VERSION at xxxxFF.

That seems to be the best thing to be done.

Without that, media applications will break, as they several of them rely at the Kernel version in order to enable some features:

drivers/media/cec/core/cec-api.c: caps.version = LINUX_VERSION_CODE;
drivers/media/mc/mc-device.c: info->media_version = LINUX_VERSION_CODE;
drivers/media/v4l2-core/v4l2-ioctl.c: cap->version = LINUX_VERSION_CODE;
drivers/media/v4l2-core/v4l2-subdev.c: cap->version = LINUX_VERSION_CODE;

The imminent stable-version apocalypse

Posted Feb 5, 2021 20:24 UTC (Fri) by nix (subscriber, #2304) [Link]

So does glibc, but thankfully it never compares the LINUX_VERSION_CODE against 4.10.x or 4.5.x. Phew, dodged a bullet.

The imminent stable-version apocalypse

Posted Feb 5, 2021 19:43 UTC (Fri) by tglx (subscriber, #31301) [Link]

> I suggest saturating at KERNEL_VERSION at xxxxFF.

Yes. And the commit message of x.x.x.255 wants to be:

This kernel has been finally stapled to death. Move on.


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds