From: "Péter Ujfalusi" <peter.ujfalusi@gmail.com>
To: Yue Haibing <yuehaibing@huawei.com>, vkoul@kernel.org
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] dmaengine: ti: k3-udma: Remove unused declarations
Date: Fri, 11 Aug 2023 18:07:45 +0300 [thread overview]
Message-ID: <5b0b1366-0a77-4e27-8b9c-b5ec26817550@gmail.com> (raw)
In-Reply-To: <20230811123209.45800-1-yuehaibing@huawei.com>
On 11/08/2023 15:32, Yue Haibing wrote:
> Commit d70241913413 ("dmaengine: ti: k3-udma: Add glue layer for non DMAengine users")
> declared but never implemented these.
Acked-by: Peter Ujfalusi <peter.ujfalusi@gmail.com>
>
> Signed-off-by: Yue Haibing <yuehaibing@huawei.com>
> ---
> drivers/dma/ti/k3-udma.h | 1 -
> include/linux/dma/k3-udma-glue.h | 2 --
> 2 files changed, 3 deletions(-)
>
> diff --git a/drivers/dma/ti/k3-udma.h b/drivers/dma/ti/k3-udma.h
> index d349c6d482ae..9062a237cd16 100644
> --- a/drivers/dma/ti/k3-udma.h
> +++ b/drivers/dma/ti/k3-udma.h
> @@ -131,7 +131,6 @@ int xudma_navss_psil_unpair(struct udma_dev *ud, u32 src_thread,
> struct udma_dev *of_xudma_dev_get(struct device_node *np, const char *property);
> struct device *xudma_get_device(struct udma_dev *ud);
> struct k3_ringacc *xudma_get_ringacc(struct udma_dev *ud);
> -void xudma_dev_put(struct udma_dev *ud);
> u32 xudma_dev_get_psil_base(struct udma_dev *ud);
> struct udma_tisci_rm *xudma_dev_get_tisci_rm(struct udma_dev *ud);
>
> diff --git a/include/linux/dma/k3-udma-glue.h b/include/linux/dma/k3-udma-glue.h
> index e443be4d3b4b..57d6e7e1e091 100644
> --- a/include/linux/dma/k3-udma-glue.h
> +++ b/include/linux/dma/k3-udma-glue.h
> @@ -126,8 +126,6 @@ u32 k3_udma_glue_rx_flow_get_fdq_id(struct k3_udma_glue_rx_channel *rx_chn,
> u32 k3_udma_glue_rx_get_flow_id_base(struct k3_udma_glue_rx_channel *rx_chn);
> int k3_udma_glue_rx_get_irq(struct k3_udma_glue_rx_channel *rx_chn,
> u32 flow_num);
> -void k3_udma_glue_rx_put_irq(struct k3_udma_glue_rx_channel *rx_chn,
> - u32 flow_num);
> void k3_udma_glue_reset_rx_chn(struct k3_udma_glue_rx_channel *rx_chn,
> u32 flow_num, void *data,
> void (*cleanup)(void *data, dma_addr_t desc_dma),
--
Péter
next prev parent reply other threads:[~2023-08-11 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 12:32 Yue Haibing
2023-08-11 15:07 ` Péter Ujfalusi [this message]
2024-08-10 9:45 Yue Haibing
2024-08-28 18:16 ` Vinod Koul
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=5b0b1366-0a77-4e27-8b9c-b5ec26817550@gmail.com \
--to=peter.ujfalusi@gmail.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vkoul@kernel.org \
--cc=yuehaibing@huawei.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
all inboxes | Powered by JetHome®