From: Jon Hunter <jonathanh@nvidia.com>
To: Dominique Martinet <asmadeus@codewreck.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@nabladev.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
sr@sladewatkins.com
Subject: Re: [PATCH 6.12 000/403] 6.12.109-rc1 review
Date: Fri, 4 Sep 2026 11:34:27 +0100 [thread overview]
Message-ID: <88e9b4e7-284b-4943-b0f7-97795d63991b@nvidia.com> (raw)
In-Reply-To: <apqKYeQe-78JWI3u@codewreck.org>
On 04/09/2026 10:07, Dominique Martinet wrote:
>
>> Dev Jain <dev.jain@arm.com>
>> mm/page_vma_mapped: use huge_ptep_get() for hugetlb
>
> This fails build on arm (config attached)
>
> CC mm/page_vma_mapped.o
> ../mm/page_vma_mapped.c: In function 'check_pte':
> ../mm/page_vma_mapped.c:103:25: error: implicit declaration of function 'huge_ptep_get' [-Wimplicit-function-declaratio]
> 103 | ptent = huge_ptep_get(pvmw->vma->vm_mm, pvmw->address,
> | ^~~~~~~~~~~~~
> make[3]: *** [../scripts/Makefile.build:229: mm/page_vma_mapped.o] Error
>
>
> Don't have time to look further right now, might have a look after kids
> sleep if nobody beat me to it
I see the same (appears to break 6.18.y too) and bisect points to ...
# first bad commit: [25fb3e9ad3b665b57e218dafb58acd13b1a672b7] mm/migrate: use huge_ptep_get() in remove_migration_pte()
Jon
--
nvpublic
next prev parent reply other threads:[~2026-09-04 10:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 4:56 Greg Kroah-Hartman
2026-09-04 9:07 ` Dominique Martinet
2026-09-04 10:34 ` Jon Hunter [this message]
2026-09-04 12:55 ` Dominique Martinet
2026-09-04 13:09 ` Pavel Machek
2026-09-04 12:52 ` Brett A C Sheffield
2026-09-04 21:11 ` Shuah Khan
2026-09-05 11:31 ` Miguel Ojeda
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=88e9b4e7-284b-4943-b0f7-97795d63991b@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=asmadeus@codewreck.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@nabladev.com \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=sr@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®