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]
Date:   Wed, 27 Oct 2021 15:19:02 +0300
From:   Dmitry Osipenko <digetx@...il.com>
To:     Rob Herring <robh+dt@...nel.org>, Tony Lindgren <tony@...mide.com>
Cc:     linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
        linux-omap@...r.kernel.org
Subject: Re: [PATCH v1] ARM: dts: elpida_ecb240abacn: Change Elpida compatible

20.10.2021 02:40, Dmitry Osipenko пишет:
> Vendor prefix shouldn't start with capital letter. The Elpida Memory
> compatible was never used in practice, hence just correct the compatible.
> 
> Signed-off-by: Dmitry Osipenko <digetx@...il.com>
> ---
>  arch/arm/boot/dts/elpida_ecb240abacn.dtsi | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/arm/boot/dts/elpida_ecb240abacn.dtsi b/arch/arm/boot/dts/elpida_ecb240abacn.dtsi
> index d87ee4794f83..9698801cbcfb 100644
> --- a/arch/arm/boot/dts/elpida_ecb240abacn.dtsi
> +++ b/arch/arm/boot/dts/elpida_ecb240abacn.dtsi
> @@ -5,7 +5,7 @@
>  
>  / {
>  	elpida_ECB240ABACN: lpddr2 {
> -		compatible	= "Elpida,ECB240ABACN","jedec,lpddr2-s4";
> +		compatible	= "elpida,ECB240ABACN","jedec,lpddr2-s4";
>  		density		= <2048>;
>  		io-width	= <32>;
>  
> 

This patch should go via OMAP tree since there is only OMAP board which
uses this dtsi. To make it more clear, "elpida" variant is now
documented in the bindings [1][2].

[1]
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=9e17f71e9c334f14ad6a8ec3edc09c7a4244e12f

[2]
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=001b8b2594db4ea24fbea4c161e665f858917fce

If there is no interest in taking the patch via OMAP tree, then it may
go via the DT git tree. Rob, you should pick it up then.

Thanks!

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ