linux-kernel - Re: [Patch RESEND 1/4] memory: tegra: sort tegra234_mc

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: <ac9e9e2a-00b8-c9e7-00c7-215cba139a39@nvidia.com>
Date:   Mon, 10 Jul 2023 22:18:54 +0530
From:   Sumit Gupta <sumitg@...dia.com>
To:     Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
        <treding@...dia.com>, <jonathanh@...dia.com>,
        <linux-kernel@...r.kernel.org>, <linux-tegra@...r.kernel.org>
CC:     <bbasu@...dia.com>, <talho@...dia.com>
Subject: Re: [Patch RESEND 1/4] memory: tegra: sort tegra234_mc_clients table
 as per register offsets



On 10/07/23 15:38, Krzysztof Kozlowski wrote:
> External email: Use caution opening links or attachments
> 
> 
> On 21/06/2023 15:43, Sumit Gupta wrote:
>> Sort the MC client entries in "tegra234_mc_clients" table as per the
>> override and security register offsets. This will help to avoid
>> creating duplicate entries.
> 
> If person cannot search for existing symbol before adding new entry, I
> doubt that sorting would solve it. OTOH, this patch makes backporting
> changes trickier, so I don't think this is good approach. Are all other
> Tegra files ordered in this matter?
> 
> 
> Best regards,
> Krzysztof
> 

They are in order for previous T194 SoC.
For T234 also, initially the entries were in order.

Thank you,
Sumit Gupta