From: Aaron Brown <aaron.f.brown@intel.com>
To: davem@davemloft.net
Cc: Aaron Brown <aaron.f.brown@intel.com>,
netdev@vger.kernel.org, gospo@redhat.com, sassmann@redhat.com
Subject: [net-next 00/14 v2] 05/14 respun.
Date: Wed, 19 Feb 2014 19:49:37 -0800 [thread overview]
Message-ID: <1392868178-7011-1-git-send-email-aaron.f.brown@intel.com> (raw)
Patch 05/14 of the series was updated to address concerns from Joe Perches.
The rest of the series remains the same.
Mitch Williams (1):
05/14 v2 i40evf: fix up strings in init task
drivers/net/ethernet/intel/i40evf/i40evf_main.c | 36 +++++++++++--------------
1 file changed, 16 insertions(+), 20 deletions(-)
--
1.8.5.GIT
next reply other threads:[~2014-02-20 3:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 3:49 Aaron Brown [this message]
2014-02-20 3:49 ` [net-next 05/14 v2] i40evf: fix up strings in init task Aaron Brown
2014-02-20 4:09 ` Joe Perches
2014-02-20 4:51 ` Aaron Brown
2014-02-20 4:58 ` Joe Perches
2014-02-20 5:16 ` Aaron Brown
2014-02-20 16:20 ` Williams, Mitch A
2014-02-20 6:23 ` [net-next 00/14 v2] 05/14 respun 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=1392868178-7011-1-git-send-email-aaron.f.brown@intel.com \
--to=aaron.f.brown@intel.com \
--cc=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sassmann@redhat.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).