DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
	John McNamara <john.mcnamara@intel.com>,
	Marko Kovacevic <marko.kovacevic@intel.com>,
	Wenzhuo Lu <wenzhuo.lu@intel.com>,
	Jingjing Wu <jingjing.wu@intel.com>,
	Bernard Iremonger <bernard.iremonger@intel.com>,
	ferruh.yigit@intel.com, keith.wiles@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] doc: document all EAL parameters in one place
Date: Fri, 23 Nov 2018 10:54:54 +0100	[thread overview]
Message-ID: <17145513.edOoxHsAiy@xps> (raw)
In-Reply-To: <d631623e-b63f-9e29-300e-5e22b4bca28a@intel.com>

23/11/2018 10:20, Burakov, Anatoly:
> On 22-Nov-18 5:27 PM, Thomas Monjalon wrote:
> > 19/11/2018 14:10, Anatoly Burakov:
> >> --- /dev/null
> >> +++ b/doc/guides/freebsd_gsg/freebsd_eal_parameters.rst
> >> @@ -0,0 +1,20 @@
> >> +..  SPDX-License-Identifier: BSD-3-Clause
> >> +    Copyright(c) 2018 Intel Corporation.
> >> +
> >> +EAL parameters
> >> +==============
> >> +
> >> +This document contains a list of all EAL parameters. These parameters can be
> >> +used by any DPDK application running on Linux.
> > 
> > Is it a typo? running on FreeBSD?
> 
> Yes, a typo. Good catch, thanks! Should i respin?

I can fix it.

  reply	other threads:[~2018-11-23  9:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-16 16:52 [dpdk-dev] [PATCH] " Anatoly Burakov
2018-11-16 17:25 ` Ferruh Yigit
2018-11-17  5:15   ` Rami Rosen
2018-11-19 11:07     ` Mcnamara, John
2018-11-19 10:15 ` Burakov, Anatoly
2018-11-19 13:10 ` [dpdk-dev] [PATCH v2] " Anatoly Burakov
2018-11-19 13:14   ` Burakov, Anatoly
2018-11-22 17:27   ` Thomas Monjalon
2018-11-23  9:20     ` Burakov, Anatoly
2018-11-23  9:54       ` Thomas Monjalon [this message]
2018-11-23 10:51   ` 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=17145513.edOoxHsAiy@xps \
    --to=thomas@monjalon.net \
    --cc=anatoly.burakov@intel.com \
    --cc=bernard.iremonger@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jingjing.wu@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=keith.wiles@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=wenzhuo.lu@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).