diff options
| -rw-r--r-- | documentation/kernel-dev/common.rst | 10 |
1 files 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:: | |||
| 650 | 650 | ||
| 651 | KBUILD_DEFCONFIG:raspberrypi2 ?= "bcm2709_defconfig" | 651 | KBUILD_DEFCONFIG:raspberrypi2 ?= "bcm2709_defconfig" |
| 652 | 652 | ||
| 653 | Aside from modifying your kernel recipe and providing your own | 653 | If the build system detects a statement that identifies an "out-of-tree" |
| 654 | ``defconfig`` file, you need to be sure no files or statements set | 654 | ``defconfig`` file, your :term:`KBUILD_DEFCONFIG` variable will take precedence |
| 655 | :term:`SRC_URI` to use a ``defconfig`` other than your "in-tree" file (e.g. | 655 | over it. |
| 656 | a kernel's ``linux-``\ `machine`\ ``.inc`` file). In other words, if the | ||
| 657 | build system detects a statement that identifies an "out-of-tree" | ||
| 658 | ``defconfig`` file, that statement will override your | ||
| 659 | :term:`KBUILD_DEFCONFIG` variable. | ||
| 660 | 656 | ||
| 661 | See the | 657 | See the |
| 662 | :term:`KBUILD_DEFCONFIG` | 658 | :term:`KBUILD_DEFCONFIG` |
