From: julia.lawall@lip6.fr (Julia Lawall)
To: linux-arm-kernel@lists.infradead.org
Subject: [Outreachy kernel] Re: [PATCH v2] staging: mt7621-dma: Add braces around else branches
Date: Wed, 24 Oct 2018 14:06:18 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.2.21.1810241404050.2371@hadrien> (raw)
In-Reply-To: <20181024110745.GV30658@n2100.armlinux.org.uk>
On Wed, 24 Oct 2018, Russell King - ARM Linux wrote:
> On Wed, Oct 24, 2018 at 12:45:44PM +0200, Matthias Brugger wrote:
> > Hi Kiberly,
> >
> > Thanks for adding all the emails in CC.
> > I would encourage you for your next patch to distinguish between CC and TO.
> > You should send your patch TO important maintainers in the get_maintainers.pl
> > list (as default, to all of them). If there is someone you really want to look
> > into the patch, then add him/her in TO as well.
> >
> > Put the rest (people and mailing lists) in CC. Why? Some people filter their
> > mails so that they can concentrate on the mails they got send directly and look
> > on mails they are in CC with lower priority (maybe not at all, because there are
> > too much?). So it is important to have the maintainers in the TO list and not in CC.
>
> +1
>
> I'm glad that there's someone else in the Linux community that agrees
> with me on this point, and is willing to speak out about it.
If it's an important point, perhaps it should be mentioned in
submitting-patches.rst? There is a mention of the Cc tag, but no
indication of who to put in CC.
julia
next prev parent reply other threads:[~2018-10-24 13:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181023211142.GA2661@v>
2018-10-24 4:56 ` [PATCH v2] staging: mt7621-dma: Add braces around else branches Kimberly Brown
2018-10-24 10:45 ` Matthias Brugger
2018-10-24 11:07 ` Russell King - ARM Linux
2018-10-24 13:06 ` Julia Lawall [this message]
2018-10-24 13:14 ` [Outreachy kernel] " Russell King - ARM Linux
2018-10-24 11:09 ` Dan Carpenter
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=alpine.DEB.2.21.1810241404050.2371@hadrien \
--to=julia.lawall@lip6.fr \
--cc=linux-arm-kernel@lists.infradead.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