From: "Wu, Jingjing" <jingjing.wu@intel.com>
To: "Xing, Beilei" <beilei.xing@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH v5] common/idpf: refine capability get
Date: Wed, 26 Apr 2023 05:17:45 +0000 [thread overview]
Message-ID: <MW3PR11MB4587CCA8738F4AD1C61BF2A4E3659@MW3PR11MB4587.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230424080822.13541-1-beilei.xing@intel.com>
> -----Original Message-----
> From: Xing, Beilei <beilei.xing@intel.com>
> Sent: Monday, April 24, 2023 4:08 PM
> To: Wu, Jingjing <jingjing.wu@intel.com>
> Cc: dev@dpdk.org; Xing, Beilei <beilei.xing@intel.com>
> Subject: [PATCH v5] common/idpf: refine capability get
>
> From: Beilei Xing <beilei.xing@intel.com>
>
> Initialize required capability in PMD, and refine
> idpf_vc_caps_get function. Then different PMDs can
> require different capability.
>
> Signed-off-by: Beilei Xing <beilei.xing@intel.com>
Acked-by: Jingjing Wu <jingjing.wu@intel.com>
next prev parent reply other threads:[~2023-04-26 5:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 6:53 [PATCH] common/idpf: move PF specific functions from common init beilei.xing
2023-03-21 7:07 ` [PATCH v2] " beilei.xing
2023-04-04 12:41 ` [PATCH v3 0/2] refine common module beilei.xing
2023-04-04 12:41 ` [PATCH v3 1/2] common/idpf: move PF specific functions from common init beilei.xing
2023-04-04 12:41 ` [PATCH v3 2/2] common/idpf: refine capability get beilei.xing
2023-04-06 7:42 ` [PATCH v4 0/2] refine common module beilei.xing
2023-04-06 7:42 ` [PATCH v4 1/2] common/idpf: move PF specific functions from common init beilei.xing
2023-04-23 8:25 ` Wu, Jingjing
2023-04-06 7:42 ` [PATCH v4 2/2] common/idpf: refine capability get beilei.xing
2023-04-24 8:08 ` [PATCH v5] " beilei.xing
2023-04-26 5:17 ` Wu, Jingjing [this message]
2023-04-26 8:11 ` 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=MW3PR11MB4587CCA8738F4AD1C61BF2A4E3659@MW3PR11MB4587.namprd11.prod.outlook.com \
--to=jingjing.wu@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@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 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).