DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Yang, Qiming" <qiming.yang@intel.com>
To: "Yang, SteveX" <stevex.yang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Zhang, Yuying" <yuying.zhang@intel.com>,
	"Xing, Beilei" <beilei.xing@intel.com>,
	"Zhang, Qi Z" <qi.z.zhang@intel.com>
Subject: RE: [PATCH v1 0/2] fix unsupported flow rule transfer attribute
Date: Mon, 26 Dec 2022 01:22:00 +0000	[thread overview]
Message-ID: <MWHPR11MB18861F5F93F9E758F6839443E5EC9@MWHPR11MB1886.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221226003715.615278-1-stevex.yang@intel.com>

Hi,

> -----Original Message-----
> From: Yang, SteveX <stevex.yang@intel.com>
> Sent: Monday, December 26, 2022 8:37 AM
> To: dev@dpdk.org
> Cc: Zhang, Yuying <yuying.zhang@intel.com>; Xing, Beilei
> <beilei.xing@intel.com>; Yang, Qiming <qiming.yang@intel.com>; Zhang, Qi Z
> <qi.z.zhang@intel.com>; Yang, SteveX <stevex.yang@intel.com>
> Subject: [PATCH v1 0/2] fix unsupported flow rule transfer attribute
> 
> ice & i40e doesn't support transfer attribute of flow rule, ignore it when
> validating rule attributes.
> 
> Steve Yang (2):
>   net/i40e: fix unsupported flow rule transfer attribute
>   net/ice: fix unsupported flow rule transfer attribute
> 
>  drivers/net/i40e/i40e_flow.c       | 8 ++++++++
>  drivers/net/ice/ice_generic_flow.c | 8 ++++++++
>  2 files changed, 16 insertions(+)
> 
> --
> 2.25.1

Acked-by: Qiming Yang <qiming.yang@intel.com>

      parent reply	other threads:[~2022-12-26  1:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-26  0:37 Steve Yang
2022-12-26  0:37 ` [PATCH v1 1/2] net/i40e: " Steve Yang
2023-01-17  1:26   ` Zhang, Qi Z
2023-01-17  1:26     ` Zhang, Qi Z
2022-12-26  0:37 ` [PATCH v1 2/2] net/ice: " Steve Yang
2023-01-17  1:29   ` Zhang, Qi Z
2022-12-26  1:22 ` Yang, Qiming [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=MWHPR11MB18861F5F93F9E758F6839443E5EC9@MWHPR11MB1886.namprd11.prod.outlook.com \
    --to=qiming.yang@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=qi.z.zhang@intel.com \
    --cc=stevex.yang@intel.com \
    --cc=yuying.zhang@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).