From: Nuo Mi <nuomi2021@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] 回复: [PATCH] x86/vvc_alf: use the x86inc instruction macros Date: Wed, 22 May 2024 20:58:32 +0800 Message-ID: <CAFXK13fEGfMHwyXtZYqtOE4C0WX5ruBgusL61qJv2zoi7Xq0EQ@mail.gmail.com> (raw) In-Reply-To: <OSZP286MB2173EB7BE005289AE2627947CAEA2@OSZP286MB2173.JPNP286.PROD.OUTLOOK.COM> On Wed, May 22, 2024 at 12:29 AM Wu Jianhua <toqsxw@outlook.com> wrote: > > 发件人: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> 代表 James Almer < > jamrial@gmail.com> > > 发送时间: 2024年5月21日 6:52 > > 收件人: ffmpeg-devel@ffmpeg.org > > 主题: [FFmpeg-devel] [PATCH] x86/vvc_alf: use the x86inc instruction macros > > > > Let its magic figure out the correct mnemonic based on target > instruction set. > > > > Signed-off-by: James Almer <jamrial@gmail.com> > > --- > > libavcodec/x86/vvc/vvc_alf.asm | 202 ++++++++++++++++----------------- > > 1 file changed, 101 insertions(+), 101 deletions(-) > > I tested this patch and LGTM. Thanks for updating them. > > And would it be better to add avcodec to the path of the commit message? > Hi Jianhua, vvc is clear in this case. Applied, thank you, Jianhua and James > Thanks, > Jianhua > _______________________________________________ > 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". > _______________________________________________ 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:[~2024-05-22 12:58 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-21 13:52 [FFmpeg-devel] " James Almer 2024-05-21 16:29 ` [FFmpeg-devel] 回复: " Wu Jianhua 2024-05-22 12:58 ` Nuo Mi [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=CAFXK13fEGfMHwyXtZYqtOE4C0WX5ruBgusL61qJv2zoi7Xq0EQ@mail.gmail.com \ --to=nuomi2021@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