Don't automatically destroy the buffer(s) passed to vaRenderPictureHEADmaster

Instead the user must call vaDestroyBuffer() to destroy a buffer explicitly.

If following the previous API specification,
1. Violate "who allocate who release" principle
2. The user cannot re-use VA buffer flexibly
3. The user still has to call vaDestroyBuffer() to destroy the buffers which
   are not going to be passed to vaRenderPicture()

We discussed the change at https://bugs.freedesktop.org/show_bug.cgi?id=97970

v2: bump version to 0.40 because this is a incompatible change to VA-API

Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com>

0 files changed, 0 insertions, 0 deletions