Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] fftools/opt_common: check the return value of av_hwdevice_get_type_name before printing it
Date: Wed, 14 Sep 2022 09:58:34 -0300
Message-ID: <cb497129-3dc8-ae89-621e-47b84f0f47da@gmail.com> (raw)
In-Reply-To: <20220912130208.2222-1-jamrial@gmail.com>

On 9/12/2022 10:02 AM, James Almer wrote:
> It may be NULL, as is the case for D3D11VA_VLD.
> 
> Running "ffmpeg -h decoder=h264" on a Windows build
> 
> Before:
> Decoder h264 [H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10]:
>      Supported hardware devices: dxva2 (null) d3d11va cuda
> 
> After:
> Decoder h264 [H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10]:
>      Supported hardware devices: dxva2 d3d11va cuda
> 
> Signed-off-by: James Almer <jamrial@gmail.com>
> ---
>   fftools/opt_common.c | 5 ++++-
>   1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/fftools/opt_common.c b/fftools/opt_common.c
> index 7cd8b1c66e..8a06df82df 100644
> --- a/fftools/opt_common.c
> +++ b/fftools/opt_common.c
> @@ -335,9 +335,12 @@ static void print_codec(const AVCodec *c)
>           printf("    Supported hardware devices: ");
>           for (int i = 0;; i++) {
>               const AVCodecHWConfig *config = avcodec_get_hw_config(c, i);
> +            const char *name;
>               if (!config)
>                   break;
> -            printf("%s ", av_hwdevice_get_type_name(config->device_type));
> +            name = av_hwdevice_get_type_name(config->device_type);
> +            if (name)
> +                printf("%s ", name);
>           }
>           printf("\n");
>       }

Applied.
_______________________________________________
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-09-14 12:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-12 13:02 James Almer
2022-09-14 12:58 ` James Almer [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=cb497129-3dc8-ae89-621e-47b84f0f47da@gmail.com \
    --to=jamrial@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