From: Tamir Duberstein <tamird@gmail.com>
To: "FUJITA Tomonori" <fujita.tomonori@gmail.com>,
"Trevor Gross" <tmgross@umich.edu>,
"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>,
"Danilo Krummrich" <dakr@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
"Andrew Lunn" <andrew@lunn.ch>
Cc: netdev@vger.kernel.org, rust-for-linux@vger.kernel.org,
linux-kernel@vger.kernel.org,
Tamir Duberstein <tamird@gmail.com>
Subject: [PATCH net-next v2 0/2] Clean up usage of ffi types
Date: Wed, 25 Jun 2025 05:25:37 -0700 [thread overview]
Message-ID: <20250625-correct-type-cast-v2-0-6f2c29729e69@gmail.com> (raw)
Remove qualification of ffi types which are included in the prelude and
change `as` casts to target the proper ffi type alias rather than the
underlying primitive.
Signed-off-by: Tamir Duberstein <tamird@gmail.com>
---
Changes in v2:
- Use unqualified types.
- Remove Fixes tag.
- Link to v1: https://lore.kernel.org/r/20250611-correct-type-cast-v1-1-06c1cf970727@gmail.com
---
Tamir Duberstein (2):
Use unqualified references to ffi types
Cast to the proper type
rust/kernel/net/phy.rs | 34 +++++++++++++---------------------
1 file changed, 13 insertions(+), 21 deletions(-)
---
base-commit: 0303584766b7bdb6564c7e8f13e0b59b6ef44984
change-id: 20250611-correct-type-cast-1de8876ddfc1
Best regards,
--
Tamir Duberstein <tamird@gmail.com>
next reply other threads:[~2025-06-25 12:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 12:25 Tamir Duberstein [this message]
2025-06-25 12:25 ` [PATCH net-next v2 1/2] Use unqualified references to ffi types Tamir Duberstein
2025-06-28 2:34 ` FUJITA Tomonori
2025-06-25 12:25 ` [PATCH net-next v2 2/2] Cast to the proper type Tamir Duberstein
2025-06-30 13:18 ` [PATCH net-next v2 0/2] Clean up usage of ffi types Tamir Duberstein
2025-07-01 8:00 ` patchwork-bot+netdevbpf
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=20250625-correct-type-cast-v2-0-6f2c29729e69@gmail.com \
--to=tamird@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=andrew@lunn.ch \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=davem@davemloft.net \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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).