From: "Xiang, Haihao" <haihao.xiang-at-intel.com@ffmpeg.org>
To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] doc/examples/qsv_transcode: EINVAL is more appropriate and ENAVAIL will fail build with visual studio
Date: Thu, 7 Dec 2023 07:36:55 +0000
Message-ID: <fe72ed6bf8f9fae83c6c3006ba6db52cc50cc1a0.camel@intel.com> (raw)
In-Reply-To: <PH7PR11MB74306DE032ED1A253C4121ACC48BA@PH7PR11MB7430.namprd11.prod.outlook.com>
On Do, 2023-12-07 at 06:44 +0000, hung kuishing wrote:
> Signed-off-by: clarkh <hungkuishing@outlook.com>
> ---
> doc/examples/qsv_transcode.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/doc/examples/qsv_transcode.c b/doc/examples/qsv_transcode.c
> index 48128b200c..972126800b 100644
> --- a/doc/examples/qsv_transcode.c
> +++ b/doc/examples/qsv_transcode.c
> @@ -62,10 +62,10 @@ static int str_to_dict(char* optstr, AVDictionary **opt)
> return 0;
> key = strtok(optstr, " ");
> if (key == NULL)
> - return AVERROR(ENAVAIL);
> + return AVERROR(EINVAL);
> value = strtok(NULL, " ");
> if (value == NULL)
> - return AVERROR(ENAVAIL);
> + return AVERROR(EINVAL);
> av_dict_set(opt, key, value, 0);
> do {
> key = strtok(NULL, " ");
> @@ -73,7 +73,7 @@ static int str_to_dict(char* optstr, AVDictionary **opt)
> return 0;
> value = strtok(NULL, " ");
> if (value == NULL)
> - return AVERROR(ENAVAIL);
> + return AVERROR(EINVAL);
> av_dict_set(opt, key, value, 0);
> } while(key != NULL);
> return 0;
> @@ -181,7 +181,7 @@ static int open_input_file(char *filename)
> break;
> default:
> fprintf(stderr, "Codec is not supportted by qsv\n");
> - return AVERROR(ENAVAIL);
> + return AVERROR(EINVAL);
> }
>
> if (!(decoder_ctx = avcodec_alloc_context3(decoder)))
LGTM, thanks for fixing the issue.
BRs
Haihao
_______________________________________________
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-07 7:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 6:44 hung kuishing
2023-12-07 7:36 ` Xiang, Haihao [this message]
2023-12-15 7:19 ` hung kuishing
2023-12-18 6:49 ` Xiang, Haihao
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=fe72ed6bf8f9fae83c6c3006ba6db52cc50cc1a0.camel@intel.com \
--to=haihao.xiang-at-intel.com@ffmpeg.org \
--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