public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation•org>
To: Mark Brown <broonie@kernel•org>
Cc: Lorenzo Stoakes <ljs@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: Mon, 18 May 2026 13:01:24 -0700	[thread overview]
Message-ID: <20260518130124.1da1d87bed04e422b585447b@linux-foundation.org> (raw)
In-Reply-To: <ags6IM0qGAkndEV5@sirena.org.uk>

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.

  reply	other threads:[~2026-05-18 20:01 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 [this message]
2026-05-19  7:21   ` Lorenzo Stoakes

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=20260518130124.1da1d87bed04e422b585447b@linux-foundation.org \
    --to=akpm@linux-foundation$(echo .)org \
    --cc=broonie@kernel$(echo .)org \
    --cc=david@kernel$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=ljs@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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