From: "Min Hu (Connor)" <humin29@huawei.com>
To: "Wang, Haiyue" <haiyue.wang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Yigit, Ferruh" <ferruh.yigit@intel.com>, "Guo, Jia" <jia.guo@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/e1000: fix param misusage when set rte flow error
Date: Wed, 28 Apr 2021 09:15:56 +0800 [thread overview]
Message-ID: <6cc502b9-2ad2-4024-8961-9ca123864c0f@huawei.com> (raw)
In-Reply-To: <BN8PR11MB37954C99A777FCDD5E0F95A4F7419@BN8PR11MB3795.namprd11.prod.outlook.com>
在 2021/4/27 21:22, Wang, Haiyue 写道:
>> -----Original Message-----
>> From: Min Hu (Connor) <humin29@huawei.com>
>> Sent: Tuesday, April 27, 2021 16:51
>> To: dev@dpdk.org
>> Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; Guo, Jia <jia.guo@intel.com>; Wang, Haiyue
>> <haiyue.wang@intel.com>
>> Subject: [PATCH] net/e1000: fix param misusage when set rte flow error
>>
>> This patch fixes parameter misusage when set rte flow action error.
>>
>> Fixes: c0688ef1eded ("net/igb: parse flow API n-tuple filter")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Min Hu (Connor) <humin29@huawei.com>
>> ---
>> drivers/net/e1000/igb_flow.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>
> Acked-by: Haiyue Wang <haiyue.wang@intel.com>
>
>
>> diff --git a/drivers/net/e1000/igb_flow.c b/drivers/net/e1000/igb_flow.c
>> index 33f6b1d..e72376f 100644
>> --- a/drivers/net/e1000/igb_flow.c
>> +++ b/drivers/net/e1000/igb_flow.c
>> @@ -350,7 +350,7 @@ cons_parse_ntuple_filter(const struct rte_flow_attr *attr,
>> memset(filter, 0, sizeof(struct rte_eth_ntuple_filter));
>> rte_flow_error_set(error, EINVAL,
>> RTE_FLOW_ERROR_TYPE_ACTION,
>> - item, "Not supported action.");
>> + act, "Not supported action.");
>
> Thanks, Connor.
>
> Just wonder how do you get this error ? With some code scan tool ? ;-)
>
No, I just read your code to help me understand flow table. I found this
part of codes are the same as others.
So I think this mistake derived from other drivers.
>> return -rte_errno;
>> }
>> filter->queue =
>> --
>> 2.7.4
>
> .
>
next prev parent reply other threads:[~2021-04-28 1:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 8:51 Min Hu (Connor)
2021-04-27 13:22 ` Wang, Haiyue
2021-04-28 1:15 ` Min Hu (Connor) [this message]
2021-04-28 1:18 ` Wang, Haiyue
2021-04-28 1:26 ` 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=6cc502b9-2ad2-4024-8961-9ca123864c0f@huawei.com \
--to=humin29@huawei.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=haiyue.wang@intel.com \
--cc=jia.guo@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).