From: Xiaozhen Ban <benhaz1024@gmail.com>
To: jia.guo@intel.com, haiyue.wang@intel.com
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/e1000: fix filter control return value
Date: Fri, 19 Mar 2021 12:08:17 +0800 [thread overview]
Message-ID: <20210319040817.64143-1-benhaz1024@gmail.com> (raw)
In-Reply-To: <BN8PR11MB3795C33F2D84F652837ACE2DF7699@BN8PR11MB3795.namprd11.prod.outlook.com>
> > -----Original Message-----
> > From: Xiaozhen Ban <benhaz1024 at gmail.com>
> > Sent: Thursday, March 18, 2021 19:44
> > To: Guo, Jia <jia.guo at intel.com>; Wang, Haiyue <haiyue.wang at intel.com>
> > Cc: dev at dpdk.org; stable at dpdk.org
> > Subject: RE: RE: [PATCH] net/e1000: fix filter control return value
> >
> > OK, but I think this bug affects all stable release about 6 years before today.
> I don't think so, since it is PMD internal ops, the real API 'rte_flow_ops_get'
> always use RTE_ETH_FILTER_GENERIC. ;-)
eth_igb_filter_ctrl() called by rte_eth_dev_filter_ctrl(), if application
developer know how to use the parameter filter_type correctly, it's OK.
otherwise he will get rte_eth_dev_filter_ctrl() return value is success
but actually is failed.
next prev parent reply other threads:[~2021-03-19 4:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 8:10 [dpdk-dev] [PATCH] net/e1000: fix incorrect return value if filter type not supported banxiaozhen, benhaz1024
2020-12-08 9:04 ` Wang, Haiyue
2020-12-08 9:58 ` haz ben
2020-12-08 10:40 ` Wang, Haiyue
2020-12-08 11:05 ` Wang, Haiyue
2021-03-17 9:15 ` [dpdk-dev] [PATCH] net/e1000: fix filter control return value Xiaozhen Ban
2021-03-17 11:23 ` Wang, Haiyue
2021-03-18 11:44 ` Xiaozhen Ban
2021-03-18 15:28 ` Wang, Haiyue
2021-03-19 4:08 ` Xiaozhen Ban [this message]
2021-03-25 8:46 ` Zhang, Qi Z
2021-04-20 8:08 ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2021-04-20 9:54 ` Zhang, Qi Z
2021-04-20 14:33 ` Luca Boccassi
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=20210319040817.64143-1-benhaz1024@gmail.com \
--to=benhaz1024@gmail.com \
--cc=dev@dpdk.org \
--cc=haiyue.wang@intel.com \
--cc=jia.guo@intel.com \
--cc=stable@dpdk.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.