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: <CANiq72mYq-53xB9WFTH3H78WLrQuJze-nEybjwyLqnrSbv8UqA@mail.gmail.com>
Date: Tue, 12 Nov 2024 00:58:47 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: 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, Nov 11, 2024 at 9:28 AM Miguel Ojeda
<miguel.ojeda.sandonis@...il.com> wrote:
>
> remapping", i.e. taking the commit as-is without the next commit,
> since we should be able to do most of the renames already.

Stephen: I went with this, since unless I did something wrong, you
should see those build failures are gone, i.e. your build resolutions
were fine.

The hashes didn't change, I just dropped the top two commits.

You should be able to reuse the resolutions from yesterday.

If needed, we may simplify further, but let's see if this way works.

Thanks!

Cheers,
Miguel