From: Jean Delvare <jdelvare@suse.de>
To: kernel test robot <lkp@intel.com>
Cc: Sean Wang <sean.wang@mediatek.com>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Matthias Brugger <matthias.bgg@gmail.com>
Subject: Re: drivers/regulator/mt6380-regulator.c:333:34: warning: 'mt6380_of_match' defined but not used
Date: Mon, 25 Jul 2022 10:00:56 +0200 [thread overview]
Message-ID: <20220725100056.0063b193@endymion.delvare> (raw)
In-Reply-To: <202207240252.ZY5hSCNB-lkp@intel.com>
On Sun, 24 Jul 2022 02:37:15 +0800, kernel test robot wrote:
> All warnings (new ones prefixed by >>):
>
> >> drivers/regulator/mt6380-regulator.c:333:34: warning: 'mt6380_of_match' defined but not used [-Wunused-const-variable=]
> 333 | static const struct of_device_id mt6380_of_match[] = {
> | ^~~~~~~~~~~~~~~
> --
> >> drivers/soc/mediatek/mtk-pmic-wrap.c:1436:34: warning: 'of_pwrap_match_tbl' defined but not used [-Wunused-const-variable=]
> 1436 | static const struct of_device_id of_pwrap_match_tbl[] = {
> | ^~~~~~~~~~~~~~~~~~
> >> drivers/soc/mediatek/mtk-pmic-wrap.c:1370:34: warning: 'of_slave_match_tbl' defined but not used [-Wunused-const-variable=]
> 1370 | static const struct of_device_id of_slave_match_tbl[] = {
> | ^~~~~~~~~~~~~~~~~~
Not sure what do to with this one. These warnings can be silenced with
__maybe_unused. But does it actually make sense to build these drivers
with CONFIG_OF disabled?
As I understand it, that's the condition which makes the warnings
appear, and from a quick look at the code, it seems to me that the
drivers are useless then. It might make more sense to make both drivers
depend on OF. What do you think?
--
Jean Delvare
SUSE L3 Support
prev parent reply other threads:[~2022-07-25 8:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-23 18:37 kernel test robot
2022-07-25 8:00 ` Jean Delvare [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=20220725100056.0063b193@endymion.delvare \
--to=jdelvare@suse.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=matthias.bgg@gmail.com \
--cc=sean.wang@mediatek.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
all inboxes | Powered by JetHome®