From: Greg KH <gregkh@linuxfoundation.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Benno Lossin <benno.lossin@proton.me>,
FUJITA Tomonori <fujita.tomonori@gmail.com>,
netdev@vger.kernel.org, rust-for-linux@vger.kernel.org,
tmgross@umich.edu, miguel.ojeda.sandonis@gmail.com,
aliceryhl@google.com
Subject: Re: [PATCH net-next v4 3/6] rust: net::phy implement AsRef<kernel::device::Device> trait
Date: Sun, 18 Aug 2024 17:45:51 +0200 [thread overview]
Message-ID: <2024081809-scoff-uncross-5061@gregkh> (raw)
In-Reply-To: <1afb6d69-f850-455f-97e2-361d490a2637@lunn.ch>
On Sun, Aug 18, 2024 at 05:38:01PM +0200, Andrew Lunn wrote:
> > Just to be sure: the `phydev.mdio.dev` struct is refcounted and
> > incrementing the refcount is fine, right?
>
> There is nothing special here. PHY devices are just normal Linux
> devices. The device core is responsible for calling .probe() and
> .remove() on a device, and these should be the first and last
> operation on a device. The device core provides refcounting of the
> struct device, so it should always be valid.
>
> So i have to wounder if you are solving this at the correct
> level. This should be generic to any device, so the Rust concept of a
> device should be stating these guarantees, not each specific type of
> device.
It should, why isn't it using the rust binding to Device that we already
have:
https://rust.docs.kernel.org/kernel/device/struct.Device.html
or is it? I'm confused now...
thanks,
greg k-h
next prev parent reply other threads:[~2024-08-18 15:45 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-17 5:19 [PATCH net-next v4 0/6] net: phy: add Applied Micro QT2025 PHY driver FUJITA Tomonori
2024-08-17 5:19 ` [PATCH net-next v4 1/6] rust: sizes: add commonly used constants FUJITA Tomonori
2024-08-17 5:53 ` Benno Lossin
2024-08-17 5:19 ` [PATCH net-next v4 2/6] rust: net::phy support probe callback FUJITA Tomonori
2024-08-17 5:59 ` Benno Lossin
2024-08-17 5:19 ` [PATCH net-next v4 3/6] rust: net::phy implement AsRef<kernel::device::Device> trait FUJITA Tomonori
2024-08-17 13:30 ` Benno Lossin
2024-08-18 2:13 ` FUJITA Tomonori
2024-08-18 6:01 ` Benno Lossin
2024-08-18 7:36 ` FUJITA Tomonori
2024-08-18 9:03 ` Benno Lossin
2024-08-18 9:15 ` FUJITA Tomonori
2024-08-18 10:42 ` Benno Lossin
2024-08-18 11:25 ` FUJITA Tomonori
2024-08-18 15:55 ` Benno Lossin
2024-08-18 15:38 ` Andrew Lunn
2024-08-18 15:45 ` Greg KH [this message]
2024-08-18 15:54 ` Benno Lossin
2024-08-18 16:16 ` Andrew Lunn
2024-08-18 16:19 ` Benno Lossin
2024-08-17 5:19 ` [PATCH net-next v4 4/6] rust: net::phy unified read/write API for C22 and C45 registers FUJITA Tomonori
2024-08-17 18:43 ` Andrew Lunn
2024-08-17 5:19 ` [PATCH net-next v4 5/6] rust: net::phy unified genphy_read_status function " FUJITA Tomonori
2024-08-17 18:44 ` Andrew Lunn
2024-08-17 5:19 ` [PATCH net-next v4 6/6] net: phy: add Applied Micro QT2025 PHY driver FUJITA Tomonori
2024-08-17 18:51 ` Andrew Lunn
2024-08-17 21:34 ` Benno Lossin
2024-08-18 15:44 ` Andrew Lunn
2024-08-18 16:16 ` Benno Lossin
2024-08-18 17:39 ` Andrew Lunn
2024-08-19 0:22 ` Miguel Ojeda
2024-08-18 16:10 ` Benno Lossin
2024-08-18 23:38 ` FUJITA Tomonori
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=2024081809-scoff-uncross-5061@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=aliceryhl@google.com \
--cc=andrew@lunn.ch \
--cc=benno.lossin@proton.me \
--cc=fujita.tomonori@gmail.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=netdev@vger.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).