From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:43069)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1UfA7q-0001pb-Nm
	for qemu-devel@nongnu.org; Wed, 22 May 2013 10:34:48 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1UfA7j-0001mK-VP
	for qemu-devel@nongnu.org; Wed, 22 May 2013 10:34:46 -0400
Received: from cantor2.suse.de ([195.135.220.15]:45946 helo=mx2.suse.de)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1UfA7j-0001m4-PK
	for qemu-devel@nongnu.org; Wed, 22 May 2013 10:34:39 -0400
Message-ID: <519CD77B.3080400@suse.de>
Date: Wed, 22 May 2013 16:34:35 +0200
From: =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= <afaerber@suse.de>
MIME-Version: 1.0
References: <1369066884-431-1-git-send-email-peter.maydell@linaro.org>
	<519A50EE.8040804@redhat.com> <871u8zp34w.fsf@codemonkey.ws>
	<519CCD21.8090008@suse.de> <871u8zjdgy.fsf@codemonkey.ws>
In-Reply-To: <871u8zjdgy.fsf@codemonkey.ws>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] New targets (was: [PATCH] qapi-schema.json:
 Reformat TargetType enum to one-per-line)
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, John Rigby <john.rigby@linaro.org>, qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>

Am 22.05.2013 16:28, schrieb Anthony Liguori:
> Andreas F=C3=A4rber <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
>=20
> 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? I thought they'd need to be able to run at
least some small image successfully, preferably Linux where possible.

Regards,
Andreas

--=20
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=C3=BCrnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imend=C3=B6rffer; HRB 16746 AG N=C3=BC=
rnberg