On Fri Jul 17, 2026 at 1:03 PM BST, Greg Kroah-Hartman wrote: > On Fri, Jul 17, 2026 at 01:22:40PM +0200, Danilo Krummrich wrote: >> On 7/17/26 1:14 PM, Markus Probst wrote: >> > On Fri, 2026-07-17 at 12:55 +0200, Greg Kroah-Hartman wrote: >> >> On Wed, Jul 15, 2026 at 09:00:14PM +0000, Markus Probst wrote: >> >>> This patch series adds the serdev device bus rust abstraction into the >> >>> kernel. >> >>> >> >>> This abstraction will be used by a driver, >> >>> which targets the MCU devices in Synology devices. >> >>> >> >>> Kari Argillander also messaged me, stating that he wants to write a >> >>> watchdog driver with this abstraction (needing initial device data). >> >>> >> >>> This series depends on [1]. >> >>> >> >>> [1] >> >>> https://lore.kernel.org/rust-for-linux/[email protected]/ >> >>> >> >>> Signed-off-by: Markus Probst <[email protected]> >> >> >> >> Given there are no objections, I'll go queue this up now, thanks. >> > Thanks for merging, but I haven't seen the dependency >> > >> > https://lore.kernel.org/rust-for-linux/[email protected]/ >> > >> > getting picked yet (its at least not in linux-next), so it might not >> > even compile. Not sure whats holding the patch back though. >> (Ah, saw this just after I replied to the other thread.) >> >> Nothing is holding them back other than requiring a user (which is your >> work), >> so I did not pick them up. >> >> Also note that tty and driver-core are different trees, so picking it up in >> driver-core would not have helped tty. > > Should I drop this from the tty tree and take it through driver-core > instead? If so, no problem for me, just let me know.
FWIW this series will also conflict quite significantly with https://lore.kernel.org/driver-core/[email protected]/ which is routed via driver-core tree. Best, GAry
