All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Julien Grall <julien.grall@arm.com>
Cc: jason@lakedaemon.net, douliyangs@gmail.com, marc.zyngier@arm.com,
	robin.murphy@arm.com, bigeasy@linutronix.de,
	linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
	miquel.raynal@bootlin.com, tglx@linutronix.de,
	logang@deltatee.com, linux-rt-users@vger.kernel.org
Subject: Re: [PATCH v3 7/7] iommu/dma-iommu: Remove iommu_dma_map_msi_msg()
Date: Fri, 3 May 2019 16:04:10 +0200	[thread overview]
Message-ID: <20190503140410.GD6731@8bytes.org> (raw)
In-Reply-To: <20190501135824.25586-8-julien.grall@arm.com>

On Wed, May 01, 2019 at 02:58:24PM +0100, Julien Grall wrote:
> A recent change split iommu_dma_map_msi_msg() in two new functions. The
> function was still implemented to avoid modifying all the callers at
> once.
> 
> Now that all the callers have been reworked, iommu_dma_map_msi_msg() can
> be removed.
> 
> Signed-off-by: Julien Grall <julien.grall@arm.com>
> Reviewed-by: Robin Murphy <robin.murphy@arm.com>
> Reviewed-by: Eric Auger <eric.auger@redhat.com>

Acked-by: Joerg Roedel <jroedel@suse.de>
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Julien Grall <julien.grall@arm.com>
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
	logang@deltatee.com, douliyangs@gmail.com,
	miquel.raynal@bootlin.com, marc.zyngier@arm.com,
	jason@lakedaemon.net, tglx@linutronix.de, robin.murphy@arm.com,
	bigeasy@linutronix.de, linux-rt-users@vger.kernel.org,
	Eric Auger <eric.auger@redhat.com>
Subject: Re: [PATCH v3 7/7] iommu/dma-iommu: Remove iommu_dma_map_msi_msg()
Date: Fri, 3 May 2019 16:04:10 +0200	[thread overview]
Message-ID: <20190503140410.GD6731@8bytes.org> (raw)
In-Reply-To: <20190501135824.25586-8-julien.grall@arm.com>

On Wed, May 01, 2019 at 02:58:24PM +0100, Julien Grall wrote:
> A recent change split iommu_dma_map_msi_msg() in two new functions. The
> function was still implemented to avoid modifying all the callers at
> once.
> 
> Now that all the callers have been reworked, iommu_dma_map_msi_msg() can
> be removed.
> 
> Signed-off-by: Julien Grall <julien.grall@arm.com>
> Reviewed-by: Robin Murphy <robin.murphy@arm.com>
> Reviewed-by: Eric Auger <eric.auger@redhat.com>

Acked-by: Joerg Roedel <jroedel@suse.de>

  reply	other threads:[~2019-05-03 14:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-01 13:58 [PATCH v3 0/7] iommu/dma-iommu: Split iommu_dma_map_msi_msg in two parts Julien Grall
2019-05-01 13:58 ` Julien Grall
2019-05-01 13:58 ` [PATCH v3 1/7] genirq/msi: Add a new field in msi_desc to store an IOMMU cookie Julien Grall
2019-05-01 13:58   ` Julien Grall
2019-05-01 13:58 ` [PATCH v3 2/7] iommu/dma-iommu: Split iommu_dma_map_msi_msg() in two parts Julien Grall
2019-05-01 13:58   ` Julien Grall
2019-05-03 14:03   ` Joerg Roedel
2019-05-03 14:03     ` Joerg Roedel
2019-05-01 13:58 ` [PATCH v3 3/7] irqchip/gicv2m: Don't map the MSI page in gicv2m_compose_msi_msg() Julien Grall
2019-05-01 13:58   ` Julien Grall
2019-05-01 13:58 ` [PATCH v3 4/7] irqchip/gic-v3-its: Don't map the MSI page in its_irq_compose_msi_msg() Julien Grall
2019-05-01 13:58   ` Julien Grall
2019-05-01 13:58 ` [PATCH v3 5/7] irqchip/ls-scfg-msi: Don't map the MSI page in ls_scfg_msi_compose_msg() Julien Grall
2019-05-01 13:58   ` Julien Grall
2019-05-01 13:58 ` [PATCH v3 6/7] irqchip/gic-v3-mbi: Don't map the MSI page in mbi_compose_m{b, s}i_msg() Julien Grall
2019-05-01 13:58   ` Julien Grall
2019-05-03 14:27   ` Marc Zyngier
2019-05-03 14:27     ` Marc Zyngier
2019-05-03 14:52     ` Robin Murphy
2019-05-03 14:52       ` Robin Murphy
2019-05-01 13:58 ` [PATCH v3 7/7] iommu/dma-iommu: Remove iommu_dma_map_msi_msg() Julien Grall
2019-05-01 13:58   ` Julien Grall
2019-05-03 14:04   ` Joerg Roedel [this message]
2019-05-03 14:04     ` 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=20190503140410.GD6731@8bytes.org \
    --to=joro@8bytes.org \
    --cc=bigeasy@linutronix.de \
    --cc=douliyangs@gmail.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jason@lakedaemon.net \
    --cc=julien.grall@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=logang@deltatee.com \
    --cc=marc.zyngier@arm.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=robin.murphy@arm.com \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.