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
| ||
|
Date: Mon, 10 Oct 2022 14:40:27 -0400 From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org> To: Dzmitry Sankouski <dsankouski@...il.com> Cc: Andy Gross <agross@...nel.org>, Bjorn Andersson <bjorn.andersson@...aro.org>, Rob Herring <robh+dt@...nel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>, Kees Cook <keescook@...omium.org>, Anton Vorontsov <anton@...msg.org>, Colin Cross <ccross@...roid.com>, Tony Luck <tony.luck@...el.com>, linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH v2] arm64: dts: qcom: starqltechn: add initial device tree for starqltechn On 10/10/2022 12:43, Dzmitry Sankouski wrote: > (...) >> >> Why do you have DTSI for one DTS? > Samsung has several devices on sdm845 SoC (at least 3 phones: > starqltechn, starq2ltechn, crownltechn). I don't have plans to > introduce support for any new Samsung sdm845 device except > starqltechn, but I guess we should extract common dtsi now to make > future contributions easier. I think I should rename common dtsi file > to '$soc-$vendor-common.dtsi', like others device trees doing now File can be easily renamed later, but if additional devices are not mainlined we will always need to deal with almost empty DTS. Best regards, Krzysztof
Powered by blists - more mailing lists