From: "Xiang, Haihao" <haihao.xiang-at-intel.com@ffmpeg.org>
To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>,
"haihao.xiang-at-intel.com@ffmpeg.org"
<haihao.xiang-at-intel.com@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2 1/3] lavc/qsv: allow to add more parameter buffers to QSV frame
Date: Sun, 30 Jan 2022 01:02:32 +0000
Message-ID: <5d788095ba4502fc37ac785fd3c99b315e5aa6b4.camel@intel.com> (raw)
In-Reply-To: <afc01303-ed9c-bf56-e0bb-712ed70eafb6@rothenpieler.org>
On Sat, 2022-01-29 at 15:41 +0100, Timo Rothenpieler wrote:
> On 29.01.2022 15:30, Timo Rothenpieler wrote:
> > On 27.01.2022 06:37, Xiang, Haihao wrote:
> > > Will apply
> > >
> > > -Haihao
> > >
> >
> > Something in this patchset broke build on Windows:
> > https://github.com/BtbN/FFmpeg-Builds/runs/4991054208#step:4:9491
>
> Seems like it really was the typo gcc suggests. Pushed a fix for it.
Sorry for this stupid error, and thanks for the patch, we'll check the ourinternal CI and review process.
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".
prev parent reply other threads:[~2022-01-30 1:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 8:24 Xiang, Haihao
2022-01-24 8:24 ` [FFmpeg-devel] [PATCH v2 2/3] lavc/qsvdec: track the runtime session version Xiang, Haihao
2022-01-24 8:24 ` [FFmpeg-devel] [PATCH v2 3/3] lavc/qsvdec: export AVFilmGrainParams side data Xiang, Haihao
2022-01-27 5:37 ` [FFmpeg-devel] [PATCH v2 1/3] lavc/qsv: allow to add more parameter buffers to QSV frame Xiang, Haihao
2022-01-29 14:30 ` Timo Rothenpieler
2022-01-29 14:41 ` Timo Rothenpieler
2022-01-30 1:02 ` Xiang, Haihao [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=5d788095ba4502fc37ac785fd3c99b315e5aa6b4.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