From: Dennis Mungai <dmngaie@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Devin Heitmueller <dheitmueller@ltnglobal.com>
Subject: Re: [FFmpeg-devel] [PATCH] libavfilter/yadif_cuda: Fix build breakage
Date: Thu, 11 May 2023 20:13:46 +0300
Message-ID: <CAKKYfmGC=icE+-LODP5VSzdSqTiip3aoN0XCAj7wNex23BMepQ@mail.gmail.com> (raw)
In-Reply-To: <1683828488-9675-1-git-send-email-dheitmueller@ltnglobal.com>
On Thu, 11 May 2023 at 20:12, Devin Heitmueller <
devin.heitmueller@ltnglobal.com> wrote:
> Address build breakage caused by my latest series when compiling
> with CUDA support. Thanks to Paul Mahol for pointing it out.
>
> Signed-off-by: Devin Heitmueller <dheitmueller@ltnglobal.com>
> ---
> libavfilter/vf_yadif_cuda.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/libavfilter/vf_yadif_cuda.c b/libavfilter/vf_yadif_cuda.c
> index f3f0b56..73f0412 100644
> --- a/libavfilter/vf_yadif_cuda.c
> +++ b/libavfilter/vf_yadif_cuda.c
> @@ -205,7 +205,7 @@ static av_cold void deint_cuda_uninit(AVFilterContext
> *ctx)
> av_frame_free(&y->prev);
> av_frame_free(&y->cur);
> av_frame_free(&y->next);
> - ff_cc_fifo_freep(&y->cc_fifo);
> + ff_ccfifo_freep(&y->cc_fifo);
>
> av_buffer_unref(&s->device_ref);
> s->hwctx = NULL;
> @@ -295,7 +295,7 @@ static int config_output(AVFilterLink *link)
> else
> link->frame_rate = ctx->inputs[0]->frame_rate;
>
> - if (!(s->cc_fifo = ff_cc_fifo_alloc(link->frame_rate, ctx))) {
> + if (!(y->cc_fifo = ff_ccfifo_alloc(link->frame_rate, ctx))) {
> av_log(ctx, AV_LOG_ERROR, "Failure to setup CC FIFO queue\n");
> ret = AVERROR(ENOMEM);
> goto exit;
> --
> 1.8.3.1
>
I had literally opened a ticket on the same seconds ago:
https://trac.ffmpeg.org/ticket/10357
Will close as soon as the patch is merged.
_______________________________________________
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-05-11 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 18:08 Devin Heitmueller
2023-05-11 17:13 ` Dennis Mungai [this message]
2023-05-12 1:47 ` Lance Wang
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='CAKKYfmGC=icE+-LODP5VSzdSqTiip3aoN0XCAj7wNex23BMepQ@mail.gmail.com' \
--to=dmngaie@gmail.com \
--cc=dheitmueller@ltnglobal.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