From: Michal Simek <michal.simek@amd.com>
To: Adrian Larumbe <adrianml@alumnos.upm.es>, Vinod Koul <vkoul@kernel.org>
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: Wed, 22 Jun 2022 17:24:35 +0200 [thread overview]
Message-ID: <687fcc3e-5ccc-78ce-fae3-98afe3dc5341@amd.com> (raw)
In-Reply-To: <20220622145021.r42vlkmokd3eqmqe@sobremesa>
On 6/22/22 16:50, Adrian Larumbe wrote:
> CAUTION: This message has originated from an External Source. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email.
>
>
> On 07.06.2022 09:33, Vinod Koul wrote:
>> 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(
>
> This is true, when I sent this I thought my at the time employer had already
> upstreamed their driver changes which make this of this API call, but apparently
> it never happened after I left.
>
> In this wise, this change series should probably go away altogether, even if
> that means it leaves that driver feature unutilised.
We also don't have a need for it. Driver which was using it is no longer used
that's why not a problem to remove it.
That's why
Acked-by: Michal Simek <michal.simek@amd.com>
Thanks,
Michal
_______________________________________________
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-22 15:25 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
2022-06-22 14:50 ` Adrian Larumbe
2022-06-22 15:24 ` Michal Simek [this message]
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=687fcc3e-5ccc-78ce-fae3-98afe3dc5341@amd.com \
--to=michal.simek@amd.com \
--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 \
--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;
as well as URLs for NNTP newsgroup(s).