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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <59864da1-a011-4ed0-9297-fd3ec2ff081b@kernel.org>
Date: Fri, 7 Mar 2025 16:54:48 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: "Rob Herring (Arm)" <robh@...nel.org>, soc@...nel.org,
 Suravee Suthikulpanit <suravee.suthikulpanit@....com>,
 Tom Lendacky <thomas.lendacky@....com>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
 <conor+dt@...nel.org>, Shyam Sundar S K <Shyam-sundar.S-k@....com>,
 Richard Cochran <richardcochran@...il.com>
Cc: devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/4] arm64: dts: amd/seattle: Base Overdrive B1 on top of
 B0 version

On 07/03/2025 02:07, Rob Herring (Arm) wrote:
> AMD Overdrive B1 version is just more peripherals enabled over B0
> version. Rework the B1 .dts to use the B0 .dts.
> 
> Signed-off-by: Rob Herring (Arm) <robh@...nel.org>
> ---
>  arch/arm64/boot/dts/amd/amd-overdrive-rev-b1.dts | 61 +-----------------------
>  1 file changed, 1 insertion(+), 60 deletions(-)
> 
> diff --git a/arch/arm64/boot/dts/amd/amd-overdrive-rev-b1.dts b/arch/arm64/boot/dts/amd/amd-overdrive-rev-b1.dts
> index 58e2b0a6f841..b34dd8d5d1b1 100644
> --- a/arch/arm64/boot/dts/amd/amd-overdrive-rev-b1.dts
> +++ b/arch/arm64/boot/dts/amd/amd-overdrive-rev-b1.dts
> @@ -8,32 +8,10 @@
>  
>  /dts-v1/;
>  
> -/include/ "amd-seattle-soc.dtsi"
> -/include/ "amd-seattle-cpus.dtsi"
> +/include/ "amd-overdrive-rev-b0.dts"

This should be just common DTSI for overdrive boards. We rather avoid
including DTS from DTS.

OTOH, that's pretty abandoned platform, so probably no one cares about
correctness, so I don't oppose current approach.

Best regards,
Krzysztof


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ