From: Krzysztof Kozlowski <krzk@kernel.org>
To: Kuldeep Singh <kuldeep.singh@oss.qualcomm.com>
Cc: Vinod Koul <vkoul@kernel.org>, Frank Li <Frank.Li@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Harshal Dev <harshal.dev@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, dmaengine@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: dma: qcom: bam-dma: Add support for kaanapali BAM v2.0.0
Date: Sat, 25 Apr 2026 12:24:40 +0200 [thread overview]
Message-ID: <19600dfe-00e7-49be-9879-95cf662e1604@kernel.org> (raw)
In-Reply-To: <20260425-handsome-papaya-porcupine-d42df7@quoll>
On 25/04/2026 12:23, Krzysztof Kozlowski wrote:
> On Fri, Apr 24, 2026 at 05:04:15PM +0530, Kuldeep Singh wrote:
>> Kaanapali support newer BAM v2.0.0 version.
>> Document the compatible string and update example along with it.
>
> And why v2.0.0 is not compatible with v1.7.0? Or what is not compatible?
>
>>
Ah, and drop redundant "support for". Write concise subjects and binding
cannot "support" something.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-04-25 10:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 11:34 [PATCH 0/3] Add support for qcrypto in kaanapali Kuldeep Singh
2026-04-24 11:34 ` [PATCH 1/3] dt-bindings: dma: qcom: bam-dma: Add support for kaanapali BAM v2.0.0 Kuldeep Singh
2026-04-25 10:23 ` Krzysztof Kozlowski
2026-04-25 10:24 ` Krzysztof Kozlowski [this message]
2026-04-27 8:48 ` Kuldeep Singh
2026-04-27 8:34 ` Kuldeep Singh
2026-04-27 11:50 ` Krzysztof Kozlowski
2026-04-28 5:56 ` Kuldeep Singh
2026-04-24 11:34 ` [PATCH 2/3] dmaengine: qcom: bam_dma: Add support for " Kuldeep Singh
2026-04-24 11:34 ` [PATCH 3/3] arm64: dts: qcom: kaanapali: Add qcrypto node support Kuldeep Singh
2026-04-24 12:03 ` Konrad Dybcio
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=19600dfe-00e7-49be-9879-95cf662e1604@kernel.org \
--to=krzk@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=harshal.dev@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kuldeep.singh@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.