Re: [PATCH v2] mm/contig_alloc: fix alloc_contig_range when __GFP_COMP and order < MAX_ORDER

[Zi Yan <ziy@nvidia.com>]

On 27 May 2025, at 22:19, Andrew Morton wrote:

> On Mon, 12 May 2025 09:13:31 +0800 Jinjiang Tu <tujinjiang@huawei.com> wrote:
>
>>
>>>>
>>>> The change below makes the code cleaner. Acked-by: Zi Yan
>>>> <ziy@nvidia.com>
>>>
>>> Jinjiang, can you integrate that into your patch and resend?
>>
>> Sorry for late reply. I will do it today.
>>
>
> As far as I know, this is still pending.  The patch does address a
> WARN() and it's cc:stable, so it's rather important.
>
> I'll move the v2 patch back into mm-new and shall keep it there to
> remind me to bug people about it ;)
>
>
> David (and everyone!), please don't be afraid to grab someone else's
> patch, apply changes and send it in.  Stuff happens, and doing this is well
> within accepted processes.

Hi Andrew,

Based on my understanding, this patch is fixing an out-of-tree driver
issue, so Jinjiang is responsible to resolve David’s concerns.

Hi Jinjiang,

Let me know if I miss anything. And if you are not planning to keep
working on it, please let Andrew know so he can drop it.

Thanks.

Best Regards,
Yan, Zi