All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android14-5.15 109/111] drivers/ufs/host/ufs-exynos.c:1598:34: warning: 'exynos_ufs_of_match' defined but not used
Date: Mon, 31 Jul 2023 05:37:17 +0800	[thread overview]
Message-ID: <202307310522.c8LiJApZ-lkp@intel.com> (raw)

Hi Bart,

First bad commit (maybe != root cause):

tree:   https://android.googlesource.com/kernel/common android14-5.15
head:   098173a46bca010e394c7e8e402e519f2ae3f88a
commit: 2d74ff4319d1c8a4254635d7a611562571a8e39f [109/111] UPSTREAM: scsi: ufs: Split the drivers/scsi/ufs directory
config: x86_64-buildonly-randconfig-r002-20230731 (https://download.01.org/0day-ci/archive/20230731/202307310522.c8LiJApZ-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce: (https://download.01.org/0day-ci/archive/20230731/202307310522.c8LiJApZ-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/202307310522.c8LiJApZ-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/ufs/host/ufs-exynos.c:1598:34: warning: 'exynos_ufs_of_match' defined but not used [-Wunused-const-variable=]
    1598 | static const struct of_device_id exynos_ufs_of_match[] = {
         |                                  ^~~~~~~~~~~~~~~~~~~


vim +/exynos_ufs_of_match +1598 drivers/ufs/host/ufs-exynos.c

55f4b1f73631a0 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28  1597  
55f4b1f73631a0 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28 @1598  static const struct of_device_id exynos_ufs_of_match[] = {
55f4b1f73631a0 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28  1599  	{ .compatible = "samsung,exynos7-ufs",
55f4b1f73631a0 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28  1600  	  .data	      = &exynos_ufs_drvs },
357cd07dd70f25 drivers/scsi/ufs/ufs-exynos.c Chanho Park 2021-10-18  1601  	{ .compatible = "samsung,exynosautov9-ufs",
357cd07dd70f25 drivers/scsi/ufs/ufs-exynos.c Chanho Park 2021-10-18  1602  	  .data	      = &exynosauto_ufs_drvs },
3580301d7f9d99 drivers/scsi/ufs/ufs-exynos.c Chanho Park 2021-10-18  1603  	{ .compatible = "samsung,exynosautov9-ufs-vh",
3580301d7f9d99 drivers/scsi/ufs/ufs-exynos.c Chanho Park 2021-10-18  1604  	  .data	      = &exynosauto_ufs_vh_drvs },
55f4b1f73631a0 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28  1605  	{},
55f4b1f73631a0 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28  1606  };
55f4b1f73631a0 drivers/scsi/ufs/ufs-exynos.c Alim Akhtar 2020-05-28  1607  

:::::: The code at line 1598 was first introduced by commit
:::::: 55f4b1f73631a0817717fe6e98517de51b4c3527 scsi: ufs: ufs-exynos: Add UFS host support for Exynos SoCs

:::::: TO: Alim Akhtar <alim.akhtar@samsung.com>
:::::: CC: Martin K. Petersen <martin.petersen@oracle.com>

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

                 reply	other threads:[~2023-07-30 21: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=202307310522.c8LiJApZ-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=cros-kernel-buildreports@googlegroups.com \
    --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 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.