From: Bruce Richardson <bruce.richardson@intel.com>
To: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Cc: <dev@dpdk.org>, <stable@dpdk.org>
Subject: Re: [PATCH] net/i40e: fix read register return status check
Date: Tue, 19 Nov 2024 12:02:37 +0000 [thread overview]
Message-ID: <Zzx-XUO1OK-i9IEF@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <Zzx8BtjXw-ARYia5@bricha3-mobl1.ger.corp.intel.com>
On Tue, Nov 19, 2024 at 11:52:38AM +0000, Bruce Richardson wrote:
> On Fri, Nov 15, 2024 at 07:14:25PM +0000, Vladimir Medvedkin wrote:
> > 'i40e_get_outer_vlan()' does not check 'i40e_aq_debug_read_register()'
> > return value. This patch fixes this issue.
>
> I think a little more detail on the scope of the changes could be good
> here. It fixes the issue by allowing the function to return error, or zero
> on success rather than the value read. This change then causes some rework
> in the calling code to handle the error code and to change the form of the
> function call.
>
> >
> > Coverity issue: 445518
> >
> > Fixes: 86eb05d6350b ("net/i40e: add flow validate function")
> > Cc: beilei.xing@intel.com
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
>
> Fix below looks good, some minor comments.
>
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
>
Patch applied to dpdk-next-net-intel with commit log additions and the two
minor comments on the code fixed on apply.
Thanks,
/Bruce
prev parent reply other threads:[~2024-11-19 12:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 19:14 Vladimir Medvedkin
2024-11-19 11:52 ` Bruce Richardson
2024-11-19 12:02 ` Bruce Richardson [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=Zzx-XUO1OK-i9IEF@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=vladimir.medvedkin@intel.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).