[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20231213.083109.2097548498951503416.fujita.tomonori@gmail.com>
Date: Wed, 13 Dec 2023 08:31:09 +0900 (JST)
From: FUJITA Tomonori <fujita.tomonori@...il.com>
To: boqun.feng@...il.com
Cc: benno.lossin@...ton.me, fujita.tomonori@...il.com, alice@...l.io,
netdev@...r.kernel.org, rust-for-linux@...r.kernel.org, andrew@...n.ch,
tmgross@...ch.edu, miguel.ojeda.sandonis@...il.com, wedsonaf@...il.com,
aliceryhl@...gle.com
Subject: Re: [PATCH net-next v10 1/4] rust: core abstractions for network
PHY drivers
On Tue, 12 Dec 2023 12:23:04 -0800
Boqun Feng <boqun.feng@...il.com> wrote:
> So the rationale here is the callsite of mdiobus_read() is just a
> open-code version of phy_read(), so if we meet the same requirement of
> phy_read(), we should be safe here. Maybe:
>
> "... open code of `phy_read()` with a valid phy_device pointer
> `phydev`"
>
> ?
I'll add the above comment with the similar for phy_write(), thanks!
Powered by blists - more mailing lists