From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Gaetan Rivet <gaetan.rivet@6wind.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: include fail-safe PMD in release note
Date: Fri, 4 Aug 2017 16:10:54 +0100 [thread overview]
Message-ID: <884d30df-aff6-6409-c485-1e0d7270b46b@intel.com> (raw)
In-Reply-To: <1501859074-16148-1-git-send-email-gaetan.rivet@6wind.com>
On 8/4/2017 4:04 PM, Gaetan Rivet wrote:
> Signed-off-by: Gaetan Rivet <gaetan.rivet@6wind.com>
> ---
> doc/guides/nics/fail_safe.rst | 2 ++
> doc/guides/rel_notes/release_17_08.rst | 5 +++++
> 2 files changed, 7 insertions(+)
>
> diff --git a/doc/guides/nics/fail_safe.rst b/doc/guides/nics/fail_safe.rst
> index 34ecae2..a3caf10 100644
> --- a/doc/guides/nics/fail_safe.rst
> +++ b/doc/guides/nics/fail_safe.rst
> @@ -27,6 +27,8 @@
> (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
> OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
>
> +.. _fail_safe:
> +
> Fail-safe poll mode driver library
> ==================================
>
> diff --git a/doc/guides/rel_notes/release_17_08.rst b/doc/guides/rel_notes/release_17_08.rst
> index 343331e..7558368 100644
> --- a/doc/guides/rel_notes/release_17_08.rst
> +++ b/doc/guides/rel_notes/release_17_08.rst
> @@ -233,6 +233,11 @@ EAL
> Drivers
> ~~~~~~~
This is under "Resolved Issues" section.
Can you please move this to the "New Features" section?
Thanks,
ferruh
>
> +* **Added Fail-Safe PMD**
> +
> + Added the new Fail-Safe PMD. This virtual device allows applications to
> + support seamless hotplug of devices. See the :ref:`Fail-Safe documentation<fail_safe>`
> + for more details about this driver.
>
> Libraries
> ~~~~~~~~~
>
next prev parent reply other threads:[~2017-08-04 15:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 15:04 Gaetan Rivet
2017-08-04 15:08 ` Mcnamara, John
2017-08-04 15:10 ` Ferruh Yigit [this message]
2017-08-04 15:33 ` [dpdk-dev] [PATCH v2] " Gaetan Rivet
2017-08-06 13:17 ` 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=884d30df-aff6-6409-c485-1e0d7270b46b@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=gaetan.rivet@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).