From: Peter Zijlstra <peterz@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: linux-tip-commits@vger.kernel.org,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
Ingo Molnar <mingo@kernel.org>,
stable@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
x86@kernel.org
Subject: Re: [tip: sched/core] x86/tsc: Always save/restore TSC sched_clock() on suspend/resume
Date: Fri, 21 Feb 2025 20:17:13 +0100 [thread overview]
Message-ID: <20250221191713.GE7373@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <174014866289.10177.10974658062988825500.tip-bot2@tip-bot2>
On Fri, Feb 21, 2025 at 02:37:42PM -0000, tip-bot2 for Guilherme G. Piccoli wrote:
> The following commit has been merged into the sched/core branch of tip:
>
> Commit-ID: d90c9de9de2f1712df56de6e4f7d6982d358cabe
> Gitweb: https://git.kernel.org/tip/d90c9de9de2f1712df56de6e4f7d6982d358cabe
> Author: Guilherme G. Piccoli <gpiccoli@igalia.com>
> AuthorDate: Sat, 15 Feb 2025 17:58:16 -03:00
> Committer: Ingo Molnar <mingo@kernel.org>
> CommitterDate: Fri, 21 Feb 2025 15:27:38 +01:00
>
> x86/tsc: Always save/restore TSC sched_clock() on suspend/resume
Should this not go into x86/core or somesuch?
prev parent reply other threads:[~2025-02-21 19:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-15 20:58 [PATCH] x86/tsc: Always save/restore TSC sched_clock on suspend/resume Guilherme G. Piccoli
2025-02-17 18:49 ` Guilherme G. Piccoli
2025-02-21 14:37 ` [tip: sched/core] x86/tsc: Always save/restore TSC sched_clock() " tip-bot2 for Guilherme G. Piccoli
2025-02-21 19:17 ` Peter Zijlstra [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=20250221191713.GE7373@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=gpiccoli@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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