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: <9a10b934-e7f3-c95f-6250-8a857bdfa912@lechnology.com>
Date:   Thu, 25 Jul 2019 09:08:28 -0500
From:   David Lechner <david@...hnology.com>
To:     Richard Tresidder <rtresidd@...ctromag.com.au>, sre@...nel.org,
        enric.balletbo@...labora.com, ncrews@...omium.org,
        andrew.smirnov@...il.com, groeck@...omium.org, tglx@...utronix.de,
        linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] power/supply/powersupply_sysfs: Add of_node name to
 uevent message if available

On 7/25/19 2:47 AM, Richard Tresidder wrote:
> If the of_node name of the supply is available from the devicetree binding
> then include it under the var POWER_SUPPLY_OF_NODE_NAME.
> This helps where a consistent name is known via the device tree binding
> but it is hard to identify based on the usual enumeration process.
> 

Would it be possible to use of_device_uevent() instead of introducing a new
property?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ