From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
Wenmeng Liu <quic_wenmliu@quicinc.com>,
rfoss@kernel.org, todor.too@gmail.com, andersson@kernel.org,
konradybcio@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
quic_depengs@quicinc.com
Subject: Re: [PATCH RESEND] arm64: dts: qcom: sm8550: Add support for camss
Date: Tue, 10 Jun 2025 20:02:43 +0100 [thread overview]
Message-ID: <dc82457e-de2b-43ec-a50c-08f7d8bdeff1@linaro.org> (raw)
In-Reply-To: <739bad1b-f26d-44a6-9cc1-eee28023474f@linaro.org>
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.
---
bod
next prev parent reply other threads:[~2025-06-10 19:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 7:27 [PATCH RESEND] arm64: dts: qcom: sm8550: Add support for camss Wenmeng Liu
2025-05-17 12:07 ` Bryan O'Donoghue
2025-05-21 19:02 ` Konrad Dybcio
2025-06-10 9:48 ` Vladimir Zapolskiy
2025-06-10 9:50 ` Bryan O'Donoghue
2025-06-10 12:49 ` Vladimir Zapolskiy
2025-06-10 19:02 ` Bryan O'Donoghue [this message]
2025-06-10 21:02 ` Vladimir Zapolskiy
2025-06-10 21:04 ` Konrad Dybcio
2025-06-10 21:13 ` Vladimir Zapolskiy
2025-06-10 22:17 ` Bryan O'Donoghue
2025-06-10 22:52 ` Vladimir Zapolskiy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dc82457e-de2b-43ec-a50c-08f7d8bdeff1@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=quic_depengs@quicinc.com \
--cc=quic_wenmliu@quicinc.com \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=todor.too@gmail.com \
--cc=vladimir.zapolskiy@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox