From: Randy Dunlap <rdunlap@infradead.org>
To: Ingo Molnar <mingo@kernel.org>,
Swaraj Gaikwad <swarajgaikwad1925@gmail.com>
Cc: bp@alien8.de, corbet@lwn.net, dave.hansen@linux.intel.com,
david.hunter.linux@gmail.com, hpa@zytor.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@redhat.com, skhan@linuxfoundation.org, tglx@linutronix.de,
x86@kernel.org, Bagas Sanjaya <bagasdotme@gmail.com>
Subject: Re: [PATCH v2] Documentation: x86/boot: Fix malformed table in boot.rst
Date: Tue, 9 Dec 2025 10:15:14 -0800 [thread overview]
Message-ID: <a0a141d8-7e22-45ba-9bc2-74a3f0285cac@infradead.org> (raw)
In-Reply-To: <aTfjlAKBNeX6my4g@gmail.com>
On 12/9/25 12:53 AM, Ingo Molnar wrote:
> * Swaraj Gaikwad <swarajgaikwad1925@gmail.com> wrote:
>
>> Sphinx reports htmldocs warnings:
>>
>> Documentation/arch/x86/boot.rst:437: ERROR: Malformed table.
>> Text in column margin in table line 2.
>>
>> The table header defined the first column width as 2 characters ("=="),
>> which is too narrow for entries like "0x10" and "0x13". This caused the
>> text to spill into the margin, triggering a docutils parsing failure.
>>
>> Fix it by extending the first column of assigned boot loader ID to 4
>> characters ("====") to fit the widest entries.
>>
>> Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
>> Tested-by: Randy Dunlap <rdunlap@infradead.org>
>> Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
>> Signed-off-by: Swaraj Gaikwad <swarajgaikwad1925@gmail.com>
>> ---
>> Changes in v2:
>> - Dropped accidental whitespace changes (the second chunk in v1).
>> - Simplified commit message as suggested by Bagas Sanjaya.
>>
>> ---
>> Documentation/arch/x86/boot.rst | 48 ++++++++++++++++-----------------
>> 1 file changed, 24 insertions(+), 24 deletions(-)
>>
>> diff --git a/Documentation/arch/x86/boot.rst b/Documentation/arch/x86/boot.rst
>> index 6d36ce86fd8e..89e785850f7e 100644
>> --- a/Documentation/arch/x86/boot.rst
>> +++ b/Documentation/arch/x86/boot.rst
>> @@ -433,30 +433,30 @@ Protocol: 2.00+
>>
>> Assigned boot loader IDs:
>>
>> - == =======================================
>> - 0x0 LILO
>> - (0x00 reserved for pre-2.00 bootloader)
>> - 0x1 Loadlin
>> - 0x2 bootsect-loader
>> - (0x20, all other values reserved)
>> - 0x3 Syslinux
>> - 0x4 Etherboot/gPXE/iPXE
>> - 0x5 ELILO
>> - 0x7 GRUB
>> - 0x8 U-Boot
>> - 0x9 Xen
>> - 0xA Gujin
>> - 0xB Qemu
>> - 0xC Arcturus Networks uCbootloader
>> - 0xD kexec-tools
>> - 0xE Extended (see ext_loader_type)
>> - 0xF Special (0xFF = undefined)
>> - 0x10 Reserved
>> - 0x11 Minimal Linux Bootloader
>> - <http://sebastian-plotz.blogspot.de>
>> - 0x12 OVMF UEFI virtualization stack
>> - 0x13 barebox
>> - == =======================================
>> +==== ==============================
>> +0x0 LILO
>> + (0x00 reserved for pre-2.00 bootloader)
>> +0x1 Loadlin
>> +0x2 bootsect-loader
>> + (0x20, all other values reserved)
>> +0x3 Syslinux
>> +0x4 Etherboot/gPXE/iPXE
>> +0x5 ELILO
>> +0x7 GRUB
>> +0x8 U-Boot
>> +0x9 Xen
>> +0xA Gujin
>> +0xB Qemu
>> +0xC Arcturus Networks uCbootloader
>> +0xD kexec-tools
>> +0xE Extended (see ext_loader_type)
>> +0xF Special (0xFF = undefined)
>> +0x10 Reserved
>> +0x11 Minimal Linux Bootloader
>> + <http://sebastian-plotz.blogspot.de>
>> +0x12 OVMF UEFI virtualization stack
>> +0x13 barebox
>> +==== ==============================
>
> So why was the leading tab dropped and why wasn't this change,
> unnecessary to the bug fix in question, declared in the changelog?
Hi Ingo,
It makes no difference to the generated html output, but for users
who read Documentation/* files in place, the leading tab indentation
looks a little nicer IMO. Yes?
Thanks for noticing.
--
~Randy
next prev parent reply other threads:[~2025-12-09 18:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 21:01 [PATCH] " Swaraj Gaikwad
2025-12-08 18:11 ` Randy Dunlap
2025-12-08 22:37 ` Bagas Sanjaya
2025-12-08 22:50 ` Jonathan Corbet
2025-12-08 22:58 ` Bagas Sanjaya
2025-12-09 8:53 ` [PATCH v2] " Swaraj Gaikwad
2025-12-09 8:53 ` Ingo Molnar
2025-12-09 18:15 ` Randy Dunlap [this message]
2025-12-09 21:10 ` Randy Dunlap
2025-12-09 23:17 ` Bagas Sanjaya
2025-12-10 9:28 ` [PATCH v3] " Swaraj Gaikwad
2025-12-10 7:40 ` [tip: x86/urgent] x86/boot/Documentation: Fix htmldocs build warning due to " tip-bot2 for Swaraj Gaikwad
2025-12-10 1:14 ` [PATCH v2] Documentation: x86/boot: Fix " Swaraj Gaikwad
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=a0a141d8-7e22-45ba-9bc2-74a3f0285cac@infradead.org \
--to=rdunlap@infradead.org \
--cc=bagasdotme@gmail.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=david.hunter.linux@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=skhan@linuxfoundation.org \
--cc=swarajgaikwad1925@gmail.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®