From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Simon A. Eugster" <simon.eu@gmail.com>, <docs@lists.yoctoproject.org>
Subject: Re: [PATCH v2] ref-manual: Describe grub-efi-cfg overrides and GRUB_TITLE
Date: Tue, 28 Jan 2025 09:20:27 +0100 [thread overview]
Message-ID: <D7DK5YLXCDJ3.31RLRC7EGPYS4@bootlin.com> (raw)
In-Reply-To: <20250128075328.20912-1-simon.eu@gmail.com>
Hi Simon,
On Tue Jan 28, 2025 at 8:53 AM CET, Simon A. Eugster wrote:
> This patch describes how to use overrides for grub-efi-cfg because that
> is otherwise only clear after reading the .bbclass file. It also adds
> a description for GRUB_TITLE.
>
> Signed-off-by: Simon A. Eugster <simon.eu@gmail.com>
> ---
> documentation/ref-manual/classes.rst | 16 ++++++++++++++++
> documentation/ref-manual/variables.rst | 5 +++++
> 2 files changed, 21 insertions(+)
>
> diff --git a/documentation/ref-manual/classes.rst b/documentation/ref-manual/classes.rst
> index 761be7b545..1de362e864 100644
> --- a/documentation/ref-manual/classes.rst
> +++ b/documentation/ref-manual/classes.rst
> @@ -991,6 +991,7 @@ This class supports several variables:
>
> - :term:`INITRD`: Indicates list of filesystem images to
> concatenate and use as an initial RAM disk (initrd) (optional).
> + Can be specified for each ``LABEL``.
>
> - :term:`ROOTFS`: Indicates a filesystem image to include
> as the root filesystem (optional).
> @@ -1004,6 +1005,9 @@ This class supports several variables:
> - :term:`APPEND`: An override list of append strings for
> each ``LABEL``.
>
> +- :term:`GRUB_TITLE`: A custom title for each ```LABEL``.
> + Defaults to ``LABEL`` if it is not defined.
> +
> - :term:`GRUB_OPTS`: Additional options to add to the
> configuration (optional). Options are delimited using semi-colon
> characters (``;``).
> @@ -1011,6 +1015,18 @@ This class supports several variables:
> - :term:`GRUB_TIMEOUT`: Timeout before executing
> the default ``LABEL`` (optional).
>
> +Each ``LABEL`` defined in the ``LABELS`` variable creates a GRUB boot entry,
> +and some variables can be defined individually per ``LABEL``. The label
> +specific override names are defined as ``grub_LABEL``.
> +
> +For example, for a label ``factory``, the override name would be
> +``grub_factory``. A custom GRUB menu entry titled "Factory Install" with the
> +additional parameter ``factory=yes`` can be achieved as follows::
> +
> + LABELS:append = " factory"
> + APPEND:grub_factory = "factory=yes"
> + GRUB_TITLE:grub_factory = "Factory Install"
> +
> .. _ref-classes-gsettings:
>
> ``gsettings``
> diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
> index 0c5c7aab97..16ffbf0e85 100644
> --- a/documentation/ref-manual/variables.rst
> +++ b/documentation/ref-manual/variables.rst
> @@ -3320,6 +3320,11 @@ system and gives an overview of their function and contents.
> :ref:`ref-classes-grub-efi` class for more information
> on how this variable is used.
>
> + :term:`GRUB_TITLE`
> + Specifies custom titles for GRUB labels defined in :ref:`LABELS`. See
Here you make a :ref: to LABELS, but like GRUB_TITLE, it needs to be added to
variables.rst, otherwise it produces a compile error. You would also use :term:,
not :ref:.
Can you add documentation for it?
Since "LABELS" by its own does not refer to Grub, just make sure to start the
description with:
"""
When inheriting the :ref:`ref-classes-grub-efi` class, ...
"""
So someone reading the description knows in which context it's used.
If you do, please also use :term: in the class description above.
Thanks for the separate mail/Signed-off-by!
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-01-28 8:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 7:53 [PATCH v2] ref-manual: Describe grub-efi-cfg overrides and GRUB_TITLE Simon A. Eugster
2025-01-28 8:20 ` Antonin Godard [this message]
2025-01-28 9:18 ` Simon Eugster
2025-01-28 9:49 ` 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=D7DK5YLXCDJ3.31RLRC7EGPYS4@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=simon.eu@gmail.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