DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: dev@dpdk.org, Daniel Mrzyglod <danielx.t.mrzyglod@intel.com>
Cc: helin.zhang@intel.com, jingjing.wu@intel.com, "Mcnamara,
	John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] [PATCH] i40e: fix unchecked return value
Date: Wed, 25 May 2016 12:42:54 +0200	[thread overview]
Message-ID: <3226148.WTHhNAa6l8@xps13> (raw)
In-Reply-To: <1464074734-199475-1-git-send-email-danielx.t.mrzyglod@intel.com>

2016-05-24 09:25, Daniel Mrzyglod:
> Fixes: 71d35259ff67 ("i40e: tear down flow director")
> Coverity ID 13198

FYI, in recent commits I've started to standardize the coverity reports
like that:

Coverity issue: XXXXX
Fixes: ...

Please spread the word.

  reply	other threads:[~2016-05-25 10:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-24  7:25 Daniel Mrzyglod
2016-05-25 10:42 ` Thomas Monjalon [this message]
2016-05-26  9:27   ` Mcnamara, John
2016-06-13 10:09 ` 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=3226148.WTHhNAa6l8@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=danielx.t.mrzyglod@intel.com \
    --cc=dev@dpdk.org \
    --cc=helin.zhang@intel.com \
    --cc=jingjing.wu@intel.com \
    --cc=john.mcnamara@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).