Recent searches
Search options
While I don't know if is the first time this has happened, it's good to acknowledge this given all the crazy, odd, and incorrect press about Rust in Linux these days.
A new in-kernel api just landed in linux-next from my tree and should hopefully show up in 6.14 to make some kinds of drivers easier to write, that has a rust binding added at the exact same time:
https://lore.kernel.org/all/2025021023-sandstorm-precise-9f5d@gregkh/
Many thanks to Lyude and Danilo and many other Rust kernel developers for the help in creating the binding and make the C side work well for both Rust and C code at the same time. The end result here for any C developer alone, is much better off for all of their help.
A new in-kernel api just landed in linux-next from my tree and should hopefully show up in 6.14 to make some kinds of drivers easier to write, that has a rust binding added at the exact same time:
https://lore.kernel.org/all/2025021023-sandstorm-precise-9f5d@gregkh/
Many thanks to Lyude and Danilo and many other Rust kernel developers for the help in creating the binding and make the C side work well for both Rust and C code at the same time. The end result here for any C developer alone, is much better off for all of their help.
lore.kernel.org[PATCH v4 0/9] Driver core: Add faux bus devices - Greg Kroah-Hartman
@gregkh Faux bus! 
It has been a kind of (anti-)pattern to create a short-lived platform device for request_firmware(). Does this work for that use case as well?
@jani Yes it does! Look at this patch that handles that case explicitly: https://lore.kernel.org/all/2025021027-stove-dolly-9aed@gregkh/
lore.kernel.org[PATCH v4 5/9] wifi: cfg80211: move away from using a fake platform device - Greg Kroah-Hartman
@gregkh Oh, I failed to look through the whole series. Good stuff!