Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Soft Works <softworkz@hotmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: OvchinnikovDmitrii <ovchinnikov.dmitrii@gmail.com>
Subject: Re: [FFmpeg-devel] [PATCH, v3] MAINTAINERS: add myself as amfenc* maintainer
Date: Sat, 5 Nov 2022 05:10:08 +0000
Message-ID: <DM8P223MB03657ADE73727E21C6C9750BBA3A9@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20221104185756.2089-1-ovchinnikov.dmitrii@gmail.com>



> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> OvchinnikovDmitrii
> Sent: Friday, November 4, 2022 7:58 PM
> To: ffmpeg-devel@ffmpeg.org
> Cc: OvchinnikovDmitrii <ovchinnikov.dmitrii@gmail.com>
> Subject: [FFmpeg-devel] [PATCH, v3] MAINTAINERS: add myself as
> amfenc* maintainer
> 
> Due to the lack of an active AMF maintainer at the moment, as well
> as plans to add the av1 encoder and other improvements of AMF,
> I added myself to the maintainers. Timely review and merging
> patches targeting AMF integration should improve support
> of AMD GPUs and APUs in FFmpeg.
> For the last couple of years I have been working on AMF related
> patches to ffmpeg and other open source projects.

Considering the lack of ambition in the past, I think there's
no point in waiting for AMD to come around, and having a maintainer
would surely be beneficial, hence
LGTM.

softworkz
_______________________________________________
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".

  parent reply	other threads:[~2022-11-05  5:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04 18:57 OvchinnikovDmitrii
2022-11-05  0:44 ` Timo Rothenpieler
2022-11-05  5:10 ` Soft Works [this message]
2022-11-10 15:29 ` Timo Rothenpieler

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=DM8P223MB03657ADE73727E21C6C9750BBA3A9@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
    --to=softworkz@hotmail.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=ovchinnikov.dmitrii@gmail.com \
    /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