From: Deborah Brouwer <deborahbrouwer3563@gmail.com>
To: outreachy-kernel <outreachy-kernel@googlegroups.com>
Subject: Cleanup patches to open mailing lists?
Date: Tue, 30 Mar 2021 17:15:21 -0700 (PDT) [thread overview]
Message-ID: <e00ba141-7636-4422-b83c-a21383d2c451n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 616 bytes --]
Hi everyone,
I am trying to get a patch ready to fix a few small checkpatch warnings
about "WARNING: Block comments use * on subsequent lines"
in drivers/staging/rtl8723bs/core/rtw_xmit.c
I noticed that the Outreachy first patch instructions [1] say not to send
the patch to the open mailing lists such as linux-staging@lists.linux.dev
(i.e. use the -nol option in the get_maintainer script) and I just wanted
to confirm that this is still correct? I should only send the patch to the
specific individuals named by the get_maintainer script?
Thanks,
Deb
[1] https://kernelnewbies.org/Outreachyfirstpatch
[-- Attachment #1.2: Type: text/html, Size: 725 bytes --]
next reply other threads:[~2021-03-31 0:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 0:15 Deborah Brouwer [this message]
2021-03-31 4:06 ` [Outreachy kernel] Cleanup patches to open mailing lists? Vaishali Thakkar
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=e00ba141-7636-4422-b83c-a21383d2c451n@googlegroups.com \
--to=deborahbrouwer3563@gmail.com \
--cc=outreachy-kernel@googlegroups.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.