From: Ben Hutchings <bhutchings@solarflare.com>
To: Vlad Zolotarov <vladz@broadcom.com>
Cc: Dave Miller <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Eilon Greenstein <eilong@broadcom.com>,
Dmitry Kravkov <dmitry@broadcom.com>,
Yaniv Rosner <yaniv.rosner@broadcom.com>
Subject: Re: [PATCH net-next 8/24] bnx2x: dump FW memory when appropriate msglvl is raised
Date: Thu, 16 Jun 2011 22:08:53 +0100 [thread overview]
Message-ID: <1308258533.2925.12.camel@bwh-desktop> (raw)
In-Reply-To: <201106141433.25717.vladz@broadcom.com>
The firmware dump functionality should be connected up to the new
ethtool operations added by:
commit 29dd54b72ba8c5ad0dd6dd33584449b5953f700b
Author: Anirban Chakraborty <anirban.chakraborty@qlogic.com>
Date: Thu May 12 12:48:32 2011 +0000
ethtool: Added support for FW dump
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
prev parent reply other threads:[~2011-06-16 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 11:33 [PATCH net-next 8/24] bnx2x: dump FW memory when appropriate msglvl is raised Vlad Zolotarov
2011-06-16 21:08 ` Ben Hutchings [this message]
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=1308258533.2925.12.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=dmitry@broadcom.com \
--cc=eilong@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=vladz@broadcom.com \
--cc=yaniv.rosner@broadcom.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;
as well as URLs for NNTP newsgroup(s).