From: David Hildenbrand <david@redhat.com>
To: Liu Shixin <liushixin2@huawei.com>,
Andrew Morton <akpm@linux-foundation.org>,
Waiman Long <longman@redhat.com>,
Zefan Li <lizefan.x@bytedance.com>,
Christoph Lameter <cl@linux.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Kefeng Wang <wangkefeng.wang@huawei.com>
Subject: Re: [PATCH v4 7/8] memory: remove unused register_hotmemory_notifier()
Date: Fri, 23 Sep 2022 09:47:48 +0200 [thread overview]
Message-ID: <9c4af0f9-22ff-4e4f-58c7-65808d55ca67@redhat.com> (raw)
In-Reply-To: <20220923033347.3935160-8-liushixin2@huawei.com>
On 23.09.22 05:33, Liu Shixin wrote:
> Remove unused register_hotmemory_notifier().
>
> Signed-off-by: Liu Shixin <liushixin2@huawei.com>
> ---
> include/linux/memory.h | 6 ------
> 1 file changed, 6 deletions(-)
>
> diff --git a/include/linux/memory.h b/include/linux/memory.h
> index aa619464a1df..98d2a2ebcc10 100644
> --- a/include/linux/memory.h
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2022-09-23 7:47 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
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 [this message]
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=9c4af0f9-22ff-4e4f-58c7-65808d55ca67@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.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