From: David Marchand <david.marchand@redhat.com>
To: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] examples/pipeline: fix resource release in table update
Date: Mon, 19 Oct 2020 09:10:19 +0200 [thread overview]
Message-ID: <CAJFAV8zVryFjqyAm06TBg67QJcXggsb-WLKwZiBAasZddeVSjw@mail.gmail.com> (raw)
In-Reply-To: <20201013184036.47101-1-cristian.dumitrescu@intel.com>
On Tue, Oct 13, 2020 at 8:41 PM Cristian Dumitrescu
<cristian.dumitrescu@intel.com> wrote:
>
> Fix the resource release sequence in table update.
>
> Fixes: 5074e1d551 ("examples/pipeline: add configuration commands")
> Coverity issues: 362882, 363041, 363044, 363047
$ ./devtools/check-git-log.sh
Missing 'Coverity issue:' tag:
examples/pipeline: fix resource release in table update
The tag is "Coverity issue:", no plural.
And reporting bz or coverity tokens are put before Fixes:.
Applied, thanks.
--
David Marchand
prev parent reply other threads:[~2020-10-19 7:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 18:40 Cristian Dumitrescu
2020-10-19 7:10 ` David Marchand [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=CAJFAV8zVryFjqyAm06TBg67QJcXggsb-WLKwZiBAasZddeVSjw@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@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).