From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Salil Mehta <salil.mehta@huawei.com>, Jijie Shao <shaojijie@huawei.com>
Cc: netdev@vger.kernel.org, helpdesk@kernel.org
Subject: Bouncing maintainer: Yisen Zhuang
Date: Tue, 24 Sep 2024 10:18:41 -0400 [thread overview]
Message-ID: <20240924-muscular-wise-stingray-dce77b@lemur> (raw)
Hello:
I'm reaching out to co-maintainers of the following subsystems:
- HISILICON NETWORK SUBSYSTEM 3 DRIVER (HNS3)
- HISILICON NETWORK SUBSYSTEM DRIVER
The email address for one of your maintainers is bouncing:
M: Yisen Zhuang <yisen.zhuang@huawei.com>
There are several possible courses of action:
1. If you know the new email address for the maintainer, please ask them to
submit a patch for MAINTAINERS and .mailmap files.
2. If this maintainer stepped away from their duties, or if co-maintainers are
equally unable to reach them via any other means, please submit a patch to
MAINTAINERS to remove their M: entry.
The goal is to have no bouncing M: entries in the maintainers file, so please
follow up as soon as you have decided on the correct course of action.
Best regards,
--
Konstantin Ryabitsev
Linux Foundation
bugspray track
reply other threads:[~2024-09-24 14:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240924-muscular-wise-stingray-dce77b@lemur \
--to=konstantin@linuxfoundation.org \
--cc=helpdesk@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=salil.mehta@huawei.com \
--cc=shaojijie@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