From: "Danilo Krummrich" <dakr@kernel.org>
To: "Miguel Ojeda" <ojeda@kernel.org>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@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>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@lists.linux.dev
Subject: Re: [PATCH 1/2] rust: io: fix broken intra-doc link to missing `flags` module
Date: Tue, 22 Jul 2025 11:29:07 +0200 [thread overview]
Message-ID: <DBIH7VEMJY0E.4KMGP0KSLZHG@kernel.org> (raw)
In-Reply-To: <20250722085500.1360401-1-ojeda@kernel.org>
On Tue Jul 22, 2025 at 10:54 AM CEST, Miguel Ojeda wrote:
> There is no `mod flags` in this case, unlike others. Instead, they are
> associated constants for the `Flags` type.
>
> Thus reword the sentence to fix the broken intra-doc link, providing
> an example of constant and linking to it to clarify which ones we are
> referring to.
>
> Fixes: 493fc33ec252 ("rust: io: add resource abstraction")
> Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
Thanks for catching this and the other documentation warning.
Applied to driver-core-testing, thanks!
prev parent reply other threads:[~2025-07-22 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 8:54 [PATCH 1/2] rust: io: fix broken intra-doc link to missing `flags` module Miguel Ojeda
2025-07-22 8:55 ` [PATCH 2/2] rust: io: fix broken intra-doc links to `platform::Device` Miguel Ojeda
2025-07-22 9:20 ` [PATCH 1/2] rust: io: fix broken intra-doc link to missing `flags` module Miguel Ojeda
2025-07-22 9:29 ` Danilo Krummrich [this message]
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=DBIH7VEMJY0E.4KMGP0KSLZHG@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=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=patches@lists.linux.dev \
--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.