From: Kuldeep Singh <singh.kuldeep87k@gmail.com>
To: Bhupesh Sharma <bhupesh.sharma@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Vinod Koul <vkoul@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org, dmaengine@vger.kernel.org
Subject: Re: [PATCH v2 6/6] dt-bindings: dma: Convert Qualcomm BAM DMA binding to json format
Date: Wed, 20 Apr 2022 21:03:16 +0530 [thread overview]
Message-ID: <20220420153316.GA63129@9a2d8922b8f1> (raw)
In-Reply-To: <20220420132955.GA63070@9a2d8922b8f1>
On Wed, Apr 20, 2022 at 06:59:55PM +0530, Kuldeep Singh wrote:
> > I appreciate your work Kuldeep, it is important and valuable
> > contribution. It is sad to see duplicated effort, I don't like it for my
> > own patches either. In general, I believe the FIFO approach should be
> > applied, so in this case Bhupesh patches.
>
> Yep, I also agree with FIFO approach w.r.t contributions. But one thing
> daunts me here is the waiting time with latest revision, it's too high.
>
> Anyway, Bhupesh had more than BAM changes and was already on v5, I can
> give benefit of doubt to him and won't argue much here.
>
> Bhupesh, feel free to include my armv7 based dts patches in your series
> otherwise you might stumble DT checks warnings.
Or do you want me to keep my changes separate? Sorry for spam.
next prev parent reply other threads:[~2022-04-20 15:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 17:50 [PATCH v2 0/6] Convert Qcom BAM dma binding to json format Kuldeep Singh
2022-04-10 17:50 ` [PATCH v2 1/6] ARM: dts: qcom: apq8064: User generic node name for DMA Kuldeep Singh
2022-04-10 19:08 ` Krzysztof Kozlowski
2022-04-11 10:43 ` Kuldeep Singh
2022-04-10 17:50 ` [PATCH v2 2/6] ARM: dts: qcom: mdm9615: " Kuldeep Singh
2022-04-10 19:09 ` Krzysztof Kozlowski
2022-04-10 17:50 ` [PATCH v2 3/6] arm64: dts: qcom: msm8996: " Kuldeep Singh
2022-04-10 19:09 ` Krzysztof Kozlowski
2022-04-10 17:50 ` [PATCH v2 4/6] ARM: dts: qcom: ipq4019: " Kuldeep Singh
2022-04-10 19:10 ` Krzysztof Kozlowski
2022-04-10 17:50 ` [PATCH v2 5/6] ARM: dts: qcom: ipq8064: " Kuldeep Singh
2022-04-10 19:10 ` Krzysztof Kozlowski
2022-04-10 17:50 ` [PATCH v2 6/6] dt-bindings: dma: Convert Qualcomm BAM DMA binding to json format Kuldeep Singh
2022-04-10 19:22 ` Krzysztof Kozlowski
2022-04-11 10:58 ` Kuldeep Singh
2022-04-11 11:38 ` Krzysztof Kozlowski
2022-04-12 6:19 ` Kuldeep Singh
2022-04-12 6:43 ` Krzysztof Kozlowski
2022-04-12 18:01 ` Kuldeep Singh
2022-04-17 5:50 ` Kuldeep Singh
2022-04-18 5:27 ` Bhupesh Sharma
2022-04-18 19:20 ` Kuldeep Singh
2022-04-19 7:47 ` Krzysztof Kozlowski
2022-04-20 13:29 ` Kuldeep Singh
2022-04-20 15:33 ` Kuldeep Singh [this message]
2022-04-20 19:17 ` Bhupesh Sharma
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=20220420153316.GA63129@9a2d8922b8f1 \
--to=singh.kuldeep87k@gmail.com \
--cc=agross@kernel.org \
--cc=bhupesh.sharma@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).