public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Zoran <mzoran@crowfest.net>
To: Scott Branden <scott.branden@broadcom.com>,
	Julia Lawall <julia.lawall@lip6.fr>
Cc: Joe Perches <joe@perches.com>,
	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,
	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: Mon, 27 Feb 2017 12:47:04 -0800	[thread overview]
Message-ID: <1488228424.5276.1.camel@crowfest.net> (raw)
In-Reply-To: <954e0bc5-cd3c-c06f-dbfa-bed486b823c6@broadcom.com>

On Mon, 2017-02-27 at 12:35 -0800, Scott Branden wrote:
> > 
> Hi Julia,
> 
> On 17-02-26 10:25 PM, Julia Lawall wrote:
> > 
> > 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

I submitted the driver to stagging, so I feel a bit responsible for
this.  

I personally don't mind e-mails like this since people have to get
started somehow, and e-mail is rather easy to ignore or delete...

Perhaps it would make sense to either update the maintainer list for
this driver or move the driver somewhere else in staging?  I was
looking at the maintainer list for bcm2835, and it already marks
vc04_services as part of the bcm2835 files.  Perhaps another mark
should be added or the driver moved under vc04_services?

      reply	other threads:[~2017-02-27 22:04 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
2017-02-27 20:47                   ` Michael Zoran [this message]

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=1488228424.5276.1.camel@crowfest.net \
    --to=mzoran@crowfest.net \
    --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=joe@perches.com \
    --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=narcisaanamaria12@gmail.com \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=rjui@broadcom.com \
    --cc=sbranden@broadcom.com \
    --cc=scott.branden@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