From: James Hogan <jhogan@kernel.org>
To: Aleksandar Markovic <aleksandar.m.mail@gmail.com>
Cc: "Philippe Mathieu-Daudé" <philippe@mathieu-daude.net>,
"Paul Burton" <paulburton@kernel.org>,
"QEMU Trivial" <qemu-trivial@nongnu.org>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
"Aleksandar Markovic" <amarkovic@wavecomp.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Aleksandar Rikalo" <aleksandar.rikalo@rt-rk.com>,
"Aurelien Jarno" <aurelien@aurel32.net>
Subject: Re: [PATCH] MAINTAINERS: Orphan MIPS KVM CPUs
Date: Sun, 16 Feb 2020 06:57:17 +0000 [thread overview]
Message-ID: <20200216065717.GA145683@jamesdev> (raw)
In-Reply-To: <CAL1e-=jdpp2W-B1cERU4srRQUkPTjewM3hVrndoh4nr-vPSRGA@mail.gmail.com>
On Thu, Feb 13, 2020 at 01:34:57AM +0100, Aleksandar Markovic wrote:
> On Wed, Feb 12, 2020 at 7:44 PM Philippe Mathieu-Daudé
> <philippe@mathieu-daude.net> wrote:
> >
> > Cc'ing qemu-trivial@ & Paolo.
> >
>
> We are in the process of handling this within the company, and this
> patch should go via MIPS tree, not trivial tree - will be updated when
> the opinions are crystallized, and all consultations with others were
> done. There is no rush.
Hi Aleksandar,
I respectfully disagree. In the mean time I am still listed as
maintainer even though this patch has reflected reality for more than 18
months since the 2018 closure of the MIPS UK offices.
If "the company" wish to eventually crystalize their opinion and assign
someone else this role (which they've had at least 6 weeks to do even
since I sent the patch) they can always submit a new patch.
In the mean time I'd appreciate if somebody could take the patch ASAP.
All the best,
James
next prev parent reply other threads:[~2020-02-16 6:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-21 15:53 [PATCH] MAINTAINERS: Orphan MIPS KVM CPUs James Hogan
2020-02-12 18:43 ` Philippe Mathieu-Daudé
2020-02-13 0:34 ` Aleksandar Markovic
2020-02-16 6:57 ` James Hogan [this message]
2020-02-16 7:47 ` Paolo Bonzini
2020-02-16 16:33 ` Aleksandar Markovic
2020-02-16 22:55 ` James Hogan
2020-02-18 18:00 ` Aleksandar Markovic
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=20200216065717.GA145683@jamesdev \
--to=jhogan@kernel.org \
--cc=aleksandar.m.mail@gmail.com \
--cc=aleksandar.rikalo@rt-rk.com \
--cc=amarkovic@wavecomp.com \
--cc=aurelien@aurel32.net \
--cc=paulburton@kernel.org \
--cc=pbonzini@redhat.com \
--cc=philippe@mathieu-daude.net \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.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).