|SUCCESS| maintainers: update RISC-V maintainer

[dpdklab at iol.unh.edu]

Test-Label: ai-code-review
Test-Status: SUCCESS
https://dpdk.org/patch/162819

_AI Code Review_

=== Patch Review: series.patch (via Claude) ===
Review date: 2026-04-02

I'll review this patch for compliance with DPDK coding standards and contribution guidelines.

```
git sha: (from patch) 20260401192401.6243-1-stanislaw.kardach at gmail.com
Author: Stanislaw Kardach <stanislaw.kardach at gmail.com>
Subject: [PATCH] maintainers: update RISC-V maintainer

This patch updates the RISC-V maintainer in the MAINTAINERS file,
promoting Sun Yuechi to primary maintainer and removing Stanislaw Kardach
due to time constraints.

> diff --git a/MAINTAINERS b/MAINTAINERS
> index 0f5539f851..eeb55951b4 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -334,11 +334,10 @@ F: examples/*/*_altivec.*
>  F: examples/common/altivec/
>  
>  RISC-V
> -M: Stanislaw Kardach <stanislaw.kardach at gmail.com>
> +M: Sun Yuechi <sunyuechi at iscas.ac.cn>
>  F: config/riscv/
>  F: doc/guides/linux_gsg/cross_build_dpdk_for_riscv.rst
>  F: lib/eal/riscv/
> -M: Sun Yuechi <sunyuechi at iscas.ac.cn>
>  F: lib/**/*rvv*

Does this reorganization unintentionally change the scope of Sun Yuechi's
maintainership? In the original structure, Sun Yuechi was listed as
maintainer specifically for lib/**/*rvv* files. After this change, they
become the primary maintainer for all RISC-V files (config/riscv/,
doc/guides/linux_gsg/cross_build_dpdk_for_riscv.rst, lib/eal/riscv/, and
lib/**/*rvv*).

Was this scope expansion intentional, or should Sun Yuechi's maintainer
entry remain positioned after lib/eal/riscv/ to indicate they maintain
only the RVV-specific files?

```