mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warning after merge of the tip-fixes tree
Date: Thu, 4 Dec 2025 16:50:50 +1100	[thread overview]
Message-ID: <20251204165050.4b07a78a@canb.auug.org.au> (raw)

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

Hi all,

After merging the tip-fixes tree, today's linux-next build (htmldocs)
produced this warning:

Documentation/arch/x86/boot.rst:437: ERROR: Malformed table.
Text in column margin in table line 2.

== =======================================
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
== ======================================= [docutils]

Introduced by commit

  1c3377bee212 ("x86/boot/Documentation: Prefix hexadecimal literals with 0x")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

                 reply	other threads:[~2025-12-04  5:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20251204165050.4b07a78a@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.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

all inboxes | Powered by JetHome®