linux-kernel - Re: [PATCH 7/7] rust: kernel: update ARef and AlwaysRefCounted imports from sync::aref

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <DBMUCVDVWM77.2M60X06IBGVA5@kernel.org>
Date: Sun, 27 Jul 2025 14:37:33 +0200
From: "Benno Lossin" <lossin@...nel.org>
To: "Miguel Ojeda" <miguel.ojeda.sandonis@...il.com>, "Shankari Anand"
 <shankari.ak0208@...il.com>
Cc: <linux-kernel@...r.kernel.org>, <rust-for-linux@...r.kernel.org>, "Greg
 Kroah-Hartman" <gregkh@...uxfoundation.org>, "Dave Ertman"
 <david.m.ertman@...el.com>, "Ira Weiny" <ira.weiny@...el.com>, "Leon
 Romanovsky" <leon@...nel.org>, "Miguel Ojeda" <ojeda@...nel.org>, "Alex
 Gaynor" <alex.gaynor@...il.com>, "Boqun Feng" <boqun.feng@...il.com>, "Gary
 Guo" <gary@...yguo.net>, Björn Roy Baron
 <bjorn3_gh@...tonmail.com>, "Andreas Hindborg" <a.hindborg@...nel.org>,
 "Alice Ryhl" <aliceryhl@...gle.com>, "Trevor Gross" <tmgross@...ch.edu>,
 "Danilo Krummrich" <dakr@...nel.org>, "Rafael J . Wysocki"
 <rafael@...nel.org>, "Abdiel Janulgue" <abdiel.janulgue@...il.com>, "Daniel
 Almeida" <daniel.almeida@...labora.com>, "Robin Murphy"
 <robin.murphy@....com>, "Viresh Kumar" <vireshk@...nel.org>, "Nishanth
 Menon" <nm@...com>, "Stephen Boyd" <sboyd@...nel.org>, "Bjorn Helgaas"
 <bhelgaas@...gle.com>, Krzysztof Wilczyński
 <kwilczynski@...nel.org>
Subject: Re: [PATCH 7/7] rust: kernel: update ARef and AlwaysRefCounted
 imports from sync::aref

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@...il.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