From: Andrew Morton <akpm@linux-foundation.org>
To: Chengkaitao <pilgrimtao@gmail.com>
Cc: linux-mm@kvack.org,
"David Hildenbrand (Red Hat)" <david@kernel.org>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v6 2/2] mm: Convert vmemmap_p?d_populate() to static functions
Date: Mon, 30 Mar 2026 20:54:05 -0700 [thread overview]
Message-ID: <20260330205405.44d128cac32b971ec9134c70@linux-foundation.org> (raw)
In-Reply-To: <CAAWJmAaOL_NUtJZfHguSdPUsNVCSU0U=GWnTeVAKhnGgwSKeEg@mail.gmail.com>
On Tue, 31 Mar 2026 11:16:33 +0800 Chengkaitao <pilgrimtao@gmail.com> wrote:
> Hi Andrew Morton，
>
> I noticed this patch was dropped; the failure report is here:
> https://lore.kernel.org/all/202603251338.grra8xt7-lkp@intel.com/#R
>
> Could this be a false positive? The series has two patches: the first
> one already removed references to vmemmap_p?d_populate() on sparc; see:
> https://lore.kernel.org/all/20260201063532.44807-3-pilgrimtao@gmail.com/T/#mefaa36aeff173d08f0508cd44be46e830c067fe9
>
> Might the build error be because only the second patch was applied,
> without the first?
There was some confusion over a later patch which was there to fix an
earlier patch, only the earlier patch was dropped!
Sorry 'bout that. Can you please resend the patch after -rc1 and we'll
try again.
prev parent reply other threads:[~2026-03-31 3:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-01 6:35 [PATCH v6 0/2] Generalize vmemmap_populate_hugepages to sparc chengkaitao
2026-02-01 6:35 ` [PATCH v6 1/2] sparc: Use vmemmap_populate_hugepages for vmemmap_populate chengkaitao
2026-03-18 15:07 ` Andreas Larsson
2026-02-01 6:35 ` [PATCH v6 2/2] mm: Convert vmemmap_p?d_populate() to static functions chengkaitao
2026-02-02 9:09 ` David Hildenbrand (arm)
2026-03-31 3:16 ` Chengkaitao
2026-03-31 3:54 ` Andrew Morton [this message]
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=20260330205405.44d128cac32b971ec9134c70@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pilgrimtao@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