From: Eduardo Habkost <ehabkost@redhat.com>
To: Tao Xu <tao3.xu@intel.com>
Cc: pbonzini@redhat.com, rth@twiddle.net, philmd@redhat.com,
qemu-devel@nongnu.org, sgarzare@redhat.com
Subject: Re: [PATCH v5 0/2] target/i386: cpu.h macros clean up
Date: Thu, 26 Sep 2019 17:17:22 -0300 [thread overview]
Message-ID: <20190926201722.GS8144@habkost.net> (raw)
In-Reply-To: <20190926021055.6970-1-tao3.xu@intel.com>
On Thu, Sep 26, 2019 at 10:10:53AM +0800, Tao Xu wrote:
> Add some comments, clean up comments over 80 chars per line. There
> is an extra line in comment of CPUID_8000_0008_EBX_WBNOINVD, remove
> the extra enter and spaces.
>
> Drop the duplicated definition of cpuid AVX512_VBMI macro and rename it
> as CPUID_7_0_ECX_AVX512_VBMI. Rename CPUID_7_0_ECX_VBMI2
> as CPUID_7_0_ECX_AVX512_VBMI2.
>
Queued, thanks!
> Changelog:
> v5:
> - correct commit messages. (Suggested by Stefano Garzarella)
> v4:
> - rename CPUID_7_0_ECX_VBMI2 as CPUID_7_0_ECX_AVX512_VBMI2.
> (Suggested by Stefano Garzarella)
> v3:
> - split the patch into 2 patches. (Suggested by Stefano Garzarella
> and Eduardo Habkost)
> v2:
> - correct the comments over 80 chars per line. (Suggested by
> Philippe Mathieu-Daudé)
>
> Tao Xu (2):
> target/i386: clean up comments over 80 chars per line
> target/i386: drop the duplicated definition of cpuid AVX512_VBMI macro
>
> target/i386/cpu.c | 8 +-
> target/i386/cpu.h | 163 +++++++++++++++++++++++-------------
> target/i386/hvf/x86_cpuid.c | 2 +-
> 3 files changed, 111 insertions(+), 62 deletions(-)
>
> --
> 2.20.1
>
--
Eduardo
prev parent reply other threads:[~2019-09-26 20:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 2:10 [PATCH v5 0/2] target/i386: cpu.h macros clean up Tao Xu
2019-09-26 2:10 ` [PATCH v5 1/2] target/i386: clean up comments over 80 chars per line Tao Xu
2019-09-26 2:10 ` [PATCH v5 2/2] target/i386: drop the duplicated definition of cpuid AVX512_VBMI macro Tao Xu
2019-09-26 4:40 ` Philippe Mathieu-Daudé
2019-09-26 20:17 ` Eduardo Habkost [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=20190926201722.GS8144@habkost.net \
--to=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=sgarzare@redhat.com \
--cc=tao3.xu@intel.com \
/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).