From: "Kovacevic, Marko" <marko.kovacevic@intel.com>
To: Gaetan Rivet <grive@u256.net>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v1 1/2] doc/failsafe: improve fail-safe documentation
Date: Tue, 3 Mar 2020 16:30:54 +0000 [thread overview]
Message-ID: <BN8PR11MB36181FD9615C1A45892F9A7EF2E40@BN8PR11MB3618.namprd11.prod.outlook.com> (raw)
In-Reply-To: <d9516604296a6db77987895950a9b47cebe13b90.1582330416.git.grive@u256.net>
Acked-by: Marko Kovacevic <marko.kovacevic@intel.com>
next prev parent reply other threads:[~2020-03-03 16:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-22 0:14 [dpdk-dev] [PATCH v1 0/2] failsafe: improve documentation Gaetan Rivet
2020-02-22 0:14 ` [dpdk-dev] [PATCH v1 1/2] doc/failsafe: improve fail-safe documentation Gaetan Rivet
2020-02-27 17:46 ` Ferruh Yigit
2020-03-03 16:30 ` Kovacevic, Marko [this message]
2020-03-04 16:41 ` Ferruh Yigit
2020-02-22 0:14 ` [dpdk-dev] [PATCH v1 2/2] doc/failsafe: fix incorrect statement regarding number of sub-device Gaetan Rivet
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=BN8PR11MB36181FD9615C1A45892F9A7EF2E40@BN8PR11MB3618.namprd11.prod.outlook.com \
--to=marko.kovacevic@intel.com \
--cc=dev@dpdk.org \
--cc=grive@u256.net \
/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).