From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Linux PM <linux-pm@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
William Breathitt Gray <vilhelm.gray@gmail.com>,
Viktor Rosendahl <Viktor.Rosendahl@bmw.de>,
Sasha Levin <sashal@kernel.org>,
Colin Ian King <colin.king@intel.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
"Zhang, Rui" <rui.zhang@intel.com>
Subject: Re: [PATCH] tools/lib/thermal: Add a thermal library
Date: Fri, 4 Feb 2022 19:13:25 +0100 [thread overview]
Message-ID: <2297b79e-b99c-30a5-1e5c-560d5553e146@linaro.org> (raw)
In-Reply-To: <CAJZ5v0gXJ8wF2ChGU1bydPiNHB4c+SVrmrTpUwxMh7ddODFV5g@mail.gmail.com>
On 04/02/2022 18:11, Rafael J. Wysocki wrote:
> CC Rui and Srinivas
>
> On Fri, Feb 4, 2022 at 5:15 PM Daniel Lezcano <daniel.lezcano@linaro.org> wrote:
>>
>> The thermal framework implements a netlink notification mechanism to
>> be used by the userspace to have a thermal configuration discovery,
>> trip point changes or violation, cooling device changes notifications,
>> etc...
>>
>> This library provides a level of abstraction for the thermal netlink
>> notification allowing the userspace to connect to the notification
>> mechanism more easily. The library is callback oriented.
>>
>> As it is the very first iteration, the API may be subject to
>> changes. For this reason, the documentation will be provided after
>> those are stabilized.
>
> So shouldn't this be an RFC?
Yes, it could be.
> Also, I would prefer documentation to be provided or at least some
> intended usage examples to be given.
Sure, no problem.
I'll resend with the RFC and the examples
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2022-02-04 18:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 16:15 Daniel Lezcano
2022-02-04 17:11 ` Rafael J. Wysocki
2022-02-04 18:13 ` Daniel Lezcano [this message]
2022-02-04 19:32 ` srinivas pandruvada
2022-02-04 22:16 ` Daniel Lezcano
2022-02-04 23:04 ` srinivas pandruvada
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=2297b79e-b99c-30a5-1e5c-560d5553e146@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=Viktor.Rosendahl@bmw.de \
--cc=colin.king@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
--cc=sashal@kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=vilhelm.gray@gmail.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
all inboxes | Powered by JetHome®