From: Nathan Chancellor <nathan@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: [GIT PULL] Clang build fix for 7.1
Date: Thu, 23 Apr 2026 17:04:13 -0700 [thread overview]
Message-ID: <20260424000413.GA1031124@ax162> (raw)
Hi Linus,
Please pull this single build fix for an instance of a new clang
subwarning under -Wunused-but-set-variable, -Wunused-but-set-global,
that appears in certs/extract-cert.c. If there are any issues, please
let me know.
Cheers,
Nathan
The following changes since commit 028ef9c96e96197026887c0f092424679298aae8:
Linux 7.0 (2026-04-12 13:48:06 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/nathan/linux.git tags/clang-fixes-7.1-1
for you to fetch changes up to 4f96b7c68a9904e01049ef610d701b382dca9574:
extract-cert: Wrap key_pass with '#ifdef USE_PKCS11_ENGINE' (2026-04-16 14:21:10 -0700)
----------------------------------------------------------------
Clang build fixes for 7.1
- Wrap declaration and assignment of key_pass in certs/extract-cert.c
with '#ifdef' that matches its only usage to clear up an instance of a
new clang subwarning, -Wunused-but-set-global.
Signed-off-by: Nathan Chancellor <nathan@kernel.org>
----------------------------------------------------------------
Nathan Chancellor (1):
extract-cert: Wrap key_pass with '#ifdef USE_PKCS11_ENGINE'
certs/extract-cert.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
next reply other threads:[~2026-04-24 0:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 0:04 Nathan Chancellor [this message]
2026-04-24 16:33 ` [GIT PULL] Clang build fix for 7.1 Linus Torvalds
2026-04-24 17:13 ` Nathan Chancellor
2026-04-24 18:32 ` pr-tracker-bot
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=20260424000413.GA1031124@ax162 \
--to=nathan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--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