From: Joerg Roedel <joerg.roedel@amd.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Alex Williamson <alex.williamson@redhat.com>,
<linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<bhelgaas@google.com>
Subject: Re: [PATCH 0/2] PCI: PRI/PASSID cleanup and fix
Date: Mon, 28 Nov 2011 11:40:55 +0100 [thread overview]
Message-ID: <20111128104055.GI11876@amd.com> (raw)
In-Reply-To: <20111123144510.56ff6d1d@jbarnes-desktop>
On Wed, Nov 23, 2011 at 02:45:10PM -0800, Jesse Barnes wrote:
> On Wed, 23 Nov 2011 11:47:05 +0100
> Joerg Roedel <joerg.roedel@amd.com> wrote:
>
> > On Fri, Nov 11, 2011 at 10:06:23AM -0700, Alex Williamson wrote:
> > > Alex Williamson (2):
> > > PCI: More PRI/PASID cleanup
> > > PCI: Enable is not exposed as a PASID capability
> >
> > For both:
> >
> > Reviewed-by: Joerg Roedel <joerg.roedel@amd.com>
> > Tested-by: Joerg Roedel <joerg.roedel@amd.com>
>
> Ok, thanks guys. I'll queue these up after Thanksgiving.
>
> --
> Jesse Barnes, Intel Open Source Technology Center
Great. Can you provide a seperate branch with these changes that I can
pull into my tree, please? I have upcoming changes that will conflict
with these patches. And I would like to solve them before merge.
Joerg
--
AMD Operating System Research Center
Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2011-11-28 10:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 17:06 [PATCH 0/2] PCI: PRI/PASSID cleanup and fix Alex Williamson
2011-11-11 17:06 ` [PATCH 1/2] PCI: Enable is not exposed as a PASID capability Alex Williamson
2011-11-11 17:07 ` [PATCH 2/2] PCI: More PRI/PASID cleanup Alex Williamson
2011-11-11 17:40 ` Jesse Barnes
2011-11-23 10:47 ` [PATCH 0/2] PCI: PRI/PASSID cleanup and fix Joerg Roedel
2011-11-23 22:45 ` Jesse Barnes
2011-11-28 10:40 ` Joerg Roedel [this message]
2011-12-05 18:24 ` Jesse Barnes
2011-12-06 10:05 ` 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=20111128104055.GI11876@amd.com \
--to=joerg.roedel@amd.com \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=jbarnes@virtuousgeek.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 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.