From: "Luck, Tony" <tony.luck@intel.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"patches@lists.linux.dev" <patches@lists.linux.dev>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: RE: [PATCH v3 52/74] x86/cpu/vfm: Update drivers/pci/pci-mid.c
Date: Tue, 16 Apr 2024 21:51:43 +0000 [thread overview]
Message-ID: <SJ1PR11MB608361540C2BE3D9A68FB7C2FC082@SJ1PR11MB6083.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20240416213813.GA171111@bhelgaas>
> > New CPU #defines encode vendor and family as well as model.
> >
> > Signed-off-by: Tony Luck <tony.luck@intel.com>
>
> Acked-by: Bjorn Helgaas <bhelgaas@google.com>
Thanks. You win the medal for the fastest turnaround!
> Possibly consider updating subject line with a hint about what
> "update" refers to, since every commit is an update. I guess "vfm" is
> some kind of a hint, but I don't know what it means. I suppose it is
> for "vendor, family, model".
Yes. vfm is indeed vendor-family-model. Agreed the commit comment
is lacking details without the context of the cover letter and the other
patches in this series.
-Tony
next prev parent reply other threads:[~2024-04-16 21:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240416211941.9369-1-tony.luck@intel.com>
2024-04-16 21:22 ` [PATCH v3 52/74] x86/cpu/vfm: Update drivers/pci/pci-mid.c Tony Luck
2024-04-16 21:38 ` Bjorn Helgaas
2024-04-16 21:51 ` Luck, Tony [this message]
2024-04-17 8:47 ` Andy Shevchenko
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=SJ1PR11MB608361540C2BE3D9A68FB7C2FC082@SJ1PR11MB6083.namprd11.prod.outlook.com \
--to=tony.luck@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=patches@lists.linux.dev \
/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).