netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: "Jakub Kiciński" <moorray3@wp.pl>
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
	netdev@vger.kernel.org, e1000-devel@lists.sourceforge.net
Subject: Re: [PATCH net-next 02/10] e1000e: add timeout for TX HW time stamping work
Date: Fri, 14 Mar 2014 11:44:15 -0700	[thread overview]
Message-ID: <1394822655.3253.7.camel@joe-AO722> (raw)
In-Reply-To: <20140314190242.4bba2b42@north>

On Fri, 2014-03-14 at 19:02 +0100, Jakub Kiciński wrote:
> On Fri, 14 Mar 2014 10:48:37 -0700, Joe Perches wrote:
> > On Fri, 2014-03-14 at 18:34 +0100, Jakub Kicinski wrote:
> > > Hardware may fail to report time stamp e.g.:
> > >  - when hardware time stamping is not enabled
> > >  - when time stamp is requested shortly after ifup
> > 
> > trivia:
> > 
> > > diff --git a/drivers/net/ethernet/intel/e1000e/netdev.c b/drivers/net/ethernet/intel/e1000e/netdev.c
> > []
> > > @@ -1155,6 +1155,12 @@ static void e1000e_tx_hwtstamp_work(struct work_struct *work)
> > >  		skb_tstamp_tx(adapter->tx_hwtstamp_skb, &shhwtstamps);
> > >  		dev_kfree_skb_any(adapter->tx_hwtstamp_skb);
> > >  		adapter->tx_hwtstamp_skb = NULL;
> > > +	} else if (time_after(jiffies, adapter->tx_hwtstamp_start
> > > +			      + adapter->tx_timeout_factor * HZ)) {
> > > +		dev_kfree_skb_any(adapter->tx_hwtstamp_skb);
> > > +		adapter->tx_hwtstamp_skb = NULL;
> > > +		adapter->tx_hwtstamp_timeouts++;
> > > +		e_warn("clearing Tx timestamp hang");
> > 
> > Missing \n termination
> 
> I copied that line from ixgbe and assumed that the magic macro adds
> termination...
> 
> I see that igb and i40e also lack the \n on similar messages.

There's a bunch of them.

>  Can I fix
> them all in a single follow-up patch?

There are also a bunch of _dbg messages that lack that
\n and those seem to be function tracing uses that should
just be deleted.

  reply	other threads:[~2014-03-14 18:44 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-14 17:34 [PATCH net-next 00/10] Small fixes for Tx time stamping in Intel drivers Jakub Kicinski
2014-03-14 17:34 ` [PATCH net-next 01/10] doc: update driver TX algorithm in timestamping.txt Jakub Kicinski
2014-03-14 19:12   ` Sergei Shtylyov
2014-03-14 17:34 ` [PATCH net-next 02/10] e1000e: add timeout for TX HW time stamping work Jakub Kicinski
2014-03-14 17:48   ` Joe Perches
2014-03-14 18:02     ` Jakub Kiciński
2014-03-14 18:44       ` Joe Perches [this message]
2014-03-14 19:14         ` Joe Perches
2014-03-14 19:16         ` Jakub Kiciński
2014-03-14 23:20   ` Jeff Kirsher
2014-03-14 17:34 ` [PATCH net-next 03/10] e1000e: remove redundant if clause from PTP work Jakub Kicinski
2014-03-14 23:17   ` Jeff Kirsher
2014-03-14 17:34 ` [PATCH net-next 04/10] ixgbe: " Jakub Kicinski
2014-03-14 23:17   ` Jeff Kirsher
2014-03-14 17:34 ` [PATCH net-next 05/10] ixgbe: never generate both software and hardware timestamps Jakub Kicinski
2014-03-14 23:17   ` Jeff Kirsher
2014-03-14 17:34 ` [PATCH net-next 06/10] ixgbe: fix race conditions on queuing skb for HW time stamp Jakub Kicinski
2014-03-14 23:18   ` Jeff Kirsher
2014-03-14 17:34 ` [PATCH net-next 07/10] igb: never generate both software and hardware timestamps Jakub Kicinski
2014-03-14 23:18   ` Jeff Kirsher
2014-03-14 17:34 ` [PATCH net-next 08/10] igb: fix race conditions on queuing skb for HW time stamp Jakub Kicinski
2014-03-14 23:18   ` Jeff Kirsher
2014-03-14 17:34 ` [PATCH net-next 09/10] i40e: never generate both software and hardware timestamps Jakub Kicinski
2014-03-14 23:18   ` Jeff Kirsher
2014-03-14 17:34 ` [PATCH net-next 10/10] i40e: fix race conditions on queuing skb for HW time stamp Jakub Kicinski

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=1394822655.3253.7.camel@joe-AO722 \
    --to=joe@perches.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=moorray3@wp.pl \
    --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 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).