kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: "Alex Bennée" <alex.bennee@linaro.org>,
	"Christoffer Dall" <christoffer.dall@linaro.org>
Cc: Andrew Jones <drjones@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [kvm-unit-tests RFC PATCH] Add MAINTAINERS file
Date: Wed, 29 Jul 2015 11:41:32 +0100	[thread overview]
Message-ID: <55B8ADDC.1050308@arm.com> (raw)
In-Reply-To: <87r3nrmh69.fsf@linaro.org>

On 29/07/15 10:44, Alex Bennée wrote:
> 
> Christoffer Dall <christoffer.dall@linaro.org> writes:
> 
>> On Tue, Jul 28, 2015 at 2:51 PM, Marc Zyngier <marc.zyngier@arm.com> wrote:
>>> On 28/07/15 13:44, Andrew Jones wrote:
>>>> On Tue, Jul 28, 2015 at 12:41:38PM +0100, Alex Bennée wrote:
>>>>>
>>>>> Paolo Bonzini <pbonzini@redhat.com> writes:
>>>>>
>>>>>> On 28/07/2015 10:56, Alex Bennée wrote:
>>>>>>> +Architecture Specific Code:
>>>>>>> +---------------------------
>>>>>>> +
>>>>>>> +ARM
>>>>>>> +M: Christoffer Dall <christoffer.dall@linaro.org>
>>>>>>> +L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
>>>>>>> +L: kvmarm@lists.cs.columbia.edu
>>>>>>> +F: arm/*
>>>>>>> +
>>>>>>
>>>>>> Hmm, shouldn't the maintainer be Drew here (or Drew + Christoffer)?
>>>>>
>>>>> I was going by his demur deferral earlier ;-)
>>>>>
>>>>>     "Also, for arm patches I usually CC Christoffer too...""
>>>>>
>>>>> But sure the more the merrier!
>>>>
>>>> Yeah, I wasn't running away from the role. I was just stating that it's
>>>> nice to get Christoffer's input on low-level arm bits. And, particularly
>>>> as we start adding real kvm tests, it'd be good to get his and/or Marc's
>>>> input to make sure the tests are complete. Anyway, feel free to add me
>>>> as a maintainer for kvm-unit-tests/arm. I'm happy to do it.
>>>
>>> I'm always happy to be CCed on architecture related questions. Just
>>> don't advertise me as a maintainer for the unit tests! ;-)
>>>
>> I'm with Marc here, don't put me in the maintainers file, I don't have
>> the bandwidth for this at the moment and I'm quite happy seeing Drew
>> taking care of this.
> 
> I shall add suggested CC's then and leave Drew as maintainer?

That'd be my preferred option. Drew is doing a great job, and he should
be recognized for it.

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

  reply	other threads:[~2015-07-29 10:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-28  8:56 [kvm-unit-tests RFC PATCH] Add MAINTAINERS file Alex Bennée
2015-07-28  9:56 ` Paolo Bonzini
2015-07-28 11:41   ` Alex Bennée
2015-07-28 12:44     ` Andrew Jones
2015-07-28 12:51       ` Marc Zyngier
2015-07-29  9:36         ` Christoffer Dall
2015-07-29  9:44           ` Alex Bennée
2015-07-29 10:41             ` Marc Zyngier [this message]
2015-07-29 13:45 ` Paolo Bonzini
2015-07-31 15:06   ` Alex Bennée
2015-07-31 15:06     ` Paolo Bonzini

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=55B8ADDC.1050308@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=alex.bennee@linaro.org \
    --cc=christoffer.dall@linaro.org \
    --cc=drjones@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.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).