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:vectorized-scrub 211/312] fs/xfs/xfs_trace.c:44:1: error: unused function 'xfs_btree_crack_agno_opdev'
Date: Tue, 26 Oct 2021 20:14:43 +0800 [thread overview]
Message-ID: <202110262034.GUlDLZdm-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2132 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git vectorized-scrub
head: 1804f4671b76293a8a792e5be4e514cefc0f012f
commit: 92db6048646f07ade20aa98b310694c94e84a0e1 [211/312] xfs: widen xfs_rmap_irec fields to handle realtime rmapbt
config: arm-buildonly-randconfig-r001-20211025 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project a461fa64bb37cffd73f683c74f6b0780379fc2ca)
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
# install arm cross compiling tool for clang build
# apt-get install binutils-arm-linux-gnueabi
# https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git/commit/?id=92db6048646f07ade20aa98b310694c94e84a0e1
git remote add djwong-xfs https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git
git fetch --no-tags djwong-xfs vectorized-scrub
git checkout 92db6048646f07ade20aa98b310694c94e84a0e1
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=arm
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: 33263 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [djwong-xfs:vectorized-scrub 211/312] fs/xfs/xfs_trace.c:44:1: error: unused function 'xfs_btree_crack_agno_opdev'
Date: Tue, 26 Oct 2021 20:14:43 +0800 [thread overview]
Message-ID: <202110262034.GUlDLZdm-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2184 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git vectorized-scrub
head: 1804f4671b76293a8a792e5be4e514cefc0f012f
commit: 92db6048646f07ade20aa98b310694c94e84a0e1 [211/312] xfs: widen xfs_rmap_irec fields to handle realtime rmapbt
config: arm-buildonly-randconfig-r001-20211025 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project a461fa64bb37cffd73f683c74f6b0780379fc2ca)
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
# install arm cross compiling tool for clang build
# apt-get install binutils-arm-linux-gnueabi
# https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git/commit/?id=92db6048646f07ade20aa98b310694c94e84a0e1
git remote add djwong-xfs https://git.kernel.org/pub/scm/linux/kernel/git/djwong/xfs-linux.git
git fetch --no-tags djwong-xfs vectorized-scrub
git checkout 92db6048646f07ade20aa98b310694c94e84a0e1
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=arm
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(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 33263 bytes --]
next reply other threads:[~2021-10-26 12:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 12:14 kernel test robot [this message]
2021-10-26 12:14 ` [djwong-xfs:vectorized-scrub 211/312] fs/xfs/xfs_trace.c:44:1: error: unused function 'xfs_btree_crack_agno_opdev' 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=202110262034.GUlDLZdm-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 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.