From: Dmitry Safonov <0x7f454c46@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@redhat.com>, Dmitry Safonov <dima@arista.com>
Subject: Re: [PATCH -next RESEND] Documentation/admin-guide: fix sysctl Sphinx warning
Date: Mon, 21 Oct 2019 14:54:50 +0100 [thread overview]
Message-ID: <c1442b1f-c90e-0604-bb50-f71a16e8b335@gmail.com> (raw)
In-Reply-To: <c5fed83a-d105-4142-8607-4b06ebadf0e8@infradead.org>
Hi Randy,
On 10/21/19 3:44 AM, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
>
> Fix Sphinx warning when building Documentation:
>
> Documentation/admin-guide/sysctl/kernel.rst:397: WARNING: Title underline too short.
>
> hung_task_interval_warnings:
> ===================
Thanks for the patch!
I'm in process of reworking the patch in akpm according to reviews,
I will incorporate your change in next version.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Dmitry Safonov <dima@arista.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Ingo Molnar <mingo@kernel.org>
> ---
> Documentation/admin-guide/sysctl/kernel.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- linux-next-20191018.orig/Documentation/admin-guide/sysctl/kernel.rst
> +++ linux-next-20191018/Documentation/admin-guide/sysctl/kernel.rst
> @@ -394,7 +394,7 @@ This file shows up if CONFIG_DETECT_HUNG
>
>
> 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
>
>
Thanks,
Dmitry
prev parent reply other threads:[~2019-10-21 13:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 2:44 Randy Dunlap
2019-10-21 13:54 ` Dmitry Safonov [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=c1442b1f-c90e-0604-bb50-f71a16e8b335@gmail.com \
--to=0x7f454c46@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dima@arista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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
all inboxes | Powered by JetHome®