qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Peter Maydell <peter.maydell@linaro.org>,
	Sergey Fedorov <sergey.fedorov@linaro.org>
Cc: "qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] tcg/ppc: maintainer's mail delivery failure
Date: Thu, 31 Mar 2016 10:33:36 -0700	[thread overview]
Message-ID: <56FD5F70.3000107@twiddle.net> (raw)
In-Reply-To: <CAFEAcA-u26x2hDB53YgqtboLZ8y=Gg1hVhKJJfg7MAFtuMBMjA@mail.gmail.com>

On 03/31/2016 10:30 AM, Peter Maydell wrote:
> On 24 March 2016 at 11:09, Peter Maydell <peter.maydell@linaro.org> wrote:
>> On 24 March 2016 at 10:55, Sergey Fedorov <sergey.fedorov@linaro.org> wrote:
>>> Probably we don't have a maintainer for PPC TCG backend.
>>>
>>>     PPC
>>>     M: Vassili Karpov (malc) <av1474@comtv.ru>
>>>     S: Maintained
>>>     F: tcg/ppc/
>>>     F: disas/ppc.c
>>
>> Yes, malc has not been with the project for some years now. We
>> should probably go through and tidy up the MAINTAINERS file.
> 
> Would anybody like to put their name forward for tcg/ppc maintainer
> (possibly at Odd Fixes status), or should we mark this as Orphaned ?
> 
> I have cc'd some plausible suspects. If nobody cares to volunteer
> within a few weeks I'll send out a patch marking it as Orphan.

I'll do odd fixes.  Thankfully the gcc compile farm makes this easy.


r~

      reply	other threads:[~2016-03-31 17:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <001a113db0d454285b052ec911f0@google.com>
2016-03-24 10:55 ` [Qemu-devel] tcg/ppc: maintainer's mail delivery failure Sergey Fedorov
2016-03-24 11:09   ` Peter Maydell
2016-03-31 17:30     ` Peter Maydell
2016-03-31 17:33       ` Richard Henderson [this message]

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=56FD5F70.3000107@twiddle.net \
    --to=rth@twiddle.net \
    --cc=agraf@suse.de \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=sergey.fedorov@linaro.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;
as well as URLs for NNTP newsgroup(s).