linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Javier Martinez Canillas <javierm@redhat.com>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>
Subject: [linux-next:master 4213/10218] drivers/gpu/drm/solomon/ssd130x-spi.c:154:35: warning: 'ssd130x_spi_table' defined but not used
Date: Tue, 10 May 2022 01:14:10 +0800	[thread overview]
Message-ID: <202205100114.K8ZUCbIZ-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   ab38272e99730375c5db3db1c4cebf691a0550ab
commit: 74373977d2ca26e5735377f8874be70bc2f030f5 [4213/10218] drm/solomon: Add SSD130x OLED displays SPI support
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20220510/202205100114.K8ZUCbIZ-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.2.0-20) 11.2.0
reproduce (this is a W=1 build):
        # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=74373977d2ca26e5735377f8874be70bc2f030f5
        git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
        git fetch --no-tags linux-next master
        git checkout 74373977d2ca26e5735377f8874be70bc2f030f5
        # 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/gpu/drm/solomon/

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/solomon/ssd130x-spi.c:154:35: warning: 'ssd130x_spi_table' defined but not used [-Wunused-const-variable=]
     154 | static const struct spi_device_id ssd130x_spi_table[] = {
         |                                   ^~~~~~~~~~~~~~~~~


vim +/ssd130x_spi_table +154 drivers/gpu/drm/solomon/ssd130x-spi.c

   145	
   146	/*
   147	 * The SPI core always reports a MODALIAS uevent of the form "spi:<dev>", even
   148	 * if the device was registered via OF. This means that the module will not be
   149	 * auto loaded, unless it contains an alias that matches the MODALIAS reported.
   150	 *
   151	 * To workaround this issue, add a SPI device ID table. Even when this should
   152	 * not be needed for this driver to match the registered SPI devices.
   153	 */
 > 154	static const struct spi_device_id ssd130x_spi_table[] = {
   155		{ "sh1106",  SH1106_ID },
   156		{ "ssd1305", SSD1305_ID },
   157		{ "ssd1306", SSD1306_ID },
   158		{ "ssd1307", SSD1307_ID },
   159		{ "ssd1309", SSD1309_ID },
   160		{ /* sentinel */ }
   161	};
   162	MODULE_DEVICE_TABLE(spi, ssd130x_spi_table);
   163	

-- 
0-DAY CI Kernel Test Service
https://01.org/lkp


                 reply	other threads:[~2022-05-09 17:14 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=202205100114.K8ZUCbIZ-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=geert+renesas@glider.be \
    --cc=javierm@redhat.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.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