From: Ben Hutchings <bhutchings@solarflare.com>
To: Somnath Kotur <Somnath.Kotur@emulex.com>
Cc: <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 2/5] be2net: Fix to allow setting of debug levels in the firmware.
Date: Thu, 26 Apr 2012 18:29:48 +0100 [thread overview]
Message-ID: <1335461388.2712.25.camel@bwh-desktop.uk.solarflarecom.com> (raw)
In-Reply-To: <464dcb28-2450-4e0b-a30f-d8c9104bac86@exht1.ad.emulex.com>
On Thu, 2012-04-26 at 19:57 +0530, Somnath Kotur wrote:
> From: Somnath Kotur <somnath.kotur@emulex.com>
[...]
> @@ -893,6 +959,7 @@ const struct ethtool_ops be_ethtool_ops = {
> .set_pauseparam = be_set_pauseparam,
> .get_strings = be_get_stat_strings,
> .set_phys_id = be_set_phys_id,
> + .set_msglevel = be_set_msglevel,
> .get_sset_count = be_get_sset_count,
> .get_ethtool_stats = be_get_ethtool_stats,
> .get_regs_len = be_get_reg_len,
This operation is intended for controlling logging by the driver, and
the flags are defined in <linux/netdevice.h>. (Not exported to userland
yet, but ethtool knows their names.)
If your firmware supports some kind of logging then it may be reasonable
to have this control both driver and firmware, but not *just* the
firmware.
You should also implement the get_msglevel operation at the same time.
Ben.
--
Ben Hutchings, Staff 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.
next prev parent reply other threads:[~2012-04-26 17:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 14:27 [PATCH net-next 2/5] be2net: Fix to allow setting of debug levels in the firmware Somnath Kotur
2012-04-26 17:29 ` Ben Hutchings [this message]
2012-04-27 6:46 ` Somnath.Kotur
2012-04-28 1:23 ` Somnath.Kotur
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=1335461388.2712.25.camel@bwh-desktop.uk.solarflarecom.com \
--to=bhutchings@solarflare.com \
--cc=Somnath.Kotur@emulex.com \
--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