[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20221017183508.de7172a0ab6b18e4a1ec4625@linux-foundation.org>
Date: Mon, 17 Oct 2022 18:35:08 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Liu Shixin <liushixin2@...wei.com>
Cc: David Hildenbrand <david@...hat.com>,
Waiman Long <longman@...hat.com>,
Zefan Li <lizefan.x@...edance.com>,
Christoph Lameter <cl@...ux.com>, <linux-mm@...ck.org>,
<linux-kernel@...r.kernel.org>,
Kefeng Wang <wangkefeng.wang@...wei.com>
Subject: Re: [PATCH v4 1/8] cgroup/cpuset: use hotplug_memory_notifier()
directly
On Fri, 23 Sep 2022 11:33:40 +0800 Liu Shixin <liushixin2@...wei.com> wrote:
> Since patch 316346243be6
That's a merge commit. I'll rewrite this to 76ae847497bc52
("Documentation: raise minimum supported version of GCC to 5.1").
Which, although misnamed is the commit which made the change.
> has already updated the minimum gcc version to 5.1.
> The previous problem mentioned in patch f02c69680088
I'll make that f02c69680088 ("include/linux/memory.h: implement
register_hotmemory_notifier()").
And hot damn I write good changelogs! Wrote :(
> is not existed. So we
> can now revert to use hotplug_memory_notifier() directly rather than
> register_hotmemory_notifier().
I redid the changelogs thusly:
: Commit 76ae847497bc52 ("Documentation: raise minimum supported version of
: GCC to 5.1") updated the minimum gcc version to 5.1. So the problem
: mentioned in f02c69680088 ("include/linux/memory.h: implement
: register_hotmemory_notifier()") no longer exist. So we can now switch to
: use hotplug_memory_notifier() directly rather than
: register_hotmemory_notifier().
Powered by blists - more mailing lists