From: Thomas Monjalon <thomas@monjalon.net>
To: Radu Nicolau <radu.nicolau@intel.com>
Cc: stable@dpdk.org, dev@dpdk.org, marko.kovacevic@intel.com,
john.mcnamara@intel.com, declan.doherty@intel.com
Subject: Re: [dpdk-stable] [PATCH v2] examples/bond: add mbuf alloc check
Date: Thu, 01 Feb 2018 01:21:08 +0100 [thread overview]
Message-ID: <3238225.zcTIVglMIO@xps> (raw)
In-Reply-To: <1516799806-16571-1-git-send-email-radu.nicolau@intel.com>
24/01/2018 14:16, Radu Nicolau:
> Fixes: cc7e8ae84faa ("examples/bond: add example application for link bonding mode 6")
> Coverity issue: 257008
> Cc: stable@dpdk.org
>
> Signed-off-by: Radu Nicolau <radu.nicolau@intel.com>
Applied, thanks
prev parent reply other threads:[~2018-02-01 0:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1516639016-28269-1-git-send-email-radu.nicolau@intel.com>
2018-01-24 13:16 ` Radu Nicolau
2018-02-01 0:21 ` Thomas Monjalon [this message]
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=3238225.zcTIVglMIO@xps \
--to=thomas@monjalon.net \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=radu.nicolau@intel.com \
--cc=stable@dpdk.org \
/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).