From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Reshma Pattan <reshma.pattan@intel.com>,
john.mcnamara@intel.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] doc: update eal option usage for FreeBSD
Date: Fri, 27 Apr 2018 14:14:37 +0100 [thread overview]
Message-ID: <c420620a-bcaf-5fe7-1ca9-d099d9846c92@intel.com> (raw)
In-Reply-To: <1524833963-7316-1-git-send-email-reshma.pattan@intel.com>
On 27-Apr-18 1:59 PM, Reshma Pattan wrote:
> EAL option -m is supported in FreeBSD,
> so move it under supported heading from non
> supported heading.
>
> Signed-off-by: Reshma Pattan <reshma.pattan@intel.com>
> ---
> v2: remove recommendation of socket-mem option.
> ---
Reviewed-by: Anatoly Burakov <anatoly.burakov@intel.com>
--
Thanks,
Anatoly
next prev parent reply other threads:[~2018-04-27 13:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 15:48 [dpdk-dev] [PATCH] " Reshma Pattan
2018-04-27 9:20 ` Burakov, Anatoly
2018-04-27 9:22 ` Pattan, Reshma
2018-04-27 12:59 ` [dpdk-dev] [PATCH v2] " Reshma Pattan
2018-04-27 13:14 ` Burakov, Anatoly [this message]
2018-04-27 22:08 ` 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=c420620a-bcaf-5fe7-1ca9-d099d9846c92@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=reshma.pattan@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).