[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <B655AC6F-B6B5-4B1A-96F4-DF9EE52993D0@nvidia.com>
Date: Thu, 14 Aug 2025 22:01:32 -0400
From: Zi Yan <ziy@...dia.com>
To: Ye Liu <ye.liu@...ux.dev>
Cc: Johannes Weiner <hannes@...xchg.org>,
Andrew Morton <akpm@...ux-foundation.org>, Vlastimil Babka <vbabka@...e.cz>,
Ye Liu <liuye@...inos.cn>, Suren Baghdasaryan <surenb@...gle.com>,
Michal Hocko <mhocko@...e.com>, Brendan Jackman <jackmanb@...gle.com>,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm/page_alloc: simplify lowmem_reserve max calculation
On 14 Aug 2025, at 21:59, Ye Liu wrote:
> 在 2025/8/14 22:07, Johannes Weiner 写道:
>> On Thu, Aug 14, 2025 at 05:00:52PM +0800, Ye Liu wrote:
>>> From: Ye Liu <liuye@...inos.cn>
>>>
>>> Use max() macro to simplify the calculation of maximum lowmem_reserve
>>> value in calculate_totalreserve_pages(), instead of open-coding the
>>> comparison. The functionality remains identical.
>>>
>>> Signed-off-by: Ye Liu <liuye@...inos.cn>
>>
>> You can remove the {} from the for block as well now.
>
> I agree to delete it, but I noticed a patch has been added to the -mm
> mm-new branch by Andrew Morton[1]. What should I do now? Send v2 ?
> Or send a new patch? If this is my first time, please feel free to give me some advice.
> [1]:https://lore.kernel.org/all/20250815004917.03FD7C4CEED@smtp.kernel.org/
If you read the message carefully, you will see:
“Please do not hesitate to respond to
review feedback and post updated versions to replace or incrementally
fixup patches in mm-new.”
So feel free to send v2.
Best Regards,
Yan, Zi
Powered by blists - more mailing lists