All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willem de Bruijn <willemb@google.com>
To: davem@davemloft.net, netdev@vger.kernel.org,
	jeffrey.t.kirscher@intel.com, eilong@broadcom.com,
	aabdulla@nvidia.com
Cc: Willem de Bruijn <willemb@google.com>
Subject: [PATCH 3/4] bnx2x: add transmit timestamping support
Date: Fri, 27 Apr 2012 15:04:06 -0400	[thread overview]
Message-ID: <1335553447-11964-4-git-send-email-willemb@google.com> (raw)
In-Reply-To: <1335553447-11964-1-git-send-email-willemb@google.com>

Signed-off-by: Willem de Bruijn <willemb@google.com>
---
 drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c b/drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c
index 60d5b54..afa6cbb 100644
--- a/drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c
+++ b/drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c
@@ -2953,6 +2953,8 @@ netdev_tx_t bnx2x_start_xmit(struct sk_buff *skb, struct net_device *dev)
 
 	netdev_tx_sent_queue(txq, skb->len);
 
+	skb_tx_timestamp(skb);
+
 	txdata->tx_pkt_prod++;
 	/*
 	 * Make sure that the BD data is updated before updating the producer
-- 
1.7.7.3

  parent reply	other threads:[~2012-04-27 19:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-27 19:04 [PATCH 0/4 net-next] another transmit timestamping driver set Willem de Bruijn
2012-04-27 19:04 ` [PATCH 1/4] e1000: add transmit timestamping support Willem de Bruijn
2012-04-28  7:47   ` Eric Dumazet
2012-05-01  1:46     ` David Miller
2012-04-27 19:04 ` [PATCH 2/4] e1000e: " Willem de Bruijn
2012-04-28  7:47   ` Eric Dumazet
2012-05-01  1:46     ` David Miller
2012-04-27 19:04 ` Willem de Bruijn [this message]
2012-04-27 19:30   ` [PATCH 3/4] bnx2x: " Eilon Greenstein
2012-04-28  7:48   ` Eric Dumazet
2012-05-01  1:46     ` David Miller
2012-04-27 19:04 ` [PATCH 4/4] forcedeth: " Willem de Bruijn
2012-04-28  7:49   ` Eric Dumazet
2012-05-01  1:47     ` 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=1335553447-11964-4-git-send-email-willemb@google.com \
    --to=willemb@google.com \
    --cc=aabdulla@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=eilong@broadcom.com \
    --cc=jeffrey.t.kirscher@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.