From: Shuah Khan <skhan@linuxfoundation.org>
To: shuah@kernel.org, trenn@suse.com, jwyatt@redhat.com, jkacur@redhat.com
Cc: Shuah Khan <skhan@linuxfoundation.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] cpupower-monitor fix error legs and remove hard-codes
Date: Wed, 5 Mar 2025 15:53:38 -0700 [thread overview]
Message-ID: <20250305225342.19447-1-skhan@linuxfoundation.org> (raw)
Two patch series fixes cpupower-monitor error legs to free cpu topology
and replaces hard-coded topology depth values with defines.
Shuah Khan (2):
pm: cpupower: Fix cmd_monitor() error legs to free cpu_topology
pm: cpupower: remove hard-coded topology depth values
.../utils/idle_monitor/cpupower-monitor.c | 42 ++++++++++++++-----
1 file changed, 31 insertions(+), 11 deletions(-)
--
2.45.2
next reply other threads:[~2025-03-05 22:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 22:53 Shuah Khan [this message]
2025-03-05 22:53 ` [PATCH 1/2] pm: cpupower: Fix cmd_monitor() error legs to free cpu_topology Shuah Khan
2025-03-05 22:53 ` [PATCH 2/2] pm: cpupower: remove hard-coded topology depth values Shuah Khan
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=20250305225342.19447-1-skhan@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=jkacur@redhat.com \
--cc=jwyatt@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=trenn@suse.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