From: "Ahmed S. Darwish" <darwi@linutronix.de>
To: linux-kernel@vger.kernel.org
Cc: linux-tip-commits@vger.kernel.org,
Thomas Gleixner <tglx@kernel.org>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Borislav Petkov <bp@alien8.de>, Ingo Molnar <mingo@kernel.org>,
Sean Christopherson <seanjc@google.com>,
x86@kernel.org
Subject: Re: [tip: x86/cpu] x86/cpu: Introduce a centralized CPUID data model
Date: Wed, 13 May 2026 18:38:31 +0200 [thread overview]
Message-ID: <agSpBwofZYaReVof@lx-t490> (raw)
In-Reply-To: <177868946446.188840.9523007426604501330.tip-bot2@tip-bot2>
On Wed, 13 May 2026, tip-bot2 for Ahmed S. Darwish wrote:
>
> The following commit has been merged into the x86/cpu branch of tip:
>
> Commit-ID: 3aa8f9fce8602d722948df641c7ca2828ee0a2f5
> Gitweb: https://git.kernel.org/tip/3aa8f9fce8602d722948df641c7ca2828ee0a2f5
> Author: Ahmed S. Darwish <darwi@linutronix.de>
> AuthorDate: Fri, 27 Mar 2026 03:15:22 +01:00
> Committer: Borislav Petkov (AMD) <bp@alien8.de>
> CommitterDate: Mon, 11 May 2026 13:09:30 +02:00
>
Thanks!
Fyi, recent tip-bot emails are missing "In-Reply-To:" headers, so they no
longer appear in the original patch thread.
It used to be nice to see which patches were merged directly from lore;
e.g. the AVS patch here:
https://lkml.kernel.org/20260327021645.555257-1-darwi@linutronix.de
All the other bot emails are thread out of bound.
next prev parent reply other threads:[~2026-05-13 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 16:24 [tip: x86/cpu] x86/cpu: Introduce a centralized CPUID data model tip-bot2 for Ahmed S. Darwish
2026-05-13 16:38 ` Ahmed S. Darwish [this message]
2026-05-13 16:54 ` Borislav Petkov
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=agSpBwofZYaReVof@lx-t490 \
--to=darwi@linutronix.de \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=seanjc@google.com \
--cc=tglx@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