[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20231012.145824.2016833275288545767.fujita.tomonori@gmail.com>
Date: Thu, 12 Oct 2023 14:58:24 +0900 (JST)
From: FUJITA Tomonori <fujita.tomonori@...il.com>
To: boqun.feng@...il.com
Cc: fujita.tomonori@...il.com, netdev@...r.kernel.org,
rust-for-linux@...r.kernel.org, andrew@...n.ch,
miguel.ojeda.sandonis@...il.com, greg@...ah.com, tmgross@...ch.edu
Subject: Re: [PATCH net-next v3 1/3] rust: core abstractions for network
PHY drivers
On Wed, 11 Oct 2023 11:29:45 -0700
Boqun Feng <boqun.feng@...il.com> wrote:
> On Mon, Oct 09, 2023 at 10:39:10AM +0900, FUJITA Tomonori wrote:
> [...]
>> +impl Device {
>> + /// Creates a new [`Device`] instance from a raw pointer.
>> + ///
>> + /// # Safety
>> + ///
>> + /// For the duration of the lifetime 'a, the pointer must be valid for writing and nobody else
>> + /// may read or write to the `phy_device` object.
>> + pub unsafe fn from_raw<'a>(ptr: *mut bindings::phy_device) -> &'a mut Self {
>> + unsafe { &mut *ptr.cast() }
>> + }
>> +
>> + /// Gets the id of the PHY.
>> + pub fn phy_id(&mut self) -> u32 {
>
> This function doesn't modify the `self`, why does this need to be a
> `&mut self` function? Ditto for a few functions in this impl block.
>
> It seems you used `&mut self` for all the functions, which looks like
> more design work is required here.
Ah, I can drop all the mut here.
Powered by blists - more mailing lists