[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <CXG0PHF8SB5K.1LNX7D7LCN0W0@kernel.org>
Date: Tue, 05 Dec 2023 03:43:50 +0200
From: "Jarkko Sakkinen" <jarkko@...nel.org>
To: "FUJITA Tomonori" <fujita.tomonori@...il.com>, <netdev@...r.kernel.org>
Cc: <rust-for-linux@...r.kernel.org>, <andrew@...n.ch>, <tmgross@...ch.edu>,
<miguel.ojeda.sandonis@...il.com>, <benno.lossin@...ton.me>,
<wedsonaf@...il.com>, <aliceryhl@...gle.com>, <boqun.feng@...il.com>
Subject: Re: [PATCH net-next v9 1/4] rust: core abstractions for network PHY
drivers
On Tue Dec 5, 2023 at 3:14 AM EET, FUJITA Tomonori wrote:
> This patch adds abstractions to implement network PHY drivers; the
> driver registration and bindings for some of callback functions in
> struct phy_driver and many genphy_ functions.
>
> This feature is enabled with CONFIG_RUST_PHYLIB_ABSTRACTIONS=y.
Just a question: is `_ABSTRACTIONS` a convention or just for this
config flag?
That would read anyway that this rust absraction of phy absraction
layer or similar.
Why not e.g.
- `CONFIG_RUST_PHYLIB_BINDINGS`
- `CONFIG_RUST_PHYLIB_API`
- Or even just `CONFIG_RUST_PHYLIB`?
BR, Jarkko
Powered by blists - more mailing lists