From: Gary Guo <gary@garyguo.net>
To: Hridesh MG <hridesh699@gmail.com>
Cc: linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org,
"Andy Whitcroft" <apw@canonical.com>,
"Joe Perches" <joe@perches.com>,
"Dwaipayan Ray" <dwaipayanray1@gmail.com>,
"Lukas Bulwahn" <lukas.bulwahn@gmail.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"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>,
"Trevor Gross" <tmgross@umich.edu>,
"Shuah Khan" <skhan@linuxfoundation.org>
Subject: Re: [PATCH v3 2/2] checkpatch: warn on empty rust doc comments
Date: Sat, 14 Sep 2024 17:42:49 +0100 [thread overview]
Message-ID: <20240914174249.107a1533.gary@garyguo.net> (raw)
In-Reply-To: <CALiyAo=Z7SCwCRD_2rBnQrkF71q4MRyMjqJZy8iWGAuFqOmWUw@mail.gmail.com>
On Sat, 14 Sep 2024 21:01:24 +0530
Hridesh MG <hridesh699@gmail.com> wrote:
> Ah, sorry. I did not intend to post this version as a reply to the
> previous thread, I wrongly assumed that editing the patch manually
> wouldn't have side effects. Should I post it again or is this fine?
I don't know what happened, somehow in my email client I saw the old
replies to your v2 patch becomes reply to your v3 patch.
Did you somehow reuse Message-ID between v3 and v2? Not sure how that's
supposed to happen...
Best,
Gary
next prev parent reply other threads:[~2024-09-14 16:42 UTC|newest]
Thread overview: 11+ 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 [this message]
2024-09-14 16:57 ` Hridesh MG
2024-09-12 5:13 ` [PATCH v2 1/2] rust: kernel: clean up empty `///` lines Greg KH
2024-09-12 11:46 ` Hridesh MG
2024-09-12 11:50 ` Alice Ryhl
2024-09-14 15:24 ` [PATCH v3 " Hridesh MG
2024-09-16 9:53 Hridesh MG
2024-09-16 9:53 ` [PATCH v3 2/2] checkpatch: warn on empty rust doc comments 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=20240914174249.107a1533.gary@garyguo.net \
--to=gary@garyguo.net \
--cc=a.hindborg@samsung.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=apw@canonical.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dwaipayanray1@gmail.com \
--cc=hridesh699@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.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
all inboxes | Powered by JetHome®