From: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
To: rafael@kernel.org
Cc: linux-pm@vger.kernel.org, shuah@kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
manaf.pallikunhi@oss.qualcomm.com,
Lukasz Luba <lukasz.luba@arm.com>
Subject: Re: [PATCH 0/2] powercap: Introduce generic hierarchy helpers and selftests
Date: Wed, 23 Sep 2026 15:47:00 +0200 [thread overview]
Message-ID: <f1019e70-f3f7-429d-90e5-c74234dc5cde@oss.qualcomm.com> (raw)
In-Reply-To: <71932f61-5721-4363-b163-427432fedab4@oss.qualcomm.com>
Hi,
On 9/15/26 12:54, Daniel Lezcano wrote:
[ ... ]
>> I can see some potential improvements there.
> This patch is a blocker for more changes: DTPM, powercap cooling device
> and SPEL drivers from Manaf.
>
> It has been tested and there is a selftest with. Is it possible to
> consider these two patches for merging.
>
> Given it is not a fast path, improvements can be proposed later.
Given that there has been no feedback so far, would it be possible to
consider merging these two patches? They are currently blocking further
work.
There is also a selftest covering this functionality, so future changes
can be made with regression testing in place.
next prev parent reply other threads:[~2026-09-23 13:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 11:01 Daniel Lezcano
2026-08-06 11:01 ` [PATCH 1/2] powercap: Add generic zone hierarchy creation helpers Daniel Lezcano
2026-08-06 11:01 ` [PATCH 2/2] selftests/powercap: Add powercap hierarchy creation API tests Daniel Lezcano
2026-09-07 10:03 ` [PATCH 0/2] powercap: Introduce generic hierarchy helpers and selftests Daniel Lezcano
2026-09-07 10:46 ` Lukasz Luba
2026-09-15 10:54 ` Daniel Lezcano
2026-09-23 13:47 ` Daniel Lezcano [this message]
2026-09-23 13:58 ` Rafael J. Wysocki (Intel)
2026-09-23 14:06 ` Daniel Lezcano
2026-09-11 15:44 ` Manaf Meethalavalappu Pallikunhi
2026-09-11 15:48 ` Daniel Lezcano
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=f1019e70-f3f7-429d-90e5-c74234dc5cde@oss.qualcomm.com \
--to=daniel.lezcano@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=manaf.pallikunhi@oss.qualcomm.com \
--cc=rafael@kernel.org \
--cc=shuah@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
all inboxes | Powered by JetHome®