All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xingxing Su <suxingxing@loongson.cn>
To: dhowells@redhat.com, dwmw2@infradead.org
Cc: keyrings@vger.kernel.org, linux-kernel@vger.kernel.org,
	yangtiezhu@loongson.cn, lixuefeng@loongson.cn
Subject: [PATCH] certs/blacklist_hashes.c: Use __initconst for const init definition
Date: Mon, 15 Jun 2020 03:53:40 +0000	[thread overview]
Message-ID: <1592193220-7460-1-git-send-email-suxingxing@loongson.cn> (raw)

Fix the following checkpatch error:

ERROR: Use of const init definition must use __initconst
#4: FILE: certs/blacklist_hashes.c:4:
+const char __initdata *const blacklist_hashes[] = {

Signed-off-by: Xingxing Su <suxingxing@loongson.cn>
---
 certs/blacklist_hashes.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/certs/blacklist_hashes.c b/certs/blacklist_hashes.c
index 3448923..d5961aa 100644
--- a/certs/blacklist_hashes.c
+++ b/certs/blacklist_hashes.c
@@ -1,7 +1,7 @@
 // SPDX-License-Identifier: GPL-2.0
 #include "blacklist.h"
 
-const char __initdata *const blacklist_hashes[] = {
+const char __initconst *const blacklist_hashes[] = {
 #include CONFIG_SYSTEM_BLACKLIST_HASH_LIST
 	, NULL
 };
-- 
2.1.0

WARNING: multiple messages have this Message-ID (diff)
From: Xingxing Su <suxingxing@loongson.cn>
To: dhowells@redhat.com, dwmw2@infradead.org
Cc: keyrings@vger.kernel.org, linux-kernel@vger.kernel.org,
	yangtiezhu@loongson.cn, lixuefeng@loongson.cn
Subject: [PATCH] certs/blacklist_hashes.c: Use __initconst for const init definition
Date: Mon, 15 Jun 2020 11:53:40 +0800	[thread overview]
Message-ID: <1592193220-7460-1-git-send-email-suxingxing@loongson.cn> (raw)

Fix the following checkpatch error:

ERROR: Use of const init definition must use __initconst
#4: FILE: certs/blacklist_hashes.c:4:
+const char __initdata *const blacklist_hashes[] = {

Signed-off-by: Xingxing Su <suxingxing@loongson.cn>
---
 certs/blacklist_hashes.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/certs/blacklist_hashes.c b/certs/blacklist_hashes.c
index 3448923..d5961aa 100644
--- a/certs/blacklist_hashes.c
+++ b/certs/blacklist_hashes.c
@@ -1,7 +1,7 @@
 // SPDX-License-Identifier: GPL-2.0
 #include "blacklist.h"
 
-const char __initdata *const blacklist_hashes[] = {
+const char __initconst *const blacklist_hashes[] = {
 #include CONFIG_SYSTEM_BLACKLIST_HASH_LIST
 	, NULL
 };
-- 
2.1.0


             reply	other threads:[~2020-06-15  3:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15  3:53 Xingxing Su [this message]
2020-06-15  3:53 ` [PATCH] certs/blacklist_hashes.c: Use __initconst for const init definition Xingxing Su

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=1592193220-7460-1-git-send-email-suxingxing@loongson.cn \
    --to=suxingxing@loongson.cn \
    --cc=dhowells@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lixuefeng@loongson.cn \
    --cc=yangtiezhu@loongson.cn \
    /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 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.