From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>, Richard Henderson <rth@twiddle.net>
Subject: [Qemu-devel] [PATCH v2 0/2] target-i386: MMReg struct cleanup
Date: Wed, 2 Dec 2015 13:51:52 -0200 [thread overview]
Message-ID: <1449071514-22867-1-git-send-email-ehabkost@redhat.com> (raw)
Changes v1 -> v2:
* Other patches from v1 are already in x86-next branch
* MMREG_UNION argument is now the number of bits
* Removed [RFC] tag
Eduardo Habkost (2):
target-i386: Define MMREG_UNION macro
target-i386: Add suffixes to MMReg struct fields
target-i386/cpu.h | 73 ++++++++++++++++++++++++++-----------------------------
1 file changed, 34 insertions(+), 39 deletions(-)
--
2.1.0
next reply other threads:[~2015-12-02 15:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 15:51 Eduardo Habkost [this message]
2015-12-02 15:51 ` [Qemu-devel] [PATCH v2 1/2] target-i386: Define MMREG_UNION macro Eduardo Habkost
2015-12-02 15:51 ` [Qemu-devel] [PATCH v2 2/2] target-i386: Add suffixes to MMReg struct fields Eduardo Habkost
2015-12-02 16:45 ` [Qemu-devel] [PATCH v2 0/2] target-i386: MMReg struct cleanup Richard Henderson
2015-12-03 18:20 ` Eduardo Habkost
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=1449071514-22867-1-git-send-email-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--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).