From: Jonathan Corbet <corbet@lwn.net>
To: Mike Rapoport <rppt@linux.vnet.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Matthew Wilcox <willy@infradead.org>,
linux-doc@vger.kernel.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] docs/vm: start moving files do Documentation/admin-guide`
Date: Fri, 27 Apr 2018 17:07:29 -0600 [thread overview]
Message-ID: <20180427170729.1d8e4123@lwn.net> (raw)
In-Reply-To: <1524038870-413-1-git-send-email-rppt@linux.vnet.ibm.com>
On Wed, 18 Apr 2018 11:07:43 +0300
Mike Rapoport <rppt@linux.vnet.ibm.com> wrote:
> These pacthes begin categorizing memory management documentation. The
> documents that describe userspace APIs and do not overload the reader with
> implementation details can be moved to Documentation/admin-guide, so let's
> do it :)
Looks good, set applied, thanks.
jon
prev parent reply other threads:[~2018-04-27 23:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 8:07 [PATCH 0/7] docs/vm: start moving files do Documentation/admin-guide` Mike Rapoport
2018-04-18 8:07 ` [PATCH 1/7] docs/vm: hugetlbpage: minor improvements Mike Rapoport
2018-04-18 8:07 ` [PATCH 2/7] docs/vm: hugetlbpage: move section about kernel development to hugetlbfs_reserv Mike Rapoport
2018-04-18 8:07 ` [PATCH 3/7] docs/vm: pagemap: formatting and spelling updates Mike Rapoport
2018-04-18 8:07 ` [PATCH 4/7] docs/vm: pagemap: change document title Mike Rapoport
2018-04-18 8:07 ` [PATCH 5/7] docs/admin-guide: introduce basic index for mm documentation Mike Rapoport
2018-04-18 8:07 ` [PATCH 6/7] docs/admin-guide/mm: start moving here files from Documentation/vm Mike Rapoport
2018-04-18 8:07 ` [PATCH 7/7] docs/admin-guide/mm: convert plain text cross references to hyperlinks Mike Rapoport
2018-04-27 23:07 ` Jonathan Corbet [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=20180427170729.1d8e4123@lwn.net \
--to=corbet@lwn.net \
--cc=akpm@linux-foundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@linux.vnet.ibm.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@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;
as well as URLs for NNTP newsgroup(s).