From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Bruce Richardson <bruce.richardson@intel.com>,
Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, Kevin Laatz <kevin.laatz@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/ring: support secondary process
Date: Wed, 17 Feb 2021 17:49:04 +0000 [thread overview]
Message-ID: <46a9029a-6d91-1b82-71f1-3a2c402ce561@intel.com> (raw)
In-Reply-To: <20200930110241.1882308-1-ferruh.yigit@intel.com>
On 9/30/2020 12:02 PM, Ferruh Yigit wrote:
> Also add missing .ini feature list documentation and document some
> existing features including new "Multiprocess aware" feature.
>
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
> Cc: Kevin Laatz <kevin.laatz@intel.com>
Hi Bruce,
Reminder of this patch waiting for review.
Thanks,
ferruh
next prev parent reply other threads:[~2021-02-17 17:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 11:02 Ferruh Yigit
2021-02-17 17:49 ` Ferruh Yigit [this message]
2021-03-01 13:38 ` Bruce Richardson
2021-03-04 17:14 ` Ferruh Yigit
2021-03-07 21:02 ` Thomas Monjalon
2021-03-08 11:30 ` Ferruh Yigit
2021-03-08 11:39 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2021-03-09 8:40 ` Ferruh Yigit
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=46a9029a-6d91-1b82-71f1-3a2c402ce561@intel.com \
--to=ferruh.yigit@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=kevin.laatz@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).