From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Xiao Wang <xiao.w.wang@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/ifcvf: remove live migration
Date: Wed, 25 Apr 2018 16:05:08 +0100 [thread overview]
Message-ID: <6bf3845e-4ecd-a845-5fd2-65e27c2857c9@intel.com> (raw)
In-Reply-To: <20180425115953.187338-1-xiao.w.wang@intel.com>
On 4/25/2018 12:59 PM, Xiao Wang wrote:
> Live migration feature will be based on future development on ifc driver,
> including port representor implementation and potential change in QEMU
> and vhost user lib.
>
> This patch removes live migration in ifcvf driver, if possible we could
> squash this patch into 7c9f28370437 ("net/ifcvf: add ifcvf vdpa driver"),
> and remove the live migration segment in that commit log.
>
> Signed-off-by: Xiao Wang <xiao.w.wang@intel.com>
Squashed into relevant commit in next-net, thanks.
prev parent reply other threads:[~2018-04-25 15:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 11:59 Xiao Wang
2018-04-25 15:05 ` Ferruh Yigit [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=6bf3845e-4ecd-a845-5fd2-65e27c2857c9@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=xiao.w.wang@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).