From: liusongtang <liusongtang@huawei.com>
To: Kefeng Wang <wangkefeng.wang@huawei.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
<akpm@linux-foundation.org>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
<nixiaoming@huawei.com>, <young.liuyang@huawei.com>,
<trivial@kernel.org>
Subject: Re: [PATCH] mm: use pgprot_val to get value of pgprot
Date: Mon, 25 Apr 2022 21:48:52 +0800 [thread overview]
Message-ID: <a22d0e25-cc72-3cf8-c893-e962c0001028@huawei.com> (raw)
In-Reply-To: <22536b1c-f38d-45b1-8187-636c158b8e4b@huawei.com>
OK, Shall I add "Suggested-by: Kefeng Wang <wangkefeng.wang@huawei.com>"
to these patches?
On 2022/4/25 18:40, Kefeng Wang wrote:
>
> On 2022/4/25 18:29, Anshuman Khandual wrote:
>> Should have added 'memory_hotplug' in the subject line. Otherwise
>> this does not specify where the change is (neither does the commit
>> message below).
>>
>> mm/memory_hotplug: use pgprot_val to get value of pgprot
>
>
> $ git grep "pgprot\.pgprot"
> arch/ia64/mm/init.c: if (WARN_ON_ONCE(params->pgprot.pgprot !=
> PAGE_KERNEL.pgprot))
> arch/s390/mm/init.c: if (WARN_ON_ONCE(params->pgprot.pgprot !=
> PAGE_KERNEL.pgprot))
> arch/sh/mm/init.c: if (WARN_ON_ONCE(params->pgprot.pgprot !=
> PAGE_KERNEL.pgprot))
> mm/memory_hotplug.c: if (WARN_ON_ONCE(!params->pgprot.pgprot))
>
> You can change other's codes too.
>
>>
>> On 4/25/22 13:47, liusongtang wrote:
>>> pgprot.pgprot is a non-portable code, it should be replaced by
>>> portable macro pgprot_val.
>>>
>>> Signed-off-by: liusongtang <liusongtang@huawei.com>
>>> ---
>>> mm/memory_hotplug.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
>>> index 416b38c..bf7d181 100644
>>> --- a/mm/memory_hotplug.c
>>> +++ b/mm/memory_hotplug.c
>>> @@ -303,7 +303,7 @@ int __ref __add_pages(int nid, unsigned long
>>> pfn, unsigned long nr_pages,
>>> 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));
>> Otherwise LGTM.
>>
>> Reviewed-by: Anshuman Khandual <anshuman.khandual@arm.com>
>>
>> .
> .
next prev parent reply other threads:[~2022-04-25 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 8:17 [PATCH] mm: use pgprot_val to get value of pgprot liusongtang
2022-04-25 10:29 ` Anshuman Khandual
2022-04-25 10:40 ` Kefeng Wang
2022-04-25 13:48 ` liusongtang [this message]
2022-04-26 5:38 ` Kefeng Wang
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=a22d0e25-cc72-3cf8-c893-e962c0001028@huawei.com \
--to=liusongtang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nixiaoming@huawei.com \
--cc=trivial@kernel.org \
--cc=wangkefeng.wang@huawei.com \
--cc=young.liuyang@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).