From: Mike Rapoport <rppt@linux.ibm.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-doc@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] docs/mm-api: link kernel-doc comments from slab_common.c
Date: Thu, 20 Dec 2018 09:59:13 +0200 [thread overview]
Message-ID: <20181220075912.GA12338@rapoport-lnx> (raw)
In-Reply-To: <1544130781-13443-1-git-send-email-rppt@linux.ibm.com>
ping?
On Thu, Dec 06, 2018 at 11:12:59PM +0200, Mike Rapoport wrote:
> Hi,
>
> These patches update formatting of function descriptions in
> mm/slab_common.c and link the comments from this file to "The Slab Cache"
> section of the MM API reference.
>
> As the changes to mm/slab_common.c only touch the comments, I think these
> patches can go via the docs tree.
>
> Mike Rapoport (2):
> slab: make kmem_cache_create{_usercopy} description proper kernel-doc
> docs/mm-api: link slab_common.c to "The Slab Cache" section
>
> Documentation/core-api/mm-api.rst | 3 +++
> mm/slab_common.c | 35 +++++++++++++++++++++++++++++++----
> 2 files changed, 34 insertions(+), 4 deletions(-)
>
> --
> 2.7.4
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2018-12-20 7:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 21:12 Mike Rapoport
2018-12-06 21:13 ` [PATCH 1/2] slab: make kmem_cache_create{_usercopy} description proper kernel-doc Mike Rapoport
2018-12-09 23:02 ` David Rientjes
2018-12-06 21:13 ` [PATCH 2/2] docs/mm-api: link slab_common.c to "The Slab Cache" section Mike Rapoport
2018-12-09 23:02 ` David Rientjes
2018-12-20 7:59 ` Mike Rapoport [this message]
2018-12-20 15:34 ` [PATCH 0/2] docs/mm-api: link kernel-doc comments from slab_common.c Jonathan Corbet
2018-12-21 14:29 ` Mike Rapoport
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=20181220075912.GA12338@rapoport-lnx \
--to=rppt@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=corbet@lwn.net \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.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