From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: Simon Glass <sjg@chromium.org>
Cc: Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Sughosh Ganu <sughosh.ganu@linaro.org>,
Tom Rini <trini@konsulko.com>,
U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: [PATCH 1/6] doc: Show more information in efi index
Date: Thu, 25 Jul 2024 18:02:56 +0200 [thread overview]
Message-ID: <ee3b019a-a0cf-4029-8bce-22515fbb48d6@gmx.de> (raw)
In-Reply-To: <20240725135629.3505072-2-sjg@chromium.org>
On 25.07.24 15:56, Simon Glass wrote:
> The index is much more helpful if it shows the next level of headings.
> Update tt.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> ---
>
> doc/develop/uefi/index.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/develop/uefi/index.rst b/doc/develop/uefi/index.rst
> index e26b1fbe05c..44540e8a537 100644
> --- a/doc/develop/uefi/index.rst
> +++ b/doc/develop/uefi/index.rst
> @@ -8,7 +8,7 @@ compliant software like Linux, GRUB, and iPXE. Furthermore U-Boot itself
> can be run an UEFI payload.
>
> .. toctree::
> - :maxdepth: 2
> + :maxdepth: 3
>
> uefi.rst
> u-boot_on_efi.rst
What we really need to do is moving usage documentation like
* Executing a UEFI binary
* Launching a UEFI binary from a FIT image
* Run on VirtualBox (x86_64)
to pages in /usage instead of having these as sections in uefi.rst and
u-boot_on_efi.rst.
Best regards
Heinrich
next prev parent reply other threads:[~2024-07-25 16:03 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 13:56 [PATCH 0/6] efi: Start tidying up memory management Simon Glass
2024-07-25 13:56 ` [PATCH 1/6] doc: Show more information in efi index Simon Glass
2024-07-25 16:02 ` Heinrich Schuchardt [this message]
2024-07-25 13:56 ` [PATCH 2/6] efi: Convert device_path allocation to use malloc() Simon Glass
2024-07-25 16:13 ` Heinrich Schuchardt
2024-07-25 23:32 ` Simon Glass
2024-07-25 13:56 ` [PATCH 3/6] efi: Allow monitoring of page allocations Simon Glass
2024-07-25 16:20 ` Heinrich Schuchardt
2024-07-25 23:33 ` Simon Glass
2024-07-25 13:56 ` [PATCH 4/6] efi: Avoid pool allocation in efi_get_memory_map_alloc() Simon Glass
2024-07-25 16:38 ` Heinrich Schuchardt
2024-07-31 14:39 ` Simon Glass
2024-07-25 13:56 ` [PATCH 5/6] efi: Use malloc() for the EFI pool Simon Glass
2024-07-25 15:49 ` Heinrich Schuchardt
2024-07-25 23:32 ` Simon Glass
2024-07-26 8:31 ` Ilias Apalodimas
2024-07-26 14:54 ` Simon Glass
2024-07-29 10:01 ` Ilias Apalodimas
2024-07-29 15:28 ` Simon Glass
2024-07-30 8:19 ` Ilias Apalodimas
2024-07-30 14:38 ` Simon Glass
2024-07-30 14:53 ` Mark Kettenis
2024-07-30 15:18 ` Simon Glass
2024-07-30 14:53 ` Ilias Apalodimas
2024-07-30 15:18 ` Simon Glass
2024-07-30 15:24 ` Tom Rini
2024-07-30 19:42 ` Simon Glass
2024-07-30 19:49 ` Tom Rini
2024-07-30 20:05 ` Simon Glass
2024-07-30 20:11 ` Tom Rini
2024-07-30 20:52 ` Simon Glass
2024-07-30 21:20 ` Tom Rini
2024-07-31 14:39 ` Simon Glass
2024-07-31 17:17 ` Tom Rini
2024-08-01 10:14 ` Ilias Apalodimas
2024-08-01 16:14 ` Simon Glass
2024-08-01 16:22 ` Ilias Apalodimas
2024-08-01 17:43 ` Simon Glass
2024-07-31 7:39 ` Ilias Apalodimas
2024-07-31 14:39 ` Simon Glass
2024-07-25 13:56 ` [PATCH 6/6] efi: Show the location of the bounce buffer Simon Glass
2024-07-25 16:31 ` Heinrich Schuchardt
2024-07-31 14:39 ` Simon Glass
2024-07-25 14:25 ` [PATCH 0/6] efi: Start tidying up memory management Ilias Apalodimas
2024-07-25 15:58 ` Simon Glass
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=ee3b019a-a0cf-4029-8bce-22515fbb48d6@gmx.de \
--to=xypron.glpk@gmx.de \
--cc=ilias.apalodimas@linaro.org \
--cc=sjg@chromium.org \
--cc=sughosh.ganu@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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