[PATCH v3 2/3] doc/buildman: describe using fragments

[Heinrich Schuchardt]

Describe the new --fragments parameter

Reviewed-by: Simon Glass <sjg at chromium.org>
Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt at canonical.com>
---
v3:
	no change
v2:
	new patch
---
 tools/buildman/buildman.rst | 22 ++++++++++------------
 1 file changed, 10 insertions(+), 12 deletions(-)

diff --git a/tools/buildman/buildman.rst b/tools/buildman/buildman.rst
index 07ecc5c110c..ba898cdae5a 100644
--- a/tools/buildman/buildman.rst
+++ b/tools/buildman/buildman.rst
@@ -1126,10 +1126,16 @@ later comparison.
 defconfig fragments
 -------------------
 
-Buildman provides some initial support for configuration fragments. It can scan
-these when present in defconfig files and handle the resuiting Kconfig
-correctly. Thus it is possible to build a board which has a ``#include`` in the
-defconfig file.
+A comma separated list of configuration fragments can be added via the
+--fragments parameter to all processed defconfig files, e.g.
+
+.. code-block:: bash
+
+    buildman -k qemu-riscv64_smode --fragments acpi.config
+
+Buildman also supports configuration fragments that are included in defconfig
+files via an ``#include`` statement. It can scan these and handle the resulting
+Kconfig correctly.
 
 For now, Buildman simply includes the files to produce a single output file,
 using the C preprocessor. It does not call the ``merge_config.sh`` script. The
@@ -1140,14 +1146,6 @@ useful.
 To specify the C preprocessor to use, set the ``CPP`` environment variable. The
 default is ``cpp``.
 
-Note that Buildman does not support adding fragments to existing boards, e.g.
-like::
-
-    make qemu_riscv64_defconfig acpi.config
-
-This is partly because there is no way for Buildman to know which fragments are
-valid on which boards.
-
 Building with clang
 -------------------
 
-- 
2.48.1