From: 许俊伟 <javen_xu@realsil.com.cn>
To: Thomas Monjalon <thomas@monjalon.net>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "byron.marohn@intel.com" <byron.marohn@intel.com>,
"david.hunt@intel.com" <david.hunt@intel.com>,
"lee.daly@intel.com" <lee.daly@intel.com>,
"xuanziyang2@huawei.com" <xuanziyang2@huawei.com>,
"kyo.liu@nebula-matrix.com" <kyo.liu@nebula-matrix.com>
Subject: RE: [PATCH] maintainers: prune unreachable contacts
Date: Tue, 24 Feb 2026 02:34:39 +0000 [thread overview]
Message-ID: <067c453863ff4b9e9e3ba90f4dfe5222@realsil.com.cn> (raw)
In-Reply-To: <202602240217.61O2Ha8G22926752@rtits1.realtek.com.tw>
>-----Original Message-----
>From: Thomas Monjalon <thomas@monjalon.net>
>Sent: 2026年2月20日 22:53
>To: dev@dpdk.org
>Cc: byron.marohn@intel.com; david.hunt@intel.com; lee.daly@intel.com;
>xuanziyang2@huawei.com; kyo.liu@nebula-matrix.com; Javen Xu
><javen_xu@realsil.com.cn>
>Subject: [PATCH] maintainers: prune unreachable contacts
>
>
>External mail : This email originated from outside the organization. Do not
>reply, click links, or open attachments unless you recognize the sender and
>know the content is safe.
>
>
>
>Some email addresses are not responding to "RCPT TO".
>Drop these maintainers as we cannot reach them.
>
>Cc: byron.marohn@intel.com
>Cc: david.hunt@intel.com
>Cc: lee.daly@intel.com
>Cc: xuanziyang2@huawei.com
>Cc: kyo.liu@nebula-matrix.com
>Cc: javen_xu@realsil.com.cn
>
>Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
>
>---
>
>This patch should confirm the email bounces.
>If this is a mistake, please reply.
>---
> MAINTAINERS | 7 -------
> 1 file changed, 7 deletions(-)
>
>diff --git a/MAINTAINERS b/MAINTAINERS
>index b7a1e28c5a..2faf28f522 100644
>--- a/MAINTAINERS
>+++ b/MAINTAINERS
>@@ -774,7 +774,6 @@ F: doc/guides/nics/hns3.rst
> F: doc/guides/nics/features/hns3.ini
>
> Huawei hinic
>-M: Ziyang Xuan <xuanziyang2@huawei.com>
> M: Xiaoyun Wang <cloud.wangxiaoyun@huawei.com>
> F: drivers/net/hinic/
> F: doc/guides/nics/hinic.rst
>@@ -1021,7 +1020,6 @@ F: doc/guides/nics/features/rnp.ini
>
> Nebulamatrix nbl
> M: Dimon Zhao <dimon.zhao@nebula-matrix.com>
>-M: Kyo Liu <kyo.liu@nebula-matrix.com>
> M: Leon Yu <leon.yu@nebula-matrix.com>
> M: Sam Chen <sam.chen@nebula-matrix.com>
> F: drivers/net/nbl/
>@@ -1032,7 +1030,6 @@ Realtek r8169
> M: Howard Wang <howard_wang@realsil.com.cn>
> M: Chunhao Lin <hau@realtek.com>
> M: Xing Wang <xing_wang@realsil.com.cn>
>-M: Javen Xu <javen_xu@realsil.com.cn>
Hi, Thomas
Please keep me in the MAINTAINERS file. My email address <javen_xu@realsil.com.cn> is valid and working properly.
The previous "RCPT TO" error was caused by our company's firewall blocking the incoming emails.
I have adjusted the firewall settings and unblocked the traffic. Sorry for the inconvenience.
Thanks,
Javen Xu
next parent reply other threads:[~2026-02-24 7:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202602240217.61O2Ha8G22926752@rtits1.realtek.com.tw>
2026-02-24 2:34 ` 许俊伟 [this message]
2026-02-20 14:53 [PATCH] maintainers: prune unreachable contacts Thomas Monjalon
2026-03-03 16:24 ` Thomas Monjalon
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=067c453863ff4b9e9e3ba90f4dfe5222@realsil.com.cn \
--to=javen_xu@realsil.com.cn \
--cc=byron.marohn@intel.com \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=kyo.liu@nebula-matrix.com \
--cc=lee.daly@intel.com \
--cc=thomas@monjalon.net \
--cc=xuanziyang2@huawei.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox