From: Joe Perches <joe@perches.com>
To: Julia Lawall <julia.lawall@lip6.fr>
Cc: Narcisa Ana Maria Vasile <narcisaanamaria12@gmail.com>,
swarren@wwwdotorg.org, lee@kernel.org, eric@anholt.net,
f.fainelli@gmail.com, rjui@broadcom.com, sbranden@broadcom.com,
daniel.baluta@spamfreegmail.com, gregkh@linuxfoundation.org,
outreachy-kernel@googlegroups.com,
bcm-kernel-feedback-list@broadcom.com, mzoran@crowfest.net,
danielperezdeandres@gmail.com, dan.carpenter@oracle.com,
devel@driverdev.osuosl.org, linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [Outreachy kernel] [PATCH] staging: bcm2835-audio: Fixed spacing around '&'
Date: Sun, 26 Feb 2017 13:56:51 -0800 [thread overview]
Message-ID: <1488146211.9188.10.camel@perches.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1702262038560.2056@hadrien>
On Sun, 2017-02-26 at 20:40 +0100, Julia Lawall wrote:
> On Sun, 26 Feb 2017, Joe Perches wrote:
> > On Sun, 2017-02-26 at 19:59 +0100, Julia Lawall wrote:
> > > On Sun, 26 Feb 2017, Joe Perches wrot
> > > > Mailing lists _should_ be copied on patch submissions.
> > > The idea of outreachy is that it should be a place for people to get
> > > started without too much criticism from the outside. Originally, only the
> > > outreachy mailing list received patches. But staging maintainers were
> > > confused to have their drivers receiving patches that they had not seen.
> > > So we expanded it to maintainers.
> >
> > That also doesn't make much sense as patches
> > should not be applied that have not reached
> > a mailing list for review.
> >
> > As long as initial outreachy patches are not
> > applied and are just for internal review by
> > any outside person but the outreachy list and
> > are not be applied by maintainers, then perhaps
> > it's best if neither maintainers nor lists are
> > cc'd on the patches.
>
> The patches are applied by Greg. Greg suggested the policy of adding
> maintainers but not including mailing lists. I'll let him consider
> whether the policy should be changed.
Well, I will comment on patches sent to the kernel list.
I'm not subscribed to outreachy and I don't want to be
subscribed to that list either.
next prev parent reply other threads:[~2017-02-26 21:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-26 17:47 [PATCH] staging: bcm2835-audio: Fixed spacing around '&' Narcisa Ana Maria Vasile
2017-02-26 18:03 ` [Outreachy kernel] " Julia Lawall
2017-02-26 18:34 ` Joe Perches
2017-02-26 18:59 ` Julia Lawall
2017-02-26 19:37 ` Joe Perches
2017-02-26 19:40 ` Julia Lawall
2017-02-26 21:56 ` Joe Perches [this message]
2017-02-27 0:08 ` Scott Branden
2017-02-27 6:25 ` Julia Lawall
2017-02-27 14:44 ` Dan Carpenter
2017-02-27 20:35 ` Scott Branden
2017-02-27 20:47 ` Michael Zoran
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=1488146211.9188.10.camel@perches.com \
--to=joe@perches.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dan.carpenter@oracle.com \
--cc=daniel.baluta@spamfreegmail.com \
--cc=danielperezdeandres@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@lip6.fr \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mzoran@crowfest.net \
--cc=narcisaanamaria12@gmail.com \
--cc=outreachy-kernel@googlegroups.com \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=swarren@wwwdotorg.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