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: <874j25dx9y.fsf@dell.be.48ers.dk>
Date: Sat, 11 Jan 2025 19:24:09 +0100
From: Peter Korsgaard <peter@...sgaard.com>
To: Guenter Roeck <linux@...ck-us.net>
Cc: Rob Herring <robh@...nel.org>,  devicetree@...r.kernel.org,
  linux-hwmon@...r.kernel.org,  Jean Delvare <jdelvare@...e.com>,
  Krzysztof Kozlowski <krzk+dt@...nel.org>,  Conor Dooley
 <conor+dt@...nel.org>,  open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4 1/2] dt-bindings: hwmon: pwm-fan: Document
 default-pwm property

>>>>> "Guenter" == Guenter Roeck <linux@...ck-us.net> writes:

Hi,

 >> Guenter, what do you say? This way we don't need any new device tree
 >> properties. I personally find it less clear than a default-pwm property,
 >> but oh well.
 >> 

 > I would not call that "default". It is more along the line of
 > "If available, use highest cooling level as maximum allowed".

Sorry, what are you referring to exactly? The commit message? The change
is about the default/initial pwm setting, there is nothing disallowing
user space to increase it afterwards?


 > Other than that, I don't like it, but since it looks like we
 > won't get approval for the devicetree property, I'd say go for it.

Great, then we agree! I'll send a v5 then once it is clear what your
comment above refers to.

-- 
Bye, Peter Korsgaard

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ