From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id A48D71B44D; Tue, 23 Apr 2019 12:42:51 +0200 (CEST) Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id C99E2307CDD6; Tue, 23 Apr 2019 10:42:50 +0000 (UTC) Received: from [10.36.116.255] (unknown [10.36.116.255]) by smtp.corp.redhat.com (Postfix) with ESMTP id BBE425D71D; Tue, 23 Apr 2019 10:42:49 +0000 (UTC) To: "Hunt, David" , "Pattan, Reshma" , "dev@dpdk.org" Cc: "stable@dpdk.org" References: <20190410124910.24537-1-david.hunt@intel.com> <3AEA2BF9852C6F48A459DA490692831F2A449608@irsmsx110.ger.corp.intel.com> <51325962-658f-b542-0bed-5e7f5bb327ab@intel.com> From: Kevin Traynor Message-ID: Date: Tue, 23 Apr 2019 11:42:48 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <51325962-658f-b542-0bed-5e7f5bb327ab@intel.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.49]); Tue, 23 Apr 2019 10:42:50 +0000 (UTC) Subject: Re: [dpdk-dev] [PATCH v1] examples/vm_power_manager: fix buffer overrun X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Apr 2019 10:42:52 -0000 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. > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id C94C6A05D3 for ; Tue, 23 Apr 2019 12:42:54 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 2ECFB1B486; Tue, 23 Apr 2019 12:42:53 +0200 (CEST) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id A48D71B44D; Tue, 23 Apr 2019 12:42:51 +0200 (CEST) Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id C99E2307CDD6; Tue, 23 Apr 2019 10:42:50 +0000 (UTC) Received: from [10.36.116.255] (unknown [10.36.116.255]) by smtp.corp.redhat.com (Postfix) with ESMTP id BBE425D71D; Tue, 23 Apr 2019 10:42:49 +0000 (UTC) To: "Hunt, David" , "Pattan, Reshma" , "dev@dpdk.org" Cc: "stable@dpdk.org" References: <20190410124910.24537-1-david.hunt@intel.com> <3AEA2BF9852C6F48A459DA490692831F2A449608@irsmsx110.ger.corp.intel.com> <51325962-658f-b542-0bed-5e7f5bb327ab@intel.com> From: Kevin Traynor Message-ID: Date: Tue, 23 Apr 2019 11:42:48 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <51325962-658f-b542-0bed-5e7f5bb327ab@intel.com> Content-Type: text/plain; charset="UTF-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.49]); Tue, 23 Apr 2019 10:42:50 +0000 (UTC) Subject: Re: [dpdk-dev] [PATCH v1] examples/vm_power_manager: fix buffer overrun X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Message-ID: <20190423104248.i4Dcdd8z38CGts9N5vs5E3JvFXgggezYjL7FuUMM74A@z> 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. >