From: Zhao Zhili via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: "xin.guo" <xin.guo@sophgo.com>, Zhao Zhili <quinkblack@foxmail.com>
Subject: [FFmpeg-devel] Re: [PATCH] avcodec/h264_vulkan: Fix param error in set_sps
Date: Tue, 28 Oct 2025 00:24:32 +0800
Message-ID: <tencent_D23FE556059CA4E1145B56346D803A340D09@qq.com> (raw)
In-Reply-To: <20251027140529.3517-1-xin.guo@sophgo.com>
> On Oct 27, 2025, at 22:05, xin.guo via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> wrote:
>
> 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 e727aafb16..0f114af34c 100644
> --- a/libavcodec/vulkan_h264.c
> +++ b/libavcodec/vulkan_h264.c
> @@ -188,7 +188,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.17.1
LGTM, thanks. Could you create a PR on code.ffmpeg.org <http://code.ffmpeg.org/>?
>
> _______________________________________________
> ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
> To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
prev parent reply other threads:[~2025-10-27 16:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 14:05 [FFmpeg-devel] " xin.guo via ffmpeg-devel
2025-10-27 16:24 ` Zhao Zhili via ffmpeg-devel [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=tencent_D23FE556059CA4E1145B56346D803A340D09@qq.com \
--to=ffmpeg-devel@ffmpeg.org \
--cc=quinkblack@foxmail.com \
--cc=xin.guo@sophgo.com \
/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