tjh.dev / kernel
Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

Documentation/process: maintainer-soc: Document purpose of defconfigs

Common mistake in commit messages of patches on mailing list adding
CONFIG options to arm/multi_v7 or arm64/defconfig is saying what that
patch is doing, e.g. "Enable driver foo". That is obvious from the diff
part, thus explaining it does not bring any value. What brings value is
to understand why "driver foo" should be in a shared, upstream
defconfig, especially considering that distros have their own defconfigs
and we do not care about non-upstream trees.

Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Link: https://lore.kernel.org/r/20260413074401.27282-4-krzysztof.kozlowski@oss.qualcomm.com
Signed-off-by: Arnd Bergmann <arnd@arndb.de>

authored by

Krzysztof Kozlowski and committed by
Arnd Bergmann 8b0beb45 f325b239

+10
+10
Documentation/process/maintainer-soc.rst
··· 207 207 a signed tag, rather than a branch. This tag should contain a short description 208 208 summarising the changes in the pull request. For more detail on sending pull 209 209 requests, please see Documentation/maintainer/pull-requests.rst. 210 + 211 + Defconfigs purpose 212 + ~~~~~~~~~~~~~~~~~~ 213 + 214 + Defconfigs are primarily used by the kernel developers, because distros have 215 + their own configs. A change adding new CONFIG options to a defconfig should 216 + explain why the kernel developers in general would want such option, e.g. by 217 + providing a name of an upstream-supported machine/board using that new option. 218 + This implies that enabling options in defconfig for non-upstream machines shall 219 + not be accepted.