On Mon, Jul 03, 2017 at 05:25:28PM -0400, John Ferlan wrote: > Now that we have a bit more control, let's convert our object into > a lockable object and let that magic handle the create and lock/unlock. > > This also involves creating a virNodeDeviceEndAPI in order to handle > the object cleaup for API's that use the Add or Find API's in order > to get a locked/reffed object. The EndAPI will unlock and unref the > object returning NULL to indicate to the caller to not use the obj. > > For now this also involves a forward reference to the Unlock, but > that'll be removed shortly when the object is convert to use the > virObjectLockable shortly. Which hunk is ^this paragraph still relevant for? Erik -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list