From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: Sumit Semwal <sumit.semwal@linaro.org>
Cc: "David Airlie" <airlied@linux.ie>,
dri-devel@lists.freedesktop.org,
"Gurchetan Singh" <gurchetansingh@chromium.org>,
"Srinivas Kandagatla" <srinivas.kandagatla@linaro.org>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Dmitry Osipenko" <digetx@gmail.com>,
kernel@collabora.com,
"Marek Szyprowski" <m.szyprowski@samsung.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Leon Romanovsky" <leon@kernel.org>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
"Rodrigo Vivi" <"rodrigo. vivi"@intel.com>,
"Russell King" <linux@armlinux.org.uk>,
"Daniel Stone" <daniel@fooishbar.org>,
"Gustavo Padovan" <gustavo.padovan@collabora.com>,
"linux-arm- msm"@vger.kernel.org,
virtualization@lists.linux-foundation.org,
"Chia-I Wu" <olvaffe@gmail.com>,
linux-media@vger.kernel.org, linux-rdma@vger.kernel.org,
"Daniel Vetter" <daniel@ffwll.ch>,
intel-gfx@lists.freedesktop.org,
"Maxime Ripard" <mripard@kernel.org>,
linaro-mm-sig@lists.linaro.org,
"Christian Gmeiner" <christian.gmeiner@gmail.com>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Juergen Gross" <jgross@suse.com>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
amd-gfx@lists.freedesktop.org,
"Tomi Valkeinen" <tomba@kernel.org>,
"Tomeu Vizoso" <tomeu.vizoso@collabora.com>,
"Gert Wollny" <gert.wollny@collabora.com>,
"Pan, Xinhui" <Xinhui.Pan@amd.com>,
linux-kernel@vger.kernel.org, "Tomasz Figa" <tfiga@chromium.org>,
"Oleksandr Tyshchenko" <oleksandr_tyshchenko@epam.com>,
"Qiang Yu" <yuq825@gmail.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Amol Maheshwari" <amahesh@qti.qualcomm.com>,
"Christian König" <christian.koenig@amd.com>,
"Lucas Stach" <l.stach@pengutronix.de>
Subject: Re: [Intel-gfx] [PATCH v5 15/21] dma-buf: Move dma_buf_vmap() to dynamic locking specification
Date: Wed, 21 Sep 2022 13:29:07 +0300 [thread overview]
Message-ID: <333ce447-05e0-a127-6f8e-2ffd75e0c992@collabora.com> (raw)
In-Reply-To: <CAO_48GFtLjR657nO+yh9KwsrWbNmGVsf7srHj19biO+NauYt4w@mail.gmail.com>
On 9/20/22 17:13, Sumit Semwal wrote:
> Hi Dmitry,
>
> Thanks very much for the series.
>
> On Wed, 14 Sept 2022 at 00:59, Dmitry Osipenko
> <dmitry.osipenko@collabora.com> wrote:
>>
>> Move dma_buf_vmap/vunmap_unlocked() functions to the dynamic locking
>> specification by asserting that the reservation lock is held.
> Thanks for the patch; just a minor nit - I think you mean dma_buf_vmap
> / vunmap() here, and not _unlocked?
Yes, the _unlocked should be dropped here. Thank you for the review!
--
Best regards,
Dmitry
next prev parent reply other threads:[~2022-09-21 10:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 19:27 [Intel-gfx] [PATCH v5 00/21] Move all drivers to a common dma-buf locking convention Dmitry Osipenko
2022-09-13 19:27 ` [Intel-gfx] [PATCH v5 01/21] dma-buf: Add unlocked variant of vmapping functions Dmitry Osipenko
2022-09-13 19:27 ` [Intel-gfx] [PATCH v5 02/21] dma-buf: Add unlocked variant of attachment-mapping functions Dmitry Osipenko
2022-09-13 19:27 ` [Intel-gfx] [PATCH v5 03/21] drm/gem: Take reservation lock for vmap/vunmap operations Dmitry Osipenko
2022-09-13 19:27 ` [Intel-gfx] [PATCH v5 04/21] drm/prime: Prepare to dynamic dma-buf locking specification Dmitry Osipenko
2022-09-13 19:27 ` [Intel-gfx] [PATCH v5 05/21] drm/armada: " Dmitry Osipenko
2022-09-13 19:27 ` [Intel-gfx] [PATCH v5 06/21] drm/i915: " Dmitry Osipenko
2022-09-15 13:19 ` Ruhl, Michael J
2022-09-13 19:27 ` [Intel-gfx] [PATCH v5 07/21] drm/omapdrm: " Dmitry Osipenko
2022-09-13 19:27 ` [Intel-gfx] [PATCH v5 08/21] drm/tegra: " Dmitry Osipenko
2022-09-13 19:27 ` [Intel-gfx] [PATCH v5 09/21] drm/etnaviv: " Dmitry Osipenko
2022-09-13 19:27 ` [Intel-gfx] [PATCH v5 10/21] RDMA/umem: " Dmitry Osipenko
2022-09-13 19:27 ` [Intel-gfx] [PATCH v5 11/21] misc: fastrpc: " Dmitry Osipenko
2022-09-13 19:27 ` [Intel-gfx] [PATCH v5 12/21] xen/gntdev: " Dmitry Osipenko
2022-09-13 19:27 ` [Intel-gfx] [PATCH v5 13/21] media: videobuf2: " Dmitry Osipenko
2022-09-13 19:27 ` [Intel-gfx] [PATCH v5 14/21] media: tegra-vde: " Dmitry Osipenko
2022-09-13 19:27 ` [Intel-gfx] [PATCH v5 15/21] dma-buf: Move dma_buf_vmap() to dynamic " Dmitry Osipenko
2022-09-20 14:13 ` Sumit Semwal
2022-09-21 10:29 ` Dmitry Osipenko [this message]
2022-09-13 19:27 ` [Intel-gfx] [PATCH v5 16/21] dma-buf: Move dma_buf_attach() " Dmitry Osipenko
2022-09-13 19:27 ` [Intel-gfx] [PATCH v5 17/21] dma-buf: Move dma_buf_map_attachment() " Dmitry Osipenko
2022-09-13 19:27 ` [Intel-gfx] [PATCH v5 18/21] dma-buf: Move dma_buf_mmap() " Dmitry Osipenko
2022-09-13 19:27 ` [Intel-gfx] [PATCH v5 19/21] dma-buf: Document dynamic locking convention Dmitry Osipenko
2022-09-13 19:27 ` [Intel-gfx] [PATCH v5 20/21] media: videobuf2: Stop using internal dma-buf lock Dmitry Osipenko
2022-09-13 19:27 ` [Intel-gfx] [PATCH v5 21/21] dma-buf: Remove obsoleted internal lock Dmitry Osipenko
2022-09-14 0:06 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for Move all drivers to a common dma-buf locking convention Patchwork
2022-09-20 14:16 ` [Intel-gfx] [PATCH v5 00/21] " Sumit Semwal
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=333ce447-05e0-a127-6f8e-2ffd75e0c992@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc="linux-arm- msm"@vger.kernel.org \
--cc="rodrigo. vivi"@intel.com \
--cc=Xinhui.Pan@amd.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=amahesh@qti.qualcomm.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.gmeiner@gmail.com \
--cc=christian.koenig@amd.com \
--cc=daniel.almeida@collabora.com \
--cc=daniel@ffwll.ch \
--cc=daniel@fooishbar.org \
--cc=digetx@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gert.wollny@collabora.com \
--cc=gurchetansingh@chromium.org \
--cc=gustavo.padovan@collabora.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jgg@ziepe.ca \
--cc=jgross@suse.com \
--cc=kernel@collabora.com \
--cc=kraxel@redhat.com \
--cc=l.stach@pengutronix.de \
--cc=leon@kernel.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@kernel.org \
--cc=mripard@kernel.org \
--cc=oleksandr_tyshchenko@epam.com \
--cc=olvaffe@gmail.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=sstabellini@kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=tfiga@chromium.org \
--cc=tomba@kernel.org \
--cc=tomeu.vizoso@collabora.com \
--cc=tzimmermann@suse.de \
--cc=virtualization@lists.linux-foundation.org \
--cc=yuq825@gmail.com \
/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