[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72mkHM3qfq66oDZyZMCuLK8Y1tJxEqFhSYpFWg7ihfcvEA@mail.gmail.com>
Date: Fri, 29 Mar 2024 14:03:40 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Valentin Obst <kernel@...entinobst.de>
Cc: wedsonaf@...il.com, a.hindborg@...sung.com, alex.gaynor@...il.com,
aliceryhl@...gle.com, benno.lossin@...ton.me, bjorn3_gh@...tonmail.com,
boqun.feng@...il.com, gary@...yguo.net, linux-kernel@...r.kernel.org,
ojeda@...nel.org, rust-for-linux@...r.kernel.org, walmeida@...rosoft.com
Subject: Re: [PATCH v2 0/5] In-place module initialisation
On Fri, Mar 29, 2024 at 1:11 PM Valentin Obst <kernel@...entinobst.de> wrote:
>
> I think the idea in [1] was to have this patch being included in the
> stable trees. I got little experience with stable trees but wouldn't the
> easiest way be that you add:
>
> Cc: stable@...r.kernel.org # 6.8.x: 715dd8950d4e rust: phy: implement `Send` for `Registration`
> Cc: stable@...r.kernel.org
> Fixes: 247b365dc8dc ("rust: add `kernel` crate")
>
> in the sign-off section for this patch? (Or mark the first one for stable
> inclusion as well, [2] has more information on that).
715dd8950d4e is your local hash for 1/5, right? So I would drop the
hash, because it may be confusing.
It may be possible to remove the first line (since 1/5 will only apply
to 6.8.x and it is already the previous patch in the series, while the
`Fixes` tag here may make it clear that 2/5 should still go everywhere
regardless of 1/5), but I guess it does not hurt to be extra clear.
What about:
Cc: stable@...r.kernel.org # 6.8.x: rust: phy: implement `Send`
for `Registration`
Cc: stable@...r.kernel.org # 6.1+
Fixes: 247b365dc8dc ("rust: add `kernel` crate")
Cheers,
Miguel
Powered by blists - more mailing lists