linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: David Hildenbrand <david@redhat.com>, linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, David Hildenbrand <david@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Anshuman Khandual <anshuman.khandual@arm.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	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: Sun, 13 Jun 2021 17:20:33 -0600	[thread overview]
Message-ID: <87y2bd9wse.fsf@meer.lwn.net> (raw)
In-Reply-To: <20210609075752.4596-1-david@redhat.com>

David Hildenbrand <david@redhat.com> writes:

> 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

So this set doesn't apply to docs-next, even when I correct for the fact
that you didn't make the patch from the top-level kernel directory.
What tree is this against?

Thanks,

jon

  parent reply	other threads:[~2021-06-13 23:20 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 ` Jonathan Corbet [this message]
2021-06-14  7:21   ` [PATCH v3 0/2] " 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

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=87y2bd9wse.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --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).