All of lore.kernel.org
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Figuring out the right patch receivers
Date: Wed, 2 Dec 2015 11:23:49 -0800	[thread overview]
Message-ID: <20151202192349.GC26294@kroah.com> (raw)
In-Reply-To: <20151202172710.GC14231@syeh-linux>

On Wed, Dec 02, 2015 at 09:27:10AM -0800, Sinclair Yeh wrote:
> Hi,
> 
> For the first time, I sent out a patch series that touched multiple
> subsystems.
> 
> I used "get_maintainer.pl" to figure out who all the maintainers are
> and decided to send the entire series to x86 at kernel.org" and Cc
> "linux-kernel at vger.kernel.org"
> 
> I also Cc'ed individual patches to (what I thought were) the
> appropriate maintainers.
> 
> One of the maintainers, GregKH, said I probably should have CC'ed him
> on the entire series, but get_maintainer.pl listed him as a
> "supporter" for only a subset of the patches.
> 
> Can someone tell me where I went wrong in my thought process so
> I can get it right the next time?
> 
> thanks,
> 
> Sinclair
> 
> PS. Mentioning GregKH rather than "a maintainer" only because I know he
> maintains kernel-stable so maybe he's got a more expanded role.  Since
> the series was not for kernel-stable, I thought following get_maintainer.pl
> is the right approach.

But, I'm the maintainer for the drivers/misc/ subsystem, which this
patch series did touch, so you should have cc:ed me on it, or at the
very least, the vmbus developers should have told you that as they
forward patches on to me.

For multi-subsystem patchsets like this, it's important to cc: everyone
relevant on the 00/XX email so we all know what is going on, not to just
copy them on a single email in a series, otherwise we will be confused
and not know what to do with only patch 03/06 or so, especially when
patach 03 depends on earlier patches.

And really, your patcheset hit all of one specific type of driver, so
the maintainers of that subsystem should take care of this all for you,
you shouldn't be responsible for sending it to all different places.

hope this helps,

greg k-h

      reply	other threads:[~2015-12-02 19:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 17:27 Figuring out the right patch receivers Sinclair Yeh
2015-12-02 19:23 ` Greg KH [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=20151202192349.GC26294@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.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.