From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Bhupesh Sharma <bhupesh.sharma@linaro.org>, devicetree@vger.kernel.org
Cc: linux-arm-msm@vger.kernel.org, bhupesh.linux@gmail.com,
linux-kernel@vger.kernel.org, vkoul@kernel.org,
agross@kernel.org, dmaengine@vger.kernel.org,
konrad.dybcio@somainline.org, robh+dt@kernel.org,
andersson@kernel.org
Subject: Re: [PATCH] dt-bindings: dma: Make minor fixes to qcom,bam-dma binding doc
Date: Mon, 26 Sep 2022 10:48:37 +0200 [thread overview]
Message-ID: <1841f368-e9db-1662-e950-c162a6b17f75@linaro.org> (raw)
In-Reply-To: <d3205b59-6b6e-2983-9e2a-39354cd1803e@linaro.org>
On 25/09/2022 21:55, Bhupesh Sharma wrote:
>
> On 9/18/22 2:19 PM, Krzysztof Kozlowski wrote:
>> On 18/09/2022 09:11, Bhupesh Sharma wrote:
>>> As a user recently noted, the qcom,bam-dma binding document
>>> describes the BAM DMA node incorrectly.
>>
>> It's a bit confusing - what is exactly incorrectly described by binding?
>> You did not make any changes to the binding itself...
>
> Sorry for the late reply. Your comment just skipped through my mail
> filters :(
>
> I understand your point. I should have made the commit message more
> descriptive (infact now I look at it, I see some key words are actually
> missing from the commit message).
>
> The commit message should infact read as:
>
> "As a user recently noted, the qcom,bam-dma binding document
> describes the BAM DMA node *in the example section* incorrectly. Fix the
OK, now it makes sense :)
Best regards,
Krzysztof
prev parent reply other threads:[~2022-09-26 8:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 8:11 [PATCH] dt-bindings: dma: Make minor fixes to qcom,bam-dma binding doc Bhupesh Sharma
2022-09-18 8:49 ` Krzysztof Kozlowski
2022-09-25 19:55 ` Bhupesh Sharma
2022-09-26 8:48 ` Krzysztof Kozlowski [this message]
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=1841f368-e9db-1662-e950-c162a6b17f75@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bhupesh.linux@gmail.com \
--cc=bhupesh.sharma@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=konrad.dybcio@somainline.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).