From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Cui Alan <AlanCui4080@outlook.com>
Cc: "workflows@vger.kernel.org" <workflows@vger.kernel.org>
Subject: Re: How can I post my patch to others
Date: Mon, 21 Mar 2022 17:59:13 -0400 [thread overview]
Message-ID: <20220321215913.uvwn3w3ivgdd4m6n@meerkat.local> (raw)
In-Reply-To: <OSZP286MB2078DB6CFC4744170871B3A9AD169@OSZP286MB2078.JPNP286.PROD.OUTLOOK.COM>
On Mon, Mar 21, 2022 at 01:54:37AM +0000, Cui Alan wrote:
> I'm going to post a patch, but I still don't know whatever can I simply post the PATCH to
> others in the "linux-kernel" mailing list. It's said that I can do that to make PATCH examined by
> others. I don't want to pollute the main list.
I suggest you follow the tutorial on this page:
https://kernelnewbies.org/FirstKernelPatch
Best regards,
-K
next prev parent reply other threads:[~2022-03-21 22:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 1:54 How can I post my patch to others Cui Alan
2022-03-21 21:59 ` Konstantin Ryabitsev [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-21 4:15 Cui Alan
2022-04-03 8:39 Cui Alan
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=20220321215913.uvwn3w3ivgdd4m6n@meerkat.local \
--to=konstantin@linuxfoundation.org \
--cc=AlanCui4080@outlook.com \
--cc=workflows@vger.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).