[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a1ddbc5c-0e41-84b2-4281-7303cc3040f8@linaro.org>
Date: Wed, 12 Jul 2023 21:40:55 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Sumit Gupta <sumitg@...dia.com>, treding@...dia.com,
jonathanh@...dia.com, linux-kernel@...r.kernel.org,
linux-tegra@...r.kernel.org
Cc: bbasu@...dia.com, talho@...dia.com,
Dmitry Osipenko <digetx@...il.com>,
Ashish Mhetre <amhetre@...dia.com>
Subject: Re: [Patch RESEND 1/4] memory: tegra: sort tegra234_mc_clients table
as per register offsets
On 10/07/2023 18:48, Sumit Gupta wrote:
>
>
> 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.
OK. This has an impact on backports, thus I would be happy to see some
acks or reviews from other developers of this code, that this change
actually helps them by making code more readable and maintainable.
Best regards,
Krzysztof
Powered by blists - more mailing lists