From: Bruce Richardson <bruce.richardson@intel.com>
To: Nicolas Pernas Maradei <nicolas.pernas.maradei@emutex.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] pcap: fix captured frame length
Date: Wed, 9 Mar 2016 18:42:31 +0000 [thread overview]
Message-ID: <20160309184231.GA8020@bricha3-MOBL3> (raw)
In-Reply-To: <56AA5A95.7000400@emutex.com>
On Thu, Jan 28, 2016 at 06:14:45PM +0000, Nicolas Pernas Maradei wrote:
> Hi Dror,
>
> Good catch. What you are saying makes sense and it is also explained in
> pcap's documentation. Was your setup unusual though?
> This might sound like a silly question but I don't remember seeing that
> issue and I should have since your fix is correct.
>
> Nico.
>
Applied to dpdk-next-net/rel_16_04
/Bruce
next prev parent reply other threads:[~2016-03-09 18:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 11:09 Dror Birkman
2016-01-28 18:14 ` Nicolas Pernas Maradei
2016-02-16 15:31 ` Bruce Richardson
2016-03-09 18:42 ` Bruce Richardson [this message]
2016-02-17 10:18 ` Nicolas Pernas Maradei
[not found] <1453968561-29085-1-git-send-email-dror.birkman@lightcyber.com>
[not found] ` <56AA5746.5030401@emutex.com>
2016-01-30 13:38 ` Dror Birkman
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=20160309184231.GA8020@bricha3-MOBL3 \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=nicolas.pernas.maradei@emutex.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).