public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joerg.roedel@amd.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Joerg Roedel <joro@8bytes.org>, <aik@ozlabs.ru>,
	<benh@kernel.crashing.org>, <linux-kernel@vger.kernel.org>,
	<iommu@lists.linux-foundation.org>, <linux-pci@vger.kernel.org>,
	<dwmw2@infradead.org>, <david@gibson.dropbear.id.au>
Subject: Re: [PATCH v3 0/5] PCI: Prep for VFIO and IOMMU Groups
Date: Tue, 12 Jun 2012 18:04:27 +0200	[thread overview]
Message-ID: <20120612160427.GE2624@amd.com> (raw)
In-Reply-To: <CAErSpo6J61+XhtEeXdE-5Evhs-SJ4=3iEZDAXGuRi9moAU8KhQ@mail.gmail.com>

Hi Bjorn,

On Tue, Jun 12, 2012 at 09:55:59AM -0600, Bjorn Helgaas wrote:
> On Tue, Jun 12, 2012 at 12:20 AM, Joerg Roedel <joro@8bytes.org> wrote:
> > Hi Bjorn,
> >
> > On Mon, Jun 11, 2012 at 06:59:25PM -0600, Bjorn Helgaas wrote:
> >> 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.
> >
> > Great. Do you applied them directly to your next branch or do you have
> > them in a seperate branch I can pull in to merge the IOMMU Groups
> > patches on-top? The later would be really good :)
> 
> Hi Joerg, I have Alex's patches on a separate topic branch.  I folded
> in the pci_get_dev() fix and pushed it to here:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git
> topic/alex-vfio-prep
> 
> This is also included in my "next" branch.


Great, thanks. I will pull in this branch and apply Alex' IOMMU group
code on-top.


	Joerg

-- 
AMD Operating System Research Center

Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach
General Managers: Alberto Bozzo
Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632


      reply	other threads:[~2012-06-12 16:05 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 ` [PATCH v3 0/5] PCI: Prep for VFIO and IOMMU Groups Bjorn Helgaas
2012-06-12  6:20   ` Joerg Roedel
2012-06-12 15:55     ` Bjorn Helgaas
2012-06-12 16:04       ` 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=20120612160427.GE2624@amd.com \
    --to=joerg.roedel@amd.com \
    --cc=aik@ozlabs.ru \
    --cc=benh@kernel.crashing.org \
    --cc=bhelgaas@google.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.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