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: <3803fad5-0dab-491c-b2bf-47ab888bb1a2@kernel.org>
Date: Fri, 3 Jan 2025 10:35:27 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Peter Korsgaard <peter@...sgaard.com>, Guenter Roeck
 <linux@...ck-us.net>, devicetree@...r.kernel.org, linux-hwmon@...r.kernel.org
Cc: Jean Delvare <jdelvare@...e.com>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
 <conor+dt@...nel.org>, open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: hwmon: pwm-fan: Document default-pwm
 property

On 03/01/2025 10:01, Peter Korsgaard wrote:
> 
> Looking at lore, v1 used target-pwm which Gunter suggested I changed to 
> default-rpm while explaining that it cannot be a generic property:
> 
> https://lore.kernel.org/linux-devicetree/b717da30-1d4c-4e09-b98c-4aa41a235234@roeck-us.net/
> 
> Which I then did as a v2, that then didn't get any additional feedback:
> 
> https://lore.kernel.org/linux-devicetree/3aa21a01-c994-4b36-8893-181e55a60c5e@korsgaard.com/
> 
> So if we agree on default-pwm, then I can send an update (a v4!) with 
> the typo in the example fixed, OK?

Yes and we go back to my first comment about commit msg:

"Also mention here shortly how Rob's comment is addressed."

e.g. we cannot use default/target-rpm because of foo bar.

Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ