linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: linux-pci@vger.kernel.org, benh@kernel.crashing.org,
	aik@ozlabs.ru, david@gibson.dropbear.id.au, joerg.roedel@amd.com,
	dwmw2@infradead.org, konrad.wilk@oracle.com,
	iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
	ddutile@redhat.com
Subject: Re: [PATCH v3 0/5] PCI: Prep for VFIO and IOMMU Groups
Date: Mon, 11 Jun 2012 18:59:25 -0600	[thread overview]
Message-ID: <CAErSpo434tDtnSOxB_REG2jFNrZL=aZERWTmmK-cdjqM4z6yWg@mail.gmail.com> (raw)
In-Reply-To: <20120611152021.25959.71601.stgit@bling.home>

On Mon, Jun 11, 2012 at 8:26 AM, Alex Williamson
<alex.williamson@redhat.com> wrote:
> v3:
>  - Small change to device specific ACS check to allow quirk to
>   support yes/no/pass type functionality. (no change to other
>   patches and no trickle down through IOMMU series)
>
> Bjorn, what's needed to get these in?  Thanks,

Sorry for the delay.  I applied these to my "next" branch (headed for
3.6).  I didn't feel comfortable pushing them towards 3.5 since
they're not bugfixes, and they haven't been in -next yet.

Bjorn

  parent reply	other threads:[~2012-06-12  0:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-11 15:26 [PATCH v3 0/5] PCI: Prep for VFIO and IOMMU Groups Alex Williamson
2012-06-11 15:26 ` [PATCH v3 1/5] pci: Add PCI DMA source ID quirk Alex Williamson
2012-06-11 15:27 ` [PATCH v3 2/5] pci: Add ACS validation utility Alex Williamson
2012-06-11 15:27 ` [PATCH v3 3/5] pci: export pci_user functions for use by other drivers Alex Williamson
2012-06-11 15:27 ` [PATCH v3 4/5] pci: Create common pcibios_err_to_errno Alex Williamson
2012-06-11 15:27 ` [PATCH v3 5/5] pci: Misc pci_reg additions Alex Williamson
2012-06-12  0:59 ` Bjorn Helgaas [this message]
2012-06-12  6:20   ` [PATCH v3 0/5] PCI: Prep for VFIO and IOMMU Groups Joerg Roedel
2012-06-12 15:55     ` Bjorn Helgaas
2012-06-12 16: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='CAErSpo434tDtnSOxB_REG2jFNrZL=aZERWTmmK-cdjqM4z6yWg@mail.gmail.com' \
    --to=bhelgaas@google.com \
    --cc=aik@ozlabs.ru \
    --cc=alex.williamson@redhat.com \
    --cc=benh@kernel.crashing.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=ddutile@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joerg.roedel@amd.com \
    --cc=konrad.wilk@oracle.com \
    --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).