From: Lorenzo Stoakes <ljs@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mark Brown <broonie@kernel.org>,
David Hildenbrand <david@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure in final buil
Date: Tue, 19 May 2026 08:21:25 +0100 [thread overview]
Message-ID: <agwPOuMRifldkUiP@lucifer> (raw)
In-Reply-To: <20260518130124.1da1d87bed04e422b585447b@linux-foundation.org>
On Mon, May 18, 2026 at 01:01:24PM -0700, Andrew Morton wrote:
> On Mon, 18 May 2026 17:11:12 +0100 Mark Brown <broonie@kernel.org> wrote:
>
> > During the final builds today's linux-next build (powerpc
> > pseries_le_defconfig) failed like this:
> >
> > /tmp/next/build/mm/hugetlb.c: In function 'hugetlb_unshare_pmds':
> > /tmp/next/build/mm/hugetlb.c:7282:17: error: implicit declaration of function '__huge_pmd_unshare'; did you mean 'huge_pmd_unshare'? [-Wimplicit-function-declaration]
> > 7282 | __huge_pmd_unshare(&tlb, vma, address, ptep, take_locks);
> > | ^~~~~~~~~~~~~~~~~~
> > | huge_pmd_unshare
> > make[4]: *** [/tmp/next/build/scripts/Makefile.build:289
> >
> > Caused by commit
> >
> > 2bb8fe16f7bf4 (mm/hugetlb: avoid false positive lockdep assertion)
> >
> > I have reverted this commit for today.
>
> I removed this from mm.git on May 15, but I cannot find the email which
> prompted me to do that :(
>
> Oh well, I assume Lorenzo will send a new version, thanks.
I sent a fix-patch for this, but will send a respin today if that's easier.
This is a trivial 'forgot to add a stub for a certain config' thing.
Cheers, Lorenzo
prev parent reply other threads:[~2026-05-19 7:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 16:11 linux-next: build failure in final buil Mark Brown
2026-05-18 20:01 ` Andrew Morton
2026-05-19 7:21 ` Lorenzo Stoakes [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=agwPOuMRifldkUiP@lucifer \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=david@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.