From: "Wu, Jingjing" <jingjing.wu@intel.com>
To: "Zhao1, Wei" <wei.zhao1@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/3] net/i40e: vf port reset
Date: Fri, 24 Mar 2017 05:57:06 +0000 [thread overview]
Message-ID: <9BB6961774997848B5B42BEC655768F810D12F0C@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1488516984-34702-1-git-send-email-wei.zhao1@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Wei Zhao
> Sent: Friday, March 3, 2017 12:56 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH 0/3] net/i40e: vf port reset
>
> The patches mainly finish following functions:
> 1) get pf reset vf comamand falg from interrupt server function.
> 2) reset vf port from testpmd app using a command.
> 3) sore and restore vf related parameters.
>
The patch order is wrong. You need to make sure the compile can be
Successful when apply each patch in order. So I think should like
1. ethdev API
2. i40e change
3. testpmd change.
Another comment is like:
The reset API can be used for device reset. Please don't limit the scope it
to VF.
next prev parent reply other threads:[~2017-03-24 5:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 4:56 Wei Zhao
2017-03-03 4:56 ` [dpdk-dev] [PATCH 1/3] app/testpmd: add port reset command into testpmd Wei Zhao
2017-03-08 11:07 ` Ferruh Yigit
2017-03-14 7:58 ` Zhao1, Wei
2017-03-27 7:08 ` Zhao1, Wei
2017-03-03 4:56 ` [dpdk-dev] [PATCH 2/3] lib/librte_ether: add support for port reset Wei Zhao
2017-03-03 4:56 ` [dpdk-dev] [PATCH 3/3] net/i40e: implement device reset on port Wei Zhao
2017-03-08 11:20 ` Ferruh Yigit
2017-03-14 6:46 ` Zhao1, Wei
2017-03-24 8:31 ` Wu, Jingjing
2017-03-24 9:07 ` Wu, Jingjing
2017-03-27 6:10 ` Zhao1, Wei
2017-03-24 5:57 ` Wu, Jingjing [this message]
2017-03-27 6:17 ` [dpdk-dev] [PATCH 0/3] net/i40e: vf port reset Zhao1, Wei
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=9BB6961774997848B5B42BEC655768F810D12F0C@SHSMSX103.ccr.corp.intel.com \
--to=jingjing.wu@intel.com \
--cc=dev@dpdk.org \
--cc=wei.zhao1@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).