On Tue, 30 Apr 2013 13:36:52 -0400, Derek Buitenhuis <[email protected]> wrote: > Signed-off-by: Derek Buitenhuis <[email protected]> > --- > Diego: I've not used @see, since it inserts a "See Also" header of > sorts at the end of teh section, and I'd rather keep thee function > references in the description of buf[], since it's where they're > relevant. Doxygen will make them links as-is, anyway. > --- > libavcodec/avcodec.h | 7 +++++-- > 1 file changed, 5 insertions(+), 2 deletions(-) > > diff --git a/libavcodec/avcodec.h b/libavcodec/avcodec.h > index d8e5d5e..c9526c7 100644 > --- a/libavcodec/avcodec.h > +++ b/libavcodec/avcodec.h > @@ -1920,8 +1920,11 @@ typedef struct AVCodecContext { > * extended_data must be allocated with av_malloc() and will be > freed in > * av_frame_unref(). > * * otherwise exended_data must point to data > - * - buf[] must contain references to the buffers that contain the frame > - * data. > + * - buf[] must contain one or more pointers to AVBufferRef structures. > Each of > + * the frame's data and extended_data pointers must be contained in > these. That > + * is, one AVBufferRef for each allocated chunk of memory, not > necessarily one > + * AVBufferRef per data[] entry. See: av_buffer_create(), > av_buffer_alloc(), > + * and av_buffer_ref(). > * - extended_buf and nb_extended_buf must be allocated with av_malloc() > by > * this callback and filled with the extra buffers if there are more > * buffers than buf[] can hold. extended_buf will be freed in > -- > 1.7.10.4 >
Fine with me -- Anton Khirnov _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
