 Home |
Products |
Support |
Community |
News |
xen-devel
Re: [Xen-devel] Re: [Xen-changelog] [xen-unstable] [LINUX][XENBUS] repla
* Anthony Liguori (aliguori@xxxxxxxxxx) wrote: > Can't we just go back to the original semantics and s/XBT_NIL/NULL/g. > The whole reason XBT_NULL was introduced was that it switched to an > integer and NULL used to represent no transaction. Don't think there's a semantic change here. Just syntax. And these opaque objects are passed by value not ref, so NULL wouldn't be right. thanks, -chris _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Xen-devel] [PATCH] remove fs/Kconfig from sparse tree in favor of a 1 line patch, Sean Dague |
|---|---|
| Next by Date: | Re: [Xen-devel] [PATCH] remove fs/Kconfig from sparse tree in favor of a 1 line patch, Chris Wright |
| Previous by Thread: | [Xen-devel] Re: [Xen-changelog] [xen-unstable] [LINUX][XENBUS] replace xenbus_transaction_t with an opaque transaction ID., Anthony Liguori |
| Next by Thread: | [Xen-devel] How come same structure has different sizes for dom0 and domU, Lily Huang |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
