linux-kernel - Re: linux-next: build failure after merge of the rust 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: <CANiq72kgAyotY71kmcABDwXVkZKnKdR4Dd1AwbYmdjeDr+-73A@mail.gmail.com>
Date: Tue, 24 Jun 2025 14:25:46 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Danilo Krummrich <dakr@...nel.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>, Alexandre Courbot <acourbot@...dia.com>, 
	Lyude Paul <lyude@...hat.com>, Andreas Hindborg <a.hindborg@...nel.org>, 
	FUJITA Tomonori <fujita.tomonori@...il.com>, Miguel Ojeda <ojeda@...nel.org>, 
	Tamir Duberstein <tamird@...il.com>, 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 rust tree

On Tue, Jun 24, 2025 at 2:00 PM Danilo Krummrich <dakr@...nel.org> wrote:
>
> It's a bit annoying to implement From explicitly for all of them, but it seems
> to be the correct thing to do.

Yeah, agreed.

> I can implement the From traits and fix up the warnings caused by enabling
> `cast_lossless` in my tree with subsequent patches, such that we do not have to
> carry all this as merge resolution.

That would be great, thanks.

Cheers,
Miguel