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

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

Message-ID: <CANiq72kd1ZCb8X+s0wWT0ENjPUJ_P8iiUa2gZ==X2_r1V0t-JA@mail.gmail.com>
Date: Mon, 24 Mar 2025 16:40:55 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Danilo Krummrich <dakr@...nel.org>
Cc: Greg KH <greg@...ah.com>, Stephen Rothwell <sfr@...b.auug.org.au>, 
	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 rust tree

On Mon, Mar 24, 2025 at 4:27 PM Danilo Krummrich <dakr@...nel.org> wrote:
>
> Correct, it is the full conflict resolution of the current rust and driver-core
> tree.
>
> Thanks, the attached patch looks perfectly fine to me to add on top.

Thanks for the quick reply, then I will send it and add it.

> One small nit: The "Link:" tag should rather be "Closes:".

Sure, will change -- I didn't use that since I am still not sure it
counts as a fix or not (so Reported-by vs. "Found-by", Closes vs. Link
etc.), given it is "in the future" :)

Cheers,
Miguel