From: "Antonin Godard" <antonin.godard@bootlin.com>
To: <reatmon@ti.com>, <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH v2] ref-manual: Document updated UBOOT_CONFIG flow
Date: Fri, 30 Jan 2026 14:29:34 +0100 [thread overview]
Message-ID: <DG1YKKEBYK3R.1RDFPILOIHIOP@bootlin.com> (raw)
In-Reply-To: <20260127225706.25153-1-reatmon@ti.com>
Hi,
Thanks, I'll merge this patch with the following typo fixes:
diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 595b90f87..a7c92e326 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -10692,7 +10692,7 @@ system and gives an overview of their function and contents.
the "sd..." configurations define an individual name for
:term:`UBOOT_CONFIG_BINARY`.
- For more information on how the :term:`UBOOT_CONFIG` is handled, see the
+ For more information on how the :term:`UBOOT_CONFIG` variable is handled, see the
:ref:`ref-classes-uboot-config` class.
:term:`UBOOT_CONFIG_BINARY`
@@ -10725,15 +10725,15 @@ system and gives an overview of their function and contents.
UBOOT_CONFIG_FRAGMENTS[foo] = "frag1 frag2"
UBOOT_CONFIG_FRAGMENTS[bar] = "frag3"
- Specify a list of fragments from the source tree that should be combined
+ It specifies a list of fragments from the source tree that should be combined
with the defconfig from :term:`UBOOT_CONFIG` that are used during ``do_configure()``
- to configure the build. These fragments are located in same
+ to configure the build. These fragments are located in same
``${S}/configs/`` directory as the defconfig.
This option is not required and you only need to specify it for
configs that need them.
- For more information on how the :term:`UBOOT_CONFIG_FRAGMENTS` is handled, see the
+ For more information on how the :term:`UBOOT_CONFIG_FRAGMENTS` variable is handled, see the
:ref:`ref-classes-uboot-config` class.
:term:`UBOOT_CONFIG_IMAGE_FSTYPES`
@@ -10750,8 +10750,8 @@ system and gives an overview of their function and contents.
This option is not required and you only need to specify flag settings for
configs that need them.
- For more information on how the :term:`UBOOT_CONFIG_IMAGE_FSTYPES` is handled, see the
- :ref:`ref-classes-uboot-config` class.
+ For more information on how the :term:`UBOOT_CONFIG_IMAGE_FSTYPES`
+ variable is handled, see the :ref:`ref-classes-uboot-config` class.
:term:`UBOOT_CONFIG_MAKE_OPTS`
This variable cannot be set to a value in a config, it is a placeholder
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-01-30 13:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 22:57 [PATCH v2] ref-manual: Document updated UBOOT_CONFIG flow Ryan Eatmon
2026-01-30 13:29 ` Antonin Godard [this message]
2026-02-13 9:06 ` Antonin Godard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DG1YKKEBYK3R.1RDFPILOIHIOP@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=reatmon@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox