mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: drivers/platform/x86/asus-tf103c-dock.c:253:22: sparse: sparse: symbol 'tf103c_dock_hid_ll_driver' was not declared. Should it be static?
Date: Thu, 13 Jan 2022 10:29:41 +0800	[thread overview]
Message-ID: <202201131019.hPdr89Fv-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   362f533a2a1098fe95020cb59340023e9b11d062
commit: 0a6509b0926dea5ebbd2c86551b7681b00585961 platform/x86: Add Asus TF103C dock driver
date:   8 days ago
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20220113/202201131019.hPdr89Fv-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.4-dirty
        # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0a6509b0926dea5ebbd2c86551b7681b00585961
        git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
        git fetch --no-tags linus master
        git checkout 0a6509b0926dea5ebbd2c86551b7681b00585961
        # save the config file to linux build tree
        mkdir build_dir
        make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/platform/x86/

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


sparse warnings: (new ones prefixed by >>)
>> drivers/platform/x86/asus-tf103c-dock.c:253:22: sparse: sparse: symbol 'tf103c_dock_hid_ll_driver' was not declared. Should it be static?
>> drivers/platform/x86/asus-tf103c-dock.c:924:1: sparse: sparse: symbol 'tf103c_dock_pm_ops' was not declared. Should it be static?

vim +/tf103c_dock_hid_ll_driver +253 drivers/platform/x86/asus-tf103c-dock.c

   252	
 > 253	struct hid_ll_driver tf103c_dock_hid_ll_driver = {
   254		.parse = tf103c_dock_hid_parse,
   255		.start = tf103c_dock_hid_start,
   256		.stop = tf103c_dock_hid_stop,
   257		.open = tf103c_dock_hid_open,
   258		.close = tf103c_dock_hid_close,
   259		.raw_request = tf103c_dock_hid_raw_request,
   260	};
   261	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

                 reply	other threads:[~2022-01-13  2:30 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=202201131019.hPdr89Fv-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=hdegoede@redhat.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.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

Powered by JetHome