linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@linux.vnet.ibm.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-mm@kvack.org,
	Mike Rapoport <rppt@linux.vnet.ibm.com>
Subject: [PATCH 0/2] docs: ReSTify memory-hotplug description
Date: Fri,  5 Oct 2018 01:10:59 +0300	[thread overview]
Message-ID: <1538691061-31289-1-git-send-email-rppt@linux.vnet.ibm.com> (raw)

Hi,

Recently I've noticed that Documentation/memory-hotplug.txt is 
   1) mostly formatted
   2) in a wrong place

These patches split the memory-hotplug.txt to two parts: user/admin
interface and memory hotplug notifier API and place these parts in the
correct places, with some formatting changes.

Mike Rapoport (2):
  docs: move memory hotplug description into admin-guide/mm
  docs/vm: split memory hotplug notifier description to Documentation/core-api

 Documentation/admin-guide/mm/index.rst             |   1 +
 .../mm/memory-hotplug.rst}                         | 152 +++++----------------
 Documentation/core-api/index.rst                   |   2 +
 Documentation/core-api/memory-hotplug-notifier.rst |  84 ++++++++++++
 4 files changed, 122 insertions(+), 117 deletions(-)
 rename Documentation/{memory-hotplug.txt => admin-guide/mm/memory-hotplug.rst} (77%)
 create mode 100644 Documentation/core-api/memory-hotplug-notifier.rst

-- 
2.7.4

             reply	other threads:[~2018-10-04 22:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-04 22:10 Mike Rapoport [this message]
2018-10-04 22:11 ` [PATCH 1/2] docs: move memory hotplug description into admin-guide/mm Mike Rapoport
2018-10-04 22:11 ` [PATCH 2/2] docs/vm: split memory hotplug notifier description to Documentation/core-api Mike Rapoport
2018-10-07 14:46   ` Jonathan Corbet
2018-10-07 16:32     ` 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=1538691061-31289-1-git-send-email-rppt@linux.vnet.ibm.com \
    --to=rppt@linux.vnet.ibm.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@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).