linux-kernel - Re: [PATCH 1/7] rust: block: update ARef and AlwaysRefCounted imports from sync::aref

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] [day] [month] [year] [list]

Message-Id: <20251013084402.300397-1-shankari.ak0208@gmail.com>
Date: Mon, 13 Oct 2025 14:14:02 +0530
From: Shankari Anand <shankari.ak0208@...il.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: Andreas Hindborg <a.hindborg@...nel.org>,
	Jens Axboe <axboe@...nel.dk>,
	Alex Gaynor <alex.gaynor@...il.com>,
	linux-block@...r.kernel.org,
	rust-for-linux@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Boqun Feng <boqun.feng@...il.com>,
	Gary Guo <gary@...yguo.net>,
	Björn Roy Baron <bjorn3_gh@...tonmail.com>,
	Benno Lossin <lossin@...nel.org>,
	Alice Ryhl <aliceryhl@...gle.com>,
	Trevor Gross <tmgross@...ch.edu>,
	Danilo Krummrich <dakr@...nel.org>,
	Shankari Anand <shankari.ak0208@...il.com>
Subject: Re: [PATCH 1/7] rust: block: update ARef and AlwaysRefCounted imports from sync::aref

On Sun, Oct 12, 2025 at 08:01:19PM +0200, Miguel Ojeda wrote:
> On Sun, Oct 12, 2025 at 4:05 PM Shankari Anand
> <shankari.ak0208@...il.com> wrote:
> >
> > I'll resend it on top of -rc1.
> 
> Yeah, please, thanks! (in v2 I think you say it is on top of
> linux-next -- did you mean -rc1?).
>
I've rebased it on linux-next, and I've included the exact base commit at the end for reference.

Let me know if you'd prefer it to be rebased onto the latest mainline instead.

> 
> I think it is simpler if I apply (even if temporarily) a commit that
> moves everything and removes the re-export in linux-next -- that way
> people will notice when they try to introduce the code during the
> cycle.
> 

That sounds good. Just to confirm - since this spans multiple drivers/subsystems,
is it still okay to send it as a single patch?

Thanks and regards,
Shankari