kvm-ppc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: kvm@vger.kernel.org, kvm-ppc@vger.kernel.org
Subject: Re: [PATCH kernel] vfio/spapr_tce: Fix the comment
Date: Fri, 22 Jul 2022 22:50:27 +0000	[thread overview]
Message-ID: <20220722165027.13dc2045.alex.williamson@redhat.com> (raw)
In-Reply-To: <20220714080912.3713509-1-aik@ozlabs.ru>

On Thu, 14 Jul 2022 18:09:12 +1000
Alexey Kardashevskiy <aik@ozlabs.ru> wrote:

> Grepping for "iommu_ops" finds this spot and gives wrong impression
> that iommu_ops is used in here, fix the comment.
> 
> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
> ---
>  drivers/vfio/vfio_iommu_spapr_tce.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/vfio/vfio_iommu_spapr_tce.c b/drivers/vfio/vfio_iommu_spapr_tce.c
> index 708a95e61831..cd7b9c136889 100644
> --- a/drivers/vfio/vfio_iommu_spapr_tce.c
> +++ b/drivers/vfio/vfio_iommu_spapr_tce.c
> @@ -1266,7 +1266,7 @@ static int tce_iommu_attach_group(void *iommu_data,
>  		goto unlock_exit;
>  	}
>  
> -	/* Check if new group has the same iommu_ops (i.e. compatible) */
> +	/* Check if new group has the same iommu_table_group_ops (i.e. compatible) */
>  	list_for_each_entry(tcegrp, &container->group_list, next) {
>  		struct iommu_table_group *table_group_tmp;
>  

Applied to vfio next branch for v5.20 with a conversion to a multi-line
comment to avoid the long line.  Thanks,

Alex

      reply	other threads:[~2022-07-22 22:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-14  8:09 [PATCH kernel] vfio/spapr_tce: Fix the comment Alexey Kardashevskiy
2022-07-22 22:50 ` Alex Williamson [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=20220722165027.13dc2045.alex.williamson@redhat.com \
    --to=alex.williamson@redhat.com \
    --cc=aik@ozlabs.ru \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.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 read-only IMAP folder(s) and NNTP newsgroup(s).