From: "Lecomte, Arnaud" <contact@arnaud-lcm.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: joe@perches.com, apw@canonical.com, dwaipayanray1@gmail.com,
lukas.bulwahn@gmail.com, ojeda@kernel.org, alex.gaynor@gmail.com,
boqun.feng@gmail.com, gary@garyguo.net, bjorn3_gh@protonmail.com,
lossin@kernel.org, a.hindborg@kernel.org, aliceryhl@google.com,
tmgross@umich.edu, dakr@kernel.org, linux-kernel@vger.kernel.org,
rust-for-linux@vger.kernel.org
Subject: Re: [PATCH 1/3] checkpatch.pl: Add warning for // comments on private Rust items
Date: Tue, 29 Jul 2025 21:29:05 +0100 [thread overview]
Message-ID: <bdfd8364-747c-4c8e-8505-f6474fe9c88e@arnaud-lcm.com> (raw)
In-Reply-To: <CANiq72=8AYUX5Xv-QE5mrPhDLtY2Zg2C2_ah48tJHCbObAg95Q@mail.gmail.com>
Oops, good catch Miguel, thanks !
On 29/07/2025 21:23, Miguel Ojeda wrote:
> On Tue, Jul 29, 2025 at 9:56 PM Arnaud Lecomte <contact@arnaud-lcm.com> wrote:
>> Background
> I think you meant to send a cover letter here (i.e. patch zero, rather
> than 1) -- you can generate one e.g. with `git format-patch
> --cover-letter`.
>
> (No need to resend just for this -- I would wait for some reviews or
> comments from maintainers)
>
> Thanks!
>
> Cheers,
> Miguel
next prev parent reply other threads:[~2025-07-29 20:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 19:56 Arnaud Lecomte
2025-07-29 20:01 ` [PATCH 2/3] checkpatch.pl: warn about " Arnaud Lecomte
2025-07-29 20:04 ` [PATCH 3/3] checkpatch.pl: --fix support for `//` comments rust private items Arnaud Lecomte
2025-07-29 20:23 ` [PATCH 1/3] checkpatch.pl: Add warning for // comments on private Rust items Miguel Ojeda
2025-07-29 20:29 ` Lecomte, Arnaud [this message]
2025-08-13 15:32 ` Lecomte, Arnaud
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=bdfd8364-747c-4c8e-8505-f6474fe9c88e@arnaud-lcm.com \
--to=contact@arnaud-lcm.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=apw@canonical.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=dwaipayanray1@gmail.com \
--cc=gary@garyguo.net \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lossin@kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@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 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®