From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: devel@driverdev.osuosl.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
outreachy-kernel@googlegroups.com,
linux-mediatek@lists.infradead.org,
"Kimberly Brown" <kimbrownkd@gmail.com>,
NeilBrown <neil@brown.name>,
"Christian Lütke-Stetzkamp" <christian@lkamp.de>,
linux-arm-kernel@lists.infradead.org,
"John Crispin" <blogic@openwrt.org>
Subject: Re: [PATCH v2] staging: mt7621-dma: Add braces around else branches
Date: Wed, 24 Oct 2018 12:07:45 +0100 [thread overview]
Message-ID: <20181024110745.GV30658@n2100.armlinux.org.uk> (raw)
In-Reply-To: <af4594cc-05c0-672c-d560-b50705ceaab3@gmail.com>
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.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
WARNING: multiple messages have this Message-ID (diff)
From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: "Kimberly Brown" <kimbrownkd@gmail.com>,
outreachy-kernel@googlegroups.com,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
devel@driverdev.osuosl.org, linux-mediatek@lists.infradead.org,
NeilBrown <neil@brown.name>,
"Christian Lütke-Stetzkamp" <christian@lkamp.de>,
linux-arm-kernel@lists.infradead.org,
"John Crispin" <blogic@openwrt.org>
Subject: Re: [PATCH v2] staging: mt7621-dma: Add braces around else branches
Date: Wed, 24 Oct 2018 12:07:45 +0100 [thread overview]
Message-ID: <20181024110745.GV30658@n2100.armlinux.org.uk> (raw)
In-Reply-To: <af4594cc-05c0-672c-d560-b50705ceaab3@gmail.com>
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.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
WARNING: multiple messages have this Message-ID (diff)
From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] staging: mt7621-dma: Add braces around else branches
Date: Wed, 24 Oct 2018 12:07:45 +0100 [thread overview]
Message-ID: <20181024110745.GV30658@n2100.armlinux.org.uk> (raw)
In-Reply-To: <af4594cc-05c0-672c-d560-b50705ceaab3@gmail.com>
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.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
next prev parent reply other threads:[~2018-10-24 11:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 21:11 [PATCH] staging: mt7621-dma: Add braces around else branches Kimberly Brown
2018-10-23 21:22 ` Matthias Brugger
2018-10-23 21:25 ` Matthias Brugger
2018-10-24 4:56 ` [PATCH v2] " Kimberly Brown
2018-10-24 4:56 ` Kimberly Brown
2018-10-24 4:56 ` Kimberly Brown
2018-10-24 10:45 ` Matthias Brugger
2018-10-24 10:45 ` Matthias Brugger
2018-10-24 10:45 ` Matthias Brugger
2018-10-24 11:07 ` Russell King - ARM Linux [this message]
2018-10-24 11:07 ` Russell King - ARM Linux
2018-10-24 11:07 ` Russell King - ARM Linux
2018-10-24 13:06 ` [Outreachy kernel] " Julia Lawall
2018-10-24 13:06 ` Julia Lawall
2018-10-24 13:06 ` Julia Lawall
2018-10-24 13:14 ` Russell King - ARM Linux
2018-10-24 13:14 ` Russell King - ARM Linux
2018-10-24 13:14 ` Russell King - ARM Linux
2018-10-24 11:09 ` Dan Carpenter
2018-10-24 11:09 ` Dan Carpenter
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=20181024110745.GV30658@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=blogic@openwrt.org \
--cc=christian@lkamp.de \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kimbrownkd@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=neil@brown.name \
--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.