From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 220117] cpufreq performance governor doesn't correctly apply in combination with isolcpus
Date: Sat, 28 Feb 2026 12:06:45 +0000 [thread overview]
Message-ID: <bug-220117-137361-BMJCHGLFJP@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220117-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220117
Rolf Leggewie (bugzilla.kernel.org@21.leggewie.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bugzilla.kernel.org@21.legg
| |ewie.org
--- Comment #2 from Rolf Leggewie (bugzilla.kernel.org@21.leggewie.org) ---
so, this is not a bug and can be closed?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2026-02-28 12:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 12:47 [Bug 220117] New: cpufreq performance governor doesn't correctly apply in combination with isolcpus bugzilla-daemon
2025-05-14 20:44 ` [Bug 220117] " bugzilla-daemon
2026-02-28 12:06 ` bugzilla-daemon [this message]
2026-02-28 16:06 ` bugzilla-daemon
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=bug-220117-137361-BMJCHGLFJP@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-pm@vger.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