From: Paul Cercueil <paul@crapouillou.net>
To: "Markus Elfring" <Markus.Elfring@web.de>,
lkp@intel.com, "Nuno Sá" <nuno.sa@analog.com>,
linux-iio@vger.kernel.org, dmaengine@vger.kernel.org,
linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org,
"Christian König" <christian.koenig@amd.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Vinod Koul" <vkoul@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
LKML <linux-kernel@vger.kernel.org>,
linux-doc@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [v11 3/7] iio: core: Add new DMABUF interface infrastructure
Date: Wed, 19 Jun 2024 13:30:27 +0200 [thread overview]
Message-ID: <e948cd137da8e4f97bfbf7ef68a5450476aeee0c.camel@crapouillou.net> (raw)
In-Reply-To: <cbcfb64a-e5c2-41a7-8847-227d4f6872de@web.de>
Le mercredi 19 juin 2024 à 13:13 +0200, Markus Elfring a écrit :
> > > Would you dare to transform the remaining goto chain into further
> > > applications
> > > of scope-based resource management?
> >
> > We discussed this after v6 or v7, DRM/DMABUF maintainers were not
> > keen
> > on doing that *just yet*.
>
> * Would you like to add any links for corresponding development
> discussions?
https://lore.kernel.org/linux-iio/219abc43b4fdd4a13b307ed2efaa0e6869e68e3f.camel@gmail.com/T/#eefd360069c4261aec9621fafde30924706571c94
(and responses below)
It's more nuanced than I remembered. Christian was OK to add cleanup.h
support to the DMABUF code as long as the examples were updated as
well, but those aren't good candidates as they don't free up the
resources in all code paths.
>
> * Will the desire grow for further collateral evolution according to
> affected software components?
Not sure what you mean by that.
Cheers,
-Paul
next prev parent reply other threads:[~2024-06-19 11:30 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 10:02 [PATCH v11 0/7] iio: new DMABUF based API v11 Paul Cercueil
2024-06-18 10:02 ` [PATCH v11 1/7] dmaengine: Add API function dmaengine_prep_peripheral_dma_vec() Paul Cercueil
2024-06-18 10:02 ` [PATCH v11 2/7] dmaengine: dma-axi-dmac: Implement device_prep_peripheral_dma_vec Paul Cercueil
2024-06-18 10:02 ` [PATCH v11 3/7] iio: core: Add new DMABUF interface infrastructure Paul Cercueil
2024-06-19 3:15 ` kernel test robot
2024-06-19 5:57 ` Nuno Sá
2024-06-19 10:03 ` [v11 " Markus Elfring
2024-06-19 10:09 ` Paul Cercueil
2024-06-19 11:13 ` Markus Elfring
2024-06-19 11:30 ` Paul Cercueil [this message]
2024-06-19 11:56 ` Markus Elfring
2024-06-19 12:21 ` Paul Cercueil
2024-06-19 12:42 ` Nuno Sá
2024-06-20 10:45 ` Markus Elfring
2024-06-20 16:09 ` Vinod Koul
2024-06-20 17:05 ` Lee Jones
2024-06-21 7:09 ` Vinod Koul
2024-06-21 7:18 ` Nuno Sá
2024-06-21 7:36 ` Markus Elfring
2024-06-21 7:44 ` Lee Jones
2024-06-21 7:27 ` Markus Elfring
2024-06-21 7:51 ` Lee Jones
2024-06-21 8:10 ` [RFC] Patch review challenges Markus Elfring
2024-06-21 8:21 ` Lee Jones
2024-06-19 11:43 ` [PATCH v11 3/7] iio: core: Add new DMABUF interface infrastructure Markus Elfring
2024-06-19 12:16 ` Paul Cercueil
2024-06-19 13:28 ` Markus Elfring
2024-06-18 10:02 ` [PATCH v11 4/7] iio: buffer-dma: Enable support for DMABUFs Paul Cercueil
2024-06-18 10:03 ` [PATCH v11 5/7] iio: buffer-dmaengine: Support new DMABUF based userspace API Paul Cercueil
2024-06-18 10:03 ` [PATCH v11 6/7] Documentation: iio: Document high-speed DMABUF based API Paul Cercueil
2024-06-19 12:22 ` Bagas Sanjaya
2024-06-18 10:03 ` [PATCH v11 7/7] Documentation: dmaengine: Document new dma_vec API Paul Cercueil
2024-06-19 12:34 ` Bagas Sanjaya
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=e948cd137da8e4f97bfbf7ef68a5450476aeee0c.camel@crapouillou.net \
--to=paul@crapouillou.net \
--cc=Markus.Elfring@web.de \
--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=lkp@intel.com \
--cc=nuno.sa@analog.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rdunlap@infradead.org \
--cc=sumit.semwal@linaro.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 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®