Re: [PATCH 01/74] x86/cpu/vfm: Add/initialize x86_vfm field to struct cpuinfo_x86

From: "Luck, Tony" <tony.luck@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Sean Christopherson <seanjc@google.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 01/74] x86/cpu/vfm: Add/initialize x86_vfm field to struct cpuinfo_x86
Date: Thu, 18 Apr 2024 01:47:34 +0000	[thread overview]
Message-ID: <B1D0D5D6-2338-4142-AF28-887FD99F3CE5@intel.com> (raw)
In-Reply-To: <20240417194207.GFZiAmD4I8sdqhV1RO@fat_crate.local>

> On Apr 17, 2024, at 12:43, Borislav Petkov <bp@alien8.de> wrote:
> 
> On Wed, Apr 17, 2024 at 12:02:21PM -0700, Sean Christopherson wrote:
>> There are two KVM changes hiding in there, but they're obviously quite trivial
>> and can to through tip, I don't expect any conflicts.
> 
> Yeah, the plan is to queue it all through tip as that would be a lot
> less conflicts and cross-tree issues so you acking them is what I was
> hoping to get.
> 
> So thanks. :-)

There’s general (justified) grumbling about
my auto-generated Subject lines. So I’ll make
a pass through the whole series to make the
initial tag match each subsystem convention. 
Also make it generally more useful. I.e. like this
for most of the arch/x86 patches:

Subject: x86/cpu: Use new Intel CPU model #defines

Perhaps all the pieces with Reviewed or Acked
tags can go into tip tree next week?

-Tony