Re: [PATCH v2 0/3] Rust abstractions for network PHY drivers
From: Andrew Lunn <andrew@lunn.ch>
Date: 2023-10-06 14:47:31
Also in:
rust-for-linux
From: Andrew Lunn <andrew@lunn.ch>
Date: 2023-10-06 14:47:31
Also in:
rust-for-linux
A tree only that contains patches 2 and 3 allow the driver to be enabled, I think. The driver depends on CONFIG_RUST, which might doesn't have PHY bindings support (the first patch).
This is part of why i said there should be a Kconfig symbol CONFIG_RUST_PHYLIB_BINDING or similar. With only patches 2 and 3, that would not exists, and so you cannot enable the driver. Once all the patches meet up in linux-next, you have both parts, and you can enable it.
So I think that merging the patchset through a single tree is easier; netdev or rust. Miguel, how do you prefer to merge the patchset?
What are the merge conflicts looking like? What has happened in the
past? Or is this the first driver to actually get this far towards
being merged?
Andrew