In non-pipeline mode, priority is ignored, a flow rule can be created
as a flow director rule or a switch rule depends on its pattern/action.
Hence removing the priority field check from ice_fdir_parse which is
causing valid flow creation to return failure.

Signed-off-by: Dhanya Pillai <dhanya.r.pil...@intel.com>
---
 drivers/net/intel/ice/ice_fdir_filter.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/drivers/net/intel/ice/ice_fdir_filter.c 
b/drivers/net/intel/ice/ice_fdir_filter.c
index 2ff0090aca..d71d14b013 100644
--- a/drivers/net/intel/ice/ice_fdir_filter.c
+++ b/drivers/net/intel/ice/ice_fdir_filter.c
@@ -2456,13 +2456,12 @@ ice_fdir_parse(struct ice_adapter *ad,
        uint64_t input_set;
        bool raw = false;
        int ret;
+       (void)priority;
 
        memset(filter, 0, sizeof(*filter));
        item = ice_search_pattern_match_item(ad, pattern, array, array_len,
                                             error);
 
-       if (priority >= 1)
-               return -rte_errno;
 
        if (!item)
                return -rte_errno;
-- 
2.43.0

Reply via email to