From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 2/3 v2] avcodec/utils: add ff_thread_replace_frame()
Date: Thu, 4 Aug 2022 15:39:42 -0300
Message-ID: <cd638411-b17f-c1c8-bfdc-916bb6e57e33@gmail.com> (raw)
In-Reply-To: <20220804183347.GN2088045@pb2>
On 8/4/2022 3:33 PM, Michael Niedermayer wrote:
> On Wed, Aug 03, 2022 at 01:02:47PM -0300, James Almer wrote:
>> Signed-off-by: James Almer <jamrial@gmail.com>
>> ---
>> libavcodec/pthread_frame.c | 30 ++++++++++++++++++++++++++++++
>> libavcodec/threadframe.h | 3 +++
>> libavcodec/utils.c | 21 +++++++++++++++++++++
>> 3 files changed, 54 insertions(+)
> [...]
>> diff --git a/libavcodec/utils.c b/libavcodec/utils.c
>> index e73e3a7d08..44ed19458c 100644
>> --- a/libavcodec/utils.c
>> +++ b/libavcodec/utils.c
>> @@ -928,6 +928,27 @@ int ff_thread_get_ext_buffer(AVCodecContext *avctx, ThreadFrame *f, int flags)
>> return ff_get_buffer(avctx, f->f, flags);
>> }
>>
>> +int ff_thread_replace_frame(AVCodecContext *avctx, , ThreadFrame *dst,
> ^^^
> typo
>
> thx
Fixed locally.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2022-08-04 18:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 16:02 [FFmpeg-devel] [PATCH 1/3 v4] avutil/frame: add av_frame_replace James Almer
2022-08-03 16:02 ` [FFmpeg-devel] [PATCH 2/3 v2] avcodec/utils: add ff_thread_replace_frame() James Almer
2022-08-04 18:33 ` Michael Niedermayer
2022-08-04 18:39 ` James Almer [this message]
2022-08-03 16:02 ` [FFmpeg-devel] [PATCH 3/3 v2] avcodec/h264_picture: use ff_thread_replace_frame() James Almer
2023-05-18 12:55 ` [FFmpeg-devel] [PATCH 1/3 v4] avutil/frame: add av_frame_replace James Almer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cd638411-b17f-c1c8-bfdc-916bb6e57e33@gmail.com \
--to=jamrial@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git