From: Stefan Agner <stefan@agner.ch> To: dhowells@redhat.com, dwmw2@infradead.org Cc: keyrings@vger.kernel.org, linux-kernel@vger.kernel.org, Stefan Agner <stefan@agner.ch>, Andi Kleen <ak@linux.intel.com> Subject: [PATCH] KEYS: fix const section declaration in certs blacklist Date: Mon, 19 Mar 2018 22:07:35 +0000 [thread overview] Message-ID: <20180319220735.11520-1-stefan@agner.ch> (raw) Use __initconst, not __initdata also in header file. This fixes a warning generated by clang: certs/blacklist_nohashes.c:4:12: warning: section does not match previous declaration [-Wsection] const char __initconst *const blacklist_hashes[] = { ^ .. certs/blacklist.h:3:19: note: previous attribute is here extern const char __initdata *const blacklist_hashes[]; ^ Cc: Andi Kleen <ak@linux.intel.com> Cc: David Howells <dhowells@redhat.com> Signed-off-by: Stefan Agner <stefan@agner.ch> --- certs/blacklist.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/certs/blacklist.h b/certs/blacklist.h index 150d82da8e99..1efd6fa0dc60 100644 --- a/certs/blacklist.h +++ b/certs/blacklist.h @@ -1,3 +1,3 @@ #include <linux/kernel.h> -extern const char __initdata *const blacklist_hashes[]; +extern const char __initconst *const blacklist_hashes[]; -- 2.16.2
WARNING: multiple messages have this Message-ID (diff)
From: Stefan Agner <stefan@agner.ch> To: dhowells@redhat.com, dwmw2@infradead.org Cc: keyrings@vger.kernel.org, linux-kernel@vger.kernel.org, Stefan Agner <stefan@agner.ch>, Andi Kleen <ak@linux.intel.com> Subject: [PATCH] KEYS: fix const section declaration in certs blacklist Date: Mon, 19 Mar 2018 23:07:35 +0100 [thread overview] Message-ID: <20180319220735.11520-1-stefan@agner.ch> (raw) Use __initconst, not __initdata also in header file. This fixes a warning generated by clang: certs/blacklist_nohashes.c:4:12: warning: section does not match previous declaration [-Wsection] const char __initconst *const blacklist_hashes[] = { ^ .. certs/blacklist.h:3:19: note: previous attribute is here extern const char __initdata *const blacklist_hashes[]; ^ Cc: Andi Kleen <ak@linux.intel.com> Cc: David Howells <dhowells@redhat.com> Signed-off-by: Stefan Agner <stefan@agner.ch> --- certs/blacklist.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/certs/blacklist.h b/certs/blacklist.h index 150d82da8e99..1efd6fa0dc60 100644 --- a/certs/blacklist.h +++ b/certs/blacklist.h @@ -1,3 +1,3 @@ #include <linux/kernel.h> -extern const char __initdata *const blacklist_hashes[]; +extern const char __initconst *const blacklist_hashes[]; -- 2.16.2
next reply other threads:[~2018-03-19 22:07 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-03-19 22:07 Stefan Agner [this message] 2018-03-19 22:07 ` [PATCH] KEYS: fix const section declaration in certs blacklist Stefan Agner
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=20180319220735.11520-1-stefan@agner.ch \ --to=stefan@agner.ch \ --cc=ak@linux.intel.com \ --cc=dhowells@redhat.com \ --cc=dwmw2@infradead.org \ --cc=keyrings@vger.kernel.org \ --cc=linux-kernel@vger.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.