Thank you for helping with the review. I understand how challenging this
process can be.
I didn't merge the two series and resubmit them because they've already
been pending for over a month, and I'm a bit worried that resubmitting them
might mean waiting for another month.
If it's necessary to o
Hi,
Le torstaina 21. marraskuuta 2024, 12.43.38 EET flow gg a écrit :
> This patch comes after:
> [PATCH 1/2] Update R-V V vvc_mc vset to support more lengths
> [PATCH 2/2] lavc/vvc_mc: R-V V dmvr.
Reviewing patchset on mailing list is miserable enough as it is.
Sorry but I can't track patchset a
This patch comes after:
[PATCH 1/2] Update R-V V vvc_mc vset to support more lengths
[PATCH 2/2] lavc/vvc_mc: R-V V dmvr.
Rémi Denis-Courmont 于2024年11月19日周二 04:10写道：
> Le sunnuntaina 17. marraskuuta 2024, 15.17.49 EET flow gg a écrit :
> > > Generally speaking, I think that moving code should be
> Generally speaking, I think that moving code should be done in dedicated
> patches.
> You can branch here. The rest of the byte code is the same in all but one
> cases.
Updated this.
于2024年11月17日周日 21:17写道：
> From: sunyuechi
>
> ---
> libavcodec/riscv/h26x/asm.S | 127 +++
Le sunnuntaina 17. marraskuuta 2024, 15.17.49 EET flow gg a écrit :
> > Generally speaking, I think that moving code should be done in dedicated
> > patches.
> >
> > You can branch here. The rest of the byte code is the same in all but one
> > cases.
>
> Updated this.
Does not apply to HEAD.
--
From: sunyuechi
---
libavcodec/riscv/h26x/asm.S | 127 ++
libavcodec/riscv/vvc/vvc_mc_rvv.S | 117 ++-
2 files changed, 132 insertions(+), 112 deletions(-)
create mode 100644 libavcodec/riscv/h26x/asm.S
diff --git a/libavcodec/riscv/h26
