All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Daniel Stekloff <dsteklof@us.ibm.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 2/3] Make it clear that	xs_get_domain_path() requires free()
Date: Tue, 01 Nov 2005 13:51:52 -0600	[thread overview]
Message-ID: <4367C758.7020407@us.ibm.com> (raw)
In-Reply-To: <1130874644.4658.10.camel@w-stekloff.beaverton.ibm.com>

Daniel Stekloff wrote:

>Just out of curiosity, why have xenstore create a buffer that must be
>freed. Why not have the calling application create a buffer and manage
>it on its own?
>  
>
Because Rusty made it that way :-)

Regards,

Anthony Liguori

>
>On Tue, 2005-11-01 at 13:11 -0600, Anthony Liguori wrote:
>  
>
>>plain text document attachment (7574-xenconsole.diff)
>># HG changeset patch
>># User Anthony Liguori <anthony@codemonkey.ws>
>># Node ID a44fde5c4e15bdf2f8b42fa41439d6725a5363dc
>># Parent  6de1d7b66c8a52ac6420f35aac03fe219caf87a3
>>Make it clear that the result of xs_get_domain_path() must be free()'d.
>>
>>diff -r 6de1d7b66c8a -r a44fde5c4e15 tools/xenstore/xs.h
>>--- a/tools/xenstore/xs.h	Tue Nov  1 11:08:31 2005 -0500
>>+++ b/tools/xenstore/xs.h	Tue Nov  1 11:09:57 2005 -0500
>>@@ -136,7 +136,7 @@
>>  */
>> bool xs_release_domain(struct xs_handle *h, unsigned int domid);
>> 
>>-/* Query the home path of a domain.
>>+/* Query the home path of a domain.  Call free() after use.
>>  */
>> char *xs_get_domain_path(struct xs_handle *h, unsigned int domid);
>> 
>>_______________________________________________
>>Xen-devel mailing list
>>Xen-devel@lists.xensource.com
>>http://lists.xensource.com/xen-devel
>>    
>>
>
>
>  
>

      reply	other threads:[~2005-11-01 19:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-01 19:11 [PATCH 2/3] Make it clear that xs_get_domain_path() requires free() Anthony Liguori
2005-11-01 19:50 ` Daniel Stekloff
2005-11-01 19:51   ` Anthony Liguori [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=4367C758.7020407@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=dsteklof@us.ibm.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.