From: "Jiawen Wu" <jiawenwu@trustnetic.com>
To: "'Stephen Hemminger'" <stephen@networkplumber.org>,
<hau@realtek.com>, <drc@linux.ibm.com>,
<howard_wang@realsil.com.cn>, <jianwang@trustnetic.com>,
<sachin.saxena@oss.nxp.com>, <xing_wang@realsil.com.cn>,
<zaiyuwang@trustnetic.com>
Cc: <dev@dpdk.org>
Subject: RE: MAINTAINERS checkin
Date: Mon, 8 Sep 2025 10:59:59 +0800 [thread overview]
Message-ID: <018c01dc206c$aa507a70$fef16f50$@trustnetic.com> (raw)
In-Reply-To: <20250906091932.33d61730@hermes.local>
Hi Stephen,
There is our old domain which names trustnetic.com.
Now we use net-swift.com, but the email address with
the old domain can still be used.
> -----Original Message-----
> From: Stephen Hemminger <stephen@networkplumber.org>
> Sent: Sunday, September 7, 2025 12:20 AM
> To: hau@realtek.com; drc@linux.ibm.com; howard_wang@realsil.com.cn; jianwang@trustnetic.com; jiawenwu@trustnetic.com;
> sachin.saxena@oss.nxp.com; xing_wang@realsil.com.cn; zaiyuwang@trustnetic.com
> Cc: dev@dpdk.org
> Subject: MAINTAINERS checkin
>
> The following email addresses no longer appear to be valid.
> See attached python script (AI generated) for validation.
>
> Invalid Emails:
> ------------------------------
> • hau@realtek.com
> - Domain does not exist or is unreachable
> • drc@linux.ibm.com
> - Domain does not exist or is unreachable
> • howard_wang@realsil.com.cn
> - Domain does not exist or is unreachable
> • jianwang@trustnetic.com
> - Domain does not exist or is unreachable
> • jiawenwu@trustnetic.com
> - Domain does not exist or is unreachable
> • sachin.saxena@oss.nxp.com
> - Domain does not exist or is unreachable
> • xing_wang@realsil.com.cn
> - Domain does not exist or is unreachable
> • zaiyuwang@trustnetic.com
> - Domain does not exist or is unreachable
next prev parent reply other threads:[~2025-09-08 3:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-06 16:19 MAINTAINERS checkin Stephen Hemminger
2025-09-08 2:59 ` Jiawen Wu [this message]
2025-09-08 3:12 ` 回复: " 王颢
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='018c01dc206c$aa507a70$fef16f50$@trustnetic.com' \
--to=jiawenwu@trustnetic.com \
--cc=dev@dpdk.org \
--cc=drc@linux.ibm.com \
--cc=hau@realtek.com \
--cc=howard_wang@realsil.com.cn \
--cc=jianwang@trustnetic.com \
--cc=sachin.saxena@oss.nxp.com \
--cc=stephen@networkplumber.org \
--cc=xing_wang@realsil.com.cn \
--cc=zaiyuwang@trustnetic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.