Linux IOMMU Development
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Dmitry Osipenko <digetx@gmail.com>, Baoquan He <bhe@redhat.com>,
	iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] iommu: Kerneldoc improvements
Date: Tue, 26 Feb 2019 11:10:55 +0100	[thread overview]
Message-ID: <20190226101055.GD20740@8bytes.org> (raw)
In-Reply-To: <20190220130053.784-1-geert+renesas@glider.be>

Hi Geert,

On Wed, Feb 20, 2019 at 02:00:50PM +0100, Geert Uytterhoeven wrote:
> This series contains a fix for an incorrect kerneldoc parameter, and
> adds the missing kerneldoc for two recently added IOMMU methods.
> 
> Thanks!
> 
> Geert Uytterhoeven (3):
>   iommu: Fix kerneldoc for iommu_ops.flush_iotlb_all()
>   iommu: Document iommu_ops.iotlb_sync_map()
>   iommu: Document iommu_ops.is_attach_deferred()
> 
>  include/linux/iommu.h | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)

Applied patches 2 and 3, I already have a change similar to patch 1 in
the tree.

Thanks,

	Joerg

      parent reply	other threads:[~2019-02-26 10:10 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
2019-02-20 13:00 ` [PATCH 3/3] iommu: Document iommu_ops.is_attach_deferred() Geert Uytterhoeven
2019-02-26 10:10 ` 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=20190226101055.GD20740@8bytes.org \
    --to=joro@8bytes.org \
    --cc=bhe@redhat.com \
    --cc=digetx@gmail.com \
    --cc=geert+renesas@glider.be \
    --cc=iommu@lists.linux-foundation.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