All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Julia Lawall <julia.lawall@lip6.fr>,
	Narcisa Ana Maria Vasile <narcisaanamaria12@gmail.com>
Cc: 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 10:34:32 -0800	[thread overview]
Message-ID: <1488134072.9188.3.camel@perches.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1702261901180.2056@hadrien>

On Sun, 2017-02-26 at 19:03 +0100, Julia Lawall wrote:
> 
> On Sun, 26 Feb 2017, Narcisa Ana Maria Vasile wrote:
> 
> > This was reported by checkpatch.pl
> > 
> > Signed-off-by: Narcisa Ana Maria Vasile <narcisaanamaria12@gmail.com>
> 
> Acked-by: Julia Lawall <julia.lawall@lip6.fr>
> 
> Actually, the outreachy tutorial says not to send patches to mailing
> lists, only to people (except in the case of IIO, where the maintainers
> asked for patches to be sent to mailing lists as well).  The
> get_maintainer command to use is shown here:
> 
> https://kernelnewbies.org/FirstKernelPatch#submit_a_patch

That doesn't make any sense to me.
Mailing lists _should_ be copied on patch submissions.

And the displayed output of that command-line does not match
the actual behavior.

The command-line is:
$ perl scripts/get_maintainer.pl --separator , --nokeywords --nogit --nogit-fallback --norolestats --nol -f drivers/staging/most/aim-sound/sound.c

And the output shown is:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,devel@driverdev.osuosl.org,linux-kernel@vger.kernel.org

That's not what's actually output by that command-line
as it would not show the mailing list.

$ perl scripts/get_maintainer.pl --separator , --nokeywords --nogit --nogit-fallback --norolestats --nol -f drivers/staging/most/aim-sound/sound.c
Greg Kroah-Hartman <gregkh@linuxfoundation.org>



WARNING: multiple messages have this Message-ID (diff)
From: joe@perches.com (Joe Perches)
To: linux-arm-kernel@lists.infradead.org
Subject: [Outreachy kernel] [PATCH] staging: bcm2835-audio: Fixed spacing around '&'
Date: Sun, 26 Feb 2017 10:34:32 -0800	[thread overview]
Message-ID: <1488134072.9188.3.camel@perches.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1702261901180.2056@hadrien>

On Sun, 2017-02-26 at 19:03 +0100, Julia Lawall wrote:
> 
> On Sun, 26 Feb 2017, Narcisa Ana Maria Vasile wrote:
> 
> > This was reported by checkpatch.pl
> > 
> > Signed-off-by: Narcisa Ana Maria Vasile <narcisaanamaria12@gmail.com>
> 
> Acked-by: Julia Lawall <julia.lawall@lip6.fr>
> 
> Actually, the outreachy tutorial says not to send patches to mailing
> lists, only to people (except in the case of IIO, where the maintainers
> asked for patches to be sent to mailing lists as well).  The
> get_maintainer command to use is shown here:
> 
> https://kernelnewbies.org/FirstKernelPatch#submit_a_patch

That doesn't make any sense to me.
Mailing lists _should_ be copied on patch submissions.

And the displayed output of that command-line does not match
the actual behavior.

The command-line is:
$ perl scripts/get_maintainer.pl --separator , --nokeywords --nogit --nogit-fallback --norolestats --nol -f drivers/staging/most/aim-sound/sound.c

And the output shown is:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,devel at driverdev.osuosl.org,linux-kernel at vger.kernel.org

That's not what's actually output by that command-line
as it would not show the mailing list.

$ perl scripts/get_maintainer.pl --separator , --nokeywords --nogit --nogit-fallback --norolestats --nol -f drivers/staging/most/aim-sound/sound.c
Greg Kroah-Hartman <gregkh@linuxfoundation.org>

  reply	other threads:[~2017-02-26 18:34 UTC|newest]

Thread overview: 24+ 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 17:47 ` Narcisa Ana Maria Vasile
2017-02-26 18:03 ` [Outreachy kernel] " Julia Lawall
2017-02-26 18:03   ` Julia Lawall
2017-02-26 18:34   ` Joe Perches [this message]
2017-02-26 18:34     ` Joe Perches
2017-02-26 18:59     ` Julia Lawall
2017-02-26 18:59       ` Julia Lawall
2017-02-26 19:37       ` Joe Perches
2017-02-26 19:37         ` Joe Perches
2017-02-26 19:40         ` Julia Lawall
2017-02-26 19:40           ` Julia Lawall
2017-02-26 21:56           ` Joe Perches
2017-02-26 21:56             ` Joe Perches
2017-02-27  0:08             ` Scott Branden
2017-02-27  0:08               ` Scott Branden
2017-02-27  6:25               ` Julia Lawall
2017-02-27  6:25                 ` Julia Lawall
2017-02-27 14:44                 ` Dan Carpenter
2017-02-27 14:44                   ` Dan Carpenter
2017-02-27 20:35                 ` Scott Branden
2017-02-27 20:35                   ` Scott Branden
2017-02-27 20:47                   ` Michael Zoran
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=1488134072.9188.3.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 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.