Hi Ben, On 26/02/25 19:11, Ben Hutchings wrote:
This shouldn't go in a linux-headers package, because we aim to support cross-builds of modules. If it doesn't depend on the kernel configuration (aside from CONFIG_RUST being enabled) then it belongs in linux-kbuild. Ben.
It does indeed depend on the configuration, because at least some abstractions are enabled via the configuration and different metadata will be produced depending on whether they are or not (Miguel should confirm this, but I'm pretty sure about it). The first example that comes to my mind is the firmware abstractions, which are already in stable. So it can't go in linux-kbuild, and if it can't go in linux-headers either then it needs a new package.