public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Baolu Lu <baolu.lu@linux.intel.com>
To: Yu Zhang <yu.c.zhang@linux.intel.com>,
	joro@8bytes.org, will@kernel.org, robin.murphy@arm.com
Cc: baolu.lu@linux.intel.com, iommu@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu: remove useless parameter in iommu_bus_init().
Date: Fri, 30 Sep 2022 16:04:41 +0800	[thread overview]
Message-ID: <badfd899-aab1-9f47-9053-e05c6bedd668@linux.intel.com> (raw)
In-Reply-To: <20220930070202.105663-1-yu.c.zhang@linux.intel.com>

On 2022/9/30 15:02, Yu Zhang wrote:
> Parameter 'ops' is no longer used by iommu_bus_init(), after
> commit 8cec63e52966 ("iommu: Remove iommu_callback_data").
> 
> So just remove it.
> 
> Signed-off-by: Yu Zhang <yu.c.zhang@linux.intel.com>
> ---
>   drivers/iommu/iommu.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
> index 3a808146b50f..bedda1e0f016 100644
> --- a/drivers/iommu/iommu.c
> +++ b/drivers/iommu/iommu.c
> @@ -1775,7 +1775,7 @@ int bus_iommu_probe(struct bus_type *bus)
>   	return ret;
>   }
>   
> -static int iommu_bus_init(struct bus_type *bus, const struct iommu_ops *ops)
> +static int iommu_bus_init(struct bus_type *bus)
>   {
>   	struct notifier_block *nb;
>   	int err;
> @@ -1836,7 +1836,7 @@ int bus_set_iommu(struct bus_type *bus, const struct iommu_ops *ops)
>   	bus->iommu_ops = ops;
>   
>   	/* Do IOMMU specific setup for this bus-type */
> -	err = iommu_bus_init(bus, ops);
> +	err = iommu_bus_init(bus);
>   	if (err)
>   		bus->iommu_ops = NULL;
>   

bus_set_iommu() has been retired. All patches are just queued in
linux-next and will show up in v6.1-rc1.

Best regards,
baolu

  reply	other threads:[~2022-09-30  8:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-30  7:02 [PATCH] iommu: remove useless parameter in iommu_bus_init() Yu Zhang
2022-09-30  8:04 ` Baolu Lu [this message]
2022-09-30  9:09   ` Yu Zhang

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=badfd899-aab1-9f47-9053-e05c6bedd668@linux.intel.com \
    --to=baolu.lu@linux.intel.com \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=will@kernel.org \
    --cc=yu.c.zhang@linux.intel.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