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: <CANiq72nqM6Ncz7pP4jfyBENK936QXqd0KP-9BQdbHwVU8zX=Xg@mail.gmail.com>
Date: Mon, 16 Dec 2024 17:24:42 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Jocelyn Falempe <jfalempe@...hat.com>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>, Miguel Ojeda <ojeda@...nel.org>, Gary Guo <gary@...yguo.net>, 
	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, Dec 16, 2024 at 11:59 AM Jocelyn Falempe <jfalempe@...hat.com> wrote:
>
> Yes, I'm fine with that change, thanks for the fix!

Thanks for the quick reply!

May I transform your reply into an Acked-by?

By the way, if you want it as an independent fix that can go to stable
too, I am happy to split it into its own (previous) commit and tag it
as such. I am not sure if it should be considered a fix, though, since
one could argue nothing is "broken" (apart from the type not being the
optimal choice).

I am also happy to split it without marking it as a fix, in case you
may want to backport it independently as a prerequisite at some point
or similar.

Cheers,
Miguel