Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Lynne <dev@lynne.ee>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: ffmpeg-devel@ffmpeg.org, d.frankiewic@samsung.com,
	Dawid Kozinski <d.kozinski@samsung.com>
Subject: Re: [FFmpeg-devel] [PATCH v18 01/10] avcodec/evc: MPEG-5 EVC codec registration
Date: Wed, 29 Mar 2023 08:03:26 +0200 (CEST)
Message-ID: <NRfxgab--3-9@lynne.ee> (raw)
In-Reply-To: <20230328134548.1580-1-d.kozinski@samsung.com>

Mar 28, 2023, 15:46 by d.kozinski@samsung.com:

> Added prerequisites that must be met before providing support for the MPEG-5 EVC codec
> - Added new entry to codec IDs list
> - Added new entry to the codec descriptor list
> - Bumped libavcodec minor version
> - Added profiles for EVC codec
>
> Signed-off-by: Dawid Kozinski <d.kozinski@samsung.com>
> ---
>  libavcodec/avcodec.h    | 3 +++
>  libavcodec/codec_desc.c | 8 ++++++++
>  libavcodec/codec_id.h   | 1 +
>  libavcodec/profiles.c   | 6 ++++++
>  libavcodec/profiles.h   | 1 +
>  libavcodec/version.h    | 2 +-
>  6 files changed, 20 insertions(+), 1 deletion(-)
>

Patchset looks good to me now. Thanks!
I'll push it tonight.

As for your change in MAINTAINERS, the discussion is still
ongoing, so I'll push it with the condition that it's just
there to let submitters know who to ping, rather than
requesting push access. If you'd like push access, just
send a request on the ML.
_______________________________________________
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".

  reply	other threads:[~2023-03-29  6:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20230328134602eucas1p28d1d547d2d0807f1af9493bfa77a5575@eucas1p2.samsung.com>
2023-03-28 13:45 ` Dawid Kozinski
2023-03-29  6:03   ` Lynne [this message]
2023-04-05  9:00     ` 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=NRfxgab--3-9@lynne.ee \
    --to=dev@lynne.ee \
    --cc=d.frankiewic@samsung.com \
    --cc=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