From: Keir Fraser <keir@xensource.com>
To: "Petersson, Mats" <Mats.Petersson@amd.com>,
xen-devel@lists.xensource.com
Subject: Re: Shouldn't XendDomainInfo.py: _releaseDevices call destroyDevice?
Date: Wed, 16 May 2007 14:42:19 +0100 [thread overview]
Message-ID: <C270C8CB.F080%keir@xensource.com> (raw)
In-Reply-To: <907625E08839C4409CE5768403633E0B018E1D27@sefsexmb1.amd.com>
On 16/5/07 14:23, "Petersson, Mats" <Mats.Petersson@amd.com> wrote:
> Now, this brings a question: The _releaseDevices attempts to remove all
> devices as one transaction, but calling destroyDevices for each device
> would of course make it into multiple transactions. Is there any reason
> why this would make it a problem?
No. I'm pretty certain not.
K.
next prev parent reply other threads:[~2007-05-16 13:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 12:04 Shouldn't XendDomainInfo.py: _releaseDevices call destroyDevice? Petersson, Mats
2007-05-16 12:33 ` Keir Fraser
2007-05-16 12:37 ` Tom Wilkie
2007-05-16 13:23 ` Petersson, Mats
2007-05-16 13:42 ` Keir Fraser [this message]
2007-05-16 14:57 ` Petersson, Mats
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=C270C8CB.F080%keir@xensource.com \
--to=keir@xensource.com \
--cc=Mats.Petersson@amd.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 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.