From: Peter Maydell <peter.maydell@linaro.org>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>,
kvm-devel <kvm@vger.kernel.org>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Richard Henderson <rth@twiddle.net>,
"Michael S. Tsirkin" <mst@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Eric Blake <eblake@redhat.com>
Subject: Re: [Qemu-devel] [PULL 0/7] x86 queue, 2018-10-30
Date: Thu, 1 Nov 2018 17:25:57 +0000 [thread overview]
Message-ID: <CAFEAcA8SDBsigHe6t-fGqfKDCe_WuSrn+S7O4JOpXzzkeamx=g@mail.gmail.com> (raw)
In-Reply-To: <20181031140710.GG3902@habkost.net>
On 31 October 2018 at 14:07, Eduardo Habkost <ehabkost@redhat.com> wrote:
> Peter, my S-o-b line was missing on some commits, I have just pushed a new
> x86-next-pull-request tag, with exactly the same tree. Sorry for the noise.
>
> Thanks to Eric Blake for reporting the issue.
>
> The following changes since commit a2e002ff7913ce93aa0f7dbedd2123dce5f1a9cd:
>
> Merge remote-tracking branch 'remotes/vivier2/tags/qemu-trivial-for-3.1-pull-request' into staging (2018-10-30 15:49:55 +0000)
>
> are available in the Git repository at:
>
> git://github.com/ehabkost/qemu.git tags/x86-next-pull-request
>
> for you to fetch changes up to 09b9ee643f90ef95e30e594df2a3c83ccaf75b1f:
>
> i386: Add PKU on Skylake-Server CPU model (2018-10-30 21:14:43 -0300)
>
> ----------------------------------------------------------------
> x86 queue, 2018-10-30
>
> * MSR-based feature support for
> MSR_IA32_ARCH_CAPABILITIES bits (Robert Hoo)
> * Cascadelake-Server CPU model (Tao Xu)
> * Add PKU on Skylake-Server CPU model (Tao Xu)
> * Correct cpu_x86_cpuid(0xd) (Sebastian Andrzej Siewior)
> * Remove dead code (Peter Maydell)
>
> ----------------------------------------------------------------
Applied, thanks.
-- PMM
prev parent reply other threads:[~2018-11-01 17:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 0:45 [Qemu-devel] [PULL 0/7] x86 queue, 2018-10-30 Eduardo Habkost
2018-10-31 0:45 ` [Qemu-devel] [PULL 1/7] i386: correct cpu_x86_cpuid(0xd) Eduardo Habkost
2018-10-31 0:45 ` [Qemu-devel] [PULL 2/7] target/i386: Remove #ifdeffed-out icebp debugging hack Eduardo Habkost
2018-10-31 0:45 ` [Qemu-devel] [PULL 3/7] kvm: Add support to KVM_GET_MSR_FEATURE_INDEX_LIST and KVM_GET_MSRS system ioctl Eduardo Habkost
2018-10-31 0:45 ` [Qemu-devel] [PULL 4/7] x86: Data structure changes to support MSR based features Eduardo Habkost
2018-10-31 13:24 ` Eric Blake
2018-10-31 14:08 ` Eduardo Habkost
2018-10-31 0:45 ` [Qemu-devel] [PULL 5/7] x86: define a new MSR based feature word -- FEATURE_WORDS_ARCH_CAPABILITIES Eduardo Habkost
2018-10-31 0:45 ` [Qemu-devel] [PULL 6/7] i386: Add new model of Cascadelake-Server Eduardo Habkost
2018-10-31 0:45 ` [Qemu-devel] [PULL 7/7] i386: Add PKU on Skylake-Server CPU model Eduardo Habkost
2018-10-31 14:07 ` [Qemu-devel] [PULL 0/7] x86 queue, 2018-10-30 Eduardo Habkost
2018-11-01 17:25 ` Peter Maydell [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='CAFEAcA8SDBsigHe6t-fGqfKDCe_WuSrn+S7O4JOpXzzkeamx=g@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=eblake@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=mtosatti@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).