From: Mike Rapoport <rppt@linux.ibm.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: David Hildenbrand <david@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Mike Rapoport <rppt@linux.ibm.com>
Subject: [PATCH 0/2] docs: memory-hotplug: add details about locking internals
Date: Thu, 11 Oct 2018 07:58:15 +0300 [thread overview]
Message-ID: <1539233897-10207-1-git-send-email-rppt@linux.ibm.com> (raw)
Hi,
As discussed at [1], the latest updates to memory hotplug documentation are
causing a conflict between docs and mmotm trees.
These patches resolve the conflict.
[1] https://lkml.org/lkml/2018/10/8/227
David Hildenbrand (1):
docs/core-api: memory-hotplug: add some details about locking internals
Mike Rapoport (1):
docs/core-api: rename memory-hotplug-notifier to memory-hotplug
Documentation/core-api/index.rst | 2 +-
Documentation/core-api/memory-hotplug-notifier.rst | 84 --------------
Documentation/core-api/memory-hotplug.rst | 125 +++++++++++++++++++++
3 files changed, 126 insertions(+), 85 deletions(-)
delete mode 100644 Documentation/core-api/memory-hotplug-notifier.rst
create mode 100644 Documentation/core-api/memory-hotplug.rst
--
2.7.4
next reply other threads:[~2018-10-11 4:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 4:58 Mike Rapoport [this message]
2018-10-11 4:58 ` [PATCH 1/2] docs/core-api: rename memory-hotplug-notifier to memory-hotplug Mike Rapoport
2018-10-11 7:43 ` David Hildenbrand
2018-10-11 4:58 ` [PATCH 2/2] docs/core-api: memory-hotplug: add some details about locking internals Mike Rapoport
2018-10-11 7:43 ` David Hildenbrand
2018-10-12 17:21 ` [PATCH 0/2] docs: memory-hotplug: add " Jonathan Corbet
2018-12-03 11:23 ` David Hildenbrand
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=1539233897-10207-1-git-send-email-rppt@linux.ibm.com \
--to=rppt@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).