Description
The upstream kernel community is where active kernel development happens but the majority of kernels deployed do not come directly from upstream but distributions. "Distribution" here can refer to a traditional Linux distribution such as Debian or Gentoo but also Android or a custom cloud distribution. The goal of this Microconference is to discuss common problems that arise when trying to maintain a kernel.
Expected topics
Backporting kernel patches and how to make it easier
Consuming the stable kernel trees
Automated testing for distributions
Managing ABIs
Distribution packaging/infrastructure
Cross distribution bug reporting and tracking
Common distribution kconfig
Distribution default settings
Which patch sets are distributions carrying?
More to be added based on CfP for this microconference
"Distribution kernel" is used in a very broad manner. If you maintain a kernel tree for use by others, we welcome you to come and share your experiences.
If you are interested in participating in this microconference and have topics to propose, please use the CfP process. More topics will be added based on CfP for this microconference.
MC lead
Laura Abbott labbott@redhat.com
We'd like to spend a few minutes to provide some background around how we're using Yocto to produce kernel builds as well as bigger images that contain userspace as well, and then try to address some of the issues we're seeing with this process.
There are a few topics we'd like to discuss with the room:
- Using a single kernel branch for multiple, very different projects?
- Working with...
The Kernel's API and ABI exposed to Kernel modules is not something that is usually maintained in upstream. Deliberately. In fact, the ability to break APIs and ABIs can greatly benefit the development. Good reasons for that have been stated multiple times. See e.g. Documentation/process/stable-api-nonsense.rst.
The reality for distributions might look different though. Especially - but not...
While kernelci.org as a project is dedicated to testing the
upstream Linux kernel, the same KernelCI software may be reused
for alternative purposes. One typical example is distribution
kernels, which often track a stable branch but also carry some
extra patches and a specific configuration. Aside from covering
a particular downstream branch, having a separate KernelCI
instance also makes it...