From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: [PATCH PV_OPS]
Date: Wed, 9 Dec 2009 15:01:56 -0500 [thread overview]
Message-ID: <20091209200156.GA4656@phenom.dumpdata.com> (raw)
In-Reply-To: <4B200245.7000508@goop.org>
On Wed, Dec 09, 2009 at 12:02:13PM -0800, Jeremy Fitzhardinge wrote:
> On 12/09/09 08:29, Konrad Rzeszutek Wilk wrote:
>> Attached are couple of patches for pciback to remove the xenbus_walk usage and
>> replace it with a registration list type mechanism as discussed in previous
>> e-mail correspondence.
>>
>> Also the last two remove functions that are not currently used.
>>
>
> What changeset are they against?
This is on top of the latest (origin/xen/master). Let me
rebase is on top of the xen/dom0/pciback and re-send the patches.
prev parent reply other threads:[~2009-12-09 20:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 16:29 [PATCH PV_OPS] Konrad Rzeszutek Wilk
2009-12-09 16:29 ` [PATCH 1/6] Revert "In xen_create_msi_irq, extract the domain id of the MSI device." Konrad Rzeszutek Wilk
2009-12-09 16:29 ` [PATCH 2/6] [xen-pci] Provide a mechanism to register domain owner of a PCI device Konrad Rzeszutek Wilk
2009-12-09 16:29 ` [PATCH 3/6] [events] Check if the PCI device is owner by a domain different than DOMID_SELF Konrad Rzeszutek Wilk
2009-12-09 16:29 ` [PATCH 4/6] [pciback] Register the owner (domain) of the PCI device Konrad Rzeszutek Wilk
2009-12-09 16:29 ` [PATCH 5/6] [pciback] Remove the vestiges of CONFIG_PCI_GUESTDEV Konrad Rzeszutek Wilk
2009-12-09 16:29 ` [PATCH 6/6] [pciback] Remove deprecated routine to find domain owner of PCI device Konrad Rzeszutek Wilk
2009-12-09 16:47 ` [PATCH] [pciback] Fix build issues Konrad Rzeszutek Wilk
2009-12-09 20:02 ` [PATCH PV_OPS] Jeremy Fitzhardinge
2009-12-09 20:01 ` Konrad Rzeszutek Wilk [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=20091209200156.GA4656@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=jeremy@goop.org \
--cc=xen-devel@lists.xensource.com \
/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.