Re: [PATCH 22/22] MAINTAINERS: add entry for the `pin-init` crate

From: Benno Lossin
Date: Tue Mar 04 2025 - 19:43:35 EST


On Wed Mar 5, 2025 at 1:17 AM CET, Jarkko Sakkinen wrote:
> On Tue, Mar 04, 2025 at 10:56:27PM +0000, Benno Lossin wrote:
>> Add maintainers entry for the `pin-init` crate.
>>
>> This crate is already being maintained by me, but until now there
>> existed two different versions: the version inside of the kernel tree
>> and a user-space version at [1]. The previous patches synchronized these
>> two versions to reduce the maintenance burden. In order to keep them
>> synchronized from now on, separate the maintenance from other Rust code.
>>
>> Link: https://github.com/Rust-for-Linux/pin-init [1]
>> Signed-off-by: Benno Lossin <benno.lossin@xxxxxxxxx>
>> ---
>> MAINTAINERS | 13 +++++++++++++
>> 1 file changed, 13 insertions(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 8e0736dc2ee0..ced7fac4dbbe 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -20735,6 +20735,19 @@ S: Maintained
>> F: rust/kernel/alloc.rs
>> F: rust/kernel/alloc/
>>
>> +RUST [PIN-INIT]
>
> In some subsystems the order is exactly the opposite. E.g.,
>
> ASIX PHY DRIVER [RUST]

I think that `RUST [PIN-INIT]` makes sense in this case, since it is a
core Rust library. In the example you gave above, the `ASIX PHY DRIVER`
subsystem already exists, so it makes sense to have a rustified version.
With pin-init, there is no C counterpart. So IMO the only other
alternative would be just `PIN-INIT`.

---
Cheers,
Benno

>> +M: Benno Lossin <benno.lossin@xxxxxxxxx>
>> +L: rust-for-linux@xxxxxxxxxxxxxxx
>> +S: Maintained
>> +W: https://rust-for-linux.com/pin-init
>> +B: https://github.com/Rust-for-Linux/pin-init/issues
>> +C: zulip://rust-for-linux.zulipchat.com
>> +P: rust/pin-init/CONTRIBUTING.md
>> +T: git https://github.com/Rust-for-Linux/linux.git pin-init-next
>> +F: rust/kernel/init.rs
>> +F: rust/pin-init/
>> +K: \bpin-init\b|pin_init\b|PinInit
>> +
>> RXRPC SOCKETS (AF_RXRPC)
>> M: David Howells <dhowells@xxxxxxxxxx>
>> M: Marc Dionne <marc.dionne@xxxxxxxxxxxx>
>> --
>> 2.47.2
>>
>>
>>
>
> BR, Jarkko