dmaengine.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Jiang <dave.jiang@intel.com>
To: Gaosheng Cui <cuigaosheng1@huawei.com>,
	vkoul@kernel.org, vinod.koul@intel.com
Cc: dmaengine@vger.kernel.org
Subject: Re: [PATCH] dmaengine: ioat: remove unused declarations in dma.h
Date: Mon, 12 Sep 2022 08:26:13 -0700	[thread overview]
Message-ID: <a5e1de92-c3a3-50b5-5ebb-322aec19a612@intel.com> (raw)
In-Reply-To: <20220911091817.3214271-1-cuigaosheng1@huawei.com>


On 9/11/2022 2:18 AM, Gaosheng Cui wrote:
> ioat_ring_alloc_order and ioat_ring_max_alloc_order have
> been removed since commit cd60cd96137f ("dmaengine: IOATDMA:
> Removing descriptor ring reshape"), so remove them.
>
> Signed-off-by: Gaosheng Cui <cuigaosheng1@huawei.com>

Acked-by: Dave Jiang <dave.jiang@intel.com>

Thanks.

> ---
>   drivers/dma/ioat/dma.h | 2 --
>   1 file changed, 2 deletions(-)
>
> diff --git a/drivers/dma/ioat/dma.h b/drivers/dma/ioat/dma.h
> index 140cfe3782fb..35e06b382603 100644
> --- a/drivers/dma/ioat/dma.h
> +++ b/drivers/dma/ioat/dma.h
> @@ -196,10 +196,8 @@ extern const struct sysfs_ops ioat_sysfs_ops;
>   extern struct ioat_sysfs_entry ioat_version_attr;
>   extern struct ioat_sysfs_entry ioat_cap_attr;
>   extern int ioat_pending_level;
> -extern int ioat_ring_alloc_order;
>   extern struct kobj_type ioat_ktype;
>   extern struct kmem_cache *ioat_cache;
> -extern int ioat_ring_max_alloc_order;
>   extern struct kmem_cache *ioat_sed_cache;
>   
>   static inline struct ioatdma_chan *to_ioat_chan(struct dma_chan *c)

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-11  9:18 [PATCH] dmaengine: ioat: remove unused declarations in dma.h Gaosheng Cui
2022-09-12 15:26 ` Dave Jiang [this message]
2022-09-29 17:07 ` 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=a5e1de92-c3a3-50b5-5ebb-322aec19a612@intel.com \
    --to=dave.jiang@intel.com \
    --cc=cuigaosheng1@huawei.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=vinod.koul@intel.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).