From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [ulfh-mmc:next 20/24] drivers/memstick/core/ms_block.c:158:13: error: implicit declaration of function 'bitmap_weight_eq'; did you mean 'bitmap_weight'?
Date: Fri, 18 Feb 2022 03:47:46 +0800 [thread overview]
Message-ID: <202202180309.LIPKYeon-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2596 bytes --]
tree: git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git next
head: 4b67100bafbb3f60e6eecf87631e4d400d9b6f17
commit: 5f8d171cd8a93ff425556e7fde5d59fefc677bf7 [20/24] memstick: replace bitmap_weight with bitmap_weight_eq where appropriate
config: alpha-randconfig-r004-20220217 (https://download.01.org/0day-ci/archive/20220218/202202180309.LIPKYeon-lkp(a)intel.com/config)
compiler: alpha-linux-gcc (GCC) 11.2.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
# https://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git/commit/?id=5f8d171cd8a93ff425556e7fde5d59fefc677bf7
git remote add ulfh-mmc git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git
git fetch --no-tags ulfh-mmc next
git checkout 5f8d171cd8a93ff425556e7fde5d59fefc677bf7
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=alpha SHELL=/bin/bash drivers/memstick/core/
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 >>):
drivers/memstick/core/ms_block.c: In function 'msb_validate_used_block_bitmap':
>> drivers/memstick/core/ms_block.c:158:13: error: implicit declaration of function 'bitmap_weight_eq'; did you mean 'bitmap_weight'? [-Werror=implicit-function-declaration]
158 | if (bitmap_weight_eq(msb->used_blocks_bitmap, msb->block_count,
| ^~~~~~~~~~~~~~~~
| bitmap_weight
cc1: some warnings being treated as errors
vim +158 drivers/memstick/core/ms_block.c
145
146 /* Debug test to validate free block counts */
147 static int msb_validate_used_block_bitmap(struct msb_data *msb)
148 {
149 int total_free_blocks = 0;
150 int i;
151
152 if (!debug)
153 return 0;
154
155 for (i = 0; i < msb->zone_count; i++)
156 total_free_blocks += msb->free_block_count[i];
157
> 158 if (bitmap_weight_eq(msb->used_blocks_bitmap, msb->block_count,
159 msb->block_count - total_free_blocks))
160 return 0;
161
162 pr_err("BUG: free block counts don't match the bitmap");
163 msb->read_only = true;
164 return -EINVAL;
165 }
166
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Yury Norov <yury.norov@gmail.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: [ulfh-mmc:next 20/24] drivers/memstick/core/ms_block.c:158:13: error: implicit declaration of function 'bitmap_weight_eq'; did you mean 'bitmap_weight'?
Date: Fri, 18 Feb 2022 03:47:46 +0800 [thread overview]
Message-ID: <202202180309.LIPKYeon-lkp@intel.com> (raw)
tree: git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git next
head: 4b67100bafbb3f60e6eecf87631e4d400d9b6f17
commit: 5f8d171cd8a93ff425556e7fde5d59fefc677bf7 [20/24] memstick: replace bitmap_weight with bitmap_weight_eq where appropriate
config: alpha-randconfig-r004-20220217 (https://download.01.org/0day-ci/archive/20220218/202202180309.LIPKYeon-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 11.2.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
# https://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git/commit/?id=5f8d171cd8a93ff425556e7fde5d59fefc677bf7
git remote add ulfh-mmc git://git.kernel.org/pub/scm/linux/kernel/git/ulfh/mmc.git
git fetch --no-tags ulfh-mmc next
git checkout 5f8d171cd8a93ff425556e7fde5d59fefc677bf7
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=alpha SHELL=/bin/bash drivers/memstick/core/
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 >>):
drivers/memstick/core/ms_block.c: In function 'msb_validate_used_block_bitmap':
>> drivers/memstick/core/ms_block.c:158:13: error: implicit declaration of function 'bitmap_weight_eq'; did you mean 'bitmap_weight'? [-Werror=implicit-function-declaration]
158 | if (bitmap_weight_eq(msb->used_blocks_bitmap, msb->block_count,
| ^~~~~~~~~~~~~~~~
| bitmap_weight
cc1: some warnings being treated as errors
vim +158 drivers/memstick/core/ms_block.c
145
146 /* Debug test to validate free block counts */
147 static int msb_validate_used_block_bitmap(struct msb_data *msb)
148 {
149 int total_free_blocks = 0;
150 int i;
151
152 if (!debug)
153 return 0;
154
155 for (i = 0; i < msb->zone_count; i++)
156 total_free_blocks += msb->free_block_count[i];
157
> 158 if (bitmap_weight_eq(msb->used_blocks_bitmap, msb->block_count,
159 msb->block_count - total_free_blocks))
160 return 0;
161
162 pr_err("BUG: free block counts don't match the bitmap");
163 msb->read_only = true;
164 return -EINVAL;
165 }
166
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next reply other threads:[~2022-02-17 19:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 19:47 kernel test robot [this message]
2022-02-17 19:47 ` [ulfh-mmc:next 20/24] drivers/memstick/core/ms_block.c:158:13: error: implicit declaration of function 'bitmap_weight_eq'; did you mean 'bitmap_weight'? 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=202202180309.LIPKYeon-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@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.