From: Varadarajan Narayanan <quic_varada@quicinc.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: <gregkh@linuxfoundation.org>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<andersson@kernel.org>, <konrad.dybcio@linaro.org>,
<quic_wcheng@quicinc.com>, <johan+linaro@kernel.org>,
<quic_kriskura@quicinc.com>, <linux-arm-msm@vger.kernel.org>,
<linux-usb@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v0 1/2] dt-bindings: usb: qcom,dwc3: Add minItems for interrupt info
Date: Thu, 11 Jul 2024 14:58:17 +0530 [thread overview]
Message-ID: <Zo+lsSwFG3+KwKUu@hu-varada-blr.qualcomm.com> (raw)
In-Reply-To: <5142d8af-2b05-4018-a9c5-0a8b99719b0d@kernel.org>
On Thu, Jul 11, 2024 at 11:03:56AM +0200, Krzysztof Kozlowski wrote:
> On 11/07/2024 10:47, Varadarajan Narayanan wrote:
> >>
> >> but x1e80100 has 4, right?
> >
> > Yes. Will have a separate block for ipq5332. Went with min/max based
> > on one of the previous blocks that had min/max as two and three for
> > a group of SoCs.
> >
>
> Did you even test it before sending?
Yes, ran dt_binding_check. After confirming that ipq5332 related
errors got resolved and no new errors for x1e80100 sent the
patch. Missed the yaml file related error generated by Rob's bot.
Will address these and send a new patch.
Thanks
Varada
next prev parent reply other threads:[~2024-07-11 9:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 6:56 [PATCH v0 1/2] dt-bindings: usb: qcom,dwc3: Add minItems for interrupt info Varadarajan Narayanan
2024-07-11 6:56 ` [PATCH v0 2/2] arm64: dts: qcom: ipq5332: Fix interrupt trigger type for usb Varadarajan Narayanan
2024-07-11 7:47 ` [PATCH v0 1/2] dt-bindings: usb: qcom,dwc3: Add minItems for interrupt info Krzysztof Kozlowski
2024-07-11 8:47 ` Varadarajan Narayanan
2024-07-11 9:03 ` Krzysztof Kozlowski
2024-07-11 9:03 ` Krzysztof Kozlowski
2024-07-11 9:28 ` Varadarajan Narayanan [this message]
2024-07-11 8:31 ` Rob Herring (Arm)
2024-07-11 14:22 ` Rob Herring
2024-07-17 9:51 ` Varadarajan Narayanan
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=Zo+lsSwFG3+KwKUu@hu-varada-blr.qualcomm.com \
--to=quic_varada@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=johan+linaro@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=quic_kriskura@quicinc.com \
--cc=quic_wcheng@quicinc.com \
--cc=robh@kernel.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