linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: David Hildenbrand <david@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Anshuman Khandual <anshuman.khandual@arm.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Matthew Wilcox <willy@infradead.org>,
	Michal Hocko <mhocko@suse.com>,
	Mike Kravetz <mike.kravetz@oracle.com>,
	Mike Rapoport <rppt@kernel.org>,
	Mike Rapoport <rppt@linux.ibm.com>,
	Muchun Song <songmuchun@bytedance.com>,
	Oscar Salvador <osalvador@suse.de>,
	Pavel Tatashin <pasha.tatashin@soleen.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH v3 0/2] memory-hotplug.rst: complete admin-guide overhaul
Date: Tue, 6 Jul 2021 15:18:51 -0700	[thread overview]
Message-ID: <20210706151851.8edeaf8dbcf7e6710d90cfa5@linux-foundation.org> (raw)
In-Reply-To: <4624932e-2022-a60d-f58f-e11b70014efa@redhat.com>

On Thu, 1 Jul 2021 17:30:13 +0200 David Hildenbrand <david@redhat.com> wrote:

> On 09.06.21 09:57, David Hildenbrand wrote:
> > This is v3 of the memory hot(un)plug admin-guide overhaul.
> > 
> > v2 -> v3:
> > - Added ACKs and RBs (thanks!)
> > - s/aarch64/arm64/
> > - Refine error handling when onlining/offlining
> > - s/memory hotplug/memory offlining/ in the vmemmap optimization section
> >    for huge pages
> > 
> > v1 -> v2:
> > - Added "memory-hotplug.rst: remove locking details from admin-guide"
> > - Incorporated all feedback from Mike and Michal (thanks!)
> > - Compressed some lines to make full use of 80 chars.
> > - Added details regarding 64bit/supported archs to the introduction.
> > - Added KASAN to the list of sizing considerations.
> > 
> > David Hildenbrand (2):
> >    memory-hotplug.rst: remove locking details from admin-guide
> >    memory-hotplug.rst: complete admin-guide overhaul
> > 
> >   .../admin-guide/mm/memory-hotplug.rst         | 800 ++++++++++--------
> >   1 file changed, 455 insertions(+), 345 deletions(-)
> > 
> 
> Andrew,
> 
> are you planning on picking+sending this for this cycle, or do you 
> prefer to let this doc update rest for a little bit longer?
> 
> I can spot that mmotm still contains v1.

Seems that whenever I take a documentation patch, Jon pops up and takes
it as well.   Except this time ;)

Please resend whatever's needed against current mainline?


      reply	other threads:[~2021-07-06 22:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-09  7:57 [PATCH v3 0/2] memory-hotplug.rst: complete admin-guide overhaul David Hildenbrand
2021-06-09  7:57 ` [PATCH v3 1/2] memory-hotplug.rst: remove locking details from admin-guide David Hildenbrand
2021-06-09  7:57 ` [PATCH v3 2/2] memory-hotplug.rst: complete admin-guide overhaul David Hildenbrand
2021-06-13 23:20 ` [PATCH v3 0/2] " Jonathan Corbet
2021-06-14  7:21   ` David Hildenbrand
2021-06-14 14:14     ` Jonathan Corbet
2021-06-14 16:16       ` David Hildenbrand
2021-07-01 15:30 ` David Hildenbrand
2021-07-06 22:18   ` Andrew Morton [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=20210706151851.8edeaf8dbcf7e6710d90cfa5@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=corbet@lwn.net \
    --cc=dave.hansen@linux.intel.com \
    --cc=david@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=mike.kravetz@oracle.com \
    --cc=osalvador@suse.de \
    --cc=pasha.tatashin@soleen.com \
    --cc=rppt@kernel.org \
    --cc=rppt@linux.ibm.com \
    --cc=sfr@canb.auug.org.au \
    --cc=songmuchun@bytedance.com \
    --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).