From: Michal Hocko <mhocko@kernel.org>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: david@redhat.com, osalvador@suse.de, akpm@linux-foundation.org,
linux-doc@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 1/2] admin-guide/memory-hotplug.rst: remove locking internal part from admin-guide
Date: Wed, 5 Dec 2018 13:11:55 +0100 [thread overview]
Message-ID: <20181205121155.GJ1286@dhcp22.suse.cz> (raw)
In-Reply-To: <20181205023426.24029-1-richard.weiyang@gmail.com>
On Wed 05-12-18 10:34:25, Wei Yang wrote:
> Locking Internal section exists in core-api documentation, which is more
> suitable for this.
>
> This patch removes the duplication part here.
>
> Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
Yes this doesn't really make any sense in an admin guide. It is a pure
implementation detail nobody should be relying on.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-12-05 12:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 2:34 Wei Yang
2018-12-05 2:34 ` [PATCH 2/2] core-api/memory-hotplug.rst: divide Locking Internal section by different locks Wei Yang
2018-12-05 8:08 ` David Hildenbrand
2018-12-05 9:23 ` Wei Yang
2018-12-05 8:40 ` Mike Rapoport
2018-12-05 9:24 ` Wei Yang
2018-12-05 12:13 ` Michal Hocko
2018-12-05 12:20 ` Wei Yang
2018-12-05 8:03 ` [PATCH 1/2] admin-guide/memory-hotplug.rst: remove locking internal part from admin-guide David Hildenbrand
2018-12-05 8:30 ` Mike Rapoport
2018-12-05 9:20 ` Wei Yang
2018-12-05 9:20 ` Wei Yang
2018-12-05 12:11 ` Michal Hocko [this message]
2018-12-06 0:26 ` [PATCH v2 " Wei Yang
2018-12-06 0:26 ` [PATCH v2 2/2] core-api/memory-hotplug.rst: divide Locking Internal section by different locks Wei Yang
2018-12-06 7:32 ` Mike Rapoport
2018-12-06 8:22 ` 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=20181205121155.GJ1286@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=richard.weiyang@gmail.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