linux-kernel - Re: linux-next: manual merge of the vfs-brauner tree with the rust-fixes 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: <CANiq72=MGrrAPfFymAS+M_svLQ84JeczDkc8B5wqtRGzEVpg7Q@mail.gmail.com>
Date: Tue, 8 Oct 2024 16:01:24 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Christian Brauner <brauner@...nel.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>, Miguel Ojeda <ojeda@...nel.org>, 
	Alice Ryhl <aliceryhl@...gle.com>, 
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, 
	Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: manual merge of the vfs-brauner tree with the
 rust-fixes tree

On Tue, Oct 8, 2024 at 2:39 PM Christian Brauner <brauner@...nel.org> wrote:
>
> I rebased the rust bindings onto v6.12-rc2. So this conflict will go away.

We are moving `AlwaysRefCounted` in `rust-next`, and the new code in
your branch uses it, so `next-20241008` does not build.

I can add a temporary re-export that we can clean up later on our
side, or I can drop the move for another time (it is not a big deal),
or we can put your branch on top of / into `rust-next`.

Cheers,
Miguel