From: "Ahmed S. Darwish" <darwi@linutronix.de>
To: Maciej Wieczor-Retman <m.wieczorretman@pm.me>
Cc: mingo@redhat.com, dave.hansen@linux.intel.com, bp@alien8.de,
hpa@zytor.com, tglx@kernel.org, sohil.mehta@intel.com,
andrew.cooper3@citrix.com, linux-kernel@vger.kernel.org,
x86@kernel.org, john.ogness@linutronix.de, ludloff@gmail.com,
maciej.wieczor-retman@intel.com, x86-cpuid@lists.linux.dev
Subject: Re: [PATCH v1 2/2] x86/cpuid: Fix a few more typos
Date: Wed, 3 Jun 2026 14:38:09 +0200 [thread overview]
Message-ID: <aiAgMebb3JpT7g84@lx-t490> (raw)
In-Reply-To: <237c2be340be63e67263c76f065b3aaa9fb1fbbe.1780487165.git.m.wieczorretman@pm.me>
Hi Maciej,
On Wed, 03 Jun 2026, Maciej Wieczor-Retman wrote:
>
> From: Ahmed S. Darwish <darwi@linutronix.de>
>
Yes, this is the the CI output from x86-cpuid-db,¹ but I did not author
this patch. Please keep the From lines as yours, since x86-cpuid-db
already has a git history with all the authorship details.
Also, could we please make the logs of the patches modifying these
auto-generated files consistent with previous patches? Please check:
49394b5af45c tools/x86/kcpuid: Update bitfields to x86-cpuid-db v2.4
300ba891418a tools/x86/kcpuid: Update bitfields to x86-cpuid-db v2.3
5e0c3c5e95f0 tools/x86/kcpuid: Update bitfields to x86-cpuid-db v2.2
...
So this series should IMHO be just two patches instead:
From: you
patch #1: tools/x86/kcpuid: Update bitfields to x86-cpuid-db v3.1
patch #2: x86/cpuid: <leaf_types.h>: Update bitfields to x86-cpuid-db v3.1
And in both of these two patches you summarize the release changes relevant
to the modified files and add a link to the v3.1 release Changelog:
https://gitlab.com/x86-cpuid.org/x86-cpuid-db/-/blob/v3.1/CHANGELOG.rst
I was confused actually what the first patch was doing, given the existence
of the second. With the above format, the git history of these auto
generated files will be much cleaner.
¹ https://msgid.link/ah8-uSSdb1KcLByV@lx-t490
Thanks!
Ahmed
next prev parent reply other threads:[~2026-06-03 12:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 12:02 [PATCH v1 0/2] x86/cpuid: kcpuid: Update to x86-cpuid-db v3.1 with fixes Maciej Wieczor-Retman
2026-06-03 12:02 ` [PATCH v1 1/2] x86/cpuid: Fix typos Maciej Wieczor-Retman
2026-06-03 12:02 ` [PATCH v1 2/2] x86/cpuid: Fix a few more typos Maciej Wieczor-Retman
2026-06-03 12:38 ` Ahmed S. Darwish [this message]
2026-06-03 12:43 ` Maciej Wieczor-Retman
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=aiAgMebb3JpT7g84@lx-t490 \
--to=darwi@linutronix.de \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ludloff@gmail.com \
--cc=m.wieczorretman@pm.me \
--cc=maciej.wieczor-retman@intel.com \
--cc=mingo@redhat.com \
--cc=sohil.mehta@intel.com \
--cc=tglx@kernel.org \
--cc=x86-cpuid@lists.linux.dev \
--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