From: Hardik Garg <hargar@linux.microsoft.com>
To: gregkh@linuxfoundation.org
Cc: akpm@linux-foundation.org, broonie@kernel.org, conor@kernel.org,
f.fainelli@gmail.com, hargar@microsoft.com, jonathanh@nvidia.com,
linux-kernel@vger.kernel.org, linux@roeck-us.net,
lkft-triage@lists.linaro.org, patches@kernelci.org,
patches@lists.linux.dev, pavel@denx.de, rwarsow@gmx.de,
shuah@kernel.org, srw@sladewatkins.net, stable@vger.kernel.org,
sudipm.mukherjee@gmail.com, torvalds@linux-foundation.org
Subject: Re: [PATCH 6.12 000/150] 6.12.18-rc1 review
Date: Thu, 6 Mar 2025 08:23:28 -0800 [thread overview]
Message-ID: <1741278208-30319-1-git-send-email-hargar@linux.microsoft.com> (raw)
In-Reply-To: <20250305174503.801402104@linuxfoundation.org>
The kernel, bpf tool, perf tool, and kselftest builds fine for v6.12.18-rc1 on x86 Azure VM.
Kernel binary size for x86 build:
text data bss dec hex filename
27755354 17713522 6397952 51866828 3176ccc vmlinux
arm64 build on Azure VM fails with the following error:
CC arch/arm64/kernel/vdso.o
arch/arm64/mm/hugetlbpage.c: In function 'huge_ptep_get_and_clear':
arch/arm64/mm/hugetlbpage.c:386:35: error: 'sz' undeclared (first use in this function); did you mean 's8'?
386 | ncontig = num_contig_ptes(sz, &pgsize);
| ^~
| s8
arch/arm64/mm/hugetlbpage.c:386:35: note: each undeclared identifier is reported only once for each function it appears in
Same issue with v6.13.6-rc1
Tested-by: Hardik Garg <hargar@linux.microsoft.com>
Thanks,
Hardik
prev parent reply other threads:[~2025-03-06 16:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 17:47 [PATCH 6.12 000/150] 6.12.18-rc1 review Greg Kroah-Hartman
2025-03-06 1:11 ` SeongJae Park
2025-03-06 2:48 ` Peter Schneider
2025-03-06 8:10 ` Ron Economos
2025-03-06 12:11 ` Naresh Kamboju
2025-03-06 13:01 ` Ryan Roberts
2025-03-06 12:14 ` Jon Hunter
2025-03-06 15:54 ` Shuah Khan
2025-03-06 16:23 ` Hardik Garg [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=1741278208-30319-1-git-send-email-hargar@linux.microsoft.com \
--to=hargar@linux.microsoft.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=jonathanh@nvidia.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@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--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