DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: web@dpdk.org
Subject: Re: [dpdk-web] [PATCH] trace existing eal config file patchset
Date: Mon, 28 Jan 2019 23:30:31 +0100	[thread overview]
Message-ID: <44280606.Lv6TcYs5yi@xps> (raw)
In-Reply-To: <20190128144252.96571-1-ferruh.yigit@intel.com>

28/01/2019 15:42, Ferruh Yigit:
> --- a/content/roadmap/_index.md
> +++ b/content/roadmap/_index.md
> @@ -26,6 +26,9 @@ This list is obviously neither complete nor guaranteed.
>  - default configuration from files
>  - generic white/blacklisting
>  - libedit integration
> +- EAL parameters from config file instead of command-line
> +    - Can benefit from existing patch: https://patches.dpdk.org/patch/26883/
> +    - Discussion: https://mails.dpdk.org/archives/dev/2019-January/123985.html

There is already an item "default configuration from files" above.
I think we should merge them.

      reply	other threads:[~2019-01-28 22:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-28 14:42 Ferruh Yigit
2019-01-28 22:30 ` Thomas Monjalon [this message]

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=44280606.Lv6TcYs5yi@xps \
    --to=thomas@monjalon.net \
    --cc=ferruh.yigit@intel.com \
    --cc=web@dpdk.org \
    /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).