From: Shankari Anand <shankari.ak0208@gmail.com>
To: Andreas Hindborg <a.hindborg@kernel.org>,
Jens Axboe <axboe@kernel.dk>, Miguel Ojeda <ojeda@kernel.org>,
Alex Gaynor <alex.gaynor@gmail.com>,
linux-block@vger.kernel.org, rust-for-linux@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: "Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Shankari Anand" <shankari.ak0208@gmail.com>
Subject: Re: [PATCH 1/7] rust: block: update ARef and AlwaysRefCounted imports from sync::aref
Date: Sun, 12 Oct 2025 19:34:51 +0530 [thread overview]
Message-ID: <20251012140451.155219-1-shankari.ak0208@gmail.com> (raw)
In-Reply-To: <CANiq72=ox809CAhMijbvxvy_-tx4QgJ=pGbbWfCcZR8J8XFrkg@mail.gmail.com>
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
next parent reply other threads:[~2025-10-12 14:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANiq72=ox809CAhMijbvxvy_-tx4QgJ=pGbbWfCcZR8J8XFrkg@mail.gmail.com>
2025-10-12 14:04 ` Shankari Anand [this message]
2025-10-12 18:01 ` [PATCH 1/7] rust: block: update ARef and AlwaysRefCounted imports from sync::aref Miguel Ojeda
2025-10-13 8:44 ` Shankari Anand
[not found] <KnSfzGK6OiA0mL5BZ32IZgEYWCuETu6ggzSHiqnzsYBLsUHWR5GcVRzt-FSa8sCXmYXz_jOKWGZ6B_QyeTZS2w==@protonmail.internalid>
2025-07-16 9:07 ` Shankari Anand
2025-07-16 12:38 ` Miguel Ojeda
2025-08-08 9:53 ` Andreas Hindborg
2025-08-10 11:42 ` Miguel Ojeda
2025-08-11 7:49 ` Andreas Hindborg
2025-08-11 10:44 ` Miguel Ojeda
2025-08-25 5:41 ` Shankari Anand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251012140451.155219-1-shankari.ak0208@gmail.com \
--to=shankari.ak0208@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=axboe@kernel.dk \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).