From: kernel test robot <lkp@intel.com>
To: David Sterba <dsterba@suse.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: fs/btrfs/tests/../ctree.h:2166:8: warning: type qualifiers ignored on function return type
Date: Mon, 27 Jul 2020 23:02:07 +0800 [thread overview]
Message-ID: <202007272305.7v7EMn6N%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 4310 bytes --]
Hi David,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 92ed301919932f777713b9172e525674157e983d
commit: f7cea56c0fff95bd5a6cd21b9fa299f66193b604 btrfs: sysfs: export supported checksums
date: 8 months ago
config: h8300-randconfig-r021-20200727 (attached as .config)
compiler: h8300-linux-gcc (GCC) 9.3.0
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
git checkout f7cea56c0fff95bd5a6cd21b9fa299f66193b604
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=h8300
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
In file included from fs/btrfs/tests/extent-map-tests.c:8:
>> fs/btrfs/tests/../ctree.h:2166:8: warning: type qualifiers ignored on function return type [-Wignored-qualifiers]
2166 | size_t __const btrfs_get_num_csums(void);
| ^~~~~~~
vim +2166 fs/btrfs/tests/../ctree.h
2113
2114 /* struct btrfs_super_block */
2115 BTRFS_SETGET_STACK_FUNCS(super_bytenr, struct btrfs_super_block, bytenr, 64);
2116 BTRFS_SETGET_STACK_FUNCS(super_flags, struct btrfs_super_block, flags, 64);
2117 BTRFS_SETGET_STACK_FUNCS(super_generation, struct btrfs_super_block,
2118 generation, 64);
2119 BTRFS_SETGET_STACK_FUNCS(super_root, struct btrfs_super_block, root, 64);
2120 BTRFS_SETGET_STACK_FUNCS(super_sys_array_size,
2121 struct btrfs_super_block, sys_chunk_array_size, 32);
2122 BTRFS_SETGET_STACK_FUNCS(super_chunk_root_generation,
2123 struct btrfs_super_block, chunk_root_generation, 64);
2124 BTRFS_SETGET_STACK_FUNCS(super_root_level, struct btrfs_super_block,
2125 root_level, 8);
2126 BTRFS_SETGET_STACK_FUNCS(super_chunk_root, struct btrfs_super_block,
2127 chunk_root, 64);
2128 BTRFS_SETGET_STACK_FUNCS(super_chunk_root_level, struct btrfs_super_block,
2129 chunk_root_level, 8);
2130 BTRFS_SETGET_STACK_FUNCS(super_log_root, struct btrfs_super_block,
2131 log_root, 64);
2132 BTRFS_SETGET_STACK_FUNCS(super_log_root_transid, struct btrfs_super_block,
2133 log_root_transid, 64);
2134 BTRFS_SETGET_STACK_FUNCS(super_log_root_level, struct btrfs_super_block,
2135 log_root_level, 8);
2136 BTRFS_SETGET_STACK_FUNCS(super_total_bytes, struct btrfs_super_block,
2137 total_bytes, 64);
2138 BTRFS_SETGET_STACK_FUNCS(super_bytes_used, struct btrfs_super_block,
2139 bytes_used, 64);
2140 BTRFS_SETGET_STACK_FUNCS(super_sectorsize, struct btrfs_super_block,
2141 sectorsize, 32);
2142 BTRFS_SETGET_STACK_FUNCS(super_nodesize, struct btrfs_super_block,
2143 nodesize, 32);
2144 BTRFS_SETGET_STACK_FUNCS(super_stripesize, struct btrfs_super_block,
2145 stripesize, 32);
2146 BTRFS_SETGET_STACK_FUNCS(super_root_dir, struct btrfs_super_block,
2147 root_dir_objectid, 64);
2148 BTRFS_SETGET_STACK_FUNCS(super_num_devices, struct btrfs_super_block,
2149 num_devices, 64);
2150 BTRFS_SETGET_STACK_FUNCS(super_compat_flags, struct btrfs_super_block,
2151 compat_flags, 64);
2152 BTRFS_SETGET_STACK_FUNCS(super_compat_ro_flags, struct btrfs_super_block,
2153 compat_ro_flags, 64);
2154 BTRFS_SETGET_STACK_FUNCS(super_incompat_flags, struct btrfs_super_block,
2155 incompat_flags, 64);
2156 BTRFS_SETGET_STACK_FUNCS(super_csum_type, struct btrfs_super_block,
2157 csum_type, 16);
2158 BTRFS_SETGET_STACK_FUNCS(super_cache_generation, struct btrfs_super_block,
2159 cache_generation, 64);
2160 BTRFS_SETGET_STACK_FUNCS(super_magic, struct btrfs_super_block, magic, 64);
2161 BTRFS_SETGET_STACK_FUNCS(super_uuid_tree_generation, struct btrfs_super_block,
2162 uuid_tree_generation, 64);
2163
2164 int btrfs_super_csum_size(const struct btrfs_super_block *s);
2165 const char *btrfs_super_csum_name(u16 csum_type);
> 2166 size_t __const btrfs_get_num_csums(void);
2167
2168
---
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: 27287 bytes --]
next reply other threads:[~2020-07-27 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 15:02 kernel test robot [this message]
2020-07-27 15:35 ` David Sterba
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=202007272305.7v7EMn6N%lkp@intel.com \
--to=lkp@intel.com \
--cc=dsterba@suse.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®