From: Shankari Anand <shankari.ak0208@gmail.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: "Andreas Hindborg" <a.hindborg@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
"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>
Subject: Re: [PATCH] rust: sync: Update ARef and AlwaysRefCounted imports from sync::aref
Date: Thu, 28 Aug 2025 18:41:35 +0530 [thread overview]
Message-ID: <20250828131135.125303-1-shankari.ak0208@gmail.com> (raw)
On Tue, Aug 26, 2025 at 11:07:31AM +0200, Miguel Ojeda wrote:
> On Mon, Aug 18, 2025 at 9:11 PM Shankari Anand
> <shankari.ak0208@gmail.com> wrote:
> >
> > Fixes: 07dad44aa9a93 ("rust: kernel: move ARef and AlwaysRefCounted to sync::aref")
>
> > Apologies, I had missed out on changing the in-file reference call for the modules. This should fix that.
>
> I am not sure if this should count as a fix -- it could have easily
> been an intentional, second patch on top of the move, so that the move
> is minimal to avoid modifying the lines at the same time, which is
> something we typically do/want. :)
>
> Thanks!
Hey, yep I agree. So should I drop the Fixes tag?
> Cheers,
> Miguel
Regards,
Shankari
next reply other threads:[~2025-08-28 13:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 13:11 Shankari Anand [this message]
2025-08-28 13:41 ` [PATCH] rust: sync: Update ARef and AlwaysRefCounted imports from sync::aref Miguel Ojeda
-- strict thread matches above, loose matches on Subject: below --
2025-08-18 19:10 Shankari Anand
2025-08-18 22:16 ` Benno Lossin
2025-08-26 9:07 ` Miguel Ojeda
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=20250828131135.125303-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=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--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).