[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20251012140451.155219-1-shankari.ak0208@gmail.com>
Date: Sun, 12 Oct 2025 19:34:51 +0530
From: Shankari Anand <shankari.ak0208@...il.com>
To: Andreas Hindborg <a.hindborg@...nel.org>,
Jens Axboe <axboe@...nel.dk>,
Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
linux-block@...r.kernel.org,
rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: 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 Tue, Sep 30, 2025 at 06:00:41PM +0200, Miguel Ojeda wrote:
>
> Thanks, that would be appreciated -- if you can, please rebase it and
> send it on top of -rc1 when it gets published in less than 2 weeks,
> then we can apply it soon after.
>
> Cheers,
> Miguel
Hi Miguel,
I'll resend it on top of -rc1.
I also noticed that several files have received new commits using
types::ARef or types::AlwaysRefCounted.
I wanted to check if it would make sense to update the documentation
to reflect their new file location.
Without clear documentation, it might become increasingly difficult
to remove the re-export as soon as possible, especially as more such commits are added.
Let me know what you think.
Best regards,
Shankari
Powered by blists - more mailing lists