Linux Power Management development
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: linux-pm@vger.kernel.org
Cc: Andy Shevchenko <andriy.shevchenko@intel.com>
Subject: [PATCH v2 0/16] x86_energy_perf_policy cleanups
Date: Tue, 27 Oct 2026 15:01:54 -0400	[thread overview]
Message-ID: <20261027191550.369122-1-lenb@kernel.org> (raw)

These patches have changed since v1:

[PATCH 01/16] x86_energy_perf_policy: Rewrite Linux/Android MSR path
	This combines the old patch 1 and patch 2, which didn't
	really stand on their own.

	Andy, I took your reviewed-by off of #1
	because it wasn't on the old #2.

[PATCH 03/16] x86_energy_perf_policy: Harden with strtol()
	Updated to address human and AI comments.

[PATCH 07/16] x86_energy_perf_policy: Bound package iteration
[PATCH 08/16] x86_energy_perf_policy: Cleanup: Define
	Andy, These had RB, but resending b/c AI review asked for some tweaks.

[PATCH 09/16] x86_energy_perf_policy: Cleanup: Define BCLK_MHZ
	Updated per Andy comments.

[PATCH 13/16] <I combined the previous trivial #14 & #15 Constify patches>

[PATCH 15/16] x86_energy_perf_policy: Simplify write_sysfs() return
	Re-written due to review comments

             reply	other threads:[~2026-10-27 19:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-27 19:01 Len Brown [this message]
2026-10-27 19:01 ` [PATCH 01/16] x86_energy_perf_policy: Rewrite Linux/Android MSR path discovery Len Brown
2026-10-27 19:01   ` [PATCH 03/16] x86_energy_perf_policy: Harden with strtol() Len Brown
2026-10-27 19:01   ` [PATCH 07/16] x86_energy_perf_policy: Bound package iteration Len Brown
2026-10-27 19:01   ` [PATCH 08/16] x86_energy_perf_policy: Cleanup: Define HWP_WINDOW_MAX_USEC Len Brown
2026-10-27 19:01   ` [PATCH 09/16] x86_energy_perf_policy: Cleanup: Define BCLK_MHZ Len Brown
2026-10-27 19:02   ` [PATCH 15/16] x86_energy_perf_policy: Simplify write_sysfs() return type 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=20261027191550.369122-1-lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=andriy.shevchenko@intel.com \
    --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