From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Shahaf Shuler <shahafs@mellanox.com>,
"thomas@monjalon.net" <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 2/3] doc: cleanup UIO hard requirement
Date: Fri, 28 Jul 2017 10:14:23 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23ED5221B@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <ef2f9dac512446c44f3bcd3efa9ec90de81408d8.1501089309.git.shahafs@mellanox.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Shahaf Shuler
> Sent: Wednesday, July 26, 2017 6:18 PM
> To: thomas@monjalon.net
> Cc: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH 2/3] doc: cleanup UIO hard requirement
>
> UIO is not a must for all PMDs.
>
> Cleaning up the Linux Getting Started Guide from this hard requirement.
>
> Signed-off-by: Shahaf Shuler <shahafs@mellanox.com>
Acked-by: John McNamara <john.mcnamara@intel.com>
next prev parent reply other threads:[~2017-07-28 10:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 17:17 [dpdk-dev] [PATCH 1/3] doc: move kernel drivers to a new chapter Shahaf Shuler
2017-07-26 17:17 ` [dpdk-dev] [PATCH 2/3] doc: cleanup UIO hard requirement Shahaf Shuler
2017-07-28 10:14 ` Mcnamara, John [this message]
2017-07-26 17:17 ` [dpdk-dev] [PATCH 3/3] doc: move i40e specific to i40e guide Shahaf Shuler
2017-07-28 10:16 ` Mcnamara, John
2017-07-28 10:13 ` [dpdk-dev] [PATCH 1/3] doc: move kernel drivers to a new chapter Mcnamara, John
2017-07-29 16:17 ` [dpdk-dev] [PATCH v2 " Shahaf Shuler
2017-07-31 22:10 ` Thomas Monjalon
2017-07-29 16:17 ` [dpdk-dev] [PATCH v2 2/3] doc: cleanup UIO hard requirement Shahaf Shuler
2017-07-29 16:17 ` [dpdk-dev] [PATCH v2 3/3] doc: move i40e specific to i40e guide Shahaf Shuler
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=B27915DBBA3421428155699D51E4CFE23ED5221B@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=shahafs@mellanox.com \
--cc=thomas@monjalon.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).