From: Sean Christopherson <seanjc@google.com>
To: Tony Luck <tony.luck@intel.com>
Cc: Borislav Petkov <bp@alien8.de>,
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: Wed, 17 Apr 2024 12:02:21 -0700 [thread overview]
Message-ID: <ZiAcvRWwl9m4x2n0@google.com> (raw)
In-Reply-To: <SJ1PR11MB6083F100B4D957EC472AFF19FC082@SJ1PR11MB6083.namprd11.prod.outlook.com>
On Tue, Apr 16, 2024, Tony Luck wrote:
> > Alternatively, we can take the arch/x86 parts and once 6.10 releases,
> > the other maintainers will have them in tree and thus not need the
> > cross-tree merges.
>
> I did a bit of this. I moved all the arch/x86 patches up to immediately follow
> the three prep patches. So you can pick through parts 0004..0039 and apply
> any that look good to you (there is no ordering requirement among these).
> Bounce anything that needs extra work back to me.
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.
next prev parent reply other threads:[~2024-04-17 19:02 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 16:37 [PATCH 00/74] New Intel CPUID families Tony Luck
2024-03-28 16:37 ` [PATCH 01/74] x86/cpu/vfm: Add/initialize x86_vfm field to struct cpuinfo_x86 Tony Luck
2024-03-28 16:48 ` Borislav Petkov
2024-03-28 16:52 ` Borislav Petkov
2024-03-28 17:00 ` Luck, Tony
2024-03-28 17:12 ` Borislav Petkov
2024-03-28 18:32 ` Luck, Tony
2024-03-28 20:52 ` Luck, Tony
2024-03-29 11:40 ` Borislav Petkov
2024-03-29 16:46 ` Tony Luck
2024-03-29 17:23 ` Borislav Petkov
2024-04-01 18:18 ` Tony Luck
2024-04-07 10:54 ` Borislav Petkov
2024-04-08 16:20 ` Luck, Tony
2024-04-09 8:22 ` Borislav Petkov
2024-04-16 18:16 ` Tony Luck
2024-04-16 18:23 ` Borislav Petkov
2024-04-16 18:37 ` Luck, Tony
2024-04-16 19:58 ` Borislav Petkov
2024-04-16 21:45 ` Luck, Tony
2024-04-17 19:02 ` Sean Christopherson [this message]
2024-04-17 19:42 ` Borislav Petkov
2024-04-18 1:47 ` Luck, Tony
2024-03-28 16:56 ` Luck, Tony
2024-03-28 17:06 ` Borislav Petkov
2024-04-01 18:23 ` [PATCH v2 " Tony Luck
2024-04-09 12:46 ` Thomas Gleixner
2024-03-28 16:37 ` [PATCH 02/74] x86/cpu/vfm: Add new macros to work with (vendor/family/model) values Tony Luck
2024-04-01 18:24 ` [PATCH v2 " Tony Luck
2024-04-09 12:47 ` Thomas Gleixner
2024-03-28 16:37 ` [PATCH 03/74] x86/cpu/vfm: Update arch/x86/include/asm/intel-family.h Tony Luck
2024-04-09 12:48 ` Thomas Gleixner
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=ZiAcvRWwl9m4x2n0@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.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