From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Richard Cochran <richardcochran@gmail.com>
Cc: Willem, netdev@vger.kernel.org, Bruijn <willemb@google.com>,
David Miller <davem@davemloft.net>,
e1000-devel@lists.sourceforge.net
Subject: Re: [PATCH net-next 3/4] e1000e: advertise transmit time stamping
Date: Mon, 23 Jul 2012 01:19:21 -0700 [thread overview]
Message-ID: <1343031561.23226.30.camel@jtkirshe-mobl> (raw)
In-Reply-To: <e0e31f0229b5bfda1684122498b4d6fb3195cf26.1342976654.git.richardcochran@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 567 bytes --]
On Sun, 2012-07-22 at 19:15 +0200, Richard Cochran wrote:
> This driver now offers software transmit time stamping, so it should
> advertise that fact via ethtool. Compile tested only.
>
> Signed-off-by: Richard Cochran <richardcochran@gmail.com>
>
> Cc: Willem de Bruijn <willemb@google.com>
> Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> Cc: e1000-devel@lists.sourceforge.net
> ---
> drivers/net/ethernet/intel/e1000e/ethtool.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
Acked-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 395 bytes --]
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
[-- Attachment #3: Type: text/plain, Size: 257 bytes --]
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
next prev parent reply other threads:[~2012-07-23 8:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1342976654.git.richardcochran@gmail.com>
2012-07-22 17:15 ` [PATCH net-next 1/4] bnx2x: advertise transmit time stamping Richard Cochran
2012-07-22 17:15 ` [PATCH net-next 2/4] e1000: " Richard Cochran
2012-07-22 17:15 ` [PATCH net-next 3/4] e1000e: " Richard Cochran
2012-07-22 17:15 ` [PATCH net-next 4/4] forcedeth: " Richard Cochran
[not found] ` <379f084af5dcbcccda309ecb0d0032196fb496f3.1342976654.git.richardcochran@gmail.com>
2012-07-22 18:29 ` [PATCH net-next 1/4] bnx2x: " Eilon Greenstein
2012-07-22 19:33 ` [PATCH net-next 0/4] Tx time stamp advertising for four drivers David Miller
[not found] ` <33885adb6b0e97e6b21fd1903fb6ede3ed7b50ab.1342976654.git.richardcochran@gmail.com>
2012-07-23 8:18 ` [PATCH net-next 2/4] e1000: advertise transmit time stamping Jeff Kirsher
[not found] ` <d95c3b5bf30e3a7d056ad7f9fb774bbf572dc217.1342976654.git.richardcochran@gmail.com>
2012-07-23 13:27 ` [PATCH net-next 4/4] forcedeth: " Willem de Bruijn
[not found] ` <e0e31f0229b5bfda1684122498b4d6fb3195cf26.1342976654.git.richardcochran@gmail.com>
2012-07-23 8:19 ` Jeff Kirsher [this message]
2012-07-23 16:07 ` [E1000-devel] [PATCH net-next 3/4] e1000e: " Allan, Bruce W
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=1343031561.23226.30.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=davem@davemloft.net \
--cc=e1000-devel@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=willemb@google.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).