From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Guilherme G. Piccoli" <gpiccoli@canonical.com>
Subject: Re: [PATCH] Documentation: fix sysctl/kernel.rst heading format warnings
Date: Fri, 19 Jun 2020 13:25:30 -0600 [thread overview]
Message-ID: <20200619132530.7f329134@lwn.net> (raw)
In-Reply-To: <8af1cb77-4b5a-64b9-da5d-f6a95e537f99@infradead.org>
On Sun, 14 Jun 2020 21:11:00 -0700
Randy Dunlap <rdunlap@infradead.org> wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
>
> Fix heading format warnings in admin-guide/sysctl/kernel.rst:
>
> Documentation/admin-guide/sysctl/kernel.rst:339: WARNING: Title underline too short.
> hung_task_all_cpu_backtrace:
> ================
>
> Documentation/admin-guide/sysctl/kernel.rst:650: WARNING: Title underline too short.
> oops_all_cpu_backtrace:
> ================
>
> Fixes: 0ec9dc9bcba0 ("kernel/hung_task.c: introduce sysctl to print all traces when a hung task is detected")
> Fixes: 60c958d8df9c ("panic: add sysctl to dump all CPUs backtraces on oops event")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Guilherme G. Piccoli <gpiccoli@canonical.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> ---
> Documentation/admin-guide/sysctl/kernel.rst | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
Applied, thanks.
jon
prev parent reply other threads:[~2020-06-19 19:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 4:11 [PATCH] Documentation: fix sysctl/kernel.rst heading format warnings Randy Dunlap
2020-06-15 6:51 ` Mauro Carvalho Chehab
2020-06-19 19:25 ` Jonathan Corbet [this message]
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=20200619132530.7f329134@lwn.net \
--to=corbet@lwn.net \
--cc=akpm@linux-foundation.org \
--cc=gpiccoli@canonical.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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).