From: Masami Hiramatsu <mhiramat@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] Documentation: bootconfig: fix Sphinx block warning
Date: Mon, 10 Feb 2020 16:16:47 +0900 [thread overview]
Message-ID: <20200210161647.416ce0dcd0710f4349a665b1@kernel.org> (raw)
In-Reply-To: <07b3e31f-9b1e-1876-aa60-4436e4dd6da0@infradead.org>
On Sun, 9 Feb 2020 19:53:17 -0800
Randy Dunlap <rdunlap@infradead.org> wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
>
> Fix Sphinx format warning:
>
> lnx-56-rc1/Documentation/admin-guide/bootconfig.rst:26: WARNING: Literal block expected; none found.
>
Good catch!
Acked-by: Masami Hiramatsu <mhiramat@kernel.org>
Thanks for the fix!
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Cc: Masami Hiramatsu <mhiramat@kernel.org>
> ---
> Documentation/admin-guide/bootconfig.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- lnx-56-rc1.orig/Documentation/admin-guide/bootconfig.rst
> +++ lnx-56-rc1/Documentation/admin-guide/bootconfig.rst
> @@ -23,7 +23,7 @@ of dot-connected-words, and key and valu
> has to be terminated by semi-colon (``;``) or newline (``\n``).
> For array value, array entries are separated by comma (``,``). ::
>
> -KEY[.WORD[...]] = VALUE[, VALUE2[...]][;]
> + KEY[.WORD[...]] = VALUE[, VALUE2[...]][;]
>
> Unlike the kernel command line syntax, spaces are OK around the comma and ``=``.
>
>
--
Masami Hiramatsu <mhiramat@kernel.org>
next prev parent reply other threads:[~2020-02-10 7:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 3:53 [PATCH] Documentation: bootconfig: fix Sphinx block warning Randy Dunlap
2020-02-10 7:16 ` Masami Hiramatsu [this message]
2020-02-10 16:54 ` Steven Rostedt
2020-02-13 17:43 ` 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=20200210161647.416ce0dcd0710f4349a665b1@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.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).