From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 1/5] avcodec/evc_frame_merge: ensure the assembled buffer fits in an AVPacket
Date: Fri, 23 Jun 2023 08:43:09 -0300
Message-ID: <8f6413c5-20f1-12d7-bc9d-07c2dc3ba913@gmail.com> (raw)
In-Reply-To: <20230622192918.3638-1-jamrial@gmail.com>
On 6/22/2023 4:29 PM, James Almer wrote:
> Signed-off-by: James Almer <jamrial@gmail.com>
> ---
> libavcodec/evc_frame_merge_bsf.c | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
Will apply set.
_______________________________________________
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:[~2023-06-23 11:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 19:29 James Almer
2023-06-22 19:29 ` [FFmpeg-devel] [PATCH 2/5] avformat/evc: remove unnecessary struct James Almer
2023-06-22 19:29 ` [FFmpeg-devel] [PATCH 3/5] avformat/evc: remove duplicate check James Almer
2023-06-22 19:29 ` [FFmpeg-devel] [PATCH 4/5] avformat/evc: add range checks to evcc_parse_sps and return proper error codes James Almer
2023-06-22 19:29 ` [FFmpeg-devel] [PATCH 5/5] avformat/evc: remove duplicate defines James Almer
2023-06-22 22:48 ` [FFmpeg-devel] [PATCH 6/7] avcodec/evc_parse: use unsigned types in structs where corresponds James Almer
2023-06-22 22:48 ` [FFmpeg-devel] [PATCH 7/7] avcodec/evc_ps: " James Almer
2023-06-23 11:43 ` James Almer [this message]
2023-06-27 10:06 ` [FFmpeg-devel] [PATCH 1/5] avcodec/evc_frame_merge: ensure the assembled buffer fits in an AVPacket Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
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=8f6413c5-20f1-12d7-bc9d-07c2dc3ba913@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