From: scott.branden@broadcom.com (Scott Branden)
To: linux-arm-kernel@lists.infradead.org
Subject: [Outreachy kernel] [PATCH] staging: bcm2835-audio: Fixed spacing around '&'
Date: Mon, 27 Feb 2017 12:35:52 -0800 [thread overview]
Message-ID: <954e0bc5-cd3c-c06f-dbfa-bed486b823c6@broadcom.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1702270724430.2187@hadrien>
Hi Julia,
On 17-02-26 10:25 PM, Julia Lawall wrote:
>
>
> On Sun, 26 Feb 2017, Scott Branden wrote:
>
>>
>>
>> On 17-02-26 01:56 PM, Joe Perches wrote:
>>> 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.
>>>
>> I would prefer this outreachy work uses their own mailing list and reviews
>> their patches first. Then once they have everything sorted out they send out
>> the patch series to the proper maintainers/mailing lists. That way we're not
>> spammed with all these emails of people as they are learning how to format and
>> send out proper patches.
>
> If you consider that you are getting too much outreachy mail at the
> moment, just let me know what subsystem you want me to add an exception
> for.
The emails seem to mostly be coming with bcm2835-audio.
>
> thanks,
> julia
Thanks,
Scott
>
next prev parent reply other threads:[~2017-02-27 20:35 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
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 [this message]
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=954e0bc5-cd3c-c06f-dbfa-bed486b823c6@broadcom.com \
--to=scott.branden@broadcom.com \
--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;
as well as URLs for NNTP newsgroup(s).