public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Wenmeng Liu <wenmeng.liu@oss.qualcomm.com>
Cc: Robert Foss <rfoss@kernel.org>, Todor Tomov <todor.too@gmail.com>,
	Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
	Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] media: dt-bindings: Add qcom,sm6150-camss
Date: Wed, 24 Dec 2025 10:43:53 +0100	[thread overview]
Message-ID: <57b55fc8-7350-4c5b-b5bf-9171b1954710@kernel.org> (raw)
In-Reply-To: <c6174a0a-9a76-4284-8675-bb5ca78a7b35@oss.qualcomm.com>

On 24/12/2025 04:18, Wenmeng Liu wrote:
> 
> 
> On 12/23/2025 9:38 PM, Krzysztof Kozlowski wrote:
>> On Mon, Dec 22, 2025 at 04:28:39PM +0800, Wenmeng Liu wrote:
>>> +  interconnects:
>>> +    maxItems: 4
>>> +
>>> +  interconnect-names:
>>> +    items:
>>> +      - const: ahb
>>> +      - const: hf0_mnoc
>>> +      - const: hf1_mnoc
>>
>> Same comments as before, do not invent names.
> 
> <&mmss_noc MASTER_CAMNOC_HF0 QCOM_ICC_TAG_ALWAYS
> &mc_virt SLAVE_EBI1 QCOM_ICC_TAG_ALWAYS>,
> <&mmss_noc MASTER_CAMNOC_HF1 QCOM_ICC_TAG_ALWAYS
> &mc_virt SLAVE_EBI1 QCOM_ICC_TAG_ALWAYS>,

How is it relevant to the names?

> 
> This platform(qcs615) is different from others. It has two types of sf, 
> namely sf0 and sf1.

How is it relevant to the names?

> The same as it is:
> sc7180 sc8180x sdm670 sdm845 sm8150
> Do you have any suggestions about this?

Open any other binding. What are the names there?




> 
>>
>> I finish review here and ignore the rest. You did not respond to
>> previous comments and I do not see any improvements.
> 
> I'm sorry about this. However, the previous comments did not clearly 
> point out the problem.
> 
>> Also, way you send patches makes it difficult for us, so I see no reason
>> why it should be my task to try to decipher all this.
>>
>> b4 diff '20251222-sm6150-camss-v2-1-df8469a8343a@oss.qualcomm.com'
>> Checking for older revisions
>> Grabbing search results from lore.kernel.org
>> ---
>> Analyzing 5 messages in the thread
>> Could not find lower series to compare against.
> 
> --in-reply-to, will pay attention in the next version.

What? No. You are supposed to use properly b4, which solves all these
problems.

Best regards,
Krzysztof

  parent reply	other threads:[~2025-12-24  9:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-22  8:28 [PATCH v2 0/3] media: qcom: camss: Add sm6150 camss support Wenmeng Liu
2025-12-22  8:28 ` [PATCH v2 1/3] media: dt-bindings: Add qcom,sm6150-camss Wenmeng Liu
2025-12-23 13:38   ` Krzysztof Kozlowski
2025-12-24  3:18     ` Wenmeng Liu
2025-12-24  4:21       ` Dmitry Baryshkov
2025-12-24  4:31         ` Wenmeng Liu
2025-12-24  5:03           ` Dmitry Baryshkov
2025-12-24  5:36             ` Wenmeng Liu
2025-12-24  6:20               ` Dmitry Baryshkov
2025-12-24  9:46               ` Krzysztof Kozlowski
2025-12-24 10:29                 ` Wenmeng Liu
2025-12-24 12:24                   ` Dmitry Baryshkov
2025-12-24  9:43       ` Krzysztof Kozlowski [this message]
2025-12-22  8:28 ` [PATCH v2 2/3] media: qcom: camss: add support for SM6150 camss Wenmeng Liu
2026-01-12  0:34   ` Bryan O'Donoghue
2026-01-12  8:12     ` Wenmeng Liu
2025-12-22  8:28 ` [PATCH v2 3/3] arm64: dts: qcom: talos: Add camss node Wenmeng Liu
2025-12-23 13:35 ` [PATCH v2 0/3] media: qcom: camss: Add sm6150 camss support Krzysztof Kozlowski
2025-12-24  3:25   ` Wenmeng Liu

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=57b55fc8-7350-4c5b-b5bf-9171b1954710@kernel.org \
    --to=krzk@kernel.org \
    --cc=andersson@kernel.org \
    --cc=bryan.odonoghue@linaro.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=mchehab@kernel.org \
    --cc=rfoss@kernel.org \
    --cc=robh@kernel.org \
    --cc=todor.too@gmail.com \
    --cc=vladimir.zapolskiy@linaro.org \
    --cc=wenmeng.liu@oss.qualcomm.com \
    /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