rust-for-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: FUJITA Tomonori <fujita.tomonori@gmail.com>
Cc: netdev@vger.kernel.org, rust-for-linux@vger.kernel.org,
	tmgross@umich.edu, miguel.ojeda.sandonis@gmail.com,
	benno.lossin@proton.me
Subject: Re: [PATCH net-next v2 2/6] rust: net::phy support probe callback
Date: Wed, 31 Jul 2024 14:24:08 +0200	[thread overview]
Message-ID: <5525a61c-01b7-4032-97ee-4997b19979ad@lunn.ch> (raw)
In-Reply-To: <20240731042136.201327-3-fujita.tomonori@gmail.com>

On Wed, Jul 31, 2024 at 01:21:32PM +0900, FUJITA Tomonori wrote:
> Support phy_driver probe callback, used to set up device-specific
> structures.
> 
> Signed-off-by: FUJITA Tomonori <fujita.tomonori@gmail.com>
> ---
>  rust/kernel/net/phy.rs | 24 ++++++++++++++++++++++++
>  1 file changed, 24 insertions(+)
> 
> diff --git a/rust/kernel/net/phy.rs b/rust/kernel/net/phy.rs
> index fd40b703d224..99a142348a34 100644
> --- a/rust/kernel/net/phy.rs
> +++ b/rust/kernel/net/phy.rs
> @@ -338,6 +338,20 @@ impl<T: Driver> Adapter<T> {
>          })
>      }
>  
> +    /// # Safety
> +    ///
> +    /// `phydev` must be passed by the corresponding callback in `phy_driver`.
> +    unsafe extern "C" fn probe_callback(phydev: *mut bindings::phy_device) -> core::ffi::c_int {
> +        from_result(|| {
> +            // SAFETY: This callback is called only in contexts
> +            // where we can exclusively access to `phy_device`, so the accessors on
> +            // `Device` are okay to call.

This one is slightly different to other callbacks. probe is called
without the mutex. Instead, probe is called before the device is
published. So the comment is correct, but given how important Rust
people take these SAFETY comments, maybe it should indicate it is
different to others?

	Andrew

  parent reply	other threads:[~2024-07-31 12:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-31  4:21 [PATCH net-next v2 0/6] net: phy: add Applied Micro QT2025 PHY driver FUJITA Tomonori
2024-07-31  4:21 ` [PATCH net-next v2 1/6] rust: sizes: add commonly used constants FUJITA Tomonori
2024-07-31  8:33   ` Alice Ryhl
2024-07-31 12:16   ` Andrew Lunn
2024-07-31 12:30     ` Alice Ryhl
2024-08-01  1:21       ` FUJITA Tomonori
2024-07-31  4:21 ` [PATCH net-next v2 2/6] rust: net::phy support probe callback FUJITA Tomonori
2024-07-31  8:33   ` Alice Ryhl
2024-07-31 12:24   ` Andrew Lunn [this message]
2024-07-31 12:32     ` Alice Ryhl
2024-07-31 20:57       ` Andrew Lunn
2024-08-01  9:07         ` Alice Ryhl
2024-08-01  0:17       ` FUJITA Tomonori
2024-08-01  9:07         ` Alice Ryhl
2024-07-31  4:21 ` [PATCH net-next v2 3/6] rust: net::phy implement AsRef<kernel::device::Device> trait FUJITA Tomonori
2024-07-31  8:38   ` Alice Ryhl
2024-08-01  1:03     ` FUJITA Tomonori
2024-07-31  4:21 ` [PATCH net-next v2 4/6] rust: net::phy unified read/write API for C22 and C45 registers FUJITA Tomonori
2024-07-31  4:21 ` [PATCH net-next v2 5/6] rust: net::phy unified genphy_read_status function " FUJITA Tomonori
2024-07-31  4:21 ` [PATCH net-next v2 6/6] net: phy: add Applied Micro QT2025 PHY driver FUJITA Tomonori
2024-08-01  1:55   ` 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=5525a61c-01b7-4032-97ee-4997b19979ad@lunn.ch \
    --to=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).