linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Nir Lichtman <nir@lichtman.org>,
	corbet@lwn.net, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: Fix x86_64 UEFI outdated references to elilo
Date: Wed, 8 Jan 2025 08:46:24 +0700	[thread overview]
Message-ID: <Z33Y8FRqVvPycCgB@archie.me> (raw)
In-Reply-To: <20250106223526.GA877278@lichtman.org>

[-- Attachment #1: Type: text/plain, Size: 956 bytes --]

On Mon, Jan 06, 2025 at 10:35:26PM +0000, Nir Lichtman wrote:
> +Refer to <Documentation/admin-guide/efi-stub.rst> for general setup guidelines on usage of the EFI stub, the following are setup specifics for EFI in general on the x86_64 platform.

"... for how to use EFI stub. Below is general EFI setup on x86_64 platform,
regardless of whether using EFI stub or separate bootloader."

> -- Create a VFAT partition on the disk
> -- Copy the following to the VFAT partition:
> +- Create a VFAT partition on the disk with the EFI System flag
> +    You can do this with fdisk with the following commands:
> +    1. g - initialize a GPT partition table
> +    2. n - create a new partition
> +    3. t - change the partition type to "EFI System" (number 1)
> +    4. w - write and save the changes

I see running paragraph instead of numbered list in htmldocs output.

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  parent reply	other threads:[~2025-01-08  1:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-06 22:35 [PATCH] Documentation: Fix x86_64 UEFI outdated references to elilo Nir Lichtman
2025-01-06 22:48 ` Nir Lichtman
2025-01-08  1:46 ` Bagas Sanjaya [this message]
2025-01-08 11:30   ` Nir Lichtman

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=Z33Y8FRqVvPycCgB@archie.me \
    --to=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nir@lichtman.org \
    /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;
as well as URLs for NNTP newsgroup(s).