From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Laurent Vivier <laurent@vivier.eu>,
qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH 2/2] m68k: Build the opcode table only once to avoid multithreading issues
Date: Wed, 3 Feb 2016 11:17:39 +0100 [thread overview]
Message-ID: <56B1D3C3.1070701@physik.fu-berlin.de> (raw)
In-Reply-To: <56B1D2DF.8080205@vivier.eu>
On 02/03/2016 11:13 AM, Laurent Vivier wrote:
> I don't know if the one who will commit this to the tree will want to
> update this.
Just sent an updated one, just in case :).
> BTW, Peter, perhaps it's the time to add me as m68k maintainer ?
> (so I will manage that :) )
Yes, please. I'm all for that! I'm really motivated to get m68k
support into best shape. qemu-m68k is fun to hack on!
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
prev parent reply other threads:[~2016-02-03 10:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 9:36 [Qemu-devel] m68k: More bug fixes for translation code John Paul Adrian Glaubitz
2016-02-03 9:37 ` [Qemu-devel] [PATCH 1/2] m68k: Fix opcode mask for fbcc instruction John Paul Adrian Glaubitz
2016-02-03 9:38 ` Laurent Vivier
2016-02-08 23:13 ` John Paul Adrian Glaubitz
2016-02-03 9:40 ` John Paul Adrian Glaubitz
2016-02-03 9:42 ` Laurent Vivier
2016-02-03 9:37 ` [Qemu-devel] [PATCH 2/2] m68k: Build the opcode table only once to avoid multithreading issues John Paul Adrian Glaubitz
2016-02-03 9:39 ` Laurent Vivier
2016-02-03 9:57 ` Laurent Vivier
2016-02-03 10:06 ` John Paul Adrian Glaubitz
2016-02-03 10:13 ` Laurent Vivier
2016-02-03 10:17 ` John Paul Adrian Glaubitz [this message]
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=56B1D3C3.1070701@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=laurent@vivier.eu \
--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 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.