From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Jakub Kicinski <kubakici@wp.pl>
Cc: netdev@vger.kernel.org, e1000-devel@lists.sourceforge.net
Subject: Re: [PATCH net-next 0/4] intel: string and rx tstamping cleanups
Date: Tue, 01 Apr 2014 18:44:57 -0700 [thread overview]
Message-ID: <1396403097.2230.1.camel@jtkirshe-mobl> (raw)
In-Reply-To: <1396399939-18420-1-git-send-email-kubakici@wp.pl>
[-- Attachment #1: Type: text/plain, Size: 554 bytes --]
On Wed, 2014-04-02 at 02:52 +0200, Jakub Kicinski wrote:
> This series contains promised string fixes and small cleanups for rx
> time
> stamping code in igb and ixgbe.
>
> String cleanups are limited to new line termination. Joe Perches
> suggested
> more improvements that seem worthwhile. [1]
>
> Rx time stamping path in igb and ixgbe was redesigned few times in the
> past
> and there are some small errors and leftovers from previous versions
> so
> I clean it up a little too.
Thanks Jakub, I will add your series to my queue.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2014-04-02 1:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 0:52 [PATCH net-next 0/4] intel: string and rx tstamping cleanups Jakub Kicinski
2014-04-02 0:52 ` [PATCH net-next 1/4] e1000: remove debug messages with function names Jakub Kicinski
2014-04-02 1:45 ` Jeff Kirsher
2014-04-02 0:52 ` [PATCH net-next 2/4] e1000e/igb/ixgbe/i40e: fix message terminations Jakub Kicinski
2014-04-02 1:45 ` Jeff Kirsher
2014-04-02 0:52 ` [PATCH net-next 3/4] ixgbe: clean up rx time stamping code Jakub Kicinski
2014-04-02 1:45 ` Jeff Kirsher
2014-04-02 0:52 ` [PATCH net-next 4/4] igb: fix last_rx_timestamp usage Jakub Kicinski
2014-04-02 1:46 ` Jeff Kirsher
2014-04-03 15:20 ` Vick, Matthew
2014-04-02 1:44 ` Jeff Kirsher [this message]
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=1396403097.2230.1.camel@jtkirshe-mobl \
--to=jeffrey.t.kirsher@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=kubakici@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).