All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Limpach <christian.limpach@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Re: [RESEND] [PATCH] Call dominfo.device_delete instead of non-existant dominfo.device_destroy
Date: Wed, 14 Sep 2005 13:49:37 +0100	[thread overview]
Message-ID: <3d8eece205091405495eb9984e@mail.gmail.com> (raw)
In-Reply-To: <20050913163112.GA5276@underhill.no-ip.org>

Thanks!

On 9/13/05, Sean Dague <sean@dague.net> wrote:
> This is a resend on the patch from late last week as I haven't seen it in
> the changelog yet.  Comments welcomed if there is an issue with the patch.
> 
>        -Sean
> 
> --
> __________________________________________________________________
> 
> Sean Dague                                       Mid-Hudson Valley
> sean at dague dot net                            Linux Users Group
> http://dague.net                                 http://mhvlug.org
> 
> There is no silver bullet.  Plus, werewolves make better neighbors
> than zombies, and they tend to keep the vampire population down.
> __________________________________________________________________
> 
> 
> 
> ---------- Forwarded message ----------
> From: Sean Dague <sean@dague.net>
> To: xen-devel@lists.xensource.com
> Date: Fri, 9 Sep 2005 15:01:43 -0400
> Subject: [PATCH] Call dominfo.device_delete instead of non-existant dominfo.device_destroy
> This patch changes the device destruction function to one that exists in
> in the XendDomainInfo class, instead of a non existent method.
> 
> 
> Signed-off-by: Sean Dague <sean@dague.net>
> 
> Diffstat output:
>  XendDomain.py |    2 +-
>  1 files changed, 1 insertion(+), 1 deletion(-)
> 
> diff -r 41a74438bcba tools/python/xen/xend/XendDomain.py
> --- a/tools/python/xen/xend/XendDomain.py       Fri Sep  9 18:36:48 2005
> +++ b/tools/python/xen/xend/XendDomain.py       Fri Sep  9 14:46:01 2005
> @@ -667,7 +667,7 @@
>         @param type: device type
>         """
>         dominfo = self.domain_lookup(id)
> -        val = dominfo.device_destroy(type, devid)
> +        val = dominfo.device_delete(type, devid)
>         dominfo.exportToDB()
>         return val
> 
> 
> --
> __________________________________________________________________
> 
> Sean Dague                                       Mid-Hudson Valley
> sean at dague dot net                            Linux Users Group
> http://dague.net                                 http://mhvlug.org
> 
> There is no silver bullet.  Plus, werewolves make better neighbors
> than zombies, and they tend to keep the vampire population down.
> __________________________________________________________________
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
> 
> 
>

      reply	other threads:[~2005-09-14 12:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-13 16:31 [RESEND] [PATCH] Call dominfo.device_delete instead of non-existant dominfo.device_destroy Sean Dague
2005-09-14 12:49 ` Christian Limpach [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=3d8eece205091405495eb9984e@mail.gmail.com \
    --to=christian.limpach@gmail.com \
    --cc=Christian.Limpach@cl.cam.ac.uk \
    --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.