From 98ca252e5603d2200f50ef5c29ddc298da299385 Mon Sep 17 00:00:00 2001 From: Adam Blank Date: Mon, 29 Sep 2025 09:16:33 +0200 Subject: [PATCH] kernel-dev/common.rst: fix the in-tree defconfig description The description of the relation between KBUILD_DEFCONFIG and SRC_URI is reversed. In fact it is the SRC_URI provided defconfig which will be dropped by the kernel-yocto class if both are provided. (From yocto-docs rev: a808420655a0976ba08f013f468cf80f379b1d89) Signed-off-by: Adam Blank Signed-off-by: Antonin Godard Signed-off-by: Richard Purdie --- documentation/kernel-dev/common.rst | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/documentation/kernel-dev/common.rst b/documentation/kernel-dev/common.rst index 654c4e0a01..bd6c3fb2cf 100644 --- a/documentation/kernel-dev/common.rst +++ b/documentation/kernel-dev/common.rst @@ -650,13 +650,9 @@ the Broadcom 2708/2709 chipset:: KBUILD_DEFCONFIG:raspberrypi2 ?= "bcm2709_defconfig" -Aside from modifying your kernel recipe and providing your own -``defconfig`` file, you need to be sure no files or statements set -:term:`SRC_URI` to use a ``defconfig`` other than your "in-tree" file (e.g. -a kernel's ``linux-``\ `machine`\ ``.inc`` file). In other words, if the -build system detects a statement that identifies an "out-of-tree" -``defconfig`` file, that statement will override your -:term:`KBUILD_DEFCONFIG` variable. +If the build system detects a statement that identifies an "out-of-tree" +``defconfig`` file, your :term:`KBUILD_DEFCONFIG` variable will take precedence +over it. See the :term:`KBUILD_DEFCONFIG`