qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@uclinux.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] m68k orphaned?
Date: Fri, 19 Jun 2015 17:17:04 +1000	[thread overview]
Message-ID: <5583C1F0.1060200@uclinux.org> (raw)
In-Reply-To: <CAFEAcA9wcpy1tUe75KhpWF5BH2++UeuN0D-ZT4EYjfGOrfTFRQ@mail.gmail.com>

Hi Peter,

On 19/06/15 17:12, Peter Maydell wrote:
> On 19 June 2015 at 06:00, 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]
>>
>> They are still relevant, still apply, and are still needed.
>> Does anyone have any suggestions how I can get them pushed into
>> mainline qemu?
> 
> If you make the minor fixes Peter C has suggested, rebase
> them onto current master and resend with the relevant
> reviewed-by: tags in the commit messages, I'll apply
> them to master.

Thats great, thanks. I'll update them and get them to you.


> If you're interested in taking on maintenance of m68k
> longer-term we can discuss that, but right now let's
> just get the fixes in.

Sounds good, thanks.

Regards
Greg

  reply	other threads:[~2015-06-19  7:16 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
2015-06-19  7:12 ` Peter Maydell
2015-06-19  7:17   ` Greg Ungerer [this message]
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=5583C1F0.1060200@uclinux.org \
    --to=gerg@uclinux.org \
    --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 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).