Skip to contentSkip to conversation

linux-next: drivers/memstick/core/ms_block.c

DISCUSSION [email protected] 2 participants 2 messages Feb 21, 2022 – Feb 22, 2022 Linux-next tree

lore
Share & tools
lore

[email protected]

author maintainer
#0 lore raw

Hi all,

After merging the mmc tree, today's linux-next build (x86 allmodconfig) failed like this:

/tmp/next/build/drivers/memstick/core/ms_block.c:158:6: 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

Caused by commit

5f8d171cd8a93f ("memstick: replace bitmap_weight with bitmap_weight_eq where appropriate")

I used the mmc tree from 20220217 instead.

#1 lore raw
Quoted 11 lines · On Mon, 21 Feb 2022 at 17:55, <[email protected]> wrote:

Hi all,

After merging the mmc tree, today's linux-next build (x86 allmodconfig) failed like this:

/tmp/next/build/drivers/memstick/core/ms_block.c:158:6: 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
Quoted 5 lines

Caused by commit

5f8d171cd8a93f ("memstick: replace bitmap_weight with bitmap_weight_eq where appropriate")

I used the mmc tree from 20220217 instead.

I have now dropped the offending commit from my tree. It turned out to have dependencies to additional patches.

Kind regards
Uffe