From: Mike Rapoport <rppt@linux.ibm.com>
To: "Tobin C. Harding" <me@tobin.cc>
Cc: Jonathan Corbet <corbet@lwn.net>,
"Tobin C. Harding" <tobin@kernel.org>,
Christopher Lameter <cl@linux.com>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 2/3] docs: Add missing colon
Date: Thu, 31 Jan 2019 11:30:33 +0200 [thread overview]
Message-ID: <20190131093033.GG28876@rapoport-lnx> (raw)
In-Reply-To: <20190131040623.15569-3-me@tobin.cc>
On Thu, Jan 31, 2019 at 03:06:22PM +1100, Tobin C. Harding wrote:
> From: "Tobin C. Harding" <tobin@kernel.org>
>
> sphinx emits warning
>
> WARNING: Inline emphasis start-string without end-string.
>
> This is caused by a missing colon.
>
> Add missing colon, clearing shpinx build warning.
>
> Signed-off-by: Tobin C. Harding <tobin@kernel.org>
Acked-by: Mike Rapoport <rppt@linux.ibm.com>
> ---
> Documentation/vm/slub.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/vm/slub.rst b/Documentation/vm/slub.rst
> index 0871c5849..933ada436 100644
> --- a/Documentation/vm/slub.rst
> +++ b/Documentation/vm/slub.rst
> @@ -66,7 +66,7 @@ Trying to find an issue in the dentry cache? Try::
> to only enable debugging on the dentry cache. You may use an asterisk at the
> end of the slab name, in order to cover all slabs with the same prefix. For
> example, here's how you can poison the dentry cache as well as all kmalloc
> -slabs:
> +slabs::
>
> slub_debug=P,kmalloc-*,dentry
>
> --
> 2.20.1
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2019-01-31 9:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 4:06 [PATCH 0/3] docs: vm: Fix typo and build warnings Tobin C. Harding
2019-01-31 4:06 ` [PATCH 1/3] docs: Fix SLUB docs typo Tobin C. Harding
2019-01-31 9:30 ` Mike Rapoport
2019-01-31 4:06 ` [PATCH 2/3] docs: Add missing colon Tobin C. Harding
2019-01-31 9:30 ` Mike Rapoport [this message]
2019-01-31 4:06 ` [PATCH 3/3] docs: Use underscore not hyphen in label Tobin C. Harding
2019-01-31 9:27 ` Mike Rapoport
2019-01-31 20:56 ` Tobin C. Harding
2019-02-01 23:03 ` Jonathan Corbet
2019-02-02 14:32 ` Mike Rapoport
2019-02-03 23:20 ` Tobin C. Harding
2019-02-04 8:38 ` Mike Rapoport
2019-02-04 21:12 ` Tobin C. Harding
2019-02-04 23:03 ` Jonathan Corbet
2019-02-05 8:30 ` Markus Heiser
2019-02-06 4:27 ` Tobin C. Harding
2019-02-06 7:49 ` Markus Heiser
2019-02-06 20:28 ` Tobin C. Harding
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=20190131093033.GG28876@rapoport-lnx \
--to=rppt@linux.ibm.com \
--cc=cl@linux.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=me@tobin.cc \
--cc=tobin@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