mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Liu Shixin <liushixin2@huawei.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>,
	Liu Shixin <liushixin2@huawei.com>,
	"Kefeng Wang" <wangkefeng.wang@huawei.com>
Subject: [PATCH 6/9] ACPI: HMAT: use hotplug_memory_notifier() directly
Date: Mon, 19 Sep 2022 16:31:49 +0800	[thread overview]
Message-ID: <20220919083152.1824305-7-liushixin2@huawei.com> (raw)
In-Reply-To: <20220919083152.1824305-1-liushixin2@huawei.com>

Since patch 316346243be6 has already updated the minimum gcc version to 5.1.
The previous problem mentioned in patch f02c69680088 is not existed. So we
can now revert to use hotplug_memory_notifier() directly rather than
register_hotmemory_notifier().

Signed-off-by: Liu Shixin <liushixin2@huawei.com>
---
 drivers/acpi/numa/hmat.c | 7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)

diff --git a/drivers/acpi/numa/hmat.c b/drivers/acpi/numa/hmat.c
index c3d783aca196..84dffb3dc30e 100644
--- a/drivers/acpi/numa/hmat.c
+++ b/drivers/acpi/numa/hmat.c
@@ -768,11 +768,6 @@ static int hmat_callback(struct notifier_block *self,
 	return NOTIFY_OK;
 }
 
-static struct notifier_block hmat_callback_nb = {
-	.notifier_call = hmat_callback,
-	.priority = 2,
-};
-
 static __init void hmat_free_structures(void)
 {
 	struct memory_target *target, *tnext;
@@ -855,7 +850,7 @@ static __init int hmat_init(void)
 	hmat_register_targets();
 
 	/* Keep the table and structures if the notifier may use them */
-	if (!register_hotmemory_notifier(&hmat_callback_nb))
+	if (!hotplug_memory_notifier(hmat_callback, 2))
 		return 0;
 out_put:
 	hmat_free_structures();
-- 
2.25.1


  parent reply	other threads:[~2022-09-19  7:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-19  8:31 [PATCH 0/9] mm: Use hotplug_memory_notifier() instead of register_hotmemory_notifier() Liu Shixin
2022-09-19  8:31 ` [PATCH 1/9] cgroup/cpuset: use hotplug_memory_notifier() directly Liu Shixin
2022-09-19  8:31 ` [PATCH 2/9] fs/proc/kcore.c: " Liu Shixin
2022-09-19  8:31 ` [PATCH 3/9] mm/slub.c: " Liu Shixin
2022-09-19  8:31 ` [PATCH 4/9] mm/mmap: " Liu Shixin
2022-09-19 16:43   ` kernel test robot
2022-09-19  8:31 ` [PATCH 5/9] mm/mm_init.c: " Liu Shixin
2022-09-19 18:54   ` kernel test robot
2022-09-19  8:31 ` Liu Shixin [this message]
2022-09-19  8:31 ` [PATCH 7/9] memory: remove unused register_hotmemory_notifier() Liu Shixin
2022-09-19  8:31 ` [PATCH 8/9] memory: replace IPC_CALLBACK_PRI with MM_BATCH_CALLBACK_PRI Liu Shixin
2022-09-19  8:31 ` [PATCH 9/9] memory: clean up hotplug memory callback priority 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=20220919083152.1824305-7-liushixin2@huawei.com \
    --to=liushixin2@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®