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
Subject: [PATCH 0/4 net-next] another transmit timestamping driver set
Date: Fri, 27 Apr 2012 15:04:03 -0400	[thread overview]
Message-ID: <1335553447-11964-1-git-send-email-willemb@google.com> (raw)

This series adds skb_tx_timestamp calls into the ndo_start_xmit
implementations of a few more drivers. All calls are added before
increasing the txqueue write offset, to avoid the race conditions
with the completion handler experienced earlier.

All changes have been tested with the txtimestamp test at
http://kernel.googlecode.com/files/txtimestamp.c before and after
applying the change (to a slightly different kernel, though) to
verify that it actually adds the missing functionality and
introduces no obvious bugs.

Apologies if I missed any driver maintainers.

Signed-off-by Willem de Bruijn <willemb@google.com>

             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 Willem de Bruijn [this message]
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 ` [PATCH 3/4] bnx2x: " Willem de Bruijn
2012-04-27 19:30   ` 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-1-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.