From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: bhutchings@solarflare.com, akeem.g.abodunrin@intel.com,
netdev@vger.kernel.org, gospo@redhat.com, sassmann@redhat.com,
footplus@gmail.com
Subject: Re: [net-next v2 05/15] igb: Support to read and export SFF-8472/8079 data
Date: Fri, 19 Apr 2013 14:20:00 -0400 (EDT) [thread overview]
Message-ID: <20130419.142000.553422110375189224.davem@davemloft.net> (raw)
In-Reply-To: <1366328515.2248.61.camel@jtkirshe-mobl>
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Thu, 18 Apr 2013 16:41:55 -0700
> On Thu, 2013-04-18 at 16:37 -0700, Jeff Kirsher wrote:
>> On Thu, 2013-04-18 at 16:30 -0700, Jeff Kirsher wrote:
>> > From: "Akeem G. Abodunrin" <akeem.g.abodunrin@intel.com>
>> >
>> > This patch adds support to read and export SFF-8472/8079 (SFP data)
>> > over i2c, through Ethtool.
>> >
>> > v2: Changed implementation to accommodate any offset within SFF
>> module
>> > length boundary.
>> >
>> > Reported-by: Aurélien Guillaume <footplus@gmail.com>
>> > CC: Aurélien Guillaume <footplus@gmail.com>
>> > CC: Ben Hutchings <bhuntchings@solarflare.com>
>>
>> Looks like Akeem made a typo in your email Ben.
>
> I have fixed up your email in the patch that resides in my net-next
> tree.
Thanks for fixing this up.
next prev parent reply other threads:[~2013-04-19 18:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 23:30 [net-next 00/15][pull request] Intel Wired LAN Driver Updates Jeff Kirsher
2013-04-18 23:30 ` [net-next 01/15] ixgbe: in shutdown, do netif_running() under rtnl_lock Jeff Kirsher
2013-04-18 23:30 ` [net-next 02/15] ixgbe: Add support for WoL on 82599 SFP+ LOM Jeff Kirsher
2013-04-18 23:30 ` [net-next 03/15] ixgbe: Remove unnecessary #ifdef CONFIG_DEBUG_FS tests Jeff Kirsher
2013-04-18 23:30 ` [net-next v2 04/15] igb: Support for 100base-fx SFP Jeff Kirsher
2013-04-18 23:30 ` [net-next v2 05/15] igb: Support to read and export SFF-8472/8079 data Jeff Kirsher
2013-04-18 23:37 ` Jeff Kirsher
2013-04-18 23:41 ` Jeff Kirsher
2013-04-19 18:20 ` David Miller [this message]
2013-04-18 23:30 ` [net-next 06/15] igb: Implement support to power sfp cage and turn on I2C Jeff Kirsher
2013-04-18 23:30 ` [net-next 07/15] igb: random code and comments fix Jeff Kirsher
2013-04-18 23:30 ` [net-next 08/15] igb: Mask off check of frag_off as we only want fragment offset Jeff Kirsher
2013-04-18 23:30 ` [net-next 09/15] igb: Pull adapter out of main path in igb_xmit_frame_ring Jeff Kirsher
2013-04-18 23:30 ` [net-next 10/15] igb: Use rx/tx_itr_setting when setting up initial value of itr Jeff Kirsher
2013-04-18 23:30 ` [net-next 11/15] igb: Fix sparse warnings on function pointers Jeff Kirsher
2013-04-18 23:30 ` [net-next 12/15] igb: Fix code comments and whitespace Jeff Kirsher
2013-04-18 23:30 ` [net-next 13/15] igb: Enable EEE LP advertisement Jeff Kirsher
2013-04-18 23:30 ` [net-next 14/15] igb: add support for spoofchk config Jeff Kirsher
2013-04-18 23:30 ` [net-next 15/15] igb: Add support for i354 devices Jeff Kirsher
2013-04-19 18:19 ` [net-next 00/15][pull request] Intel Wired LAN Driver Updates David Miller
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=20130419.142000.553422110375189224.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akeem.g.abodunrin@intel.com \
--cc=bhutchings@solarflare.com \
--cc=footplus@gmail.com \
--cc=gospo@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=sassmann@redhat.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).