From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: fs/btrfs/disk-io.c:2263:2: warning: There is an unknown macro here somewhere. Configuration is required. If rbtree_postorder_for_each_entry_safe is a macro then please configure it. [unknownMacro]
Date: Fri, 01 Apr 2022 04:38:30 +0800 [thread overview]
Message-ID: <202204010449.LxLEFp4c-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2117 bytes --]
CC: kbuild-all(a)lists.01.org
BCC: lkp(a)intel.com
CC: linux-kernel(a)vger.kernel.org
TO: Josef Bacik <josef@toxicpanda.com>
CC: David Sterba <dsterba@suse.com>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 787af64d05cd528aac9ad16752d11bb1c6061bb9
commit: abed4aaae4f71a7bcdbe90a65319b6e772a2689d btrfs: track the csum, extent, and free space trees in a rb tree
date: 3 months ago
:::::: branch date: 22 hours ago
:::::: commit date: 3 months ago
compiler: ia64-linux-gcc (GCC) 11.2.0
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
cppcheck possible warnings: (new ones prefixed by >>, may not real problems)
>> fs/btrfs/disk-io.c:2263:2: warning: There is an unknown macro here somewhere. Configuration is required. If rbtree_postorder_for_each_entry_safe is a macro then please configure it. [unknownMacro]
rbtree_postorder_for_each_entry_safe(root, tmp,
^
>> fs/btrfs/volumes.c:1181:2: warning: There is an unknown macro here somewhere. Configuration is required. If list_for_each_entry_safe is a macro then please configure it. [unknownMacro]
list_for_each_entry_safe(device, tmp, &fs_devices->devices, dev_list)
^
vim +2263 fs/btrfs/disk-io.c
2e9f5954978cd5 Rashika 2013-10-31 2258
abed4aaae4f71a Josef Bacik 2021-11-05 2259 static void free_global_root_pointers(struct btrfs_fs_info *fs_info)
abed4aaae4f71a Josef Bacik 2021-11-05 2260 {
abed4aaae4f71a Josef Bacik 2021-11-05 2261 struct btrfs_root *root, *tmp;
abed4aaae4f71a Josef Bacik 2021-11-05 2262
abed4aaae4f71a Josef Bacik 2021-11-05 @2263 rbtree_postorder_for_each_entry_safe(root, tmp,
abed4aaae4f71a Josef Bacik 2021-11-05 2264 &fs_info->global_root_tree,
abed4aaae4f71a Josef Bacik 2021-11-05 2265 rb_node)
abed4aaae4f71a Josef Bacik 2021-11-05 2266 free_root_extent_buffers(root);
abed4aaae4f71a Josef Bacik 2021-11-05 2267 }
abed4aaae4f71a Josef Bacik 2021-11-05 2268
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-03-31 20:38 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=202204010449.LxLEFp4c-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild@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.