From: Mike Rapoport <rppt@linux.vnet.ibm.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-doc <linux-doc@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
lkml <linux-kernel@vger.kernel.org>,
Mike Rapoport <rppt@linux.vnet.ibm.com>
Subject: [PATCH 0/3] docs/vm: move numa_memory_policy.rst to admin-guide/mm
Date: Tue, 8 May 2018 10:02:07 +0300 [thread overview]
Message-ID: <1525762930-28163-1-git-send-email-rppt@linux.vnet.ibm.com> (raw)
Hi,
These patches include minor formatting and spelling updates to
Documentation/vm/numa_memory_policy.rst and move this file to
Documentation/admin-guide/mm.
Mike Rapoport (3):
docs/vm: numa_memory_policy: formatting and spelling updates
docs/vm: numa_memory_policy: s/Linux memory policy/NUMA memory policy/
docs/vm: move numa_memory_policy.rst to Documentation/admin-guide/mm
Documentation/admin-guide/mm/hugetlbpage.rst | 2 +-
Documentation/admin-guide/mm/index.rst | 1 +
.../{vm => admin-guide/mm}/numa_memory_policy.rst | 38 ++++++++++++++--------
Documentation/filesystems/proc.txt | 2 +-
Documentation/filesystems/tmpfs.txt | 5 +--
Documentation/vm/00-INDEX | 2 --
Documentation/vm/index.rst | 1 -
Documentation/vm/numa.rst | 2 +-
8 files changed, 31 insertions(+), 22 deletions(-)
rename Documentation/{vm => admin-guide/mm}/numa_memory_policy.rst (95%)
--
2.7.4
next reply other threads:[~2018-05-08 7:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 7:02 Mike Rapoport [this message]
2018-05-08 7:02 ` [PATCH 1/3] docs/vm: numa_memory_policy: formatting and spelling updates Mike Rapoport
2018-05-08 7:02 ` [PATCH 2/3] docs/vm: numa_memory_policy: s/Linux memory policy/NUMA memory policy/ Mike Rapoport
2018-05-08 7:02 ` [PATCH 3/3] docs/vm: move numa_memory_policy.rst to Documentation/admin-guide/mm Mike Rapoport
2018-05-08 15:44 ` [PATCH 0/3] docs/vm: move numa_memory_policy.rst to admin-guide/mm Jonathan Corbet
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=1525762930-28163-1-git-send-email-rppt@linux.vnet.ibm.com \
--to=rppt@linux.vnet.ibm.com \
--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 \
/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).