From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: "Varghese, Vipin" <vipin.varghese@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Kovacevic, Marko" <marko.kovacevic@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: update device options in multi process
Date: Fri, 11 May 2018 09:27:19 +0000 [thread overview]
Message-ID: <E923DB57A917B54B9182A2E928D00FA65E1371BB@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <1526016255-1918-1-git-send-email-vipin.varghese@intel.com>
> From: Varghese, Vipin
> Sent: Friday, May 11, 2018 6:24 AM
> To: dev@dpdk.org; Van Haaren, Harry <harry.van.haaren@intel.com>; Kovacevic,
> Marko <marko.kovacevic@intel.com>
> Cc: Varghese, Vipin <vipin.varghese@intel.com>
> Subject: [PATCH] doc: update device options in multi process
>
> Update information for blacklist and whitelist options for secondary
> process to share same from primary process.
>
> Signed-off-by: Vipin Varghese <vipin.varghese@intel.com>
Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
next prev parent reply other threads:[~2018-05-11 9:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 5:24 Vipin Varghese
2018-05-11 9:27 ` Van Haaren, Harry [this message]
2018-05-22 21:14 ` 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=E923DB57A917B54B9182A2E928D00FA65E1371BB@IRSMSX102.ger.corp.intel.com \
--to=harry.van.haaren@intel.com \
--cc=dev@dpdk.org \
--cc=marko.kovacevic@intel.com \
--cc=vipin.varghese@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).