From: "John W. Linville" <linville@tuxdriver.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Rich Lane <rich.lane@bigswitch.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] af_packet: add byte counters
Date: Thu, 26 May 2016 11:01:57 -0400 [thread overview]
Message-ID: <20160526150157.GB5045@tuxdriver.com> (raw)
In-Reply-To: <57470C9F.4060903@intel.com>
On Thu, May 26, 2016 at 03:47:59PM +0100, Ferruh Yigit wrote:
> On 5/25/2016 10:03 PM, Rich Lane wrote:
> > Signed-off-by: Rich Lane <rich.lane@bigswitch.com>
>
> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Acked-by: John W. Linville <linville@tuxdriver.com>
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2016-05-26 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 21:03 Rich Lane
2016-05-26 14:47 ` Ferruh Yigit
2016-05-26 15:01 ` John W. Linville [this message]
2016-06-09 16:03 ` Bruce Richardson
2016-05-26 16:59 ` Rich Lane
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=20160526150157.GB5045@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=rich.lane@bigswitch.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).