From: kernel test robot <lkp@intel.com>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Steev Klimaszewski <steev@kali.org>
Subject: [steev:c630-6.0.0-rc3 55/94] drivers/soc/qcom/pmic_glink.c:200:34: warning: 'pmic_glink_of_match' defined but not used
Date: Sat, 3 Sep 2022 21:42:07 +0800 [thread overview]
Message-ID: <202209032155.zm12fhX7-lkp@intel.com> (raw)
tree: https://github.com/steev/linux c630-6.0.0-rc3
head: 012f3cdd2a60528b877305877b52135b0076e028
commit: 20a897f2e309490859a53e4627b72227768dcd84 [55/94] soc: qcom: pmic_glink: Introduce base PMIC GLINK driver
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20220903/202209032155.zm12fhX7-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-5) 11.3.0
reproduce (this is a W=1 build):
# https://github.com/steev/linux/commit/20a897f2e309490859a53e4627b72227768dcd84
git remote add steev https://github.com/steev/linux
git fetch --no-tags steev c630-6.0.0-rc3
git checkout 20a897f2e309490859a53e4627b72227768dcd84
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/soc/qcom/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/soc/qcom/pmic_glink.c:200:34: warning: 'pmic_glink_of_match' defined but not used [-Wunused-const-variable=]
200 | static const struct of_device_id pmic_glink_of_match[] = {
| ^~~~~~~~~~~~~~~~~~~
vim +/pmic_glink_of_match +200 drivers/soc/qcom/pmic_glink.c
199
> 200 static const struct of_device_id pmic_glink_of_match[] = {
201 { .compatible = "qcom,pmic-glink", },
202 {}
203 };
204 MODULE_DEVICE_TABLE(of, pmic_glink_of_match);
205
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-09-03 13:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202209032155.zm12fhX7-lkp@intel.com \
--to=lkp@intel.com \
--cc=bjorn.andersson@linaro.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=steev@kali.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
all inboxes | Powered by JetHome®