From: Mike Rapoport <rppt@linux.ibm.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
Christoph Lameter <cl@linux.com>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Subject: Re: [PATCH] Documentation: fix vm/slub.rst warning
Date: Mon, 11 Feb 2019 09:35:37 +0200 [thread overview]
Message-ID: <20190211073537.GA25868@rapoport-lnx> (raw)
In-Reply-To: <1e992162-c4ac-fe4e-f1b0-d8a16a51d5e7@infradead.org>
On Sun, Feb 10, 2019 at 10:34:11PM -0800, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
>
> Fix markup warning by quoting the '*' character with a backslash.
>
> Documentation/vm/slub.rst:71: WARNING: Inline emphasis start-string without end-string.
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Christoph Lameter <cl@linux.com>
> Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Acked-by: Mike Rapoport <rppt@linux.ibm.com>
> ---
> Documentation/vm/slub.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- lnx-50-rc6.orig/Documentation/vm/slub.rst
> +++ lnx-50-rc6/Documentation/vm/slub.rst
> @@ -68,7 +68,7 @@ end of the slab name, in order to cover
> example, here's how you can poison the dentry cache as well as all kmalloc
> slabs:
>
> - slub_debug=P,kmalloc-*,dentry
> + slub_debug=P,kmalloc-\*,dentry
>
> Red zoning and tracking may realign the slab. We can just apply sanity checks
> to the dentry cache with::
>
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2019-02-11 7:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 6:34 [PATCH] Documentation: fix vm/slub.rst warning Randy Dunlap
2019-02-11 7:35 ` Mike Rapoport [this message]
2019-02-11 7:43 ` Sergey Senozhatsky
2019-02-11 15:27 ` Jonathan Corbet
2019-02-11 17:31 ` Randy Dunlap
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=20190211073537.GA25868@rapoport-lnx \
--to=rppt@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rdunlap@infradead.org \
--cc=sergey.senozhatsky.work@gmail.com \
/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).