linux-kernel - Re: [PATCH] of: reserved_mem: Remove the use of phandle from the reserved

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: <24c894ae-5c4a-4462-b036-5929db2fc5ac@quicinc.com>
Date: Tue, 23 Apr 2024 16:33:29 -0700
From: Oreoluwa Babatunde <quic_obabatun@...cinc.com>
To: Jeff Johnson <quic_jjohnson@...cinc.com>, <robh@...nel.org>,
        <saravanak@...gle.com>
CC: <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <kernel@...cinc.com>
Subject: Re: [PATCH] of: reserved_mem: Remove the use of phandle from the
 reserved_mem APIs


On 4/23/2024 7:32 AM, Jeff Johnson wrote:
> On 4/22/2024 4:52 PM, Oreoluwa Babatunde wrote:
>> The __find_rmem() function is the only place that references the phandle
>> field of the reserved_mem struct. __find_rmem() is used to match a
>> device_node object to its corresponding entry in the reserved_mem array
>> using its phandle value. But, there is already a function called
>> of_reserved_mem_lookup() which carries out the same action using the
>> name of the node.
>>
>> Using the of_reserved_mem_lookup() function is more reliable because
>> every node is gauranteed to have a name, but not all nodes will have a
> s/gauranteed /guaranteed /
>
> (jumped out at me while scanning the kernel patches)

ack.

Thank you Jeff!