From: kernel test robot <lkp@intel.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
"Darrick J. Wong" <darrick.wong@oracle.com>,
linux-kernel@vger.kernel.org
Subject: [djwong-xfs:zero-initialize-pmem 196/309] fs/xfs/xfs_trace.c:44:1: error: unused function 'xfs_btree_crack_agno_opdev'
Date: Sat, 18 Sep 2021 16:29:47 +0800 [thread overview]
Message-ID: <202109181640.XvLBE4dE-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2034 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git zero-initialize-pmem
head: f712bfd382f71deb666686b6d969dc10592e7d79
commit: e6f089b0fbe14a417feecac395659e10224a7441 [196/309] xfs: widen xfs_rmap_irec fields to handle realtime rmapbt
config: x86_64-buildonly-randconfig-r004-20210918 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project c8b3d7d6d6de37af68b2f379d0e37304f78e115f)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git/commit/?id=e6f089b0fbe14a417feecac395659e10224a7441
git remote add djwong-xfs https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git
git fetch --no-tags djwong-xfs zero-initialize-pmem
git checkout e6f089b0fbe14a417feecac395659e10224a7441
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> fs/xfs/xfs_trace.c:44:1: error: unused function 'xfs_btree_crack_agno_opdev' [-Werror,-Wunused-function]
xfs_btree_crack_agno_opdev(
^
1 error generated.
vim +/xfs_btree_crack_agno_opdev +44 fs/xfs/xfs_trace.c
42
43 static inline void
> 44 xfs_btree_crack_agno_opdev(
45 struct xfs_btree_cur *cur,
46 xfs_agnumber_t *agno,
47 dev_t *opdev)
48 {
49 if (cur->bc_flags & XFS_BTREE_ROOT_IN_INODE) {
50 *agno = 0;
51 *opdev = cur->bc_mp->m_rtdev_targp->bt_dev;
52 } else {
53 *agno = cur->bc_ag.pag->pag_agno;
54 *opdev = cur->bc_mp->m_super->s_dev;
55 }
56 }
57
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 44213 bytes --]
reply other threads:[~2021-09-18 8: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=202109181640.XvLBE4dE-lkp@intel.com \
--to=lkp@intel.com \
--cc=darrick.wong@oracle.com \
--cc=djwong@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@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
Powered by JetHome