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
| ||
|
Message-ID: <1883d9d7-26d4-40b1-9848-ae0477cf95c7@linaro.org> Date: Wed, 11 Jun 2025 00:02:43 +0300 From: Vladimir Zapolskiy <vladimir.zapolskiy@...aro.org> To: Bryan O'Donoghue <bryan.odonoghue@...aro.org>, Wenmeng Liu <quic_wenmliu@...cinc.com>, rfoss@...nel.org, todor.too@...il.com, andersson@...nel.org, konradybcio@...nel.org, robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org Cc: linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, linux-media@...r.kernel.org, quic_depengs@...cinc.com Subject: Re: [PATCH RESEND] arm64: dts: qcom: sm8550: Add support for camss On 6/10/25 22:02, Bryan O'Donoghue wrote: > On 10/06/2025 13:49, Vladimir Zapolskiy wrote: >>> >>> List feedback from DT people is isp@ is the correct prefix. >>> >> >> My bad, but I don't understand this comment, it seems irrelevant... >> >> The expressed concern is about the novel label name. > > I mean to say the feedback from Krzysztof was that we should use isp@ > not camss@ and I agree. > Let me repeat it thrice, it's okay... I don't object against the properly selected device tree node name "isp", here I object against a never used and very questionable label name "isp". Please feel free to ask more questions, if you still find it confusing. Again, I may missed a discussion about the need to get and use a novel label name, then please share a link to it, it'll be very much appreciated. -- Best wishes, Vladimir
Powered by blists - more mailing lists