|SUCCESS| maintainers: prune unreachable contacts

[dpdklab at iol.unh.edu]

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

_AI Code Review_

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

This patch removes maintainer email addresses from the MAINTAINERS file due to unreachable contacts. Let me review it against the DPDK contribution guidelines.

commit a1b2c3d4e5f6 (placeholder - actual sha not provided)
Author: Thomas Monjalon <thomas at monjalon.net>

    maintainers: prune unreachable contacts

    Emails to the maintainers of ZTE zsda and HiSilicon uadk
    crypto and compress drivers do not respond.

    Signed-off-by: Thomas Monjalon <thomas at monjalon.net>

> diff --git a/MAINTAINERS b/MAINTAINERS
> index 0f5539f851..9164c736db 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1201,7 +1201,6 @@ F: drivers/crypto/scheduler/
>  F: doc/guides/cryptodevs/scheduler.rst
>  
>  HiSilicon UADK crypto
> -M: Zhangfei Gao <zhangfei.gao at linaro.org>
>  F: drivers/crypto/uadk/
>  F: doc/guides/cryptodevs/uadk.rst
>  F: doc/guides/cryptodevs/features/uadk.ini

Removing the maintainer for HiSilicon UADK crypto leaves this subsystem
as "Orphan" according to MAINTAINERS file conventions. Is there a plan to
identify a new maintainer? The Cc list includes several engineers from
Huawei - are any of them willing to take over maintenance?

> @@ -1300,7 +1299,6 @@ F: doc/guides/cryptodevs/virtio.rst
>  F: doc/guides/cryptodevs/features/virtio.ini
>  
>  ZTE Storage Data Accelerator (ZSDA)
> -M: Hanxiao Li <li.hanxiao at zte.com.cn>
>  F: drivers/crypto/zsda/
>  F: doc/guides/cryptodevs/zsda.rst
>  F: doc/guides/cryptodevs/features/zsda.ini

Similar concern for ZSDA crypto - does this become orphaned? The Cc list
includes ZTE engineers. Has anyone from ZTE been contacted to take over?

> @@ -1318,7 +1316,6 @@ F: doc/guides/compressdevs/octeontx.rst
>  F: doc/guides/compressdevs/features/octeontx.ini
>  
>  HiSilicon UADK compress
> -M: Zhangfei Gao <zhangfei.gao at linaro.org>
>  F: drivers/compress/uadk/
>  F: doc/guides/compressdevs/uadk.rst
>  F: doc/guides/compressdevs/features/uadk.ini

This removes the same maintainer for UADK compress. With both the crypto
and compress drivers losing their maintainer, should these sections be
marked with "Orphan" status explicitly?

> @@ -1352,7 +1349,6 @@ F: doc/guides/compressdevs/zlib.rst
>  F: doc/guides/compressdevs/features/zlib.ini
>  
>  ZTE Storage Data Accelerator (ZSDA)
> -M: Hanxiao Li <li.hanxiao at zte.com.cn>
>  F: drivers/common/zsda/
>  F: drivers/compress/zsda/
>  F: doc/guides/compressdevs/zsda.rst

Same ZTE maintainer removed here for the compress driver. This affects
three subsystems total (crypto, common, compress).

The technical changes are straightforward. However, from a project
governance perspective, were these individuals notified before removal?
The DPDK guidelines recommend attempting to contact maintainers through
multiple channels before declaring them unreachable. Additionally, when
subsystems become orphaned, they should ideally be marked as such or
deprecated if no new maintainer can be found.