From: Vinod Koul <vkoul@kernel.org>
To: Adrian Larumbe <adrianml@alumnos.upm.es>
Cc: Christoph Hellwig <hch@lst.de>,
michal.simek@xilinx.com, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] dmaengine: remove DMA_MEMCPY_SG once again
Date: Tue, 7 Jun 2022 09:33:33 +0530 [thread overview]
Message-ID: <Yp7OFYFp7oyjyKx1@matsya> (raw)
In-Reply-To: <20220606195455.qmq3yu6mc6g4rmm2@sobremesa>
On 06-06-22, 20:54, Adrian Larumbe wrote:
> >On 06.06.2022 23:23, Vinod Koul wrote:
> >On 06-06-22, 09:47, Christoph Hellwig wrote:
> >> This was removed before due to the complete lack of users, but
> >> 3218910fd585 ("dmaengine: Add core function and capability check for
> >> DMA_MEMCPY_SG") and 29cf37fa6dd9 ("dmaengine: Add consumer for the new
> >> DMA_MEMCPY_SG API function.") added it back despite still not having
> >> any users whatsoever.
> >>
> >> Fixes: 3218910fd585 ("dmaengine: Add core function and capability check for DMA_MEMCPY_SG")
> >> Fixes: 29cf37fa6dd9 ("dmaengine: Add consumer for the new DMA_MEMCPY_SG API function.")
> >
> >This is consumer of the driver API and it was bought back with the
> >premise that user will also come...
>
> It's commit 29cf37fa6dd9 ("dmaengine: Add consumer for the new DMA_MEMCPY_SG API function.")
>
> The two previous commits add the new driver API callback and document it.
>
> >Adrianm, Michal any reason why user is not mainline yet..?
>
> Just double checked the mainline, and all three commits are there.
There are no clients in mainline which call this API. There is a driver
which implements this API, but no users...
$ git grep dmaengine_prep_dma_memcpy_sg
include/linux/dmaengine.h:static inline struct dma_async_tx_descriptor *dmaengine_prep_dma_memcpy_sg(
--
~Vinod
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-07 4:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 7:47 [PATCH] dmaengine: remove DMA_MEMCPY_SG once again Christoph Hellwig
2022-06-06 17:53 ` Vinod Koul
2022-06-06 19:54 ` Adrian Larumbe
2022-06-07 4:03 ` Vinod Koul [this message]
2022-06-22 14:50 ` Adrian Larumbe
2022-06-22 15:24 ` Michal Simek
2022-06-22 18:34 ` Pandey, Radhey Shyam
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=Yp7OFYFp7oyjyKx1@matsya \
--to=vkoul@kernel.org \
--cc=adrianml@alumnos.upm.es \
--cc=dmaengine@vger.kernel.org \
--cc=hch@lst.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.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;
as well as URLs for NNTP newsgroup(s).