From: David Hildenbrand <david@redhat.com>
To: Peng Liu <liupeng256@huawei.com>,
mike.kravetz@oracle.com, akpm@linux-foundation.org,
yaozhenguo1@gmail.com, baolin.wang@linux.alibaba.com,
songmuchun@bytedance.com, liuyuntao10@huawei.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
wangkefeng.wang@huawei.com, dave@stgolabs.net,
wangborong@cdjrlc.com, linux-ia64@vger.kernel.org,
adobriyan@gmail.com
Subject: Re: [PATCH v4] mm: Using for_each_online_node and node_online instead of open coding
Date: Fri, 29 Apr 2022 11:29:30 +0200 [thread overview]
Message-ID: <95216c6f-0614-cadc-d256-92a172d8b8cd@redhat.com> (raw)
In-Reply-To: <20220429030218.644635-1-liupeng256@huawei.com>
On 29.04.22 05:02, Peng Liu wrote:
> Use more generic functions to deal with issues related to online
> nodes. The changes will make the code simplified.
>
> Signed-off-by: Peng Liu <liupeng256@huawei.com>
> Suggested-by: Davidlohr Bueso <dave@stgolabs.net>
> Suggested-by: Andrew Morton <akpm@linux-foundation.org>
> ---
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2022-04-29 9:29 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 3:29 [PATCH v3 0/4] hugetlb: Fix some incorrect behavior Peng Liu
2022-04-13 3:29 ` [PATCH v3 1/4] hugetlb: Fix wrong use of nr_online_nodes Peng Liu
2022-04-13 4:42 ` Andrew Morton
[not found] ` <692ee24c-a705-0c54-7cad-a9ecf49a8f15@huawei.com>
2022-04-13 22:04 ` Andrew Morton
2022-04-13 6:29 ` Baolin Wang
2022-04-14 23:36 ` Mike Kravetz
2022-04-15 2:09 ` Davidlohr Bueso
2022-04-15 5:41 ` Kefeng Wang
2022-04-16 1:21 ` Kefeng Wang
2022-04-19 4:40 ` Andrew Morton
2022-04-19 8:54 ` Kefeng Wang
2022-04-16 10:35 ` [PATCH v4] " Peng Liu
2022-04-18 5:53 ` Kefeng Wang
2022-04-19 4:03 ` Andrew Morton
2022-04-19 14:07 ` Kefeng Wang
2022-04-20 6:17 ` liupeng (DM)
2022-04-29 9:32 ` David Hildenbrand
2022-04-13 3:29 ` [PATCH v3 2/4] hugetlb: Fix hugepages_setup when deal with pernode Peng Liu
2022-04-14 23:50 ` Mike Kravetz
2022-04-29 9:30 ` David Hildenbrand
2022-04-13 3:29 ` [PATCH v3 3/4] hugetlb: Fix return value of __setup handlers Peng Liu
2022-04-13 6:39 ` Baolin Wang
2022-04-13 7:55 ` Muchun Song
[not found] ` <5bbf45e7-1d92-f543-5cfc-bc0141999d46@huawei.com>
2022-04-13 8:21 ` Muchun Song
2022-04-13 8:45 ` Kefeng Wang
2022-04-13 9:01 ` Muchun Song
2022-04-15 0:01 ` Mike Kravetz
2022-04-15 2:24 ` Davidlohr Bueso
2022-04-29 3:02 ` [PATCH v4] mm: Using for_each_online_node and node_online instead of open coding Peng Liu
2022-04-29 9:29 ` David Hildenbrand [this message]
2022-04-29 11:44 ` Muchun Song
2022-04-13 3:29 ` [PATCH v3 4/4] hugetlb: Clean up hugetlb_cma_reserve Peng Liu
2022-04-13 5:50 ` Muchun Song
2022-04-13 6:41 ` Baolin Wang
2022-04-15 0:03 ` Mike Kravetz
2022-04-15 2:15 ` Davidlohr Bueso
2022-04-29 9:28 ` David Hildenbrand
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=95216c6f-0614-cadc-d256-92a172d8b8cd@redhat.com \
--to=david@redhat.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=dave@stgolabs.net \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liupeng256@huawei.com \
--cc=liuyuntao10@huawei.com \
--cc=mike.kravetz@oracle.com \
--cc=songmuchun@bytedance.com \
--cc=wangborong@cdjrlc.com \
--cc=wangkefeng.wang@huawei.com \
--cc=yaozhenguo1@gmail.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).