linux-kernel - Re: linux-next: build failure after merge of the block tree

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAJ-ks9=V_JmzEaXUrHPm6K-DyTgkxEhrPCW=2ZgDJpc+4Z83_A@mail.gmail.com>
Date: Mon, 19 Jan 2026 13:18:09 -0500
From: Tamir Duberstein <tamird@...il.com>
To: Mark Brown <broonie@...nel.org>, Andreas Hindborg <a.hindborg@...nel.org>
Cc: Jens Axboe <axboe@...nel.dk>, Miguel Ojeda <ojeda@...nel.org>, 
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, 
	Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the block tree

On Mon, Jan 19, 2026 at 1:13 PM Mark Brown <broonie@...nel.org> wrote:
>
> On Mon, Jan 19, 2026 at 06:02:20PM +0000, Mark Brown wrote:
>
> > Caused by commit
>
> >   4cef2fcda3ada (rnull: replace `kernel::c_str!` with C-Strings)
>
> > I have used the version from 20260116 instead.
>
> Actually that's been there for a while so I'll just revert the commit
> instead.

Ah yes, this is the combination of
https://lore.kernel.org/all/20251222-cstr-configfs-v1-1-cc1665c51c43@gmail.com/
and https://lore.kernel.org/all/20251222-cstr-block-v1-1-fdab28bb7367@gmail.com/
going through different trees. With both changes, the import becomes
unused. Can the import be removed as part of the merge commit?