From: "xin.guo via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: "xin.guo" <code@ffmpeg.org>
Subject: [FFmpeg-devel] [PATCH] avcodec/h264_vulkan: Fix param error in set_sps (PR #20772)
Date: Tue, 28 Oct 2025 03:51:20 -0000
Message-ID: <176162348151.81.5366122626914672187@7d278768979e> (raw)
PR #20772 opened by xin.guo
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20772
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20772.patch
Signed-off-by: xin.guo <xin.guo@sophgo.com>
>From 23b19ef03c764cb65f30874ac8d89bdcd1cee6dd Mon Sep 17 00:00:00 2001
From: "xin.guo" <xin.guo@sophgo.com>
Date: Tue, 28 Oct 2025 11:43:58 +0800
Subject: [PATCH] avcodec/h264_vulkan: Fix param error in set_sps
Signed-off-by: xin.guo <xin.guo@sophgo.com>
---
libavcodec/vulkan_h264.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavcodec/vulkan_h264.c b/libavcodec/vulkan_h264.c
index ebe305e7b5..bcc5c99b4b 100644
--- a/libavcodec/vulkan_h264.c
+++ b/libavcodec/vulkan_h264.c
@@ -195,7 +195,7 @@ static void set_sps(const SPS *sps,
.video_signal_type_present_flag = sps->vui.video_signal_type_present_flag,
.video_full_range_flag = sps->vui.video_full_range_flag,
.color_description_present_flag = sps->vui.colour_description_present_flag,
- .chroma_loc_info_present_flag = sps->vui.chroma_location,
+ .chroma_loc_info_present_flag = sps->vui.chroma_loc_info_present_flag,
.timing_info_present_flag = sps->timing_info_present_flag,
.fixed_frame_rate_flag = sps->fixed_frame_rate_flag,
.bitstream_restriction_flag = sps->bitstream_restriction_flag,
--
2.49.1
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
reply other threads:[~2025-10-28 3:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=176162348151.81.5366122626914672187@7d278768979e \
--to=ffmpeg-devel@ffmpeg.org \
--cc=code@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