Re: [libvirt] [PATCH 1/7] rpc: refactor way connection object is generated for remote dispatch

2018-04-05 Thread Daniel P . Berrangé
On Wed, Apr 04, 2018 at 01:41:54PM -0400, John Ferlan wrote: > > > On 03/28/2018 11:18 AM, Daniel P. Berrangé wrote: > > Calling a push_privconn method to directly push the connection object > > name into the arg list is inconvenient. Refactor so that we acquire > > the connection variable name

Re: [libvirt] [PATCH 1/7] rpc: refactor way connection object is generated for remote dispatch

2018-04-04 Thread John Ferlan
On 03/28/2018 11:18 AM, Daniel P. Berrangé wrote: > Calling a push_privconn method to directly push the connection object > name into the arg list is inconvenient. Refactor so that we acquire > the connection variable name upfront, and push it to the arg list > separately. This allows various

[libvirt] [PATCH 1/7] rpc: refactor way connection object is generated for remote dispatch

2018-03-28 Thread Daniel P . Berrangé
Calling a push_privconn method to directly push the connection object name into the arg list is inconvenient. Refactor so that we acquire the connection variable name upfront, and push it to the arg list separately. This allows various hardcoded usage of "priv->conn" to be parameterized.