From: Simon Glass <sjg@chromium.org>
Date: Mon, 31 Jul 2023 03:01:46 +0000 (-0600)
Subject: env: Explain how to use #include files in text environment
X-Git-Url: http://git.dujemihanovic.xyz/?a=commitdiff_plain;h=63af90e7f0cab3b5197c19744f5e807ebc325c81;p=u-boot.git

env: Explain how to use #include files in text environment

Provide documentation on how to share common settings among boards.

Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> # Intel Edison
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
---

diff --git a/doc/usage/environment.rst b/doc/usage/environment.rst
index 91dc07b17b..c6439dde66 100644
--- a/doc/usage/environment.rst
+++ b/doc/usage/environment.rst
@@ -81,6 +81,12 @@ Example::
         echo CONFIG_SYS_BOARD boot failed - please check your image
         echo Load address is CONFIG_SYS_LOAD_ADDR
 
+Settings which are common to a group of boards can use #include to bring in
+a common file in the `include/env` directory, containing environment
+settings. For example::
+
+   #include <env/ti/mmc.env>
+
 If CONFIG_ENV_SOURCE_FILE is empty and the default filename is not present, then
 the old-style C environment is used instead. See below.