On Fri, Dec 14, 2018 at 12:08:55PM +0100, Erik Skultety wrote:
> On Fri, Dec 14, 2018 at 10:11:55AM +, Daniel P. Berrangé wrote:
> > On Fri, Dec 14, 2018 at 10:18:39AM +0100, Erik Skultety wrote:
> > > For some reason, xdr_free uses char * instead of void * for its 2nd
> > > argument which is p
On Fri, Dec 14, 2018 at 10:11:55AM +, Daniel P. Berrangé wrote:
> On Fri, Dec 14, 2018 at 10:18:39AM +0100, Erik Skultety wrote:
> > For some reason, xdr_free uses char * instead of void * for its 2nd
> > argument which is passed to a custom free routine. Commit
> > dc54b3ec missed this detail
On Fri, Dec 14, 2018 at 10:18:39AM +0100, Erik Skultety wrote:
> For some reason, xdr_free uses char * instead of void * for its 2nd
> argument which is passed to a custom free routine. Commit
> dc54b3ec missed this detail which made the build fail on a number of
> platforms. Fix it by explicitly c
For some reason, xdr_free uses char * instead of void * for its 2nd
argument which is passed to a custom free routine. Commit
dc54b3ec missed this detail which made the build fail on a number of
platforms. Fix it by explicitly casting the object pointer to char *
just like we do in other places thr