From: Andrew Morton <akpm@linux-foundation.org>
To: Liu Shixin <liushixin2@huawei.com>
Cc: David Hildenbrand <david@redhat.com>,
Waiman Long <longman@redhat.com>,
Zefan Li <lizefan.x@bytedance.com>,
Christoph Lameter <cl@linux.com>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>,
Kefeng Wang <wangkefeng.wang@huawei.com>
Subject: Re: [PATCH v4 1/8] cgroup/cpuset: use hotplug_memory_notifier() directly
Date: Mon, 17 Oct 2022 18:35:08 -0700 [thread overview]
Message-ID: <20221017183508.de7172a0ab6b18e4a1ec4625@linux-foundation.org> (raw)
In-Reply-To: <20220923033347.3935160-2-liushixin2@huawei.com>
On Fri, 23 Sep 2022 11:33:40 +0800 Liu Shixin <liushixin2@huawei.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().
next prev parent reply other threads:[~2022-10-18 1:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 3:33 [PATCH v4 0/8] mm: Use hotplug_memory_notifier() instead of register_hotmemory_notifier() Liu Shixin
2022-09-23 3:33 ` [PATCH v4 1/8] cgroup/cpuset: use hotplug_memory_notifier() directly Liu Shixin
2022-10-18 1:35 ` Andrew Morton [this message]
2022-09-23 3:33 ` [PATCH v4 2/8] fs/proc/kcore.c: " Liu Shixin
2022-09-23 3:33 ` [PATCH v4 3/8] mm/slub.c: " Liu Shixin
2022-09-23 3:33 ` [PATCH v4 4/8] mm/mmap: " Liu Shixin
2022-09-23 3:33 ` [PATCH v4 5/8] mm/mm_init.c: " Liu Shixin
2022-09-23 3:33 ` [PATCH v4 6/8] ACPI: HMAT: " Liu Shixin
2022-09-23 3:33 ` [PATCH v4 7/8] memory: remove unused register_hotmemory_notifier() Liu Shixin
2022-09-23 7:47 ` David Hildenbrand
2022-09-23 3:33 ` [PATCH v4 8/8] memory: move hotplug memory notifier priority to same file for easy sorting Liu Shixin
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=20221017183508.de7172a0ab6b18e4a1ec4625@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liushixin2@huawei.com \
--cc=lizefan.x@bytedance.com \
--cc=longman@redhat.com \
--cc=wangkefeng.wang@huawei.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;
as well as URLs for NNTP newsgroup(s).