LKP FAQ

Contents

• General Questions
  • How to request testing a new kernel tree on LKP
  • Is there a way not to trigger kbuild tests on a specific branch
  • How is one meant to act on W=1 reports like [-Wmissing-prototypes]

General Questions

How to request testing a new kernel tree on LKP

LKP monitors and tests various kernel trees, if you want lkp to test your kernel tree, please send a request to lkp@intel.com or create a pull request on this repo. The configurations are managed at repo/linux, and the introduce is at Repo Spec.

Is there a way not to trigger kbuild tests on a specific branch

LKP maintains the configurations for each Repo, there's a item named "branch_denylist" which defines the branches to be denied for testing, and details can be found in Repo Spec, besides, if you want to disable a branch quickly, please use the following naming conventions when pushing branches: ".*experimental.*" or ".*dont-build".

How is one meant to act on W=1 reports like [-Wmissing-prototypes]

Thanks Nick Desaulnier for providing the explanation.

make W=1 enabled -Wmissing-prototypes via scripts/Makfile.extrawarn.

Both GCC and Clang will warn for -Wmissing-prototypes when you define a function without a previous declaration of it, for non-static functions. If the linkage is extern, and there was no previous declaration, then callers may have the wrong signature. Mostly, this isn't a bug, which is why it's not an error. But sometimes the signature has changed but the callers have not been updated, which is an ABI breakage resulting in a bug. Mostly this is not an issue due to -Wimplicit-function-declaration being on by default, which also helps in this case.

See: https://godbolt.org/z/aYrYfS

Functions with external linkage should have a forward declaration, or be marked static if in a .c file, or be marked static inline if in a header file.

See Also:

https://github.com/intel/lkp-tests/blob/master/doc/faq.md