From: "Zouwei (Samuel)" <zou_wei@huawei.com>
To: "michal.simek@xilinx.com" <michal.simek@xilinx.com>,
"rajan.vaja@xilinx.com" <rajan.vaja@xilinx.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"jolly.shah@xilinx.com" <jolly.shah@xilinx.com>,
"tejas.patel@xilinx.com" <tejas.patel@xilinx.com>,
"manish.narani@xilinx.com" <manish.narani@xilinx.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: 答复: [PATCH -next] firmware: xilinx: Mark pm_api_features_map with static keyword
Date: Tue, 1 Dec 2020 11:35:16 +0000 [thread overview]
Message-ID: <8684fa57bc064ed8a949e555e7e0ec94@huawei.com> (raw)
In-Reply-To: <1606821343-121199-1-git-send-email-zou_wei@huawei.com>
Hi all,
Please ignore this patch, there is a mistake.
I will send v2 soon
-----邮件原件-----
发件人: Zouwei (Samuel)
发送时间: 2020年12月1日 19:16
收件人: michal.simek@xilinx.com; rajan.vaja@xilinx.com; gregkh@linuxfoundation.org; jolly.shah@xilinx.com; tejas.patel@xilinx.com; manish.narani@xilinx.com
抄送: linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org; Zouwei (Samuel) <zou_wei@huawei.com>
主题: [PATCH -next] firmware: xilinx: Mark pm_api_features_map with static keyword
Fix the following sparse warning:
drivers/firmware/xilinx/zynqmp.c:32:1: warning: symbol 'pm_api_features_map' was not declared. Should it be static?
Signed-off-by: Zou Wei <zou_wei@huawei.com>
---
drivers/firmware/xilinx/zynqmp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/firmware/xilinx/zynqmp.c b/drivers/firmware/xilinx/zynqmp.c
index d08ac82..943c2ac5 100644
--- a/drivers/firmware/xilinx/zynqmp.c
+++ b/drivers/firmware/xilinx/zynqmp.c
@@ -29,7 +29,7 @@
#define PM_API_FEATURE_CHECK_MAX_ORDER 7
static bool feature_check_enabled;
-DEFINE_HASHTABLE(pm_api_features_map, PM_API_FEATURE_CHECK_MAX_ORDER);
+static EFINE_HASHTABLE(pm_api_features_map, PM_API_FEATURE_CHECK_MAX_ORDER);
/**
* struct pm_api_feature_data - PM API Feature data
--
2.6.2
prev parent reply other threads:[~2020-12-01 11:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 11:15 [PATCH -next] firmware: xilinx: Mark pm_api_features_map with static keyword Zou Wei
2020-12-01 11:35 ` Zouwei (Samuel) [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=8684fa57bc064ed8a949e555e7e0ec94@huawei.com \
--to=zou_wei@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=jolly.shah@xilinx.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manish.narani@xilinx.com \
--cc=michal.simek@xilinx.com \
--cc=rajan.vaja@xilinx.com \
--cc=tejas.patel@xilinx.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).