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>] [day] [month] [year] [list]
Message-ID: <9b86de44-c80c-42d9-a0eb-d39b077ce8f8@kernel.org>
Date: Tue, 17 Sep 2024 08:05:33 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Diogo Silva <diogompaissilva@...il.com>
Cc: robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
 shawnguo@...nel.org, s.hauer@...gutronix.de, kernel@...gutronix.de,
 festevam@...il.com, aisheng.dong@....com, Frank.Li@....com,
 devicetree@...r.kernel.org, imx@...ts.linux.dev,
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arm64: dts: imx8: Fix lvds0 device tree

On 16/09/2024 22:47, Diogo Silva wrote:
> Hey,
> 
> Sorry for the broken tag, will fix on a resend.
> 
> As for the naming, if there is any reason for them to be named qm_* it's
> totally fine, I'll revert it and only touch the clock names. I changed them

It's just unnecessary.

> because comparing with lvds1, those ones do not contain the qm_ prefix and
> I don't see how this dtsi relates specifically to the imx8qm, since it is a
> imx8-ss... and not imx8qm-ss...
> I didn't quite get the question about the nodes. Could you elaborate? Thanks
> 

Usually they have alphabetical order and your change does not look like
keeping it.

Best regards,
Krzysztof


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ