From: Rob Herring <robherring2@gmail.com>
To: Grant Likely <grant.likely@linaro.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
devicetree@vger.kernel.org,
Ian Campbell <ian.campbell@citrix.com>,
Pawel Moll <pawel.moll@arm.com>,
devicetree-discuss <devicetree-discuss@lists.ozlabs.org>
Subject: Re: [PATCH 3/3] MAINTAINERS: Refactor device tree maintainership
Date: Mon, 22 Jul 2013 15:31:16 -0500 [thread overview]
Message-ID: <51ED9694.9060303@gmail.com> (raw)
In-Reply-To: <CACxGe6sGdkMuLFs3K_ERKot+ryTArs6qTiwpXNe+LyoAQ8HGDw@mail.gmail.com>
On 07/21/2013 07:35 PM, Grant Likely wrote:
> On Sun, Jul 21, 2013 at 7:56 PM, Rob Herring <robherring2@gmail.com> wrote:
>> On 07/19/2013 10:19 PM, Grant Likely wrote:
>>> +OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS
>>> +M: Pawel Moll <pawel.moll@arm.com>
>>> +M: Mark Rutland <mark.rutland@arm.com>
>>> +M: Stephen Warren <swarren@wwwdotorg.org>
>>> +M: Ian Campbell <ian.campbell@citrix.com>
>>
>> You can add me. I was not intending to step down.
>
> Done.
>
>> What about creating an email alias for the group instead?
>
> Would that be any different from the mailing list address?
My own selfish desire is to easily separate emails for DT bindings and
DT core code. I suppose I could do that with a suffix on my email address.
It seems to work well for arm-soc where you have a group of maintainers
and don't necessarily know who is actively maintaining things. Not sure
if we want to timeshare like that, but it would give us the flexibility.
Rob
next prev parent reply other threads:[~2013-07-22 20:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1374290388-19308-1-git-send-email-grant.likely@linaro.org>
2013-07-20 3:19 ` [PATCH 2/3] MAINTAINERS: Change device tree mailing list Grant Likely
[not found] ` <1374290388-19308-1-git-send-email-grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-07-20 3:19 ` [PATCH 3/3] MAINTAINERS: Refactor device tree maintainership Grant Likely
2013-07-20 16:20 ` Linus Walleij
[not found] ` <CACRpkdb2bPQOD2CBzbF0K33mZZwKwGSCO6B4djesVd5DR-Z1tA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-07-21 13:46 ` Jon Loeliger
[not found] ` <E1V0txk-0007v7-0J-CYoMK+44s/E@public.gmane.org>
2013-07-22 0:33 ` Grant Likely
2013-07-22 1:27 ` David Gibson
2013-07-22 17:38 ` Jon Loeliger
2013-07-21 0:17 ` Olof Johansson
2013-07-21 0:29 ` Joe Perches
2013-07-21 9:46 ` Grant Likely
2013-07-22 0:36 ` Grant Likely
2013-07-22 17:29 ` Olof Johansson
[not found] ` <1374290388-19308-3-git-send-email-grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-07-21 18:56 ` Rob Herring
2013-07-22 0:35 ` Grant Likely
2013-07-22 20:31 ` Rob Herring [this message]
2013-07-22 21:36 ` Jon Loeliger
2013-07-23 3:27 ` Rob Herring
2013-07-22 16:50 ` Pawel Moll
2013-07-22 20:03 ` Rob Herring
2013-07-23 17:14 ` Pawel Moll
2013-07-23 17:59 ` Stephen Warren
2013-07-23 18:09 ` Ian Campbell
2013-07-23 18:44 ` Rob Herring
2013-07-23 18:55 ` Ian Campbell
2013-07-23 19:28 ` Rob Herring
2013-07-23 19:53 ` Stephen Warren
2013-08-07 10:53 ` Ian Campbell
2013-07-23 19:26 ` Nicolas Pitre
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=51ED9694.9060303@gmail.com \
--to=robherring2@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=ian.campbell@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pawel.moll@arm.com \
/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;
as well as URLs for NNTP newsgroup(s).