These kernel releases are not hosted at kernel.org and kernel developers can provide no support for them. It is easy to tell if you are running a distribution kernel.
The following manuals are written for users of the kernel — those who are trying to get it to work optimally on a given system and application developers seeking information on the kernel’s user-space APIs.
Kernel.org accounts are usually reserved for subsystem maintainers or high-profile developers. It is absolutely not necessary to have an account on kernel.org to contribute to the development of the Linux kernel, unless you submit pull requests directly to Linus Torvalds.
The maintainers of the various kernel subsystems — and also many kernel subsystem developers — expose their current state of development in source repositories.
This is the beginning of a section with information of interest to application developers and system integrators doing analysis of the Linux kernel for safety critical applications.
The kernel code base is logically broken down into a set of subsystems: networking, specific architecture support, memory management, video devices, etc. Most subsystems have a designated maintainer, a developer who has overall responsibility for the code within that subsystem.
RISC-V Kernel Boot Requirements and Constraints Boot image header in RISC-V Linux Virtual Memory Layout on RISC-V Linux RISC-V Hardware Probing Interface arch/riscv maintenance guidelines for developers RISC-V Linux User ABI Vector Extension Support for RISC-V Linux Concurrent Modification and Execution of Instructions (CMODX) for RISC-V Linux
The Per-CPU Pagesets are a vital mechanism in the kernel’s memory management system. By handling most frequent allocations and frees locally on each CPU, the Per-CPU Pagesets improve performance and scalability, especially on systems with many cores.
You can determine if your kernel currently has firmware loader support by looking for the CONFIG_FW_LOADER definition on your kernel’s .config file. In addition to having the firmware_class support in your kernel, you must also have a working userspace infrastructure configured.
