From: kernel test robot <lkp@intel.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [freescale-fslc:pr/640 15326/24604] drivers/leds/leds-pca995x.c:280:34: warning: 'of_pca995x_match' defined but not used
Date: Thu, 7 Sep 2023 01:20:42 +0800 [thread overview]
Message-ID: <202309070106.sAD2CnSF-lkp@intel.com> (raw)
tree: https://github.com/Freescale/linux-fslc pr/640
head: 20d5c9a132fc5a44f95fe7410c3cac6f43f0bd6c
commit: 8d95b5f8d03c993efd374d585823eefe84138d2c [15326/24604] LF-6247-3: driver: leds: pca995x: Add support for PCA995X chips
config: x86_64-randconfig-016-20230906 (https://download.01.org/0day-ci/archive/20230907/202309070106.sAD2CnSF-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230907/202309070106.sAD2CnSF-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202309070106.sAD2CnSF-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/leds/leds-pca995x.c:280:34: warning: 'of_pca995x_match' defined but not used [-Wunused-const-variable=]
static const struct of_device_id of_pca995x_match[] = {
^~~~~~~~~~~~~~~~
vim +/of_pca995x_match +280 drivers/leds/leds-pca995x.c
279
> 280 static const struct of_device_id of_pca995x_match[] = {
281 {.compatible = "nxp,pca9955btw", .data = (void *) pca9955btw},
282 {.compatible = "nxp,pca995xtw", .data = (void *) pca995xtw},
283 {},
284 };
285
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-09-06 17:21 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=202309070106.sAD2CnSF-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=otavio@ossystems.com.br \
/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.