From: "Huang, Kai" <kai.huang@intel.com>
To: <linux-kernel@vger.kernel.org>, <linux-tip-commits@vger.kernel.org>
Cc: Dave Hansen <dave.hansen@linux.intel.com>, <x86@kernel.org>
Subject: Re: [tip: x86/cpu] x86/cpu: Move AMD erratum 1386 table over to 'x86_cpu_id'
Date: Wed, 18 Dec 2024 22:04:09 +0800 [thread overview]
Message-ID: <c8641989-fa0c-4dde-a8e6-8bcd90bd83b9@intel.com> (raw)
In-Reply-To: <173448361317.7135.17921207841466608654.tip-bot2@tip-bot2>
On 18/12/2024 9:00 am, tip-bot2 for Dave Hansen wrote:
> The following commit has been merged into the x86/cpu branch of tip:
>
> Commit-ID: 064e8b122b65525115c4c2f181bd2ea33265e0c6
> Gitweb: https://git.kernel.org/tip/064e8b122b65525115c4c2f181bd2ea33265e0c6
> Author: Dave Hansen <dave.hansen@linux.intel.com>
> AuthorDate: Fri, 13 Dec 2024 10:51:32 -08:00
> Committer: Dave Hansen <dave.hansen@linux.intel.com>
> CommitterDate: Tue, 17 Dec 2024 16:19:57 -08:00
>
> x86/cpu: Move AMD erratum 1386 table over to 'x86_cpu_id'
>
> The AMD erratum 1386 detection code uses and old style 'x86_cpu_desc'
> table. Replace it with 'x86_cpu_id' so the old style can be removed.
>
> I did not create a new helper macro here. The new table is certainly
> more noisy than the old and it can be improved on. But I was hesitant
> to create a new macro just for a single site that is only two ugly
> lines in the end.
>
> Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
> Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
Hi Dave,
Just let you know there's a duplicated SoB here.
next prev parent reply other threads:[~2024-12-18 14:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 1:00 [tip: x86/cpu] x86/cpu: Move AMD erratum 1386 table over to 'x86_cpu_id' tip-bot2 for Dave Hansen
2024-12-18 14:04 ` Huang, Kai [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-18 14:22 tip-bot2 for Dave Hansen
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=c8641989-fa0c-4dde-a8e6-8bcd90bd83b9@intel.com \
--to=kai.huang@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--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