From: Alice Ryhl <aliceryhl@google.com>
To: Hridesh MG <hridesh699@gmail.com>
Cc: rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
"Andreas Hindborg" <a.hindborg@samsung.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Trevor Gross" <tmgross@umich.edu>,
"Jens Axboe" <axboe@kernel.dk>,
"Matt Gilbride" <mattgilbride@google.com>
Subject: Re: [PATCH v3 1/2 RESEND] rust: kernel: clean up empty `///` lines
Date: Mon, 30 Sep 2024 09:44:30 +0200 [thread overview]
Message-ID: <CAH5fLgiCAW68tGaG0imi7ia4XvOp+EQcENjF-P-ec_MonEuFrQ@mail.gmail.com> (raw)
In-Reply-To: <dbb63b5698aa507bbe3dec54b4458a3f151899d3.1727606659.git.hridesh699@gmail.com>
On Sun, Sep 29, 2024 at 1:15 PM Hridesh MG <hridesh699@gmail.com> wrote:
>
> Remove unnecessary empty `///` lines in the rust docs.
>
> Suggested-by: Miguel Ojeda <ojeda@kernel.org>
> Link: https://github.com/Rust-for-Linux/linux/issues/1109
> Signed-off-by: Hridesh MG <hridesh699@gmail.com>
Reviewed-by: Alice Ryhl <aliceryhl@google.com>
next prev parent reply other threads:[~2024-09-30 7:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-29 11:15 [PATCH v3 1/2 RESEND] rust: kernel: clean up empty `///` lines Hridesh MG
2024-09-29 11:15 ` [PATCH v3 2/2 RESEND] checkpatch: warn on empty rust doc comments Hridesh MG
2024-09-29 22:15 ` Trevor Gross
2024-09-30 2:41 ` Patrick Miller
2024-09-30 10:34 ` Hridesh MG
2024-09-30 10:44 ` Miguel Ojeda
2024-09-30 12:30 ` Hridesh MG
2024-10-02 2:17 ` Patrick Miller
2024-09-29 22:01 ` [PATCH v3 1/2 RESEND] rust: kernel: clean up empty `///` lines Trevor Gross
2024-09-30 7:44 ` Alice Ryhl [this message]
2024-09-30 8:49 ` Miguel Ojeda
2024-09-30 10:35 ` Hridesh MG
2024-09-30 11: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=CAH5fLgiCAW68tGaG0imi7ia4XvOp+EQcENjF-P-ec_MonEuFrQ@mail.gmail.com \
--to=aliceryhl@google.com \
--cc=a.hindborg@samsung.com \
--cc=alex.gaynor@gmail.com \
--cc=axboe@kernel.dk \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=hridesh699@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mattgilbride@google.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--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).