Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Wu Jianhua <toqsxw@outlook.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avcodec: add D3D12VA hardware accelerated H264, HEVC, VP9, and AV1 decoding
Date: Wed, 12 Oct 2022 16:25:35 +0000
Message-ID: <OSZP286MB217359E839C1298B145E952DCA229@OSZP286MB2173.JPNP286.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <125f720e-9c99-fed9-93ba-434e9550fc5c@gmail.com>

James Almer<mailto:jamrial@gmail.com> wrote:
> On 10/12/2022 12:12 PM, Jean-Baptiste Kempf wrote:
>> Hello,
>>
>> You really need to split this patch into logical patches.
>>
>> jb
>
> To expand on this, you should split into the following: One patch adding
> the hwcontext and pixel format to libavutil plus an entry in the
> APIChanges file mentioning the new public symbols and defines, then one
> patch per new hwaccel in libavcodec, the first of which should contain
> the shared code, and the last one the Changelog entry and the version
> bump (The changes in configure should of course be split across said
> patches).
>
> Compilation must succeed for every patch, hence the above suggested order.
>

I’ll try to do that. Thanks for the advice.

>>
>> On Wed, 12 Oct 2022, at 13:09, Wu Jianhua wrote:
>>> [PATCH] avcodec: add D3D12VA hardware accelerated H264, HEVC, VP9, and
>>> AV1 decoding
>>>
>>> Patch attached.
>>>
>>>


_______________________________________________
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:[~2022-10-12 16:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OSZP286MB2173BE661B9E9F1FDBAB4D1DCA229@OSZP286MB2173.JPNP286.PROD.OUTLOOK.COM>
2022-10-12 11:09 ` Wu Jianhua
2022-10-12 15:12   ` Jean-Baptiste Kempf
2022-10-12 15:25     ` James Almer
2022-10-12 16:25       ` Wu Jianhua [this message]
2022-10-13 12:37   ` Lynne
2022-10-13 15:48     ` Wu Jianhua
2022-10-13 16:04       ` James Almer
2022-10-13 16:08         ` Wu Jianhua
2022-10-13 22:28       ` Lynne
2022-10-14 12:32         ` Wu Jianhua
2022-10-15  5:16           ` Lynne
2022-11-11 16:41             ` Wu Jianhua
2022-11-11 16:50             ` Wu Jianhua

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=OSZP286MB217359E839C1298B145E952DCA229@OSZP286MB2173.JPNP286.PROD.OUTLOOK.COM \
    --to=toqsxw@outlook.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