From: David Miller <davem@davemloft.net>
To: bhutchings@solarflare.com
Cc: bruce.w.allan@intel.com, netdev@vger.kernel.org,
sathya.perla@emulex.com, subbu.seetharaman@emulex.com,
ajit.khaparde@emulex.com, mchan@broadcom.com,
eilong@broadcom.com, divy@chelsio.com, pcnet32@frontier.com,
jdmason@kudzu.us, linux-net-drivers@solarflare.com,
shodgson@solarflare.com, shemminger@linux-foundation.org,
mcarlson@broadcom.com
Subject: Re: [net-next-2.6 RFC PATCH v3] ethtool: allow custom interval for physical identification
Date: Thu, 14 Apr 2011 21:19:34 -0700 (PDT) [thread overview]
Message-ID: <20110414.211934.193722116.davem@davemloft.net> (raw)
In-Reply-To: <1302830785.5282.691.camel@localhost>
From: Ben Hutchings <bhutchings@solarflare.com>
Date: Fri, 15 Apr 2011 02:26:25 +0100
> On Wed, 2011-04-13 at 16:09 -0700, Bruce Allan wrote:
>> When physical identification of an adapter is done by toggling the
>> mechanism on and off through software utilizing the set_phys_id operation,
>> it is done with a fixed duration for both on and off states. Some drivers
>> may want to set a custom duration for the on/off intervals. This patch
>> changes the API so the return code from the driver's entry point when it
>> is called with ETHTOOL_ID_ACTIVE can specify the frequency at which to
>> cycle the on/off states, and updates the drivers that have already been
>> converted to use the new set_phys_id and use the synchronous method for
>> identifying an adapter.
>>
>> The physical identification frequency set in the updated drivers is based
>> on how it was done prior to the introduction of set_phys_id.
>>
>> Compile tested only. Also fixes a compiler warning in sfc.
>>
>> v2: drivers do not return -EINVAL for ETHOOL_ID_ACTIVE
>> v3: fold patchset into single patch and cleanup per Ben's feedback
>>
>> Signed-off-by: Bruce Allan <bruce.w.allan@intel.com>
>> Cc: Ben Hutchings <bhutchings@solarflare.com>
> [...]
> Acked-by: Ben Hutchings <bhutchings@solarflare.com>
Applied, thanks everyone.
prev parent reply other threads:[~2011-04-15 4:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-13 23:09 [net-next-2.6 RFC PATCH v3] ethtool: allow custom interval for physical identification Bruce Allan
2011-04-14 18:55 ` Jon Mason
2011-04-15 1:26 ` Ben Hutchings
2011-04-15 4:19 ` David Miller [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=20110414.211934.193722116.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ajit.khaparde@emulex.com \
--cc=bhutchings@solarflare.com \
--cc=bruce.w.allan@intel.com \
--cc=divy@chelsio.com \
--cc=eilong@broadcom.com \
--cc=jdmason@kudzu.us \
--cc=linux-net-drivers@solarflare.com \
--cc=mcarlson@broadcom.com \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pcnet32@frontier.com \
--cc=sathya.perla@emulex.com \
--cc=shemminger@linux-foundation.org \
--cc=shodgson@solarflare.com \
--cc=subbu.seetharaman@emulex.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).