patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Ke Zhang <ke1x.zhang@intel.com>,
	stable@dpdk.org, wenzhuo.lu@intel.com, jingjing.wu@intel.com,
	bernard.iremonger@intel.com,
	Christian Ehrhardt <christian.ehrhardt@canonical.com>
Cc: "Xueming(Steven) Li" <xuemingl@nvidia.com>,
	Luca Boccassi <bluca@debian.org>
Subject: Re: [PATCH 19.11.14-rc1 LTS] app/testpmd: fix compile error
Date: Wed, 8 Feb 2023 10:52:46 +0000	[thread overview]
Message-ID: <3ddb871c-673e-50a7-c94c-0d726f0ef8dd@redhat.com> (raw)
In-Reply-To: <20230208054518.159406-1-ke1x.zhang@intel.com>

On 08/02/2023 05:45, Ke Zhang wrote:
> [ upstream commit f99f2e55af7a49a6ee6555a5554847094086017f]
> 

Hi,

DPDK 19.11 LTS is EOL. Please see: https://core.dpdk.org/roadmap/#stable

For reference, the named commit does not exist in dpdk main. It looks 
like the patch is a rebase of:

commit 2809981e858f5cfa3ea9182e400a2c67f7c4744d
Author: David Marchand <david.marchand@redhat.com>
Date:   Fri Nov 18 09:53:10 2022 +0100

     app/testpmd: fix build with clang 15 in flow code

     This variable is not used and has been copy/pasted in a lot of other
     code.

     Fixes: 938a184a1870 ("app/testpmd: implement basic support for flow 
API")


> variable 'c' is set but not used, it should be cleard.
> 
> Fixes: 938a184a1870 ("app/testpmd: implement basic support for flow API")
> 
> Signed-off-by: Ke Zhang <ke1x.zhang@intel.com>
> ---
>   app/test-pmd/config.c | 2 --
>   1 file changed, 2 deletions(-)
> 
> diff --git a/app/test-pmd/config.c b/app/test-pmd/config.c
> index 9f96e77ba3..a04ce0ec64 100644
> --- a/app/test-pmd/config.c
> +++ b/app/test-pmd/config.c
> @@ -1457,7 +1457,6 @@ port_flow_destroy(portid_t port_id, uint32_t n, const uint32_t *rule)
>   {
>   	struct rte_port *port;
>   	struct port_flow **tmp;
> -	uint32_t c = 0;
>   	int ret = 0;
>   
>   	if (port_id_is_invalid(port_id, ENABLED_WARN) ||
> @@ -1490,7 +1489,6 @@ port_flow_destroy(portid_t port_id, uint32_t n, const uint32_t *rule)
>   		}
>   		if (i == n)
>   			tmp = &(*tmp)->next;
> -		++c;
>   	}
>   	return ret;
>   }


      reply	other threads:[~2023-02-08 10:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08  5:45 Ke Zhang
2023-02-08 10:52 ` Kevin Traynor [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=3ddb871c-673e-50a7-c94c-0d726f0ef8dd@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=bernard.iremonger@intel.com \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=jingjing.wu@intel.com \
    --cc=ke1x.zhang@intel.com \
    --cc=stable@dpdk.org \
    --cc=wenzhuo.lu@intel.com \
    --cc=xuemingl@nvidia.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).