On 2013-09-10 09:50, Fam Zheng wrote:
On Tue, 09/10 09:45, Max Reitz wrote:
On 2013-09-10 09:37, Fam Zheng wrote:
On Tue, 09/10 09:22, Max Reitz wrote:
On 2013-09-10 05:26, Fam Zheng wrote:
On Fri, 09/06 15:12, Max Reitz wrote:
Add the new ImageInfoSpecific type also to BlockDriverInfo.
To
On Tue, 09/10 09:45, Max Reitz wrote:
> On 2013-09-10 09:37, Fam Zheng wrote:
> >On Tue, 09/10 09:22, Max Reitz wrote:
> >>On 2013-09-10 05:26, Fam Zheng wrote:
> >>>On Fri, 09/06 15:12, Max Reitz wrote:
> Add the new ImageInfoSpecific type also to BlockDriverInfo.
>
> To prevent memor
On 2013-09-10 09:37, Fam Zheng wrote:
On Tue, 09/10 09:22, Max Reitz wrote:
On 2013-09-10 05:26, Fam Zheng wrote:
On Fri, 09/06 15:12, Max Reitz wrote:
Add the new ImageInfoSpecific type also to BlockDriverInfo.
To prevent memory leaks, this field has to be initialized to NULL every
time befo
On Tue, 09/10 09:22, Max Reitz wrote:
> On 2013-09-10 05:26, Fam Zheng wrote:
> >On Fri, 09/06 15:12, Max Reitz wrote:
> >>Add the new ImageInfoSpecific type also to BlockDriverInfo.
> >>
> >>To prevent memory leaks, this field has to be initialized to NULL every
> >>time before calling bdrv_get_in
On 2013-09-10 05:26, Fam Zheng wrote:
On Fri, 09/06 15:12, Max Reitz wrote:
Add the new ImageInfoSpecific type also to BlockDriverInfo.
To prevent memory leaks, this field has to be initialized to NULL every
time before calling bdrv_get_info and qapi_free_ImageInfoSpecific has to
be called on i
On Fri, 09/06 15:12, Max Reitz wrote:
> Add the new ImageInfoSpecific type also to BlockDriverInfo.
>
> To prevent memory leaks, this field has to be initialized to NULL every
> time before calling bdrv_get_info and qapi_free_ImageInfoSpecific has to
> be called on it when the BlockDriverInfo obje
