Rust for Linux List
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
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>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Jens Axboe" <axboe@kernel.dk>,
	"Matt Gilbride" <mattgilbride@google.com>,
	"Shuah Khan" <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2 1/2] rust: kernel: clean up empty `///` lines
Date: Thu, 12 Sep 2024 07:13:22 +0200	[thread overview]
Message-ID: <2024091253-bling-syndrome-da28@gregkh> (raw)
In-Reply-To: <aa1b4059dfac001945745db02b6f6d9db2e5d1cb.1726072795.git.hridesh699@gmail.com>

On Wed, Sep 11, 2024 at 11:14:34PM +0530, Hridesh MG wrote:
> From: hridesh <hridesh699@gmail.com>
> 
> 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>

This name needs to match your "From:" line, sorry.  Can you fix that up
and send a v3 series?

thanks,

greg k-h

  parent reply	other threads:[~2024-09-12  5:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-11 17:44 [PATCH v2 1/2] rust: kernel: clean up empty `///` lines Hridesh MG
2024-09-11 17:44 ` [PATCH v2 2/2] checkpatch: warn on empty rust doc comments Hridesh MG
2024-09-14 15:24   ` [PATCH v3 " Hridesh MG
2024-09-14 15:31   ` Hridesh MG
2024-09-14 16:42     ` Gary Guo
2024-09-14 16:57       ` Hridesh MG
2024-09-12  5:13 ` Greg KH [this message]
2024-09-12 11:46   ` [PATCH v2 1/2] rust: kernel: clean up empty `///` lines Hridesh MG
2024-09-12 11:50 ` Alice Ryhl
2024-09-14 15:24 ` [PATCH v3 " Hridesh MG

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=2024091253-bling-syndrome-da28@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=a.hindborg@samsung.com \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.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=skhan@linuxfoundation.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