From: Len Brown <lenb@kernel.org>
To: linux-pm@vger.kernel.org
Subject: [PATCH 0/9] turbostat-2026.09.28: fixes for Linux-7.3-rc7
Date: Mon, 12 Oct 2026 14:32:25 -0400 [thread overview]
Message-ID: <20261012183457.92243-1-lenb@kernel.org> (raw)
Please let me know if you see any troubles with these fixes.
thanks,
-Len
[PATCH 1/9] tools/power turbostat: Read complete CPU lists
[PATCH 2/9] tools/power turbostat: Warn, but don't Err on out-dated
[PATCH 3/9] tools/power turbostat: add NULL check after calloc()
[PATCH 4/9] tools/power turbostat: Sanity check GFX%rc6 and SAM%mc6
[PATCH 5/9] tools/power turbostat: Fix fd_perf leak on reset
[PATCH 6/9] tools/power turbostat: Fix CWF PMT off-by-one
[PATCH 7/9] tools/power turbostat: Fix PMT error path fd handling
[PATCH 8/9] tools/power turbostat: Fix add_counter issue if > 24
[PATCH 9/9] turbostat 2026.09.28
next reply other threads:[~2026-10-12 18:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 18:32 Len Brown [this message]
2026-10-12 18:32 ` [PATCH 1/9] tools/power turbostat: Read complete CPU lists Len Brown
2026-10-12 18:32 ` [PATCH 2/9] tools/power turbostat: Warn, but don't Err on out-dated perf systems Len Brown
2026-10-12 18:32 ` [PATCH 3/9] tools/power turbostat: add NULL check after calloc() Len Brown
2026-10-12 18:32 ` [PATCH 4/9] tools/power turbostat: Sanity check GFX%rc6 and SAM%mc6 percentages Len Brown
2026-10-12 18:32 ` [PATCH 5/9] tools/power turbostat: Fix fd_perf leak on reset Len Brown
2026-10-12 18:32 ` [PATCH 6/9] tools/power turbostat: Fix CWF PMT off-by-one Len Brown
2026-10-12 18:32 ` [PATCH 7/9] tools/power turbostat: Fix PMT error path fd handling Len Brown
2026-10-12 18:32 ` [PATCH 8/9] tools/power turbostat: Fix add_counter issue if > 24 counters Len Brown
2026-10-12 18:32 ` [PATCH 9/9] turbostat 2026.09.28 Len Brown
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=20261012183457.92243-1-lenb@kernel.org \
--to=lenb@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