summaryrefslogtreecommitdiff
path: root/io_uring/loop.h
diff options
context:
space:
mode:
authorLyude Paul <lyude@redhat.com>2026-06-12 15:43:35 -0400
committerDanilo Krummrich <dakr@kernel.org>2026-06-25 23:13:20 +0200
commitfa8cc4e3067f958ea2057f37a8a6f9c6b10a9c03 (patch)
treeb251ed475b69294bfda3ed2c8caf273529a5f8d2 /io_uring/loop.h
parent616c229ab010a31c5d1f793b925c7fb2eaad664c (diff)
downloadlinux-next-fa8cc4e3067f958ea2057f37a8a6f9c6b10a9c03.tar.gz
linux-next-fa8cc4e3067f958ea2057f37a8a6f9c6b10a9c03.zip
rust: faux: Allow retrieving a bound Device
When writing up some rust code that used faux devices for unit testing, I noticed that we never actually added the Bound device context to faux::Registration's AsRef<device::Device> implementation. This being said: the Registration object itself is proof that a driver is bound to the device - so this should be safe. Signed-off-by: Lyude Paul <lyude@redhat.com> Reviewed-by: Alexandre Courbot <acourbot@nvidia.com> Reviewed-by: Alice Ryhl <aliceryhl@google.com> Acked-by: Danilo Krummrich <dakr@kernel.org> Link: https://patch.msgid.link/20260612194436.585385-4-lyude@redhat.com Signed-off-by: Danilo Krummrich <dakr@kernel.org>
Diffstat (limited to 'io_uring/loop.h')
0 files changed, 0 insertions, 0 deletions