From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>
Subject: [GIT PULL] CPU hotplug changes for v6.8
Date: Mon, 8 Jan 2024 11:23:02 +0100 [thread overview]
Message-ID: <ZZvNBnboWjpkQuW9@gmail.com> (raw)
Linus,
Please pull the latest smp/core git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git smp-core-2024-01-08
# HEAD: fe22944cf05ede8e6f841cfecdb7093a53a3d9b3 cpu/hotplug: Increase the number of dynamic states
CPU hotplug changes for v6.8:
- Remove unused CPU hotplug states
- Increase the number of dynamic CPU hotplug states
from 30 to 40, because existing drivers can exhaust
the allocation space
Thanks,
Ingo
------------------>
Zenghui Yu (1):
cpu/hotplug: Remove unused CPU hotplug states
xiaoming Wang (1):
cpu/hotplug: Increase the number of dynamic states
include/linux/cpuhotplug.h | 16 +---------------
1 file changed, 1 insertion(+), 15 deletions(-)
next reply other threads:[~2024-01-08 10:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 10:23 Ingo Molnar [this message]
2024-01-09 4:04 ` [GIT PULL] CPU hotplug changes for v6.8 pr-tracker-bot
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=ZZvNBnboWjpkQuW9@gmail.com \
--to=mingo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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