From: Peter Maydell <peter.maydell@linaro.org>
To: Auger Eric <eric.auger@redhat.com>
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Eric Auger" <eric.auger.pro@gmail.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
qemu-arm <qemu-arm@nongnu.org>, "Thomas Huth" <thuth@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-3.1] MAINTAINERS: Add an ARM SMMU section
Date: Fri, 23 Nov 2018 09:08:45 +0000 [thread overview]
Message-ID: <CAFEAcA_s50WTbdJ9QWPjmXw0Xo=RpkAFPQJjzwSc3pQXL5neaA@mail.gmail.com> (raw)
In-Reply-To: <43381cce-1af0-8613-edf3-c216afdbe142@redhat.com>
On 23 November 2018 at 08:04, Auger Eric <eric.auger@redhat.com> wrote:
> On 11/22/18 11:33 PM, Philippe Mathieu-Daudé wrote:
>> On 22/11/18 19:01, Eric Auger wrote:
>>> +ARM SMMU
>>> +M: Eric Auger <eric.auger@redhat.com>
>>> +L: qemu-arm@nongnu.org
>>> +S: Maintained
>>
>> Shouldn't you use 'Supported': "Someone is actually paid to look after
>> this."?
> Not sure this is really important as long as get_maintainer.pl returns
> the right contacts. Many ARM sections do not feature the "Supported"
> tag. I will follow Peter's guidance though.
I don't really understand the purpose of the Supported vs
Maintained distinction. Mostly I list stuff as just
Maintained when I am dealing with it.
I think in particular that if a part of QEMU is just one
of a whole set of things that you are doing as part of
your job then Supported is a bit overstating things.
thanks
-- PMM
next prev parent reply other threads:[~2018-11-23 9:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 18:01 [Qemu-devel] [PATCH for-3.1] MAINTAINERS: Add an ARM SMMU section Eric Auger
2018-11-22 22:33 ` Philippe Mathieu-Daudé
2018-11-23 8:04 ` Auger Eric
2018-11-23 9:08 ` Peter Maydell [this message]
2018-11-26 13:41 ` Peter Maydell
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='CAFEAcA_s50WTbdJ9QWPjmXw0Xo=RpkAFPQJjzwSc3pQXL5neaA@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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 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.