From: kernel test robot <lkp@intel.com>
To: Kent Overstreet <kmo@daterainc.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Brian Foster <bfoster@redhat.com>,
linux-bcachefs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [linux-next:master 15635/16110] fs/bcachefs/disk_groups.c:534:6: sparse: sparse: symbol 'bch2_target_to_text_sb' was not declared. Should it be static?
Date: Fri, 3 Nov 2023 10:41:43 +0800 [thread overview]
Message-ID: <202311031030.xZT1XBXd-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: ab57716449b3438c0136f6f412a2e59e0cf037a9
commit: bf0d9e89de2e62fe9967ebb77b68d58d3812e4db [15635/16110] bcachefs: Split apart bch2_target_to_text(), bch2_target_to_text_sb()
config: i386-randconfig-061-20231102 (https://download.01.org/0day-ci/archive/20231103/202311031030.xZT1XBXd-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231103/202311031030.xZT1XBXd-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/202311031030.xZT1XBXd-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
fs/bcachefs/disk_groups.c: note: in included file:
fs/bcachefs/bcachefs.h:957:9: sparse: sparse: array of flexible structures
>> fs/bcachefs/disk_groups.c:534:6: sparse: sparse: symbol 'bch2_target_to_text_sb' was not declared. Should it be static?
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-11-03 2:42 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=202311031030.xZT1XBXd-lkp@intel.com \
--to=lkp@intel.com \
--cc=bfoster@redhat.com \
--cc=kmo@daterainc.com \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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