From: George Zaguri via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: "Martin Storsjö" <martin@martin.st>
Cc: FFmpeg development discussions and patches
<ffmpeg-devel@ffmpeg.org>,
George Zaguri <george.zaguri@gmail.com>
Subject: [FFmpeg-devel] Re: [PATCH] avcodec/aarch64/vvc: optimised alf_classify function 8/10/12bit of vvc codec for aarch64
Date: Sun, 31 Aug 2025 11:05:16 +0100
Message-ID: <CAGQfSO0y06pZC8yGWbc4y0Xr4c7DHcVA5qNqVdFMM9ghqWam-A@mail.gmail.com> (raw)
In-Reply-To: <aec61cd5-a8f0-c62e-769a-efe2e6bc1348@martin.st>
Hello Martin,
I opened PR as you requested:
https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20377
I fixed most of the comments, except the one about decrement operation
instead of increment. I have done increment of loops in less conditions as
you told me, but I have logic based on index of loop which requires to have
increment (y loop & vb_pos check), otherwise I need to change logic in
there, what I would try to avoid and keep it close to generic version in
that case. For x loop I left increment as well to have the same logic as
for y loop.
All other comments I fixed.
All the best,
Georgii Zagoruiko
On Sat, Aug 30, 2025, 10:55 PM Martin Storsjö <martin@martin.st> wrote:
> On Sat, 30 Aug 2025, George Zaguri wrote:
>
> > You mentioned submition of patch as a PR, you mean open merge request I
> > guess, how it works with mailing list? Do I need to update the patch in
> > mailing list as well? Should I reflect opened PR somewhere?
>
> Not sure what I mentioned earlier (that was probably before we set up the
> new Forgejo instance), but nowadays, you can sign up at
> https://code.ffmpeg.org, fork https://code.ffmpeg.org/FFmpeg/FFmpeg and
> send a PR there, and I can take another look at it. In that form you don't
> need to send the patches to the mailing list at all, and only interact
> with the review through the Forgejo tool.
>
> // Martin
>
>
_______________________________________________
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-08-31 10:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 7:56 [FFmpeg-devel] " Georgii Zagoruiko
2025-08-01 17:50 ` Martin Storsjö
2025-08-03 17:54 ` George Zaguri
2025-08-30 12:44 ` [FFmpeg-devel] " George Zaguri via ffmpeg-devel
2025-08-30 21:55 ` Martin Storsjö via ffmpeg-devel
2025-08-31 10:05 ` George Zaguri 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=CAGQfSO0y06pZC8yGWbc4y0Xr4c7DHcVA5qNqVdFMM9ghqWam-A@mail.gmail.com \
--to=ffmpeg-devel@ffmpeg.org \
--cc=george.zaguri@gmail.com \
--cc=martin@martin.st \
/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