From: "Liu, Mingxia" <mingxia.liu@intel.com>
To: "Zhang, Qi Z" <qi.z.zhang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Wu, Jingjing" <jingjing.wu@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>
Subject: RE: [PATCH v2] net/idpf: refine dev_link_update function
Date: Mon, 3 Jul 2023 03:17:29 +0000 [thread overview]
Message-ID: <PH0PR11MB5877FCE1AC8B9DF08FDB293CEC29A@PH0PR11MB5877.namprd11.prod.outlook.com> (raw)
In-Reply-To: <DM4PR11MB599459A324F98E5C11BE6C15D729A@DM4PR11MB5994.namprd11.prod.outlook.com>
> -----Original Message-----
> From: Zhang, Qi Z <qi.z.zhang@intel.com>
> Sent: Monday, July 3, 2023 10:22 AM
> To: Liu, Mingxia <mingxia.liu@intel.com>; dev@dpdk.org
> Cc: Wu, Jingjing <jingjing.wu@intel.com>; Xing, Beilei <beilei.xing@intel.com>;
> Liu, Mingxia <mingxia.liu@intel.com>
> Subject: RE: [PATCH v2] net/idpf: refine dev_link_update function
>
>
>
> > -----Original Message-----
> > From: Mingxia Liu <mingxia.liu@intel.com>
> > Sent: Saturday, July 1, 2023 2:56 AM
> > To: dev@dpdk.org
> > Cc: Wu, Jingjing <jingjing.wu@intel.com>; Xing, Beilei
> > <beilei.xing@intel.com>; Liu, Mingxia <mingxia.liu@intel.com>
> > Subject: [PATCH v2] net/idpf: refine dev_link_update function
>
> net/idpf: refine dev link update
>
> >
> > This patch refines idpf_dev_link_update callback function according to
> > CPFL PMD basic code.
>
> The patch is for idpf PMD, not the common/idpf part, why ref CPFL PMD here?
>
[Liu, Mingxia] Because this change referred to cpfl basic code, maybe it's better to delete it. New patch has been sent.
next prev parent reply other threads:[~2023-07-03 3:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 11:14 [PATCH] " Mingxia Liu
2023-06-30 8:27 ` Zhang, Qi Z
2023-06-30 10:46 ` Liu, Mingxia
2023-06-30 18:55 ` [PATCH v2] " Mingxia Liu
2023-07-03 2:21 ` Zhang, Qi Z
2023-07-03 3:17 ` Liu, Mingxia [this message]
2023-07-03 11:22 ` [PATCH v3] " Mingxia Liu
2023-07-03 6:51 ` 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=PH0PR11MB5877FCE1AC8B9DF08FDB293CEC29A@PH0PR11MB5877.namprd11.prod.outlook.com \
--to=mingxia.liu@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=qi.z.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).