mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Borislav Petkov" <bp@alien8.de>,
	"He Chen" <he.chen@linux.intel.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	x86@kernel.org, "Radim Krčmář" <rkrcmar@redhat.com>,
	"Ingo Molnar" <mingo@redhat.com>,
	"H . Peter Anvin" <hpa@zytor.com>,
	"Luwei Kang" <luwei.kang@intel.com>,
	"Piotr Luc" <Piotr.Luc@intel.com>
Subject: Re: [PATCH v3] x86/cpuid: expose AVX512_4VNNIW and AVX512_4FMAPS features to kvm guest
Date: Mon, 7 Nov 2016 17:52:50 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1611071751130.3709@nanos> (raw)
In-Reply-To: <39d57b21-671d-8c25-8d25-ba2cfd0dc4f9@redhat.com>

On Fri, 4 Nov 2016, Paolo Bonzini wrote:
> On 04/11/2016 16:06, Borislav Petkov wrote:
> > > With no usage?  Sounds like a good use of Acked-by. :)
> > I don't understand what do you mean here?
> 
> I mean that the changes to scattered.c are small, so it makes no sense
> to split them.  With an Acked-by I could simply take the patch into my tree.

Nope. We have other changes in that area coming up, so I rather take the
cpuid bits into tip and provide you a branch with that commit to pull from.

Thanks,

	tglx

  parent reply	other threads:[~2016-11-07 16:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-04  7:07 He Chen
2016-11-04 10:52 ` Borislav Petkov
2016-11-04 14:53   ` Paolo Bonzini
2016-11-04 15:06     ` Borislav Petkov
2016-11-04 15:13       ` Paolo Bonzini
2016-11-04 15:57         ` Borislav Petkov
2016-11-04 15:58           ` Paolo Bonzini
2016-11-07 16:52         ` Thomas Gleixner [this message]
2016-11-07  2:10   ` He Chen
2016-11-07  9:05     ` Borislav Petkov
2016-11-07 16:47       ` Thomas Gleixner
2016-11-07 17:07         ` Borislav Petkov

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=alpine.DEB.2.20.1611071751130.3709@nanos \
    --to=tglx@linutronix.de \
    --cc=Piotr.Luc@intel.com \
    --cc=bp@alien8.de \
    --cc=he.chen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luwei.kang@intel.com \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=x86@kernel.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
all inboxes | Powered by JetHome®