From: Thomas Gleixner <tglx@kernel.org>
To: "Ionut Nechita (Sunlight Linux)" <sunlightlinux@gmail.com>
Cc: anna-maria@linutronix.de, frederic@kernel.org,
ionut_n2001@yahoo.com, linux-kernel@vger.kernel.org,
mingo@kernel.org, sunlightlinux@gmail.com
Subject: Re: [PATCH 1/1] tick/nohz: Add fast-path tick stopping for idle isolated cores
Date: Mon, 26 Jan 2026 22:32:16 +0100 [thread overview]
Message-ID: <87343scb6n.ffs@tglx> (raw)
In-Reply-To: <20260126193108.6501-2-sunlightlinux@gmail.com>
On Mon, Jan 26 2026 at 21:31, Ionut Nechita wrote:
> Should I prepare a v2 based on your suggestion, or would you prefer to
> submit this as a separate patch?
Go wild. I have enough things on my plate already :)
next prev parent reply other threads:[~2026-01-26 21:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 15:36 [PATCH 0/1] tick/nohz: Optimize tick stopping for isolated cores Ionut Nechita (Sunlight Linux)
2026-01-06 15:36 ` [PATCH 1/1] tick/nohz: Add fast-path tick stopping for idle " Ionut Nechita (Sunlight Linux)
2026-01-13 10:02 ` Thomas Gleixner
2026-01-26 19:31 ` Ionut Nechita (Sunlight Linux)
2026-01-26 21:32 ` Thomas Gleixner [this message]
2026-01-27 13:40 ` Frederic Weisbecker
2026-01-28 7:26 ` Ionut Nechita (Sunlight Linux)
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=87343scb6n.ffs@tglx \
--to=tglx@kernel.org \
--cc=anna-maria@linutronix.de \
--cc=frederic@kernel.org \
--cc=ionut_n2001@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=sunlightlinux@gmail.com \
/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