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] [day] [month] [year] [list]
Message-ID: <b16d1ace-b113-47e2-9c48-7c89d122e2a9@kernel.org>
Date: Fri, 5 Jul 2024 11:45:20 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Andrei.Simion@...rochip.com, robh@...nel.org, krzk+dt@...nel.org,
 conor+dt@...nel.org, Nicolas.Ferre@...rochip.com,
 alexandre.belloni@...tlin.com, claudiu.beznea@...on.dev
Cc: devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/7] ARM: dts: microchip: at91-sama5d34ek: Align the
 eeprom nodename

On 05/07/2024 11:31, Andrei.Simion@...rochip.com wrote:
> On 05.07.2024 09:43, Krzysztof Kozlowski wrote:
>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>
>> On 04/07/2024 17:14, Andrei Simion wrote:
>>> Align the eeprom nodename according to device tree specification
>>> and at24.yaml.
>>>
>>> Signed-off-by: Andrei Simion <andrei.simion@...rochip.com>
>>
>> Squash.
>>
> 
> I will squash.
> 
>>> ---
>>>  arch/arm/boot/dts/microchip/sama5d34ek.dts | 2 +-
>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/arch/arm/boot/dts/microchip/sama5d34ek.dts b/arch/arm/boot/dts/microchip/sama5d34ek.dts
>>> index bffd61397cb5..18943b873fff 100644
>>> --- a/arch/arm/boot/dts/microchip/sama5d34ek.dts
>>> +++ b/arch/arm/boot/dts/microchip/sama5d34ek.dts
>>> @@ -36,7 +36,7 @@ i2c0: i2c@...14000 {
>>>                       i2c1: i2c@...18000 {
>>>                               status = "okay";
>>>
>>> -                             24c256@50 {
>>> +                             eeprom@50 {
>>
>> What about other names? Why not fixing everything at once?
>>
> 
> There are 149 dts+dtsi files. I would like to fix them step by step. (lots to check)

I meant, if doing cosmetic changes like this to these files, why not
fixing other names? Some of the work is automatic.

Best regards,
Krzysztof


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ