[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d517106f-64ba-5d3a-59f5-c87d5e032bdc@redhat.com>
Date: Mon, 14 Jun 2021 09:21:33 +0200
From: David Hildenbrand <david@...hat.com>
To: Jonathan Corbet <corbet@....net>, linux-kernel@...r.kernel.org
Cc: linux-mm@...ck.org, Andrew Morton <akpm@...ux-foundation.org>,
Anshuman Khandual <anshuman.khandual@....com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Matthew Wilcox <willy@...radead.org>,
Michal Hocko <mhocko@...e.com>,
Mike Kravetz <mike.kravetz@...cle.com>,
Mike Rapoport <rppt@...nel.org>,
Mike Rapoport <rppt@...ux.ibm.com>,
Muchun Song <songmuchun@...edance.com>,
Oscar Salvador <osalvador@...e.de>,
Pavel Tatashin <pasha.tatashin@...een.com>,
Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: [PATCH v3 0/2] memory-hotplug.rst: complete admin-guide overhaul
On 14.06.21 01:20, Jonathan Corbet wrote:
> David Hildenbrand <david@...hat.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.
Hi Jon,
oh, looks like I messed up v3 by git-format-patching from the wrong
directory ...
> What tree is this against?
>
Essentially against Andrew's mmotm, which already contains v1. Note
mmotm was chosen due to a conflict in:
https://lkml.kernel.org/r/20210510030027.56044-1-songmuchun@bytedance.com
I'd suggest we take this via Andrew's tree, unless you have other
preference on how to handle the conflict. Thanks!
> Thanks,
>
> jon
>
--
Thanks,
David / dhildenb
Powered by blists - more mailing lists