From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v4] config: sort PMD config options
Date: Mon, 22 Jan 2018 01:54:15 +0100 [thread overview]
Message-ID: <3520211.fDHBviLKSF@xps> (raw)
In-Reply-To: <20180120165054.21005-1-ferruh.yigit@intel.com>
20/01/2018 17:50, Ferruh Yigit:
> No config option changed, added or removed.
> Only reshuffle PMD config options mostly to help new PMDs where to put
> their new config option.
>
> Ordered as physical, paravirtual and virtual groups. Alphabetical order
> within a group.
>
> Also tried to group vendor devices together which breaks alphabetical
> order in some places.
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied, thanks
prev parent reply other threads:[~2018-01-22 0:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 22:39 [dpdk-dev] [PATCH] " Ferruh Yigit
2017-11-21 23:17 ` Aleksey Baulin
2017-11-22 0:27 ` Ferruh Yigit
2018-01-09 15:34 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2018-01-17 21:02 ` [dpdk-dev] [PATCH v3] " Ferruh Yigit
2018-01-20 16:50 ` [dpdk-dev] [PATCH v4] " Ferruh Yigit
2018-01-22 0:54 ` 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=3520211.fDHBviLKSF@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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).