From: Joe Perches <joe@perches.com>
To: netdev <netdev@vger.kernel.org>,
Ariel.Elior@qlogic.com,
Dmitry Kravkov <Dmitry.Kravkov@qlogic.com>,
Eilon Greenstein <eilong@broadcom.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Who is the linux bnx2x maintainer?
Date: Fri, 16 May 2014 00:15:58 -0700 [thread overview]
Message-ID: <1400224558.30884.12.camel@joe-AO725> (raw)
Hello.
I just got email bounces for Ariel Elior and
how Dmitry Kravkov @broadcom.
Ariel is listed in the MAINTAINERS file as the BNX2X
maintainer. I doubt this is correct.
Anyone know who or if anyone should be listed as the
BNX2X maintainer?
-------- Forwarded Message --------
From: Ariel Elior <ariele@broadcom.com>
To: Joe Perches <joe@perches.com>
Subject: Automatic reply: [PATCH] bnx2x: Convert return 0 to return rc
The person you are trying to contact, Ariel Elior, has transferred
to QLogic Corporation. Please send your message to the following new
address: Ariel.Elior@qlogic.com
reply other threads:[~2014-05-16 7:15 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=1400224558.30884.12.camel@joe-AO725 \
--to=joe@perches.com \
--cc=Ariel.Elior@qlogic.com \
--cc=Dmitry.Kravkov@qlogic.com \
--cc=eilong@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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