From: "Arnd Bergmann" <arnd@arndb.de>
To: "Dev Jain" <dev.jain@arm.com>, "Arnd Bergmann" <arnd@kernel.org>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Will Deacon" <will@kernel.org>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Ryan Roberts" <ryan.roberts@arm.com>,
"Anshuman Khandual" <anshuman.khandual@arm.com>,
"Rohan McLure" <rmclure@linux.ibm.com>,
"Kevin Brodsky" <kevin.brodsky@arm.com>,
"Baolin Wang" <baolin.wang@linux.alibaba.com>,
"Alistair Popple" <apopple@nvidia.com>,
"Andrew Donnellan" <ajd@linux.ibm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [v2] arm64: hugetlbpage: avoid unused-but-set-parameter warning (gcc-16)
Date: Mon, 16 Feb 2026 12:48:59 +0100 [thread overview]
Message-ID: <6482195e-5230-468c-95ac-625da1b233d8@app.fastmail.com> (raw)
In-Reply-To: <b7711ebd-02fb-4cab-ade3-f4ff2f738de9@arm.com>
On Mon, Feb 16, 2026, at 07:31, Dev Jain wrote:
> On 13/02/26 9:52 pm, Arnd Bergmann wrote:
>>
>> The issue here is that __pte_clear() does not actually use its second
>> argument when CONFIG_ARM64_CONTPTE is disabled.
>
> But that is true even when the config is on? __pte_clear has an
> unconditional definition.
>
No, you're right. I'll rephrase the changelog and send a v3.
When CONFIG_ARM64_CONTPTE is disabled, the warning doesn't
appear because the argument is unused by never changed as the
loop collapses into a single call.
Arnd
prev parent reply other threads:[~2026-02-16 11:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 16:22 Arnd Bergmann
2026-02-16 6:31 ` Dev Jain
2026-02-16 11:48 ` Arnd Bergmann [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=6482195e-5230-468c-95ac-625da1b233d8@app.fastmail.com \
--to=arnd@arndb.de \
--cc=ajd@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=apopple@nvidia.com \
--cc=arnd@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=catalin.marinas@arm.com \
--cc=dev.jain@arm.com \
--cc=kevin.brodsky@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmclure@linux.ibm.com \
--cc=ryan.roberts@arm.com \
--cc=will@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 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®