From: "Danilo Krummrich" <dakr@kernel.org>
To: "Daniel Almeida" <daniel.almeida@collabora.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org
Subject: [PATCH] rust: io: mem: enable IoRequest doc-tests
Date: Sat, 19 Jul 2025 16:08:16 +0200 [thread overview]
Message-ID: <DBG39YMN2TX6.1VR4PEQSI8PSG@kernel.org> (raw)
In-Reply-To: <DBG2XI0UZ3B5.I9KLFJUYQUMC@kernel.org>
When introduced, the IoRequest doc-tests did depend on infrastructure
added in subsequent patches, hence they temporarily had to be disabled.
Now that we have the corresponding platform device infrastructure,
enable them.
Signed-off-by: Danilo Krummrich <dakr@kernel.org>
---
rust/kernel/io/mem.rs | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/rust/kernel/io/mem.rs b/rust/kernel/io/mem.rs
index 58c384291f15..ecef19f7d176 100644
--- a/rust/kernel/io/mem.rs
+++ b/rust/kernel/io/mem.rs
@@ -43,7 +43,7 @@ pub unsafe fn new(device: &'a Device<Bound>, resource: &'a Resource) -> Self {
/// The following example uses a [`platform::Device`] for illustration
/// purposes.
///
- /// ```ignore
+ /// ```no_run
/// use kernel::{bindings, c_str, platform, of, device::Core};
/// struct SampleDriver;
///
@@ -101,7 +101,7 @@ pub fn iomap_exclusive_sized<const SIZE: usize>(
/// The following example uses a [`platform::Device`] for illustration
/// purposes.
///
- /// ```ignore
+ /// ```no_run
/// use kernel::{bindings, c_str, platform, of, device::Core};
/// struct SampleDriver;
///
--
2.50.0
next prev parent reply other threads:[~2025-07-19 14:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 15:55 [PATCH v15 0/3] rust: platform: add Io support Daniel Almeida
2025-07-17 15:55 ` [PATCH v15 1/3] rust: io: add resource abstraction Daniel Almeida
2025-07-17 15:55 ` [PATCH v15 2/3] rust: io: mem: add a generic iomem abstraction Daniel Almeida
2025-07-17 19:45 ` Danilo Krummrich
2025-07-18 12:23 ` Daniel Almeida
2025-07-19 13:51 ` Danilo Krummrich
2025-07-19 14:08 ` Danilo Krummrich [this message]
2025-07-20 17:47 ` [PATCH] rust: io: mem: enable IoRequest doc-tests Danilo Krummrich
2025-07-17 15:55 ` [PATCH v15 3/3] rust: platform: add resource accessors Daniel Almeida
2025-07-19 13:15 ` Danilo Krummrich
2025-07-19 16:19 ` Miguel Ojeda
2025-07-19 16:29 ` Miguel Ojeda
2025-07-19 8:01 ` [PATCH v15 0/3] rust: platform: add Io support Greg Kroah-Hartman
2025-07-19 10:16 ` Danilo Krummrich
2025-07-20 0:34 ` Daniel Almeida
2025-07-20 17:46 ` Danilo Krummrich
2025-07-23 7:35 ` Dirk Behme
2025-07-23 13:33 ` Daniel Almeida
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DBG39YMN2TX6.1VR4PEQSI8PSG@kernel.org \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=daniel.almeida@collabora.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=rafael@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.