linux-kernel - linux-next: drivers/memstick/core/ms

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20220221165508.2633962-1-broonie@kernel.org>
Date:   Mon, 21 Feb 2022 16:55:08 +0000
From:   broonie@...nel.org
To:     Ulf Hansson <ulf.hansson@...aro.org>
Cc:     build@...r.kernel.org, failure@...r.kernel.org,
        after@...r.kernel.org, merge@...r.kernel.org, of@...r.kernel.org,
        the@...r.kernel.org, BRANCH@...r.kernel.org, tree@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: linux-next: drivers/memstick/core/ms_block.c

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.