From: Vinod Koul <vkoul@kernel.org>
To: devicetree@vger.kernel.org, dmaengine@vger.kernel.org,
Bhupesh Sharma <bhupesh.sharma@linaro.org>
Cc: krzysztof.kozlowski+dt@linaro.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, andersson@kernel.org,
bhupesh.linux@gmail.com, agross@kernel.org,
konrad.dybcio@linaro.org, conor+dt@kernel.org,
robh+dt@kernel.org
Subject: Re: [PATCH v9 0/2] dt-bindings: dma: Add support for SM6115 and QCM2290 SoCs
Date: Tue, 11 Jul 2023 22:13:54 +0530 [thread overview]
Message-ID: <168909383458.208679.6618239187680530710.b4-ty@kernel.org> (raw)
In-Reply-To: <20230630082230.2264698-1-bhupesh.sharma@linaro.org>
On Fri, 30 Jun 2023 13:52:28 +0530, Bhupesh Sharma wrote:
> Add support for SM6115 and QCM2290 SoCs in qcom,bam-dma bindings.
> Also increase iommu maxItems for BAM DMA to 6 which is the number
> required on sm8250 SoC.
>
> This patchset is rebased on linux-next/master.
>
> Changes since v8:
> -----------------
> - v8 can be viewed here: https://www.spinics.net/lists/linux-crypto/msg72349.html
> - As rest of the patches from v8 have been applied to linux-next, dropped them from v9.
> - Added dma list and maintainer in Cc again as the Cc list got messed up while
> sending out v8.
>
> [...]
Applied, thanks!
[1/2] dt-bindings: dma: Add support for SM6115 and QCM2290 SoCs
commit: 80159ca4314224f5778d5fa8ded24d6ef7876c53
[2/2] dt-bindings: dma: Increase iommu maxItems for BAM DMA
commit: ffcde05811d97e9320358674625f28002102f7c9
Best regards,
--
~Vinod
prev parent reply other threads:[~2023-07-11 16:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 8:22 Bhupesh Sharma
2023-06-30 8:22 ` [PATCH v9 1/2] " Bhupesh Sharma
2023-06-30 8:22 ` [PATCH v9 2/2] dt-bindings: dma: Increase iommu maxItems for BAM DMA Bhupesh Sharma
2023-07-11 16:43 ` Vinod Koul [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=168909383458.208679.6618239187680530710.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=bhupesh.linux@gmail.com \
--cc=bhupesh.sharma@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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
all inboxes | Powered by JetHome®