linux-kernel - Re: 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 for Android: free password hash cracker in your pocket

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

Message-ID: <CAPDyKFpBfZ3-03Tdm=cTcV7Rzwo6Z6bR1vKOJnexrrGupODQvw@mail.gmail.com>
Date:   Tue, 22 Feb 2022 16:50:17 +0100
From:   Ulf Hansson <ulf.hansson@...aro.org>
To:     broonie@...nel.org
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: drivers/memstick/core/ms_block.c

On Mon, 21 Feb 2022 at 17:55, <broonie@...nel.org> 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
>
> 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