From: Vinod Koul <vkoul@kernel.org>
To: "Jonathan Cameron" <jic23@kernel.org>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>,
"Paul Cercueil" <paul@crapouillou.net>
Cc: Jonathan Corbet <corbet@lwn.net>, Nuno Sa <nuno.sa@analog.com>,
linux-iio@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org,
linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org
Subject: Re: (subset) [PATCH v12 0/7] iio: new DMABUF based API v12
Date: Fri, 21 Jun 2024 15:36:24 +0530 [thread overview]
Message-ID: <171896438479.273533.11227587889239181030.b4-ty@kernel.org> (raw)
In-Reply-To: <20240620122726.41232-1-paul@crapouillou.net>
On Thu, 20 Jun 2024 14:27:19 +0200, Paul Cercueil wrote:
> Here's the v12 of my patchset that introduces DMABUF support to IIO.
>
> Apart from a small documentation fix, it reverts to using
> mutex_lock/mutex_unlock in one particular place, which used cleanup
> GOTOs (which don't play well with scope-managed cleanups).
>
> Changelog:
> - [3/7]:
> - Revert to mutex_lock/mutex_unlock in iio_buffer_attach_dmabuf(),
> as it uses cleanup GOTOs
> - [6/7]:
> - "obtained using..." -> "which can be obtained using..."
>
> [...]
Applied, thanks!
[1/7] dmaengine: Add API function dmaengine_prep_peripheral_dma_vec()
commit: 5878853fc9389e7d0988d4b465a415cf96fd14fa
[2/7] dmaengine: dma-axi-dmac: Implement device_prep_peripheral_dma_vec
commit: 74609e5686701ed8e8adc3082d15f009e327286d
[7/7] Documentation: dmaengine: Document new dma_vec API
commit: 380afccc2a55e8015adae4266e8beff96ab620be
Best regards,
--
Vinod Koul <vkoul@kernel.org>
next prev parent reply other threads:[~2024-06-21 10:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 12:27 Paul Cercueil
2024-06-20 12:27 ` [PATCH v12 1/7] dmaengine: Add API function dmaengine_prep_peripheral_dma_vec() Paul Cercueil
2024-06-20 12:27 ` [PATCH v12 2/7] dmaengine: dma-axi-dmac: Implement device_prep_peripheral_dma_vec Paul Cercueil
2024-06-20 12:27 ` [PATCH v12 3/7] iio: core: Add new DMABUF interface infrastructure Paul Cercueil
2024-06-20 16:32 ` Markus Elfring
2024-06-20 16:55 ` Lee Jones
2024-06-20 12:27 ` [PATCH v12 4/7] iio: buffer-dma: Enable support for DMABUFs Paul Cercueil
2024-06-20 12:27 ` [PATCH v12 5/7] iio: buffer-dmaengine: Support new DMABUF based userspace API Paul Cercueil
2024-06-20 12:27 ` [PATCH v12 6/7] Documentation: iio: Document high-speed DMABUF based API Paul Cercueil
2024-06-20 14:08 ` Bagas Sanjaya
2024-06-20 12:27 ` [PATCH v12 7/7] Documentation: dmaengine: Document new dma_vec API Paul Cercueil
2024-06-20 16:20 ` [PATCH v12 0/7] iio: new DMABUF based API v12 Vinod Koul
2024-06-20 19:11 ` Jonathan Cameron
2024-06-20 19:14 ` Jonathan Cameron
2024-06-21 10:08 ` Vinod Koul
2024-06-21 10:10 ` Vinod Koul
2024-06-21 10:06 ` Vinod Koul [this message]
2024-06-30 10:32 ` (subset) " Jonathan Cameron
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=171896438479.273533.11227587889239181030.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=christian.koenig@amd.com \
--cc=corbet@lwn.net \
--cc=dmaengine@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=paul@crapouillou.net \
--cc=sumit.semwal@linaro.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®