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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 24 Apr 2019 08:28:46 +0000
From:   Igor Russkikh <>
To:     Andrew Lunn <>
CC:     "David S . Miller" <>,
        "" <>,
        Nikita Danilov <>,
        Dmitry Bogdanov <>,
        Yana Esina <>
Subject: Re: [PATCH v2 net-next 02/16] net: aquantia: implement hwmon api for
 chip temperature

>> +static u32 aq_hwmon_temp_config[] = {
>> +	0,
> It would be nice to also have
>         HWMON_T_MAX | HWMON_T_MIN |
> which the PHY probably has.
> At gives some degree of context. A temperature on its own of say 65C
> is hard to interpret. Is it too hot?  But if we have a critical of 85C
> and a max of 95C we know we are O.K.

I can give here only suggested constants, since we don't have now any interface
on reading/configuring these.

Do you think that will be ok?


Powered by blists - more mailing lists