mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
	Joerg Roedel <joro@8bytes.org>
Cc: Baoquan He <bhe@redhat.com>,
	iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] iommu: Document iommu_ops.iotlb_sync_map()
Date: Wed, 20 Feb 2019 16:39:14 +0300	[thread overview]
Message-ID: <2fff24cd-5591-8ac9-3665-6d9a6e1689c1@gmail.com> (raw)
In-Reply-To: <20190220130053.784-3-geert+renesas@glider.be>

20.02.2019 16:00, Geert Uytterhoeven пишет:
> Add missing kerneldoc for iommu_ops.iotlb_sync_map().
> 
> Fixes: 1d7ae53b152dbc5b ("iommu: Introduce iotlb_sync_map callback")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
>  include/linux/iommu.h | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/include/linux/iommu.h b/include/linux/iommu.h
> index 848fb07026b67169..3ed5d372b090af54 100644
> --- a/include/linux/iommu.h
> +++ b/include/linux/iommu.h
> @@ -169,6 +169,7 @@ struct iommu_resv_region {
>   * @unmap: unmap a physically contiguous memory region from an iommu domain
>   * @flush_iotlb_all: Synchronously flush all hardware TLBs for this domain
>   * @iotlb_range_add: Add a given iova range to the flush queue for this domain
> + * @iotlb_sync_map: Sync mappings created recently using @map to the hardware
>   * @iotlb_sync: Flush all queued ranges from the hardware TLBs and empty flush
>   *            queue
>   * @iova_to_phys: translate iova to physical address
> 

Pretty sure there was a kerneldoc in some version of the original patch that introduced the iotlb_sync_map(), but probably it got lost after a rebase. The kerneldoc comment is correct, thank you! BTW, for some reason gmail marked this series as a spam, maybe you need to check the email headers and whatnot.

Reviewed-by: Dmitry Osipenko <digetx@gmail.com>

  reply	other threads:[~2019-02-20 13:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-20 13:00 [PATCH 0/3] iommu: Kerneldoc improvements Geert Uytterhoeven
2019-02-20 13:00 ` [PATCH 1/3] iommu: Fix kerneldoc for iommu_ops.flush_iotlb_all() Geert Uytterhoeven
2019-02-20 13:00 ` [PATCH 2/3] iommu: Document iommu_ops.iotlb_sync_map() Geert Uytterhoeven
2019-02-20 13:39   ` Dmitry Osipenko [this message]
2019-02-20 13:00 ` [PATCH 3/3] iommu: Document iommu_ops.is_attach_deferred() Geert Uytterhoeven
2019-02-26 10:10 ` [PATCH 0/3] iommu: Kerneldoc improvements Joerg Roedel

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=2fff24cd-5591-8ac9-3665-6d9a6e1689c1@gmail.com \
    --to=digetx@gmail.com \
    --cc=bhe@redhat.com \
    --cc=geert+renesas@glider.be \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®