From: Andrew Morton <akpm@linux-foundation.org>
To: Jinjiang Tu <tujinjiang@huawei.com>
Cc: David Hildenbrand <david@redhat.com>, Zi Yan <ziy@nvidia.com>,
<yuzhao@google.com>, <linux-mm@kvack.org>,
<wangkefeng.wang@huawei.com>
Subject: Re: [PATCH v2] mm/contig_alloc: fix alloc_contig_range when __GFP_COMP and order < MAX_ORDER
Date: Tue, 27 May 2025 19:19:48 -0700 [thread overview]
Message-ID: <20250527191948.2ffdc5d432dbacedeb473965@linux-foundation.org> (raw)
In-Reply-To: <4023fc44-aafb-1895-e6db-b27f11ddc7cc@huawei.com>
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.
next prev parent reply other threads:[~2025-05-28 2:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 1:36 Jinjiang Tu
2025-04-21 1:52 ` Zi Yan
2025-04-25 10:33 ` David Hildenbrand
2025-04-25 11:04 ` Zi Yan
2025-05-11 8:04 ` David Hildenbrand
2025-05-12 1:13 ` Jinjiang Tu
2025-05-28 2:19 ` Andrew Morton [this message]
2025-05-28 2:25 ` Zi Yan
2025-05-28 2:58 ` Jinjiang Tu
2025-05-28 8:43 ` David Hildenbrand
2025-05-28 12:14 ` Jinjiang Tu
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=20250527191948.2ffdc5d432dbacedeb473965@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-mm@kvack.org \
--cc=tujinjiang@huawei.com \
--cc=wangkefeng.wang@huawei.com \
--cc=yuzhao@google.com \
--cc=ziy@nvidia.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