From: "Wang, Haiyue" <haiyue.wang@intel.com>
To: Yunjian Wang <wangyunjian@huawei.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "dingxiaoxiong@huawei.com" <dingxiaoxiong@huawei.com>,
"xudingke@huawei.com" <xudingke@huawei.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH v2 1/1] net/ixgbe: check ixgbe filter init failure
Date: Thu, 30 Dec 2021 05:32:30 +0000 [thread overview]
Message-ID: <BYAPR11MB3495323A5237463A03EFBDA9F7459@BYAPR11MB3495.namprd11.prod.outlook.com> (raw)
In-Reply-To: <68c35e56d29ee7d8dcd7b9734ea067c0111a120c.1640344520.git.wangyunjian@huawei.com>
> -----Original Message-----
> From: Yunjian Wang <wangyunjian@huawei.com>
> Sent: Friday, December 24, 2021 19:27
> To: dev@dpdk.org
> Cc: Wang, Haiyue <haiyue.wang@intel.com>; dingxiaoxiong@huawei.com; xudingke@huawei.com; Yunjian Wang
> <wangyunjian@huawei.com>; stable@dpdk.org
> Subject: [PATCH v2 1/1] net/ixgbe: check ixgbe filter init failure
>
> The function ixgbe_fdir_filter_init() and ixgbe_l2_tn_filter_init()
> could return errors, the return value need to be checked and returned.
>
> Fixes: 080e3c0ee989 ("net/ixgbe: store flow director filter")
> Fixes: d0c0c416ef1f ("net/ixgbe: store L2 tunnel filter")
> Cc: stable@dpdk.org
>
> Signed-off-by: Yunjian Wang <wangyunjian@huawei.com>
> ---
> v2: update code suggested by Haiyue Wang
> ---
> drivers/net/ixgbe/ixgbe_ethdev.c | 32 +++++++++++++++++++++++---------
> 1 file changed, 23 insertions(+), 9 deletions(-)
>
Thanks!
Acked-by: Haiyue Wang <haiyue.wang@intel.com>
> --
> 2.27.0
next prev parent reply other threads:[~2021-12-30 5:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-04 10:23 [dpdk-dev] [PATCH] " Yunjian Wang
2021-12-20 7:37 ` Wang, Haiyue
2021-12-24 11:05 ` wangyunjian
2021-12-24 11:26 ` [PATCH v2 1/1] " Yunjian Wang
2021-12-30 5:32 ` Wang, Haiyue [this message]
2022-01-30 2:56 ` Zhang, Qi Z
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=BYAPR11MB3495323A5237463A03EFBDA9F7459@BYAPR11MB3495.namprd11.prod.outlook.com \
--to=haiyue.wang@intel.com \
--cc=dev@dpdk.org \
--cc=dingxiaoxiong@huawei.com \
--cc=stable@dpdk.org \
--cc=wangyunjian@huawei.com \
--cc=xudingke@huawei.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).