From: "Benno Lossin" <lossin@kernel.org>
To: "Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>,
"Shankari Anand" <shankari.ak0208@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>,
"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 14:37:33 +0200 [thread overview]
Message-ID: <DBMUCVDVWM77.2M60X06IBGVA5@kernel.org> (raw)
In-Reply-To: <CANiq72kw-OiU6YO8TKMVMdtJF+j7r9nBDsAa9Q2tdBzM=DyxDg@mail.gmail.com>
On Sun Jul 27, 2025 at 2:28 PM CEST, Miguel Ojeda wrote:
> On Sun, Jul 27, 2025 at 9:30 AM Shankari Anand
> <shankari.ak0208@gmail.com> wrote:
>> 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 -- sometimes people do it in a single series, even if they are
> technically independent, especially if they expect everything to go in
> at once (which may not be the case here).
>
> However, I was mainly talking about using the "7/7" notation but
> having the emails be separate, i.e. if one uses that notation, then
> people will likely be a bit confused when they don't see the other
> patches in the series. So if it is not a series, then it is best to
> avoid that notation; and if it is a series, then the notation should
> be used.
That's good advice. I want to add that in this case, I think a series is
better sending 7 independent patches. Using a series allows people to
see if it is complete (ie there might be places that are missed). It
also allows someone to send a single mail reviewing all patches & giving
general comments about all patches in the series.
---
Cheers,
Benno
next prev parent reply other threads:[~2025-07-27 12:37 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
2025-07-27 12:28 ` Miguel Ojeda
2025-07-27 12:37 ` Benno Lossin [this message]
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=DBMUCVDVWM77.2M60X06IBGVA5@kernel.org \
--to=lossin@kernel.org \
--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=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=shankari.ak0208@gmail.com \
--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).