From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Jonathan Corbet <corbet@lwn.net>,
Ross Philipson <ross.philipson@oracle.com>,
Daniel Kiper <daniel.kiper@oracle.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Ard Biesheuvel <ardb@kernel.org>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH 0/2] Documentation: x86: Note fixes for boot protocol doc
Date: Mon, 6 Nov 2023 17:12:03 +0700 [thread overview]
Message-ID: <20231106101206.76487-1-bagasdotme@gmail.com> (raw)
When I was reviewing generated html output of my web font series [1]
by viewing boot protocol doc (Documentation/output/arch/x86/boot.html),
I noticed that notes there wasn't right: the first note extended to
the end of doc; and the last one wasn't marked up as note either.
Let's fix them up.
[1]: https://lore.kernel.org/lkml/20231102120053.30630-1-bagasdotme@gmail.com/
Bagas Sanjaya (2):
Documentation: x86: Indent note directive for protocol version number
note
Documentation: x86: Wrap EFI handover deprecation in note block
Documentation/arch/x86/boot.rst | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
base-commit: 77fa2fbe87fc605c4bfa87dff87be9bfded0e9a3
--
An old man doll... just what I always wanted! - Clara
next reply other threads:[~2023-11-06 10:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 10:12 Bagas Sanjaya [this message]
2023-11-06 10:12 ` [PATCH 1/2] Documentation: x86: Indent note directive for protocol version number note Bagas Sanjaya
2023-11-06 11:58 ` [tip: x86/urgent] x86/Documentation: Indent 'note::' " tip-bot2 for Bagas Sanjaya
2023-11-06 10:12 ` [PATCH 2/2] Documentation: x86: Wrap EFI handover deprecation in note block Bagas Sanjaya
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=20231106101206.76487-1-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=daniel.kiper@oracle.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=ross.philipson@oracle.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®