From: Trevor Gross <tmgross@umich.edu>
To: Miguel Ojeda <ojeda@kernel.org>
Cc: "Wedson Almeida Filho" <wedsonaf@gmail.com>,
"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" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@samsung.com>,
"Alice Ryhl" <aliceryhl@google.com>,
rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@lists.linux.dev
Subject: Re: [PATCH] rust: macros: indent list item in `module!`'s docs
Date: Fri, 26 Jul 2024 07:05:47 -0400 [thread overview]
Message-ID: <CALNs47sFD_GqhXNa7v+eC=O96A+SpPm4QtZ3=GbSxZ4zkTm3Zg@mail.gmail.com> (raw)
In-Reply-To: <20240725184644.135185-1-ojeda@kernel.org>
On Thu, Jul 25, 2024 at 2:47 PM Miguel Ojeda <ojeda@kernel.org> wrote:
>
> Like commit e516211f615f ("rust: macros: indent list item in `paste!`'s
> docs"), but for `module!`.
>
> Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
> ---
> rust/macros/lib.rs | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/rust/macros/lib.rs b/rust/macros/lib.rs
> index 159e75292970..5be0cb9db3ee 100644
> --- a/rust/macros/lib.rs
> +++ b/rust/macros/lib.rs
> @@ -94,7 +94,7 @@
> /// - `license`: ASCII string literal of the license of the kernel module (required).
> /// - `alias`: array of ASCII string literals of the alias names of the kernel module.
> /// - `firmware`: array of ASCII string literals of the firmware files of
> -/// the kernel module.
> +/// the kernel module.
> #[proc_macro]
> pub fn module(ts: TokenStream) -> TokenStream {
> module::module(ts)
>
> base-commit: b1263411112305acf2af728728591465becb45b0
> --
> 2.45.2
Not much needing review here, but
Reviewed-by: Trevor Gross <tmgross@umich.edu>
:)
next prev parent reply other threads:[~2024-07-26 11:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 18:46 [PATCH] rust: macros: indent list item in `module!`'s docs Miguel Ojeda
2024-07-26 11:05 ` Trevor Gross [this message]
2024-07-29 12:47 ` Miguel Ojeda
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='CALNs47sFD_GqhXNa7v+eC=O96A+SpPm4QtZ3=GbSxZ4zkTm3Zg@mail.gmail.com' \
--to=tmgross@umich.edu \
--cc=a.hindborg@samsung.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=patches@lists.linux.dev \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).