From: "Iremonger, Bernard" <bernard.iremonger@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: update release notes
Date: Thu, 14 Jul 2016 15:34:22 +0000 [thread overview]
Message-ID: <8CEF83825BEC744B83065625E567D7C21A04E8EB@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1867672.nEzVQfjTFZ@xps13>
Hi Thomas,
<snip>
> Subject: Re: [dpdk-dev] [PATCH] doc: update release notes
>
> 2016-07-14 13:45, Iremonger, Bernard:
> > > 2016-07-01 15:10, Bernard Iremonger:
> > > > add release note for live migration of a VM with SRIOV VF
> > > [...]
> > > > +* **Added support for live migration of a VM with SRIOV VF.**
> > > > +
> > > > + Live migration of a VM with Virtio and VF PMD's using the bonding
> PMD.
> > >
> > > Is there some new code for this feature?
> > > I am not sure we need to update the release notes for a doc addition.
> >
> > The testpmd patches which I submitted and were applied, were made to
> enable testing of this feature.
> > This doc patch is to announce that this feature is available now.
>
> The feature was not available before?
It has not been announced previously.
Regards,
Bernard.
next prev parent reply other threads:[~2016-07-14 15:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 14:10 Bernard Iremonger
2016-07-14 13:32 ` Thomas Monjalon
2016-07-14 13:45 ` Iremonger, Bernard
2016-07-14 15:04 ` Thomas Monjalon
2016-07-14 15:34 ` Iremonger, Bernard [this message]
2016-07-22 17:14 ` Thomas Monjalon
-- strict thread matches above, loose matches on Subject: below --
2020-04-17 16:35 Ajit Khaparde
2020-04-17 22:29 ` Ferruh Yigit
2020-04-17 22:40 ` Ajit Khaparde
2020-04-22 21:42 ` Thomas Monjalon
2018-05-10 4:19 Qi Zhang
2015-11-12 3:18 Helin Zhang
2015-12-13 23:26 ` Thomas Monjalon
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=8CEF83825BEC744B83065625E567D7C21A04E8EB@IRSMSX108.ger.corp.intel.com \
--to=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=thomas.monjalon@6wind.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).