From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Robert Sanford <rsanford@prolexic.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Question: Can't make pcap and refcnt to match
Date: Tue, 26 Nov 2013 17:05:13 +0100 [thread overview]
Message-ID: <201311261705.14030.thomas.monjalon@6wind.com> (raw)
In-Reply-To: <CAFmpvUNpB16a8rkM=d7R0B-+6aufzP32qrP3ddC8wG2Ux2Y1ig@mail.gmail.com>
Hello,
26/11/2013 16:42, Robert Sanford :
> I've been meaning to submit a change, but I'm not familiar with the
> process.
The process is to send your patch with git (format-patch + send-email).
You have to set a short title and a longer commit log explaining what was the
problem and how you fix it.
The commit log must have a Signed-off-by line (see "Developer's Certificate of
Origin" in https://www.kernel.org/doc/Documentation/SubmittingPatches
> + /*
> + * Fix buffer overflow problems.
> + * 1. Frame may be longer than mbuf.
> + * 2. Capture length (caplen) may be less than original packet length.
> + */
This should be in the commit log.
Keep only comments needed to understand the code.
> + /****
> + RTE_LOG(INFO, PMD, "eth_pcap_rx: i=%u caplen=%u framelen=%u tail=%u
> len=%u\n",
> + i, header.caplen, header.len, tailroom, len);
> + ****/
Why it is commented out ?
If it's important, it is an INFO log.
If it's useful when debugging, set it to DEBUG.
If it's a temporary debug, remove it.
By the way, thank you for your patch.
--
Thomas
next prev parent reply other threads:[~2013-11-26 16:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 13:07 Mats Liljegren
2013-11-26 13:46 ` Richardson, Bruce
2013-11-26 15:42 ` Robert Sanford
2013-11-26 16:05 ` Thomas Monjalon [this message]
2013-12-03 17:04 ` Mats Liljegren
2013-12-04 10:44 ` Richardson, Bruce
2013-12-04 11:02 ` Mats Liljegren
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=201311261705.14030.thomas.monjalon@6wind.com \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=rsanford@prolexic.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).