From: Jonathan Corbet <corbet@lwn.net>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Swaraj Gaikwad <swarajgaikwad1925@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
"open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<linux-kernel@vger.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>
Cc: skhan@linuxfoundation.org, david.hunter.linux@gmail.com
Subject: Re: [PATCH] Documentation: x86/boot: Fix malformed table in boot.rst
Date: Mon, 08 Dec 2025 15:50:02 -0700 [thread overview]
Message-ID: <874iq0fv1h.fsf@trenco.lwn.net> (raw)
In-Reply-To: <aTdTRY_7TtGqWvQx@archie.me>
Bagas Sanjaya <bagasdotme@gmail.com> writes:
> I'd like to instead write the patch description as (more concise):
The original was indeed on the verbose side, but please (for the nth
time) resist the temptation to tell other contributors what to do.
> x86 maintainers: please route this patch through x86/urgent branch.
Seriously, Bagas? I think we can figure out how to get this patch
applied.
jon
next prev parent reply other threads:[~2025-12-08 22:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 21:01 [PATCH] Documentation: x86/boot: Fix malformed table in boot.rst Swaraj Gaikwad
2025-12-08 18:11 ` Randy Dunlap
2025-12-08 22:37 ` Bagas Sanjaya
2025-12-08 22:50 ` Jonathan Corbet [this message]
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
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=874iq0fv1h.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=bagasdotme@gmail.com \
--cc=bp@alien8.de \
--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@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