From: Mukesh Savaliya <mukesh.savaliya@oss.qualcomm.com>
To: Mukesh Kumar Savaliya <quic_msavaliy@quicinc.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
alexandre.belloni@bootlin.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
jarkko.nikula@linux.intel.com, linux-i3c@lists.infradead.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Frank.Li@nxp.com,
wsa+renesas@sang-engineering.com, alok.a.tiwari@oracle.com
Cc: andersson@kernel.org, konradybcio@kernel.org
Subject: Re: [PATCH v6 1/3] dt-bindings: i3c: Add support for Qualcomm I3C controller
Date: Tue, 22 Sep 2026 02:01:00 +0530 [thread overview]
Message-ID: <ea53d79c-4aa9-4e98-b829-cdf6f43cab66@oss.qualcomm.com> (raw)
In-Reply-To: <b7d120c8-1215-4923-8810-83cc0d7cdc36@quicinc.com>
Hi Krzysztof , Apologies for the delayed response. I was waiting to
verify the changes and ensure all the suggested updates were properly
incorporated. The effort was further delayed due to some slave-side
setup issues.
Since, I migrated from my @quicinc.com email address to
@oss.qualcomm.com and could not locate the original email thread. The
replies below are from a draft I had saved earlier.
I have now addressed and validated all the suggested changes except one,
which I have responded to separately below. I shall upload V7 cleanly soon.
> On 7/1/2025 2:03 PM, Krzysztof Kozlowski wrote:
>> On 01/07/2025 09:18, Mukesh Kumar Savaliya wrote:
>>> Add device tree bindings for the Qualcomm I3C controller. This includes
>>> the necessary documentation and properties required to describe the
>>> hardware in the device tree.
>>>
>>> Signed-off-by: Mukesh Kumar Savaliya <mukesh.savaliya@oss.qualcomm.com>
>>> Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
>>> ---
>>> .../bindings/i3c/qcom,geni-i3c.yaml | 59 +++++++++++++++++++
>>> 1 file changed, 59 insertions(+)
>>> create mode 100644 Documentation/devicetree/bindings/i3c/qcom,geni-
>>> i3c.yaml
>>>
>>
>> It's v6, you really should have started testing your changes by that
>> time. :/
>>
yes, clock-names - Got added by mistake while uploading, will remove it
in next patch. Will run both dtbs_check and dt_binding_check before next
patch.
>> Nothing in the changelog explains the change made here, so you just
>> sneaked something which did not work.
>>
I didn't made any change into this binding file. I would have added in
change log V5 to V6 if there was any change in this yaml file.
If you find anything else getting added, except "clock-names", please
let me know.
>
>> Best regards,
>> Krzysztof
>>
>
next prev parent reply other threads:[~2026-09-21 20:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-01 7:18 [PATCH v6 0/3] Add Qualcomm i3c controller driver support Mukesh Kumar Savaliya
2025-07-01 7:18 ` [PATCH v6 1/3] dt-bindings: i3c: Add support for Qualcomm I3C controller Mukesh Kumar Savaliya
2025-07-01 8:30 ` Rob Herring (Arm)
2025-07-01 8:33 ` Krzysztof Kozlowski
[not found] ` <b7d120c8-1215-4923-8810-83cc0d7cdc36@quicinc.com>
2026-09-21 20:31 ` Mukesh Savaliya [this message]
2025-07-01 8:53 ` ALOK TIWARI
2025-07-01 8:58 ` Krzysztof Kozlowski
2025-07-17 20:51 ` Konrad Dybcio
2026-09-21 20:28 ` Mukesh Savaliya
2026-09-22 10:10 ` Konrad Dybcio
2026-09-23 9:35 ` Mukesh Savaliya
2025-07-01 7:18 ` [PATCH v6 2/3] i3c: master: Add Qualcomm I3C controller driver Mukesh Kumar Savaliya
2025-07-01 8:43 ` Krzysztof Kozlowski
2026-09-21 20:33 ` Mukesh Savaliya
2025-07-01 8:48 ` ALOK TIWARI
2026-09-21 20:32 ` Mukesh Savaliya
2025-07-01 16:40 ` Frank Li
[not found] ` <c1060b7d-a621-4805-8fac-11621b6f564f@quicinc.com>
2026-09-21 20:34 ` Mukesh Savaliya
2025-07-01 20:56 ` Bjorn Andersson
[not found] ` <9e3da313-ab1f-435d-8e3c-1a0c946a7790@quicinc.com>
2026-09-21 20:35 ` Mukesh Savaliya
2025-07-01 7:18 ` [PATCH v6 3/3] MAINTAINERS: Add maintainer for Qualcomm's " Mukesh Kumar Savaliya
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=ea53d79c-4aa9-4e98-b829-cdf6f43cab66@oss.qualcomm.com \
--to=mukesh.savaliya@oss.qualcomm.com \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=alok.a.tiwari@oracle.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jarkko.nikula@linux.intel.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_msavaliy@quicinc.com \
--cc=robh@kernel.org \
--cc=wsa+renesas@sang-engineering.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
all inboxes | Powered by JetHome®