From: Daniel Kiper <daniel.kiper@oracle.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>, X86 ML <x86@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] Documentation: x86: fix boot.rst warning and format
Date: Mon, 9 Dec 2019 17:13:40 +0100 [thread overview]
Message-ID: <20191209161340.kdsikc2hvbhmpi6k@tomti.i.net-space.pl> (raw)
In-Reply-To: <c6fbf592-0aca-69d9-e903-e869221a041a@infradead.org>
On Sun, Dec 08, 2019 at 08:25:10PM -0800, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
>
> Fix a Sphinx documentation format warning by breaking a long line
> into 2 lines.
>
> Also drop the ':' usage after the Protocol version numbers since
> other Protocol versions don't use colons.
>
> Documentation/x86/boot.rst:72: WARNING: Malformed table.
> Text in column margin in table line 57.
>
> Fixes: 2c33c27fd603 ("x86/boot: Introduce kernel_info")
> Fixes: 00cd1c154d56 ("x86/boot: Introduce kernel_info.setup_type_max")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: linux-doc@vger.kernel.org
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Borislav Petkov <bp@alien8.de>
> Cc: "H. Peter Anvin" <hpa@zytor.com>
> Cc: x86@kernel.org
> Cc: Daniel Kiper <daniel.kiper@oracle.com>
Reviewed-by: Daniel Kiper <daniel.kiper@oracle.com>
What can I do next time to avoid mistakes like that? I suppose that
I can run something to get this warning but I do not know what exactly
it should be.
Daniel
next prev parent reply other threads:[~2019-12-09 16:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 4:25 [PATCH] Documentation: x86: fix boot.rst warning and format Randy Dunlap
2019-12-09 16:13 ` Daniel Kiper [this message]
2019-12-09 16:26 ` Randy Dunlap
2019-12-09 16:58 ` Matthew Wilcox
2019-12-19 16:25 ` Jonathan Corbet
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=20191209161340.kdsikc2hvbhmpi6k@tomti.i.net-space.pl \
--to=daniel.kiper@oracle.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=hpa@zytor.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rdunlap@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).