From: Shankari Anand <shankari.ak0208@gmail.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Dave Ertman" <david.m.ertman@intel.com>,
"Ira Weiny" <ira.weiny@intel.com>,
"Leon Romanovsky" <leon@kernel.org>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
"Abdiel Janulgue" <abdiel.janulgue@gmail.com>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Robin Murphy" <robin.murphy@arm.com>,
"Viresh Kumar" <vireshk@kernel.org>, "Nishanth Menon" <nm@ti.com>,
"Stephen Boyd" <sboyd@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>
Subject: Re: [PATCH 7/7] rust: kernel: update ARef and AlwaysRefCounted imports from sync::aref
Date: Sun, 27 Jul 2025 13:00:00 +0530 [thread overview]
Message-ID: <CAPRMd3kXUJC6rC_X4i41dWNpS2tx4aEXFmBuEwncXmdJewinDA@mail.gmail.com> (raw)
In-Reply-To: <CANiq72=uDrg9HBVM97dgJGaC946Or964-2aF6OJVV0ih_vWuRA@mail.gmail.com>
> It has been only a week (and we are close to the merge window, thus
> maintainers are typically dealing with other things/patches):
> https://docs.kernel.org/process/submitting-patches.html#don-t-get-discouraged-or-impatient
Apologies for the early ping, I was unsure about the appropriate way
to split the patches and wanted to confirm before proceeding.
> Having said that, I am not sure why this one in particular has e.g.
> `opp.rs` and `devres.rs` -- those are different
> entries/trees/maintainers in `MAINTAINERS`. So it would likely help to
> perform a split that doesn't involve different subsystems.
Sure, I'll carefully split the patches accordingly in the next version
to align with the relevant maintainers and trees.
> By the way, if you meant to send the patches as completely independent
> ones, then I would suggest avoiding the series notation (e.g. "7/7")
> -- at least I see them in Lore as separate threads:
Regarding the series notation (e.g., "7/7"), I included it to indicate
the overall scope of changes as part of the same effort. However,
since the patches are independent and target different subsystems,
I’ll avoid that format going forward, as suggested.
Thanks for your guidance.
~ Shankari
On Fri, Jul 25, 2025 at 7:33 PM Miguel Ojeda
<miguel.ojeda.sandonis@gmail.com> wrote:
>
> On Fri, Jul 25, 2025 at 3:02 PM Shankari Anand
> <shankari.ak0208@gmail.com> wrote:
> >
> > Can this be picked up for review? Should I be splitting each core
> > kernel file into a separate patch?
>
> It has been only a week (and we are close to the merge window, thus
> maintainers are typically dealing with other things/patches):
>
> https://docs.kernel.org/process/submitting-patches.html#don-t-get-discouraged-or-impatient
>
> Having said that, I am not sure why this one in particular has e.g.
> `opp.rs` and `devres.rs` -- those are different
> entries/trees/maintainers in `MAINTAINERS`. So it would likely help to
> perform a split that doesn't involve different subsystems.
>
> By the way, if you meant to send the patches as completely independent
> ones, then I would suggest avoiding the series notation (e.g. "7/7")
> -- at least I see them in Lore as separate threads:
>
> https://lore.kernel.org/rust-for-linux/20250717073450.15090-1-shankari.ak0208@gmail.com/
>
> Thanks!
>
> Cheers,
> Miguel
next prev parent reply other threads:[~2025-07-27 7:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 7:34 [PATCH 7/7] rust: kernel: update ARef and AlwaysRefCounted imports from sync::aref Shankari Anand
2025-07-25 13:02 ` Shankari Anand
2025-07-25 14:03 ` Miguel Ojeda
2025-07-27 7:30 ` Shankari Anand [this message]
2025-07-27 12:28 ` Miguel Ojeda
2025-07-27 12:37 ` Benno Lossin
2025-07-27 14:26 ` Miguel Ojeda
2025-07-27 17:20 ` Benno Lossin
2025-07-27 18:05 ` Miguel Ojeda
2025-08-01 8:39 ` Danilo Krummrich
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=CAPRMd3kXUJC6rC_X4i41dWNpS2tx4aEXFmBuEwncXmdJewinDA@mail.gmail.com \
--to=shankari.ak0208@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=abdiel.janulgue@gmail.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bhelgaas@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=david.m.ertman@intel.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=ira.weiny@intel.com \
--cc=kwilczynski@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=nm@ti.com \
--cc=ojeda@kernel.org \
--cc=rafael@kernel.org \
--cc=robin.murphy@arm.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=tmgross@umich.edu \
--cc=vireshk@kernel.org \
/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).