From: "mypopy@gmail.com" <mypopy@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 1/3] lavfi/metal: fix mixing declarations and code warning Date: Sat, 8 Apr 2023 20:17:40 +0800 Message-ID: <CACYjbn1rY36WQiGnD2cTj0OGnu0FEiVd4yvXZZ8pA_OL9+Vncg@mail.gmail.com> (raw) In-Reply-To: <tencent_E621276338B29675CD1E2067CD93CFB15507@qq.com> On Mon, Apr 3, 2023 at 9:29 PM "zhilizhao(赵志立)" <quinkblack@foxmail.com> wrote: > > > > > On Apr 3, 2023, at 20:25, Jun Zhao <mypopydev@gmail.com> wrote: > > > > fix mixing declarations and code warning > > > > Signed-off-by: Jun Zhao <barryjzhao@tencent.com> > > --- > > libavfilter/vf_yadif_videotoolbox.m | 3 ++- > > 1 file changed, 2 insertions(+), 1 deletion(-) > > I have noticed the -Wdeclaration-after-statement flag has been applied > on Objective-C, but I’m not sure whether the rule should applies or not. > I will hold on the Objective-C part and push the other patches in the patch sets > > > > diff --git a/libavfilter/vf_yadif_videotoolbox.m b/libavfilter/vf_yadif_videotoolbox.m > > index 69186c2254..3656a673b3 100644 > > --- a/libavfilter/vf_yadif_videotoolbox.m > > +++ b/libavfilter/vf_yadif_videotoolbox.m > > @@ -208,6 +208,7 @@ static av_cold int do_init(AVFilterContext *ctx) API_AVAILABLE(macos(10.11), ios > > YADIFVTContext *s = ctx->priv; > > NSError *err = nil; > > CVReturn ret; > > + dispatch_data_t libData; > > > > s->mtlDevice = MTLCreateSystemDefaultDevice(); > > if (!s->mtlDevice) { > > @@ -217,7 +218,7 @@ static av_cold int do_init(AVFilterContext *ctx) API_AVAILABLE(macos(10.11), ios > > > > av_log(ctx, AV_LOG_INFO, "Using Metal device: %s\n", s->mtlDevice.name.UTF8String); > > > > - dispatch_data_t libData = dispatch_data_create( > > + libData = dispatch_data_create( > > ff_vf_yadif_videotoolbox_metallib_data, > > ff_vf_yadif_videotoolbox_metallib_len, > > nil, > > -- > > 2.25.1 _______________________________________________ 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:[~2023-04-08 12:18 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-03 12:25 Jun Zhao 2023-04-03 12:25 ` [FFmpeg-devel] [PATCH 2/3] lavc/videotoolboxenc: fix warnings Jun Zhao 2023-04-03 12:25 ` [FFmpeg-devel] [PATCH 3/3] lavc/videotoolbox: " Jun Zhao 2023-04-03 13:29 ` [FFmpeg-devel] [PATCH 1/3] lavfi/metal: fix mixing declarations and code warning "zhilizhao(赵志立)" 2023-04-08 12:17 ` mypopy [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=CACYjbn1rY36WQiGnD2cTj0OGnu0FEiVd4yvXZZ8pA_OL9+Vncg@mail.gmail.com \ --to=mypopy@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