public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Yue Haibing <yuehaibing@huawei.com>
Cc: suravee.suthikulpanit@amd.com, will@kernel.org,
	robin.murphy@arm.com, vasant.hegde@amd.com,
	iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] iommu/amd: Remove unused declarations
Date: Thu, 17 Aug 2023 12:58:40 +0200	[thread overview]
Message-ID: <ZN39YE8MCF6CTp9F@8bytes.org> (raw)
In-Reply-To: <20230814135502.4808-1-yuehaibing@huawei.com>

On Mon, Aug 14, 2023 at 09:55:02PM +0800, Yue Haibing wrote:
> Commit aafd8ba0ca74 ("iommu/amd: Implement add_device and remove_device")
> removed the implementations but left declarations in place. Remove it.
> 
> Signed-off-by: Yue Haibing <yuehaibing@huawei.com>
> ---
>  drivers/iommu/amd/amd_iommu.h | 3 ---
>  1 file changed, 3 deletions(-)

Applied, thanks.

      reply	other threads:[~2023-08-17 10:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-14 13:55 [PATCH -next] iommu/amd: Remove unused declarations Yue Haibing
2023-08-17 10:58 ` Joerg Roedel [this message]

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=ZN39YE8MCF6CTp9F@8bytes.org \
    --to=joro@8bytes.org \
    --cc=iommu@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=vasant.hegde@amd.com \
    --cc=will@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