From: syeh@vmware.com (Sinclair Yeh)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Figuring out the right patch receivers
Date: Wed, 2 Dec 2015 09:27:10 -0800 [thread overview]
Message-ID: <20151202172710.GC14231@syeh-linux> (raw)
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.
next reply other threads:[~2015-12-02 17:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 17:27 Sinclair Yeh [this message]
2015-12-02 19:23 ` Figuring out the right patch receivers Greg KH
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=20151202172710.GC14231@syeh-linux \
--to=syeh@vmware.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.