From: Greg Ungerer <gerg@uclinux.org>
To: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Cc: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] m68k orphaned?
Date: Fri, 19 Jun 2015 17:15:15 +1000 [thread overview]
Message-ID: <5583C183.2000506@uclinux.org> (raw)
In-Reply-To: <CAEgOgz4yjVug2JdNKGfcwFxuDTa1Pm=Ani2R2+fG9Zb4ywT7ow@mail.gmail.com>
Hi Peter,
On 19/06/15 15:53, Peter Crosthwaite wrote:
> On Thu, Jun 18, 2015 at 10:00 PM, Greg Ungerer <gerg@uclinux.org> wrote:
>> Hi All,
>>
>> I see in the MAINTAINERS file that pretty much everything related
>> to the m68k architecture is listed as "Orphan".
>>
>> I have some patches that have been around for quite a while (posted
>> here twice) to fix some issues with the ColdFire support.
>> [See https://lists.nongnu.org/archive/html/qemu-devel/2014-08/msg03224.html]
>>
>
> I found a 3 patch series and did a review. I see RTH put and RB to
> patch 2 so I skipped over that.
>
>> They are still relevant, still apply, and are still needed.
>> Does anyone have any suggestions how I can get them pushed into
>> mainline qemu?
>>
>
> It suggests that you are the closest thing we have to a maintainer.
> You could try sending a PULL as there is no submaintainer that is
> going to actively pick this up. The other alternative is the trivial
> patches queue, although they are a little non-trivial due to
> functional change.
Thanks for the advice. Do I send the request to Peter Maydell?
I don't currently have a public git tree for this, can I just
send the patches? I can always set up a git hub tree if that
is a must.
Regards
Greg
next prev parent reply other threads:[~2015-06-19 7:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 5:00 [Qemu-devel] m68k orphaned? Greg Ungerer
2015-06-19 5:53 ` Peter Crosthwaite
2015-06-19 7:15 ` Greg Ungerer [this message]
2015-06-19 7:12 ` Peter Maydell
2015-06-19 7:17 ` Greg Ungerer
2015-06-19 7:22 ` 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=5583C183.2000506@uclinux.org \
--to=gerg@uclinux.org \
--cc=peter.crosthwaite@xilinx.com \
--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.