From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] kirkwood: fix spelling mistake
Date: Fri, 18 Nov 2016 14:04:57 +0100 [thread overview]
Message-ID: <87lgwh9bwm.fsf@free-electrons.com> (raw)
In-Reply-To: <trinity-8590509b-8acc-44c0-86dc-8cf16ea8ad8a-1479448964051@3capp-gmx-bs34> (p. wassi's message of "Fri, 18 Nov 2016 07:02:44 +0100")
Hi Paul,
On ven., nov. 18 2016, p.wassi at gmx.at wrote:
> Hi Andrew,
>
>> You should also send the patch to the Marvell MVEBU
>> maintainers.
>
> how do I find Marvell mvebu maintainers?
> The list in
> https://www.kernel.org/doc/linux/MAINTAINERS
> (line 1429) references mvebu/kirkwood and gave me the
> mailing list's address. Should the other two maintainers
> be addressed directly?
About putting the maintainer in Cc. Using ./scripts/get_maintainer.pl
coudl help you to find the people to put in CC. For example for your
patch:
Jason Cooper <jason@lakedaemon.net> (maintainer:ARM/Marvell Kirkwood and Armada 370, 375, 38x,...)
Andrew Lunn <andrew@lunn.ch> (maintainer:ARM/Marvell Kirkwood and Armada 370, 375, 38x,...)
Gregory Clement <gregory.clement@free-electrons.com> (maintainer:ARM/Marvell Kirkwood and Armada 370, 375, 38x,...)
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> (maintainer:ARM/Marvell Kirkwood and Armada 370, 375, 38x,...)
So indeed you should put the 4 co-maintainers in Cc.
Thanks,
Gregory
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2016-11-18 13:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 20:29 [PATCH] kirkwood: fix spelling mistake p.wassi at gmx.at
2016-11-17 21:00 ` Andrew Lunn
2016-11-17 21:02 ` Andrew Lunn
2016-11-18 6:02 ` p.wassi at gmx.at
2016-11-18 13:04 ` Gregory CLEMENT [this message]
2016-11-18 13:02 ` Gregory CLEMENT
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=87lgwh9bwm.fsf@free-electrons.com \
--to=gregory.clement@free-electrons.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