DMA Engine development
 help / color / mirror / Atom feed
From: Dave Jiang <dave.jiang@intel.com>
To: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>, fenghua.yu@intel.com
Cc: vkoul@kernel.org, dmaengine@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH] dmaengine: idxd: Remove the unused function set_completion_address()
Date: Mon, 12 Dec 2022 08:32:43 -0700	[thread overview]
Message-ID: <4ea86d83-610a-9a14-fda8-e25bd9d4addb@intel.com> (raw)
In-Reply-To: <20221212033514.5831-1-jiapeng.chong@linux.alibaba.com>



On 12/11/2022 8:35 PM, Jiapeng Chong wrote:
> The function set_completion_address is defined in the dma.c file, but not
> called elsewhere, so remove this unused function.
> 
> drivers/dma/idxd/dma.c:66:20: warning: unused function 'set_completion_address'.
> 
> Link: https://bugzilla.openanolis.cn/show_bug.cgi?id=3416
> Reported-by: Abaci Robot <abaci@linux.alibaba.com>
> Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>

Acked-by: Dave Jiang <dave.jiang@intel.com>
Thanks for the cleanup
> ---
>   drivers/dma/idxd/dma.c | 6 ------
>   1 file changed, 6 deletions(-)
> 
> diff --git a/drivers/dma/idxd/dma.c b/drivers/dma/idxd/dma.c
> index e0874cb4721c..eb35ca313684 100644
> --- a/drivers/dma/idxd/dma.c
> +++ b/drivers/dma/idxd/dma.c
> @@ -63,12 +63,6 @@ static void op_flag_setup(unsigned long flags, u32 *desc_flags)
>   		*desc_flags |= IDXD_OP_FLAG_RCI;
>   }
>   
> -static inline void set_completion_address(struct idxd_desc *desc,
> -					  u64 *compl_addr)
> -{
> -		*compl_addr = desc->compl_dma;
> -}
> -
>   static inline void idxd_prep_desc_common(struct idxd_wq *wq,
>   					 struct dsa_hw_desc *hw, char opcode,
>   					 u64 addr_f1, u64 addr_f2, u64 len,

  reply	other threads:[~2022-12-12 15:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-12  3:35 [PATCH] dmaengine: idxd: Remove the unused function set_completion_address() Jiapeng Chong
2022-12-12 15:32 ` Dave Jiang [this message]
2022-12-28  6:59 ` 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=4ea86d83-610a-9a14-fda8-e25bd9d4addb@intel.com \
    --to=dave.jiang@intel.com \
    --cc=abaci@linux.alibaba.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=fenghua.yu@intel.com \
    --cc=jiapeng.chong@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.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