xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Doug Magee <djmagee@mageenet.net>
To: xen-devel@lists.xensource.com
Cc: ian.jackson@eu.citrix.com, stefano.stabellini@eu.citrix.com
Subject: [PATCH 0 of 2] libxl_pci: verify device is assignable, rename misleading function
Date: Tue, 17 Jan 2012 10:25:05 -0500	[thread overview]
Message-ID: <patchbomb.1326813905@mnetdjm4.mageenet.host> (raw)

This series contains one patch that changes the behavior of libxl__device_pci_add to verify the device is properly assignable.  There's also a patch that renames a function so it's not misleading.

             reply	other threads:[~2012-01-17 15:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-17 15:25 Doug Magee [this message]
2012-01-17 15:25 ` [PATCH 1 of 2] libxl_pci: rename is_assigned to is_pcidev_in_array Doug Magee
2012-01-17 16:38   ` Ian Campbell
2012-01-24 15:37   ` Ian Jackson
2012-01-17 15:25 ` [PATCH 2 of 2] libxl_pci: verify device is assignable before adding to a domain Doug Magee
2012-01-17 16:41   ` Ian Campbell

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=patchbomb.1326813905@mnetdjm4.mageenet.host \
    --to=djmagee@mageenet.net \
    --cc=ian.jackson@eu.citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --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 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).