mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Daisuke Iwasa <iwadjp@gmail.com>,
	tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
	dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
	corbet@lwn.net, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: x86: fix malformed table in boot protocol doc
Date: Wed, 7 Jan 2026 22:54:08 -0800	[thread overview]
Message-ID: <84aa1a20-e507-4db0-a1f1-3a0b7342f2c3@infradead.org> (raw)
In-Reply-To: <20260108064615.144113-1-iwadjp@gmail.com>

Hi,

On 1/7/26 10:46 PM, Daisuke Iwasa wrote:
> Sphinx reports a malformed table warning in
> Documentation/arch/x86/boot.rst.
> 
> Rewrite the "Assigned boot loader IDs" table using a simple table format
> so the multi-line entries are properly represented.
> 
> Signed-off-by: Daisuke Iwasa <iwadjp@gmail.com>
> ---
>  Documentation/arch/x86/boot.rst | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/arch/x86/boot.rst b/Documentation/arch/x86/boot.rst
> index 6d36ce86fd8e..18574f010d46 100644
> --- a/Documentation/arch/x86/boot.rst
> +++ b/Documentation/arch/x86/boot.rst
> @@ -433,7 +433,7 @@ Protocol:	2.00+
>  
>    Assigned boot loader IDs:
>  
> -	== =======================================
> +	==== =======================================
>  	0x0  LILO
>  	     (0x00 reserved for pre-2.00 bootloader)
>  	0x1  Loadlin
> @@ -456,7 +456,7 @@ Protocol:	2.00+
>  	     <http://sebastian-plotz.blogspot.de>
>  	0x12 OVMF UEFI virtualization stack
>  	0x13 barebox
> -	== =======================================
> +	==== =======================================
>  
>    Please contact <hpa@zytor.com> if you need a bootloader ID value assigned.

That looks good, but this has already been fixed:
commit 5288176a5412
Author: Swaraj Gaikwad <swarajgaikwad1925@gmail.com>
Date:   Wed Dec 10 09:28:14 2025 +0000
    x86/boot/Documentation: Fix htmldocs build warning due to malformed table in boot.rst

Be sure to use an up-to-date kernel source tree when making & posting patches.

thanks.
-- 
~Randy


  reply	other threads:[~2026-01-08  6:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-08  6:46 Daisuke Iwasa
2026-01-08  6:54 ` Randy Dunlap [this message]
2026-01-08 22:02   ` iwadjp

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=84aa1a20-e507-4db0-a1f1-3a0b7342f2c3@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=bp@alien8.de \
    --cc=corbet@lwn.net \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=iwadjp@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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

all inboxes | Powered by JetHome®