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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CANiq72nS94wv50XyOJq5CeiVQvb0+3mNdWxJpFy_+2FH1x4RYQ@mail.gmail.com>
Date: Mon, 19 Jan 2026 19:59:26 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Mark Brown <broonie@...nel.org>
Cc: Tamir Duberstein <tamird@...il.com>, Andreas Hindborg <a.hindborg@...nel.org>, 
	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 7:54 PM Mark Brown <broonie@...nel.org> wrote:
>
> I could do that as a merge fixup instead of the revert, I'll have a look
> at some point but not for today.  Someone will need to work out how this
> works when things go to Linus...

That would be great, thanks Mark!

And, indeed, when the PRs are sent to Linus, ideally the submitters
should warn him about it (at least that is what I usually do for other
Rust conflicts -- I usually point him to the resolution in -next
and/or a custom merge pre-PR).

By the way, I will send you the details we briefly talked about in LPC
for the Rust bits.

Cheers,
Miguel