From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Remy Horton <remy.horton@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 0/2] fix Coverity issues
Date: Tue, 21 Jun 2016 15:58:13 +0200 [thread overview]
Message-ID: <44461562.UbL4hluZO6@xps13> (raw)
In-Reply-To: <1466436187-5225-1-git-send-email-remy.horton@intel.com>
> Remy Horton (2):
> app/test-pmd: fix Coverity issues
> examples/l2fwd-keepalive: fix Coverity issues
Applied with titles reworded as suggested by Pablo, thanks
next prev parent reply other threads:[~2016-06-21 13:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 13:49 [dpdk-dev] [PATCH v1] app: " Remy Horton
2016-06-20 13:56 ` Thomas Monjalon
2016-06-20 14:50 ` Remy Horton
2016-06-20 15:23 ` [dpdk-dev] [PATCH v2 0/2] " Remy Horton
2016-06-20 15:23 ` [dpdk-dev] [PATCH v2 1/2] app/test-pmd: " Remy Horton
2016-06-20 15:33 ` De Lara Guarch, Pablo
2016-06-20 15:23 ` [dpdk-dev] [PATCH v2 2/2] examples/l2fwd-keepalive: " Remy Horton
2016-06-21 13:58 ` Thomas Monjalon [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-04-21 3:42 [dpdk-dev] [PATCH 0/6] fix i40e problematic dereference Helin Zhang
2016-06-26 15:46 ` [dpdk-dev] [PATCH v2 0/2] fix coverity issues Helin Zhang
2016-06-28 12:01 ` Bruce Richardson
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=44461562.UbL4hluZO6@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=remy.horton@intel.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).