linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: linux-pci@vger.kernel.org, bhelgaas@google.com,
	iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/5] iommu: Move REQ_ACS_FLAGS out to header and rename
Date: Thu, 10 Nov 2016 13:27:13 +0100	[thread overview]
Message-ID: <20161110122713.GI9996@8bytes.org> (raw)
In-Reply-To: <20161026180134.23495.27520.stgit@gimli.home>

On Wed, Oct 26, 2016 at 12:01:34PM -0600, Alex Williamson wrote:
> Allow other parts of the kernel to see which PCI ACS flags the IOMMU
> layer considers necessary for isolation.
> 
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> Cc: Joerg Roedel <joro@8bytes.org>
> ---
>  drivers/iommu/iommu.c |   18 +++++-------------
>  include/linux/iommu.h |   11 +++++++++++
>  2 files changed, 16 insertions(+), 13 deletions(-)

Applied, thanks Alex.

  reply	other threads:[~2016-11-10 12:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-26 18:01 [PATCH 0/5] PCI: ACS enable quirk for link balancing switches Alex Williamson
2016-10-26 18:01 ` [PATCH 1/5] PCI: Make pci_std_enable_acs() non-static Alex Williamson
2016-11-14 20:59   ` Bjorn Helgaas
2016-10-26 18:01 ` [PATCH 2/5] PCI: Extract link speed & width retrieval from pcie_get_minimum_link() Alex Williamson
2016-11-14 21:02   ` Bjorn Helgaas
2016-10-26 18:01 ` [PATCH 3/5] PCI: Extract link retraining from pcie_aspm_configure_common_clock() Alex Williamson
2016-10-26 20:42   ` Alex Williamson
2016-10-26 18:01 ` [PATCH 4/5] iommu: Move REQ_ACS_FLAGS out to header and rename Alex Williamson
2016-11-10 12:27   ` Joerg Roedel [this message]
2016-11-11 22:57     ` Bjorn Helgaas
2016-11-14 12:48       ` Joerg Roedel
2016-10-26 18:01 ` [PATCH 5/5] PCI: Balance ports to avoid ACS errata on Pericom switches Alex Williamson
2016-11-14 21:03   ` Bjorn Helgaas
2016-11-14 21:21     ` Alex Williamson

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=20161110122713.GI9996@8bytes.org \
    --to=joro@8bytes.org \
    --cc=alex.williamson@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@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 NNTP newsgroup(s).