From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Wu, Jingjing" <jingjing.wu@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Peng, Yuan" <yuan.peng@intel.com>
Subject: RE: [PATCH] net/idpf: add supported ptypes get
Date: Fri, 18 Nov 2022 09:47:53 +0000 [thread overview]
Message-ID: <DM4PR11MB5994E43D983E377B03B2F5FAD7099@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <MW3PR11MB45871EB5FD352BC15C0094D4E3099@MW3PR11MB4587.namprd11.prod.outlook.com>
> -----Original Message-----
> From: Wu, Jingjing <jingjing.wu@intel.com>
> Sent: Friday, November 18, 2022 2:43 PM
> To: Xing, Beilei <beilei.xing@intel.com>
> Cc: dev@dpdk.org; Peng, Yuan <yuan.peng@intel.com>
> Subject: RE: [PATCH] net/idpf: add supported ptypes get
>
>
>
> > -----Original Message-----
> > From: Xing, Beilei <beilei.xing@intel.com>
> > Sent: Friday, November 18, 2022 11:51 AM
> > To: Wu, Jingjing <jingjing.wu@intel.com>
> > Cc: dev@dpdk.org; Peng, Yuan <yuan.peng@intel.com>; Xing, Beilei
> > <beilei.xing@intel.com>
> > Subject: [PATCH] net/idpf: add supported ptypes get
> >
> > From: Beilei Xing <beilei.xing@intel.com>
> >
> > Failed to launch l3fwd, the log shows:
> > port 0 cannot parse packet type, please add --parse-ptype This patch
> > adds dev_supported_ptypes_get ops.
> >
> > Fixes: 549343c25db8 ("net/idpf: support device initialization")
> >
> > Signed-off-by: Beilei Xing <beilei.xing@intel.com>
> Reviewed-by: Jingjing Wu <jingjing.wu@intel.com>
Applied to dpdk-next-net-intel.
Thanks
Qi
next prev parent reply other threads:[~2022-11-18 9:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 3:50 beilei.xing
2022-11-18 6:42 ` Wu, Jingjing
2022-11-18 9:47 ` Zhang, Qi Z [this message]
2022-11-18 9:59 ` Peng, Yuan
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=DM4PR11MB5994E43D983E377B03B2F5FAD7099@DM4PR11MB5994.namprd11.prod.outlook.com \
--to=qi.z.zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=yuan.peng@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).