On 05/26/2017 08:56 AM, Peter Krempa wrote:
> On Fri, May 26, 2017 at 07:59:08 -0400, John Ferlan wrote:
>> For now it'll just call the virInterfaceObjUnlock, but a future adjustment
>> will do something different.
>>
>> The virInterfaceObjUnlock is now private to virinterfaceobj.c with a
>>
On Fri, May 26, 2017 at 07:59:08 -0400, John Ferlan wrote:
> For now it'll just call the virInterfaceObjUnlock, but a future adjustment
> will do something different.
>
> The virInterfaceObjUnlock is now private to virinterfaceobj.c with a
> short term forward reference.
>
> Additionally, make
For now it'll just call the virInterfaceObjUnlock, but a future adjustment
will do something different.
The virInterfaceObjUnlock is now private to virinterfaceobj.c with a
short term forward reference.
Additionally, make virInterfaceObjLock private since it's only used in
virinterfaceobj