linux-sgx.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
	linux-sgx@vger.kernel.org, Andy Lutomirski <luto@kernel.org>,
	Sean Christopherson <sean.j.christopherson@intel.com>
Subject: Re: v25-rc1
Date: Mon, 13 Jan 2020 15:04:07 +0100	[thread overview]
Message-ID: <20200113140407.GI13310@zn.tnic> (raw)
In-Reply-To: <95fc04cb-c305-2ef1-2449-ecb37796c661@redhat.com>

On Mon, Jan 13, 2020 at 03:00:49PM +0100, Paolo Bonzini wrote:
> Sorry I missed that.  What about sending me a topic branch, that will be
> merged into both tip and kvm-next?

... and I'll put all patches in it except the KVM ones:

  KVM: VMX: Drop initialization of IA32_FEAT_CTL MSR
  KVM: VMX: Use VMX feature flag to query BIOS enabling
  KVM: VMX: Check for full VMX support when verifying CPU compatibility
  KVM: VMX: Use VMX_FEATURE_* flags to define VMCS control bits
  KVM: VMX: Allow KVM_INTEL when building for Centaur and/or Zhaoxin CPUs

which you can then take?

Makes sense to me...

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2020-01-13 14:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-13  3:59 v25-rc1 Jarkko Sakkinen
2020-01-13  8:48 ` v25-rc1 Borislav Petkov
2020-01-13 14:00   ` v25-rc1 Paolo Bonzini
2020-01-13 14:04     ` Borislav Petkov [this message]
2020-01-13 15:20       ` v25-rc1 Paolo Bonzini
2020-01-13 16:07         ` v25-rc1 Borislav Petkov
2020-01-14  9:39           ` v25-rc1 Borislav Petkov
2020-01-14 10:44             ` v25-rc1 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=20200113140407.GI13310@zn.tnic \
    --to=bp@alien8.de \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=linux-sgx@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=sean.j.christopherson@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).