oe-kbuild-all.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Baolin Wang <baolin.wang7@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	Bjorn Andersson <bjorn.andersson@linaro.org>
Subject: drivers/hwspinlock/omap_hwspinlock.c:165:34: warning: 'omap_hwspinlock_of_match' defined but not used
Date: Mon, 20 Feb 2023 17:37:07 +0800	[thread overview]
Message-ID: <202302201728.S4sOFmKE-lkp@intel.com> (raw)

Hi Baolin,

First bad commit (maybe != root cause):

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   c9c3395d5e3dcc6daee66c6908354d47bf98cb0c
commit: ffd0bbfb378ecd56eac22bf932ccdbf89ac7f725 hwspinlock: Allow drivers to be built with COMPILE_TEST
date:   2 years, 11 months ago
config: x86_64-buildonly-randconfig-r004-20230220 (https://download.01.org/0day-ci/archive/20230220/202302201728.S4sOFmKE-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
reproduce (this is a W=1 build):
        # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ffd0bbfb378ecd56eac22bf932ccdbf89ac7f725
        git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
        git fetch --no-tags linus master
        git checkout ffd0bbfb378ecd56eac22bf932ccdbf89ac7f725
        # save the config file
        mkdir build_dir && cp config build_dir/.config
        make W=1 O=build_dir ARCH=x86_64 olddefconfig
        make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/clk/imx/ drivers/hwspinlock/ drivers/mmc/host/ drivers/usb/phy/

If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202302201728.S4sOFmKE-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/hwspinlock/omap_hwspinlock.c:165:34: warning: 'omap_hwspinlock_of_match' defined but not used [-Wunused-const-variable=]
     165 | static const struct of_device_id omap_hwspinlock_of_match[] = {
         |                                  ^~~~~~~~~~~~~~~~~~~~~~~~


vim +/omap_hwspinlock_of_match +165 drivers/hwspinlock/omap_hwspinlock.c

70ba4cc26b9f53 Simon Que  2011-02-17  164  
65bd4341d61678 Suman Anna 2015-03-04 @165  static const struct of_device_id omap_hwspinlock_of_match[] = {
65bd4341d61678 Suman Anna 2015-03-04  166  	{ .compatible = "ti,omap4-hwspinlock", },
6fa154e282f9c8 Suman Anna 2019-05-30  167  	{ .compatible = "ti,am654-hwspinlock", },
65bd4341d61678 Suman Anna 2015-03-04  168  	{ /* end */ },
65bd4341d61678 Suman Anna 2015-03-04  169  };
65bd4341d61678 Suman Anna 2015-03-04  170  MODULE_DEVICE_TABLE(of, omap_hwspinlock_of_match);
65bd4341d61678 Suman Anna 2015-03-04  171  

:::::: The code at line 165 was first introduced by commit
:::::: 65bd4341d61678494ea14994d0d7df73644ca014 hwspinlock/omap: add support for dt nodes

:::::: TO: Suman Anna <s-anna@ti.com>
:::::: CC: Ohad Ben-Cohen <ohad@wizery.com>

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests

                 reply	other threads:[~2023-02-20  9:37 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=202302201728.S4sOFmKE-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=baolin.wang7@gmail.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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).