qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	John Rigby <john.rigby@linaro.org>,
	qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] New targets (was: [PATCH] qapi-schema.json: Reformat TargetType enum to one-per-line)
Date: Wed, 22 May 2013 09:48:59 -0500	[thread overview]
Message-ID: <87mwrncbok.fsf@codemonkey.ws> (raw)
In-Reply-To: <519CD77B.3080400@suse.de>

Andreas Färber <afaerber@suse.de> writes:

> Am 22.05.2013 16:28, schrieb Anthony Liguori:
>> Andreas Färber <afaerber@suse.de> writes:
>>> More common is however that people start writing a new target and don't
>>> submit it yet (ahem!) while another target gets added, and the current
>>> form of rebreaking this block of enum values causes more conflicts
>> 
>> Sounds like a good reason to submit the target upstream to me...
>
> So are incompletely implemented targets (wrt instruction set) eligible
> for upstream these days?

Aren't most of our target incomplete by some standard?

I thought the typical approach for a target was to get linux-user
working first, and then go for softmmu.  As long as linux-user can run
application, I think it's fair game for merging.

> I thought they'd need to be able to run at
> least some small image successfully, preferably Linux where possible.

I think that's far too high of a hurdle.

Regards,

Anthony Liguori

>
> Regards,
> Andreas
>
> -- 
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2013-05-22 14:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-20 16:21 [Qemu-devel] [PATCH] qapi-schema.json: Reformat TargetType enum to one-per-line Peter Maydell
2013-05-20 16:35 ` Paolo Bonzini
2013-05-20 16:38   ` Peter Maydell
2013-05-20 17:14     ` Paolo Bonzini
2013-05-22 13:15   ` Anthony Liguori
2013-05-22 13:50     ` Andreas Färber
2013-05-22 14:28       ` Anthony Liguori
2013-05-22 14:34         ` [Qemu-devel] New targets (was: [PATCH] qapi-schema.json: Reformat TargetType enum to one-per-line) Andreas Färber
2013-05-22 14:48           ` Anthony Liguori [this message]
2013-05-22 15:33             ` Peter Maydell
2013-05-22 16:10               ` Anthony Liguori
2013-05-22 13:51     ` [Qemu-devel] [PATCH] qapi-schema.json: Reformat TargetType enum to one-per-line Peter Maydell
2013-05-22 14:29       ` Anthony Liguori
2013-05-22 14:38         ` Paolo Bonzini
2013-05-24 21:38         ` [Qemu-devel] [libvirt] " Eric Blake
2013-05-25  9:18           ` Peter Maydell
2013-05-25 12:31             ` Andreas Färber
2013-05-20 16:41 ` [Qemu-devel] " Eric Blake
2013-05-20 16:47   ` Peter Maydell
2013-05-20 16:57     ` Eric Blake
2013-05-20 17:05       ` Paolo Bonzini
2013-05-22 13:12 ` Anthony Liguori
2013-05-22 13:38   ` 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=87mwrncbok.fsf@codemonkey.ws \
    --to=aliguori@us.ibm.com \
    --cc=afaerber@suse.de \
    --cc=john.rigby@linaro.org \
    --cc=pbonzini@redhat.com \
    --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).