From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, nixiaoming@huawei.com,
anshuman.khandual@arm.com, liusongtang@huawei.com,
akpm@linux-foundation.org
Subject: [merged mm-stable] mm-memory_hotplug-use-pgprot_val-to-get-value-of-pgprot.patch removed from -mm tree
Date: Mon, 09 May 2022 21:15:36 -0700 [thread overview]
Message-ID: <20220510041536.A708FC385C2@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm/memory_hotplug: use pgprot_val to get value of pgprot
has been removed from the -mm tree. Its filename was
mm-memory_hotplug-use-pgprot_val-to-get-value-of-pgprot.patch
This patch was dropped because it was merged into mm-stable
------------------------------------------------------
From: liusongtang <liusongtang@huawei.com>
Subject: mm/memory_hotplug: use pgprot_val to get value of pgprot
pgprot.pgprot is non-portable code. It should be replaced by portable
macro pgprot_val.
Link: https://lkml.kernel.org/r/20220426071302.220646-1-liusongtang@huawei.com
Signed-off-by: liusongtang <liusongtang@huawei.com>
Reviewed-by: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: Xiaoming Ni <nixiaoming@huawei.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/memory_hotplug.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/memory_hotplug.c~mm-memory_hotplug-use-pgprot_val-to-get-value-of-pgprot
+++ a/mm/memory_hotplug.c
@@ -303,7 +303,7 @@ int __ref __add_pages(int nid, unsigned
int err;
struct vmem_altmap *altmap = params->altmap;
- if (WARN_ON_ONCE(!params->pgprot.pgprot))
+ if (WARN_ON_ONCE(!pgprot_val(params->pgprot)))
return -EINVAL;
VM_BUG_ON(!mhp_range_allowed(PFN_PHYS(pfn), nr_pages * PAGE_SIZE, false));
_
Patches currently in -mm which might be from liusongtang@huawei.com are
reply other threads:[~2022-05-10 4:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220510041536.A708FC385C2@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liusongtang@huawei.com \
--cc=mm-commits@vger.kernel.org \
--cc=nixiaoming@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.