From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>, <dev@dpdk.org>
Cc: Shahaji Bhosle <sbhosle@broadcom.com>, <stable@dpdk.org>,
Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v4 11/20] net/bnxt: fix clang compiler warnings
Date: Wed, 3 Nov 2021 13:24:30 +0000 [thread overview]
Message-ID: <787527e3-29b8-a621-5953-27237dd80579@intel.com> (raw)
In-Reply-To: <20211103005251.25524-12-ajit.khaparde@broadcom.com>
On 11/3/2021 12:52 AM, Ajit Khaparde wrote:
> From: Shahaji Bhosle <sbhosle@broadcom.com>
>
> Typecast flow_item type, action_item type and the ENUMs to uint32_t
> before comparing.
>
> Fixes: 53a0d4f7663 ("net/bnxt: support flow API item parsing")
> Cc: stable@dpdk.org
Hi Ajit,
Is above Fixes commit correct? It is from v20.05.
As far as I can see the error comes from:
Fixes: bdf4a3c6316b ("net/bnxt: support tunnel offload")
if that is correct, stable tag is not needed.
>
> Bugzilla ID: 821
Can you please move the tag above 'Fixes' line?
> Signed-off-by: Shahaji Bhosle <sbhosle@broadcom.com>
> Signed-off-by: Venkat Duvvuru <venkatkumar.duvvuru@broadcom.com>
> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
<...>
next prev parent reply other threads:[~2021-11-03 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211102040556.7840-1-venkatkumar.duvvuru@broadcom.com>
[not found] ` <20211103005251.25524-1-ajit.khaparde@broadcom.com>
2021-11-03 0:52 ` [dpdk-stable] [PATCH v4 03/20] net/bnxt: fix out of bounds issue in hash list Ajit Khaparde
2021-11-03 0:52 ` [dpdk-stable] [PATCH v4 11/20] net/bnxt: fix clang compiler warnings Ajit Khaparde
2021-11-03 13:24 ` Ferruh Yigit [this message]
[not found] ` <20211104215846.58672-1-ajit.khaparde@broadcom.com>
2021-11-04 21:58 ` [dpdk-stable] [PATCH v5 03/22] net/bnxt: fix out of bounds issue in hash list Ajit Khaparde
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=787527e3-29b8-a621-5953-27237dd80579@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=sbhosle@broadcom.com \
--cc=stable@dpdk.org \
--cc=venkatkumar.duvvuru@broadcom.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).