qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Peter Crosthwaite <crosthwaitepeter@gmail.com>, qemu-devel@nongnu.org
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
	Richard Henderson <rth@twiddle.net>,
	Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
	Alexander Graf <agraf@suse.de>,
	Peter Crosthwaite <crosthwaite.peter@gmail.com>
Subject: Re: [Qemu-devel] [PATCH 0/8] Disas QOMification, round 2
Date: Thu, 27 Aug 2015 16:47:04 -0600	[thread overview]
Message-ID: <55DF9368.2040606@suse.de> (raw)
In-Reply-To: <55A25B32.5080203@suse.de>

Am 12.07.2015 um 06:18 schrieb Andreas Färber:
> Am 12.07.2015 um 03:59 schrieb Peter Crosthwaite:
>> Continue QOMifying target-specific disassembly. Convert all arches except for
>> X86 and PPC. They will be round 3 and are non-trivial.
>>
>> This brings us close to no arch-specific code in disas.c allow conversion to
>> common-obj and preparing these arches for inclusion in multi-arch.
> 
> I was about to say that this is for individual target maintainers now,
> for lack of CPUClass changes, but I guess they'll collide in disas.c...
> 
> Once it's reviewed I can queue it on qom-cpu-next, unless Peter or
> someone wants to.

I have queued them on qom-cpu-next now (subjects to be adjusted), but I
am still missing acks for s390x, moxie, sparc and alpha.

https://github.com/afaerber/qemu-cpu/commits/qom-cpu-next

Regards,
Andreas

> 
> Thanks for your efforts,
> Andreas
> 


-- 
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg)

  parent reply	other threads:[~2015-08-27 22:47 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-12  1:59 [Qemu-devel] [PATCH 0/8] Disas QOMification, round 2 Peter Crosthwaite
2015-07-12  1:59 ` [Qemu-devel] [PATCH 1/8] disas: s390x: QOMify target specific disas setup Peter Crosthwaite
2015-08-16  2:39   ` Peter Crosthwaite
2015-07-12  1:59 ` [Qemu-devel] [PATCH 2/8] disas: moxie: " Peter Crosthwaite
2015-07-12  2:00 ` [Qemu-devel] [PATCH 3/8] disas: m68k: " Peter Crosthwaite
2015-07-12  8:43   ` Laurent Vivier
2015-07-13  3:58   ` Greg Ungerer
2015-07-12  2:00 ` [Qemu-devel] [PATCH 4/8] disas: sparc: " Peter Crosthwaite
2015-07-12  2:00 ` [Qemu-devel] [PATCH 5/8] disas: lm32: " Peter Crosthwaite
2015-07-12 10:06   ` Michael Walle
2015-07-12  2:00 ` [Qemu-devel] [PATCH 6/8] disas: sh4: " Peter Crosthwaite
2015-07-14 15:47   ` Aurelien Jarno
2015-07-12  2:00 ` [Qemu-devel] [PATCH 7/8] disas: mips: " Peter Crosthwaite
2015-07-13 16:00   ` Leon Alrae
2015-07-12  2:00 ` [Qemu-devel] [PATCH 8/8] disas: alpha: " Peter Crosthwaite
2015-08-16  2:40   ` Peter Crosthwaite
2015-07-12 12:18 ` [Qemu-devel] [PATCH 0/8] Disas QOMification, round 2 Andreas Färber
2015-08-16  2:38   ` Peter Crosthwaite
2015-08-23 19:22     ` Peter Crosthwaite
2015-08-27 22:47   ` Andreas Färber [this message]
2015-08-28  4:20     ` Richard Henderson
2015-08-28 15:46       ` Andreas Färber
2015-08-28 16:02         ` Peter Maydell
2015-08-28 16:19           ` Peter Crosthwaite
2015-08-28 16: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=55DF9368.2040606@suse.de \
    --to=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=crosthwaite.peter@gmail.com \
    --cc=crosthwaitepeter@gmail.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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).