Linux IOMMU Development
 help / color / mirror / Atom feed
From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>
Cc: arnd-r2nGTMty4D4@public.gmane.org,
	marc.zyngier-5wv7dgnIgG8@public.gmane.org,
	robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org,
	iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
	m-karicheri2-l0cyMroinI0@public.gmane.org,
	grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org
Subject: Re: [PATCH] of: iommu: Silence misleading warning
Date: Mon, 3 Aug 2015 16:10:08 +0200	[thread overview]
Message-ID: <20150803141008.GA20968@8bytes.org> (raw)
In-Reply-To: <12584a8f40b08b9a12e12dbd3baa9e3d2a513d1b.1437586703.git.robin.murphy-5wv7dgnIgG8@public.gmane.org>

On Wed, Jul 22, 2015 at 06:47:00PM +0100, Robin Murphy wrote:
> Printing "IOMMU is currently not supported for PCI" for every PCI device
> probed on a DT-based system proves to be both irritatingly noisy and
> confusing to users who have misinterpreted it to mean they can no longer
> use VFIO device assignment.
> 
> Since configuring DMA masks for PCI devices via of_dma_configure() has
> not in fact changed anything with regard to IOMMUs there really is nothing
> to warn about here; shut it up.
> 
> Signed-off-by: Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>
> ---
>  drivers/iommu/of_iommu.c | 8 +++++---
>  1 file changed, 5 insertions(+), 3 deletions(-)

Applied, thanks.

      parent reply	other threads:[~2015-08-03 14:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-22 17:47 [PATCH] of: iommu: Silence misleading warning Robin Murphy
     [not found] ` <12584a8f40b08b9a12e12dbd3baa9e3d2a513d1b.1437586703.git.robin.murphy-5wv7dgnIgG8@public.gmane.org>
2015-07-22 18:03   ` Marc Zyngier
2015-08-03 14: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=20150803141008.GA20968@8bytes.org \
    --to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
    --cc=arnd-r2nGTMty4D4@public.gmane.org \
    --cc=bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
    --cc=grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=m-karicheri2-l0cyMroinI0@public.gmane.org \
    --cc=marc.zyngier-5wv7dgnIgG8@public.gmane.org \
    --cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=robin.murphy-5wv7dgnIgG8@public.gmane.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