From: Anton Khirnov <anton@khirnov.net> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] Subject: [PATCH 1/3] lvac/dnxhdenc: add ff_dnxhdenc_init Date: Wed, 20 Dec 2023 10:51:04 +0100 Message-ID: <170306586433.8914.16398386237744409368@lain.khirnov.net> (raw) In-Reply-To: <CAEa-L+vyHJp6eZMiCGv5PL+kL8dZHP8Oqq0x5nwwOusc5gDu7A@mail.gmail.com> Quoting flow gg (2023-12-20 09:39:57) > > > From 3f8adabeac408ada6048a1e2ac472534f970364e Mon Sep 17 00:00:00 2001 > From: sunyuechi <sunyuechi@iscas.ac.cn> > Date: Wed, 20 Dec 2023 16:17:32 +0800 > Subject: [PATCH 1/3] lvac/dnxhdenc: add ff_dnxhdenc_init typo in 'lavc' > > This is for clarity and use in testing, consistent with other parts of the code. > --- > libavcodec/dnxhdenc.c | 6 ++++++ > libavcodec/dnxhdenc.h | 1 + > 2 files changed, 7 insertions(+) > > diff --git a/libavcodec/dnxhdenc.c b/libavcodec/dnxhdenc.c > index f52a2e9918..1ac8116f53 100644 > --- a/libavcodec/dnxhdenc.c > +++ b/libavcodec/dnxhdenc.c > @@ -1377,3 +1377,9 @@ const FFCodec ff_dnxhd_encoder = { > .p.profiles = NULL_IF_CONFIG_SMALL(ff_dnxhd_profiles), > .caps_internal = FF_CODEC_CAP_INIT_CLEANUP, > }; > + > +void ff_dnxhdenc_init(DNXHDEncContext *ctx) { Brace should be on its own line > +#if ARCH_X86 > + ff_dnxhdenc_init_x86(ctx); > +#endif > +} > diff --git a/libavcodec/dnxhdenc.h b/libavcodec/dnxhdenc.h > index e581312ce4..95aea83d28 100644 > --- a/libavcodec/dnxhdenc.h > +++ b/libavcodec/dnxhdenc.h > @@ -111,6 +111,7 @@ typedef struct DNXHDEncContext { > const uint8_t *pixels, ptrdiff_t line_size); > } DNXHDEncContext; > > +void ff_dnxhdenc_init(DNXHDEncContext *ctx); Shouldn't it actually replace the existing ff_dnxhdenc_init_x86() call in dnxhdenc.c? -- Anton Khirnov _______________________________________________ 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".
next prev parent reply other threads:[~2023-12-20 9:51 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-20 8:39 flow gg 2023-12-20 9:51 ` Anton Khirnov [this message] 2023-12-20 10:12 ` flow gg
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=170306586433.8914.16398386237744409368@lain.khirnov.net \ --to=anton@khirnov.net \ --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