[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250612.094805.256395171864740471.fujita.tomonori@gmail.com>
Date: Thu, 12 Jun 2025 09:48:05 +0900 (JST)
From: FUJITA Tomonori <fujita.tomonori@...il.com>
To: tamird@...il.com
Cc: aliceryhl@...gle.com, fujita.tomonori@...il.com, tmgross@...ch.edu,
ojeda@...nel.org, alex.gaynor@...il.com, boqun.feng@...il.com,
gary@...yguo.net, bjorn3_gh@...tonmail.com, lossin@...nel.org,
a.hindborg@...nel.org, dakr@...nel.org, davem@...emloft.net,
andrew@...n.ch, netdev@...r.kernel.org, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] rust: cast to the proper type
On Wed, 11 Jun 2025 09:30:46 -0400
Tamir Duberstein <tamird@...il.com> wrote:
> On Wed, Jun 11, 2025 at 7:42 AM Alice Ryhl <aliceryhl@...gle.com> wrote:
>>
>> On Wed, Jun 11, 2025 at 12:28 PM Tamir Duberstein <tamird@...il.com> wrote:
>> >
>> > Use the ffi type rather than the resolved underlying type.
>> >
>> > Fixes: f20fd5449ada ("rust: core abstractions for network PHY drivers")
>>
>> Does this need to be backported? If not, I wouldn't include a Fixes tag.
>
> I'm fine with omitting it. I wanted to leave a breadcrumb to the
> commit that introduced the current code.
I also don't think this tag is necessary because this is not a bug
fix. And since this tag points to the file's initial commit, I don't
think it's particularly useful.
Powered by blists - more mailing lists