All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [kdave-btrfs-devel:misc-next 100/109] fs/btrfs/sysfs.c:1355:5: sparse: sparse: symbol 'btrfs_sysfs_add_fs_devices' was not declared. Should it be
Date: Thu, 10 Sep 2020 20:38:52 +0800	[thread overview]
Message-ID: <202009102049.EdhTzGW4%lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]

tree:   https://github.com/kdave/btrfs-devel.git misc-next
head:   a99530d13cc95eec4869544f8000bbf7755d671b
commit: fd8e11fb8ffcb957a87dd0897b2e8c8535167391 [100/109] btrfs: simplify parameters of btrfs_sysfs_add_devices_dir
config: i386-randconfig-s002-20200909 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce:
        # apt-get install sparse
        # sparse version: v0.6.2-191-g10164920-dirty
        git checkout fd8e11fb8ffcb957a87dd0897b2e8c8535167391
        # save the attached .config to linux build tree
        make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=i386 

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 >>)

>> fs/btrfs/sysfs.c:1355:5: sparse: sparse: symbol 'btrfs_sysfs_add_fs_devices' was not declared. Should it be static?
   fs/btrfs/sysfs.c:534:9: sparse: sparse: context imbalance in 'btrfs_show_u64' - different lock contexts for basic block

Please review and possibly fold the followup patch.

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

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 38635 bytes --]

             reply	other threads:[~2020-09-10 12:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-10 12:38 kernel test robot [this message]
2020-09-10 12:38 ` [RFC PATCH kdave-btrfs-devel] btrfs: btrfs_sysfs_add_fs_devices() can be static kernel test robot

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=202009102049.EdhTzGW4%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 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.