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: <20241112122945.06acc684@canb.auug.org.au>
Date: Tue, 12 Nov 2024 12:29:45 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
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

Hi Miguel,

On Tue, 12 Nov 2024 00:58:47 +0100 Miguel Ojeda <miguel.ojeda.sandonis@...il.com> wrote:
>
> 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, I will let you know.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped