All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Alrae <leon.alrae@imgtec.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Anthony Liguori <aliguori@amazon.com>,
	Aurelien Jarno <aurelien@aurel32.net>,
	"afaerber@suse.de" <afaerber@suse.de>
Subject: Re: [Qemu-devel] pending target-mips patches
Date: Thu, 2 Oct 2014 09:46:31 +0100	[thread overview]
Message-ID: <542D10E7.9090300@imgtec.com> (raw)
In-Reply-To: <CAFEAcA_NznQgq2eSX-iPFBnkAkBBijxSGEGNEJvRgpqnFRbVow@mail.gmail.com>

Hi Peter,

On 01/10/2014 17:32, Peter Maydell wrote:
> On 1 October 2014 16:35, Leon Alrae <leon.alrae@imgtec.com> wrote:
>> I noticed that it's quite difficult to get target-mips changes
>> reviewed/accepted. There is already a queue of relatively big features
>> and bug fixes which are stuck for months. Does anyone have an idea how
>> to improve this situation? Wouldn't it help to have a target-mips
>> co-maintainer assisting Aurelien?
> 
> I agree that an active co-maintainer for target-mips would
> be a good idea. Is anybody volunteering? (Are you? :-))

I would be happy to help maintaining target-mips, but I'm wondering if
there are any more experienced (especially in legacy MIPS) volunteers.

> If somebody wants to take on this job, a good first start
> would be to assemble a git tree of patches which have got
> code review (ie which have accumulated at least one
> reviewed-by tag and aren't the subject of on-list
> disagreement about whether they're correct), test it, and
> submit it as a pull request (in the right format, and with
> your signed-off-by lines on the patches and any reviewed-by
> or acked-by lines from the list)... If somebody does that
> I will take a look at the result and if I'm happy with it
> I'll apply them.

Sounds straightforward, thanks.

Regards,
Leon

  reply	other threads:[~2014-10-02  8:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-01 15:35 [Qemu-devel] pending target-mips patches Leon Alrae
2014-10-01 16:32 ` Peter Maydell
2014-10-02  8:46   ` Leon Alrae [this message]
2014-10-01 16:33 ` Andreas Färber
2014-10-16 10:12 ` Aurelien Jarno
2014-10-16 10:19   ` Leon Alrae

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=542D10E7.9090300@imgtec.com \
    --to=leon.alrae@imgtec.com \
    --cc=afaerber@suse.de \
    --cc=aliguori@amazon.com \
    --cc=aurelien@aurel32.net \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@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 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.