From: Matthew Wilcox <willy@infradead.org>
To: Mike Rapoport <rppt@linux.vnet.ibm.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
linux-doc@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/7] docs/core-api: split memory management API to a separate file
Date: Wed, 25 Jul 2018 05:05:00 -0700 [thread overview]
Message-ID: <20180725120500.GA9352@bombadil.infradead.org> (raw)
In-Reply-To: <1532517970-16409-6-git-send-email-rppt@linux.vnet.ibm.com>
On Wed, Jul 25, 2018 at 02:26:08PM +0300, Mike Rapoport wrote:
> +User Space Memory Access
> +========================
> +
> +.. kernel-doc:: arch/x86/include/asm/uaccess.h
> + :internal:
> +
> +.. kernel-doc:: arch/x86/lib/usercopy_32.c
> + :export:
> +
> +The Slab Cache
> +==============
> +
> +.. kernel-doc:: include/linux/slab.h
> + :internal:
> +
> +.. kernel-doc:: mm/slab.c
> + :export:
> +
> +.. kernel-doc:: mm/util.c
> + :functions: kfree_const kvmalloc_node kvfree get_user_pages_fast
get_user_pages_fast would fit better in the previous 'User Space Memory
Access' section.
next prev parent reply other threads:[~2018-07-25 12:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 11:26 [PATCH 0/7] memory management documentation updates Mike Rapoport
2018-07-25 11:26 ` [PATCH 1/7] mm/util: make strndup_user description a kernel-doc comment Mike Rapoport
2018-07-25 11:26 ` [PATCH 2/7] mm/util: add kernel-doc for kvfree Mike Rapoport
2018-07-25 11:26 ` [PATCH 3/7] docs/core-api: kill trailing whitespace in kernel-api.rst Mike Rapoport
2018-07-25 11:26 ` [PATCH 4/7] docs/core-api: move *{str,mem}dup* to "String Manipulation" Mike Rapoport
2018-07-25 11:26 ` [PATCH 5/7] docs/core-api: split memory management API to a separate file Mike Rapoport
2018-07-25 12:05 ` Matthew Wilcox [this message]
2018-07-25 13:30 ` Mike Rapoport
2018-07-25 11:26 ` [PATCH 6/7] docs/mm: make GFP flags descriptions usable as kernel-doc Mike Rapoport
2018-07-25 11:26 ` [PATCH 7/7] docs/core-api: mm-api: add section about GFP flags 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=20180725120500.GA9352@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@linux.vnet.ibm.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).