From: Paolo Bonzini <pbonzini@redhat.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/3] remove dead code from target-i386/exec.h
Date: Fri, 15 Jan 2010 16:12:35 +0100 [thread overview]
Message-ID: <4B5085E3.6040605@redhat.com> (raw)
In-Reply-To: <AD51D4DF-98A3-4F5B-A2D5-EB1B3DDB3E1D@adacore.com>
On 01/15/2010 03:54 PM, Tristan Gingold wrote:
>
> On Jan 15, 2010, at 8:56 AM, Paolo Bonzini wrote:
>
>> These are unused since edea5f0 (no need to define global registers in
>> cpu-exec.c, 2008-05-10).
>
> Why not removing env_to_regs and regs_to_env ?
That's 2/3 indeed. :-)
Paolo
next prev parent reply other threads:[~2010-01-15 15:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 7:56 [Qemu-devel] [PATCH 0/3] cleanup cpu_exec 1/n Paolo Bonzini
2010-01-15 7:56 ` [Qemu-devel] [PATCH 1/3] remove dead code from target-i386/exec.h Paolo Bonzini
2010-01-15 14:54 ` Tristan Gingold
2010-01-15 15:12 ` Paolo Bonzini [this message]
2010-01-19 22:39 ` Anthony Liguori
2010-01-15 7:56 ` [Qemu-devel] [PATCH 2/3] kill regs_to_env and env_to_regs Paolo Bonzini
2010-01-15 7:56 ` [Qemu-devel] [PATCH 3/3] fix wrong indentation Paolo Bonzini
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=4B5085E3.6040605@redhat.com \
--to=pbonzini@redhat.com \
--cc=gingold@adacore.com \
--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).