From: George Dunlap <george.dunlap@eu.citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Roger Pau Monne <roger.pau@citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
Valtteri Kiviniemi <kiviniemi.valtteri@gmail.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH V3] libxl: write IO ABI for disk frontends
Date: Fri, 26 Apr 2013 12:01:35 +0100 [thread overview]
Message-ID: <517A5E8F.6000406@eu.citrix.com> (raw)
In-Reply-To: <1366971779.3142.59.camel@zakaz.uk.xensource.com>
On 26/04/13 11:22, Ian Campbell wrote:
> On Fri, 2013-04-26 at 11:11 +0100, Wei Liu wrote:
>> On Fri, Apr 26, 2013 at 10:52:35AM +0100, Ian Campbell wrote:
>> [...]
>>>>>> + flexarray_append(front, p);
>>>>> GCSPRINTF would be the right way to do this, but actually you can pass
>>>>> protocol directly to flexarray_append, that is fine since the flexarray
>>>>> never frees the values which it contains so they either need to be gc'd,
>>>>> string constants or managed manually.
>>>>>
>>>> Oh thanks for the hint. This saves serveral lines of code. The (void *)
>>>> argument of flexarray_append misled me. ;-)
>>>>
>>>> Below is updated version of the patch. Casting "protocol" to (void *) is
>>>> necessary to have it compiled. Otherwise gcc complains we discard the
>>>> const quilifier.
>>> Oh, sorry, if this is the case the libxl__strdup(gc,protocol) is better
>>> than the cast. Sorry for misleading :-(
>>>
>>> Now you mention it I do seem to recall trying to correctly constify
>>> flexarray's at one point and not quite being able to make it work.
>>>
>> Another version with libxl__strdup(). :-)
> Thanks!
>
> George, this is on your tracking list and is a bug fix and/or a
> regression from Xend. Are you happy to give it a freeze exception?
Yes, I think this is fine to go in.
-George
next prev parent reply other threads:[~2013-04-26 11:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 21:36 [PATCH V3] libxl: write IO ABI for disk frontends Wei Liu
2013-04-26 9:18 ` Ian Campbell
2013-04-26 9:44 ` Wei Liu
2013-04-26 9:52 ` Ian Campbell
2013-04-26 10:11 ` Wei Liu
2013-04-26 10:22 ` Ian Campbell
2013-04-26 11:01 ` George Dunlap [this message]
2013-04-26 15:34 ` Ian Campbell
2013-05-16 12:43 ` Valtteri Kiviniemi
2013-05-16 13:33 ` Wei Liu
2013-05-16 14:01 ` Valtteri Kiviniemi
2013-05-17 7:36 ` Valtteri Kiviniemi
2013-05-17 8:33 ` Wei Liu
2013-05-17 8:56 ` George Dunlap
2013-05-17 9:07 ` Wei Liu
2013-05-17 9:18 ` George Dunlap
2013-05-17 9:22 ` Wei Liu
2013-05-17 10:53 ` Valtteri Kiviniemi
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=517A5E8F.6000406@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=kiviniemi.valtteri@gmail.com \
--cc=roger.pau@citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/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).