From: Jonathan Corbet <corbet@lwn.net>
To: Adam Zerella <adam.zerella@gmail.com>
Cc: gor@linux.ibm.com, akpm@linux-foundation.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs: admin-guide: Extend short title underline in sysctl
Date: Tue, 15 Oct 2019 12:32:22 -0600 [thread overview]
Message-ID: <20191015123222.46527701@lwn.net> (raw)
In-Reply-To: <20191014110008.GA3814@gmail.com>
On Mon, 14 Oct 2019 22:00:08 +1100
Adam Zerella <adam.zerella@gmail.com> wrote:
> Title underlines should extend the full length of a title,
> Sphinx is currently displaying the following warning when
> building the htmldocs:
>
> sysctl/kernel.rst:397: WARNING: Title underline too short.
>
> hung_task_interval_warnings:
> ===================
>
> Signed-off-by: Adam Zerella <adam.zerella@gmail.com>
> ---
> Documentation/admin-guide/sysctl/kernel.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/admin-guide/sysctl/kernel.rst b/Documentation/admin-guide/sysctl/kernel.rst
> index 614179dc79a9..383eda89f411 100644
> --- a/Documentation/admin-guide/sysctl/kernel.rst
> +++ b/Documentation/admin-guide/sysctl/kernel.rst
> @@ -394,7 +394,7 @@ This file shows up if CONFIG_DETECT_HUNG_TASK is enabled.
>
>
> hung_task_interval_warnings:
> -===================
> +============================
>
> The same as hung_task_warnings, but set the number of interval
> warnings to be issued about detected hung tasks during check
So this is a good fix, but it's not an actual patch that I can apply.
Randy meanwhile says he fixed it, but the patch wasn't sent to me. I
guess this warning will live a little longer...:(
Thanks,
jon
next prev parent reply other threads:[~2019-10-15 18:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 11:00 [PATCH] docs: admin-guide: Extend short title underline in sysctl Adam Zerella
2019-10-14 15:15 ` Randy Dunlap
2019-10-15 18:32 ` Jonathan Corbet [this message]
2019-10-15 21:28 ` Randy Dunlap
2019-10-15 21:48 ` 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=20191015123222.46527701@lwn.net \
--to=corbet@lwn.net \
--cc=adam.zerella@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=gor@linux.ibm.com \
--cc=linux-doc@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.