[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20231014.135007.2233950345551386934.fujita.tomonori@gmail.com>
Date: Sat, 14 Oct 2023 13:50:07 +0900 (JST)
From: FUJITA Tomonori <fujita.tomonori@...il.com>
To: andrew@...n.ch
Cc: benno.lossin@...ton.me, fujita.tomonori@...il.com,
netdev@...r.kernel.org, rust-for-linux@...r.kernel.org,
miguel.ojeda.sandonis@...il.com, tmgross@...ch.edu, boqun.feng@...il.com,
wedsonaf@...il.com, greg@...ah.com
Subject: Re: [PATCH net-next v4 1/4] rust: core abstractions for network
PHY drivers
On Sat, 14 Oct 2023 04:12:57 +0200
Andrew Lunn <andrew@...n.ch> wrote:
>> > +config RUST_PHYLIB_ABSTRACTIONS
>> > + bool "PHYLIB abstractions support"
>> > + depends on RUST
>> > + depends on PHYLIB=y
>> > + help
>> > + Adds support needed for PHY drivers written in Rust. It provides
>> > + a wrapper around the C phylib core.
>> > +
>>
>> I find it a bit weird that this is its own option under "General". I think
>> it would be reasonable to put it under "Rust", since that would also scale
>> better when other subsystems do this.
>
> To some extent, this is just a temporary location. Once the
> restrictions of the build systems are solved, i expect this will move
> into drivers/net/phy/Kconfig, inside the 'if PHYLIB'. However, i
> agree, this should be under the Rust menu.
Sure, I'll do in the next patchset.
Powered by blists - more mailing lists