lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2297b79e-b99c-30a5-1e5c-560d5553e146@linaro.org>
Date:   Fri, 4 Feb 2022 19:13:25 +0100
From:   Daniel Lezcano <daniel.lezcano@...aro.org>
To:     "Rafael J. Wysocki" <rafael@...nel.org>
Cc:     Linux PM <linux-pm@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Jonathan Cameron <Jonathan.Cameron@...wei.com>,
        William Breathitt Gray <vilhelm.gray@...il.com>,
        Viktor Rosendahl <Viktor.Rosendahl@....de>,
        Sasha Levin <sashal@...nel.org>,
        Colin Ian King <colin.king@...el.com>,
        Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
        "Zhang, Rui" <rui.zhang@...el.com>
Subject: Re: [PATCH] tools/lib/thermal: Add a thermal library

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@...aro.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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ