From: "Dawid Kozinski/Multimedia \(PLT\) /SRPOL/Staff Engineer/Samsung Electronics" <d.kozinski@samsung.com>
To: "'FFmpeg development discussions and patches'" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/5] avcodec/evc_frame_merge: ensure the assembled buffer fits in an AVPacket
Date: Tue, 27 Jun 2023 12:06:42 +0200
Message-ID: <009401d9a8df$12e485c0$38ad9140$@samsung.com> (raw)
In-Reply-To: <8f6413c5-20f1-12d7-bc9d-07c2dc3ba913@gmail.com>
Hi James,
I would like to thank you for the thorough review and merging of the
majority of the 10-patchset into the FFmpeg master branch. Your personal
dedication to making numerous valuable and impactful improvements to the
code has been remarkable.
I am really grateful for your work and your time devoted to merging the EVC
implementation into FFmpeg master branch.
While the progress made so far has been significant, there are still two
remaining patches. I mean the implementation of wrappers for the EVC encoder
and decoder. I wanted to inquire about merging these two patches into the
master branch. We are looking forward to seeing the complete integration of
these essential components.
Furthermore, I wanted to ask if there is anything we can do to facilitate
the integration of our patchset with the FFmpeg project.
Whether it involves providing additional changes, conducting further
testing, or assisting in the code review process, we are more than willing
to collaborate and contribute in any way we can. Let us know what we can do
to enhance the overall integration process.
Once again, I would like to express my deep appreciation for your invaluable
contributions, thorough review, and the multitude of changes you have made
to the code.
Thank you for your time, contribution, and consideration. I look forward to
your response.
Kind regards
Dawid
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of James
> Almer
> Sent: piątek, 23 czerwca 2023 13:43
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH 1/5] avcodec/evc_frame_merge: ensure
> the assembled buffer fits in an AVPacket
>
> 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://protect2.fireeye.com/v1/url?k=322c563f-53a74374-322ddd70-
> 74fe485fb305-d0a347f67d0a53df&q=1&e=5018ca25-0c81-4d7a-8598-
> 9876a225f78c&u=https%3A%2F%2Fffmpeg.org%2Fmailman%2Flistinfo%2Fffmp
> eg-devel
>
> To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org
> with subject "unsubscribe".
_______________________________________________
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".
prev parent reply other threads:[~2023-06-27 10:06 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 ` [FFmpeg-devel] [PATCH 1/5] avcodec/evc_frame_merge: ensure the assembled buffer fits in an AVPacket James Almer
2023-06-27 10:06 ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics [this message]
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='009401d9a8df$12e485c0$38ad9140$@samsung.com' \
--to=d.kozinski@samsung.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