From: Kevin Traynor <ktraynor@redhat.com>
To: "Hunt, David" <david.hunt@intel.com>,
"Pattan, Reshma" <reshma.pattan@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v1] examples/vm_power_manager: fix buffer overrun
Date: Tue, 23 Apr 2019 11:42:48 +0100 [thread overview]
Message-ID: <b50bd860-dc7e-a982-999f-17f2554f57d6@redhat.com> (raw)
Message-ID: <20190423104248.i4Dcdd8z38CGts9N5vs5E3JvFXgggezYjL7FuUMM74A@z> (raw)
In-Reply-To: <51325962-658f-b542-0bed-5e7f5bb327ab@intel.com>
On 23/04/2019 11:31, Hunt, David wrote:
> Hi Kevin,
>
> On 23/4/2019 11:26 AM, Kevin Traynor wrote:
>> On 18/04/2019 16:14, Pattan, Reshma wrote:
>>>> Fixes: d26c18c93260 ("examples/vm_power: cpu frequency in host")
>>>> Coverity issue: 337660
>>> Candidate for stable@dpdk.org?
>> There is no reply to this comment - re-asking as I will probably have
>> the same question in a few weeks :-)
>
>
> There was a v2 this morning and it had a --cc stable on it. :)
>
Yes, you're right, but that just puts it in the email and it gets lost
from the commit message. The 'Cc: stable@dpdk.org' tag is needed in the
commit message so it can be picked up by scripts later when finding
which patches should be backported.
https://doc.dpdk.org/guides/contributing/stable.html#what-changes-should-be-backported
As it's discussed, maybe Thomas can add it for this patch when applying.
thanks,
Kevin.
> Rgds,
> Dave.
>
next prev parent reply other threads:[~2019-04-23 10:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 12:49 David Hunt
2019-04-10 12:49 ` David Hunt
2019-04-18 15:14 ` Pattan, Reshma
2019-04-18 15:14 ` Pattan, Reshma
2019-04-23 10:26 ` Kevin Traynor
2019-04-23 10:26 ` Kevin Traynor
2019-04-23 10:31 ` Hunt, David
2019-04-23 10:31 ` Hunt, David
2019-04-23 10:42 ` Kevin Traynor [this message]
2019-04-23 10:42 ` Kevin Traynor
2019-04-22 21:54 ` Thomas Monjalon
2019-04-22 21:54 ` Thomas Monjalon
2019-04-23 8:21 ` Hunt, David
2019-04-23 8:21 ` Hunt, David
2019-04-23 8:33 ` Thomas Monjalon
2019-04-23 8:33 ` Thomas Monjalon
2019-04-23 8:35 ` Hunt, David
2019-04-23 8:35 ` Hunt, David
2019-04-23 8:53 ` [dpdk-dev] [PATCH v2] " David Hunt
2019-04-23 8:53 ` David Hunt
2019-04-26 8:42 ` [dpdk-dev] [PATCH v3] " David Hunt
2019-04-26 8:42 ` David Hunt
2019-05-02 23:38 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2019-05-02 23:38 ` Thomas Monjalon
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=b50bd860-dc7e-a982-999f-17f2554f57d6@redhat.com \
--to=ktraynor@redhat.com \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=reshma.pattan@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).