From: Thomas Gleixner <tglx@linutronix.de>
To: "Petr Vaněk" <arkamar@atlas.cz>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [tip: x86/urgent] x86/acpi: Don't limit CPUs to 1 for Xen PV guests due to disabled ACPI
Date: Tue, 08 Apr 2025 10:50:18 +0200 [thread overview]
Message-ID: <87o6x7ujed.ffs@tglx> (raw)
In-Reply-To: <20254861939-Z_S_-ybv1at7EdUO-arkamar@atlas.cz>
On Tue, Apr 08 2025 at 08:19, Petr Vaněk wrote:
> On Mon, Apr 07, 2025 at 02:44:29PM -0000, tip-bot2 for Petr Vaněk wrote:
>> The following commit has been merged into the x86/urgent branch of tip:
>>
>> Commit-ID: 8b37357a78d7fa13d88ea822b35b40137da1c85e
>> Gitweb: https://git.kernel.org/tip/8b37357a78d7fa13d88ea822b35b40137da1c85e
>> Author: Petr Vaněk <arkamar@atlas.cz>
>> AuthorDate: Mon, 07 Apr 2025 15:24:27 +02:00
>> Committer: Thomas Gleixner <tglx@linutronix.de>
>> CommitterDate: Mon, 07 Apr 2025 16:35:21 +02:00
>>
>> x86/acpi: Don't limit CPUs to 1 for Xen PV guests due to disabled ACPI
>
> Thank you for accepting the patch.
>
> Out of curiosity, why did you remove the Cc: stable@vger.kernel.org
> trailer? I thought it should be backported as it is a regression.
Accidentally. Ooops.
The stable bot should pick it up nevertheless because of the Fixes tag
once it hit Linus tree. If it does not after a week or so, please send a
backport request to the stable folks.
Thanks,
tglx
prev parent reply other threads:[~2025-04-08 8:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-05 18:16 [PATCH 0/1] x86/topology: Fix regression limiting Xen PV DomU CPUs to 1 Petr Vaněk
2025-04-05 18:16 ` [PATCH 1/1] x86/cpu/topology: Don't limit CPUs to 1 for Xen PV guests due to disabled APIC Petr Vaněk
2025-04-06 10:08 ` Thomas Gleixner
2025-04-07 13:24 ` Petr Vaněk
2025-04-07 13:24 ` [PATCH v2 1/1] x86/acpi: Don't limit CPUs to 1 for Xen PV guests due to disabled ACPI Petr Vaněk
2025-04-07 14:44 ` [tip: x86/urgent] " tip-bot2 for Petr Vaněk
2025-04-08 6:19 ` Petr Vaněk
2025-04-08 8:50 ` Thomas Gleixner [this message]
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=87o6x7ujed.ffs@tglx \
--to=tglx@linutronix.de \
--cc=arkamar@atlas.cz \
--cc=linux-kernel@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