On 11/02/2018 19:14, Mark Thompson wrote:
... instead of making the caller allocate it themselves.  This is
more consistent with other APIs in libav.
---
This one and the following two have been hanging around for a while (they came 
from the merge into the other tine).


  libavcodec/cbs.c                    | 20 +++++++++++++++++---
  libavcodec/cbs.h                    |  6 +++---
  libavcodec/h264_metadata_bsf.c      | 20 ++++++++++----------
  libavcodec/h264_redundant_pps_bsf.c | 18 +++++++++---------
  libavcodec/h265_metadata_bsf.c      | 18 +++++++++---------
  libavcodec/mpeg2_metadata_bsf.c     | 16 ++++++++--------
  libavcodec/trace_headers_bsf.c      | 14 +++++++-------
  libavcodec/vaapi_encode_h264.c      | 14 +++++++-------
  libavcodec/vaapi_encode_h265.c      | 10 +++++-----
  libavcodec/vaapi_encode_mpeg2.c     | 10 +++++-----
  10 files changed, 80 insertions(+), 66 deletions(-)


Probably ok.
_______________________________________________
libav-devel mailing list
libav-devel@libav.org
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to