From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Michael Ellerman <mpe@ellerman.id.au>,
PowerPC <linuxppc-dev@lists.ozlabs.org>
Cc: Eric Richter <erichte@linux.ibm.com>,
Nayna Jain <nayna@linux.ibm.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: linux-next: build warning after merge of the powerpc tree
Date: Thu, 14 Nov 2019 09:34:03 +1100 [thread overview]
Message-ID: <20191114093403.43a1aa21@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]
Hi all,
After merging the powerpc tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
security/integrity/platform_certs/load_uefi.c:17:19: warning: 'efi_cert_sha256_guid' defined but not used [-Wunused-variable]
17 | static efi_guid_t efi_cert_sha256_guid __initdata = EFI_CERT_SHA256_GUID;
| ^~~~~~~~~~~~~~~~~~~~
security/integrity/platform_certs/load_uefi.c:15:19: warning: 'efi_cert_x509_sha256_guid' defined but not used [-Wunused-variable]
15 | static efi_guid_t efi_cert_x509_sha256_guid __initdata =
| ^~~~~~~~~~~~~~~~~~~~~~~~~
security/integrity/platform_certs/load_uefi.c:14:19: warning: 'efi_cert_x509_guid' defined but not used [-Wunused-variable]
14 | static efi_guid_t efi_cert_x509_guid __initdata = EFI_CERT_X509_GUID;
| ^~~~~~~~~~~~~~~~~~
Introduced by commit
ad723674d675 ("x86/efi: move common keyring handler functions to new file")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-11-13 22:36 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 22:34 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-13 10:28 linux-next: build warning after merge of the powerpc tree Stephen Rothwell
2025-05-29 23:44 ` Stephen Rothwell
2025-05-30 13:10 ` Athira Rajeev
2025-04-29 8:57 Stephen Rothwell
2025-04-29 8:17 Stephen Rothwell
2025-02-19 4:46 Stephen Rothwell
2025-02-19 5:23 ` Madhavan Srinivasan
2025-02-19 5:49 ` Andrew Donnellan
2024-11-20 6:13 Stephen Rothwell
2024-05-15 6:37 Stephen Rothwell
2024-05-16 2:42 ` Michael Ellerman
2024-05-16 4:36 ` Stephen Rothwell
2023-02-16 3:40 Stephen Rothwell
2023-02-16 18:06 ` Josh Poimboeuf
2023-02-17 1:35 ` Michael Ellerman
2023-02-17 7:05 ` Josh Poimboeuf
2021-08-23 9:55 Stephen Rothwell
2021-08-23 10:48 ` Stephen Rothwell
2021-08-23 14:19 ` Jonathan Corbet
2021-08-23 23:21 ` Stephen Rothwell
2021-08-24 5:18 ` Aneesh Kumar K.V
2021-08-24 13:46 ` Jonathan Corbet
2021-04-15 8:52 Stephen Rothwell
2021-04-16 10:54 ` Michael Ellerman
2021-04-14 23:36 Stephen Rothwell
2017-09-04 8:53 Stephen Rothwell
2017-09-04 8:59 ` Cédric Le Goater
2015-10-20 5:21 Stephen Rothwell
2015-10-20 10:06 ` Michael Ellerman
2015-10-20 20:45 ` Stephen Rothwell
2011-05-19 3:19 Stephen Rothwell
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=20191114093403.43a1aa21@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=erichte@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=nayna@linux.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).