qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	John Rigby <john.rigby@linaro.org>,
	qemu-devel <qemu-devel@nongnu.org>,
	Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
	Alexander Graf <agraf@suse.de>,
	"Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Subject: Re: [Qemu-devel] [PATCH v2 01/12] ARM: Export cpu_env
Date: Wed, 01 May 2013 10:29:40 +0100	[thread overview]
Message-ID: <5180E084.4090300@twiddle.net> (raw)
In-Reply-To: <517FB25F.7070501@suse.de>

On 2013-04-30 13:00, Andreas Färber wrote:
> Not sure if you understood my point? Exposing cpu_env from target-arm
> would seem to torpedo our efforts to link target-arm and, e.g.,
> target-microblaze together, since they all have cpu_env. I don't really
> care if it's qom/cpu.c or tcg/shared.c or renaming to arm_cpu_env. :)

cpu_env is still static within target-microblaze/translate.c;
there is no conflict ... yet.


r~

  parent reply	other threads:[~2013-05-01  9:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-30  6:36 [Qemu-devel] [PATCH v2 01/12] ARM: Export cpu_env John Rigby
2013-04-30 11:42 ` Andreas Färber
2013-04-30 11:54   ` Alexander Graf
2013-04-30 12:00     ` Andreas Färber
2013-04-30 12:33       ` Alexander Graf
2013-05-01  9:29       ` Richard Henderson [this message]
2013-06-28 14:20       ` Peter Maydell
2013-06-28 14:25         ` Alexander Graf
2013-06-28 14:28         ` Andreas Färber
2013-06-28 14:35           ` Peter Maydell
2013-06-28 14:42             ` Andreas Färber

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=5180E084.4090300@twiddle.net \
    --to=rth@twiddle.net \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=edgar.iglesias@gmail.com \
    --cc=john.rigby@linaro.org \
    --cc=peter.crosthwaite@xilinx.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).