From: Joe Perches <joe@perches.com>
To: Leon Romanovsky <leon@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Yufeng Mo <moyufeng@huawei.com>,
HuazhongTan <tanhuazhong@huawei.com>,
YangShen <shenyang39@huawei.com>,
Guangbin Huang <huangguangbin2@huawei.com>
Cc: Leon Romanovsky <leonro@nvidia.com>,
linux-kernel@vger.kernel.org,
linux-netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net] MAINTAINERS: Remove Bin Luo as his email bounces
Date: Wed, 29 Sep 2021 22:21:28 -0700 [thread overview]
Message-ID: <553c081e8e4e8c3eb146f4ddf1ca24f9a007afa2.camel@perches.com> (raw)
In-Reply-To: <045a32ccf394de66b7899c8b732f44dc5f4a1154.1632978665.git.leonro@nvidia.com>
On Thu, 2021-09-30 at 08:12 +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> The emails sent to luobin9@huawei.com bounce with error:
> "Recipient address rejected: Failed recipient validation check."
>
> So let's remove his entry and change the status of hinic driver till
> someone in Huawei will step-in to maintain it again.
It's probably better to at least cc the other huawei folks
that have also submitted patches for this driver recently.
> Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
> ---
> MAINTAINERS | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index b585e6092a74..1e39189b4004 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -8609,9 +8609,8 @@ F: Documentation/devicetree/bindings/iio/humidity/st,hts221.yaml
> F: drivers/iio/humidity/hts221*
>
> HUAWEI ETHERNET DRIVER
> -M: Bin Luo <luobin9@huawei.com>
> L: netdev@vger.kernel.org
> -S: Supported
> +S: Orphan
> F: Documentation/networking/device_drivers/ethernet/huawei/hinic.rst
> F: drivers/net/ethernet/huawei/hinic/
>
>
next prev parent reply other threads:[~2021-09-30 5:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 5:12 [PATCH net] MAINTAINERS: Remove Bin Luo as his email bounces Leon Romanovsky
2021-09-30 5:21 ` Joe Perches [this message]
2021-10-01 22:20 ` patchwork-bot+netdevbpf
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=553c081e8e4e8c3eb146f4ddf1ca24f9a007afa2.camel@perches.com \
--to=joe@perches.com \
--cc=davem@davemloft.net \
--cc=huangguangbin2@huawei.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=moyufeng@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=shenyang39@huawei.com \
--cc=tanhuazhong@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 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.