linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Kuldeep Singh <singh.kuldeep87k@gmail.com>,
	Bhupesh Sharma <bhupesh.sharma@linaro.org>
Cc: Rob Herring <robh+dt@kernel.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: Tue, 19 Apr 2022 09:47:45 +0200	[thread overview]
Message-ID: <1965ed9f-0258-cd28-f1c3-ef87272f6c03@linaro.org> (raw)
In-Reply-To: <20220418192012.GA6868@9a2d8922b8f1>

On 18/04/2022 21:20, Kuldeep Singh wrote:
> On Mon, Apr 18, 2022 at 10:57:55AM +0530, Bhupesh Sharma wrote:
>> Please see <https://lore.kernel.org/lkml/20220211214941.f55q5yksittut3ep@amazon.com/T/#m6700c2695ee78e79060ac338d208ffd08ac39592>,
>> I already have an effort ongoing for converting qcom bam DMA bindings
>> to YAML format.
> 
> Ohh ok, I wasn't aware you had similar series.
> I just noticed your latest v5 version was rolled out ~5 months back,
> usually this is a very long time considering the duration. Wondering
> reason behind this..
> 
> My updated series(v3 version[1]) is kind of complete and mostly reviewed
> by Krzysztof and takes care of armv7/8 based platforms. 

My review was only about patch correctness, not overall patch preference.

> With no offence,
> I believe we should go with the current one as your series includes
> changes more than BAM and will take long time to merge. Anyway, I'll be
> fine with choice of the maintainers.

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.

Before starting the conversion the best is to look for prior work on lore:
https://lore.kernel.org/lkml/?q=dfn%3Aqcom_bam_dma.txt
This way you could easily avoid doing the same.

Bhupesh,
Please check what was stopping your work, you might need to rebase it
and resend it.

Best regards,
Krzysztof

  reply	other threads:[~2022-04-19  7:47 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 [this message]
2022-04-20 13:29         ` Kuldeep Singh
2022-04-20 15:33           ` Kuldeep Singh
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=1965ed9f-0258-cd28-f1c3-ef87272f6c03@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --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=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=singh.kuldeep87k@gmail.com \
    --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).