DMA Engine development
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: linux-arm-msm@vger.kernel.org, dmaengine@vger.kernel.org,
	 linux-kernel@vger.kernel.org,
	 Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: (subset) [PATCH 0/3] dmengine: qcom: bam_dma: some driver refactoring
Date: Tue, 16 Dec 2025 22:29:25 +0530	[thread overview]
Message-ID: <176590436523.430148.5029789142471290220.b4-ty@kernel.org> (raw)
In-Reply-To: <20251106-qcom-bam-dma-refactor-v1-0-0e2baaf3d81a@linaro.org>


On Thu, 06 Nov 2025 16:44:49 +0100, Bartosz Golaszewski wrote:
> Here are some changes I figured would be nice to have while working on
> the BAM locking feature.
> 
> 

Applied, thanks!

[1/3] dmaengine: qcom: bam_dma: order includes alphabetically
      commit: 892f2bb487916cb15432912cd6aae445ab2f48f0
[2/3] dmaengine: qcom: bam_dma: use lock guards
      commit: 20f581834aacd743b3d95bbbb37a802d14cf3690

Best regards,
-- 
~Vinod



      parent reply	other threads:[~2025-12-16 16:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-06 15:44 [PATCH 0/3] dmengine: qcom: bam_dma: some driver refactoring Bartosz Golaszewski
2025-11-06 15:44 ` [PATCH 1/3] dmaengine: qcom: bam_dma: order includes alphabetically Bartosz Golaszewski
2025-11-12  3:11   ` Dmitry Baryshkov
2025-11-06 15:44 ` [PATCH 2/3] dmaengine: qcom: bam_dma: use lock guards Bartosz Golaszewski
2025-11-06 15:44 ` [PATCH 3/3] dmaengine: qcom: bam_dma: convert tasklet to a workqueue Bartosz Golaszewski
2025-11-12  3:10   ` Dmitry Baryshkov
2025-11-12 16:19   ` Bjorn Andersson
2025-11-13 10:26     ` Bartosz Golaszewski
2025-11-22  9:10   ` Vinod Koul
2025-11-24  7:58     ` Bartosz Golaszewski
2025-12-16 16:59 ` 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=176590436523.430148.5029789142471290220.b4-ty@kernel.org \
    --to=vkoul@kernel.org \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.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