From: Thomas Monjalon <thomas@monjalon.net>
To: Bing Zhao <bingz@nvidia.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>, Ori Kam <orika@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Matan Azrad <matan@nvidia.com>,
dev@dpdk.org, Raslan Darawsheh <rasland@nvidia.com>,
"andrew.rybchenko@oktetlabs.ru" <andrew.rybchenko@oktetlabs.ru>
Subject: Re: [dpdk-dev] [PATCH] doc: add new feature for connection tracking
Date: Tue, 18 May 2021 15:44:00 +0200 [thread overview]
Message-ID: <13627037.LXhn9qPFKt@thomas> (raw)
In-Reply-To: <CH0PR12MB50415AB19DB6669D5F0B0F76D02C9@CH0PR12MB5041.namprd12.prod.outlook.com>
18/05/2021 15:33, Bing Zhao:
> From: Ferruh Yigit <ferruh.yigit@intel.com>
> > On 5/18/2021 1:52 PM, Bing Zhao wrote:
> > > The feature support of connection tracking is added in the feature
> > > table of networking drivers. The feature overview part is also
> > > updated.
> > >
> > > Signed-off-by: Bing Zhao <bingz@nvidia.com>
> >
> > Hi Bing,
> >
> > Thomas is suggestion another table to list flow API item/actions in
> > separate table, can this change can be replaced by it?
>
> It is OK for me. But I might need the comments from Thomas, Ori and ETHDEV maintainers since you all are much more familiar with the documents and their scopes.
>
> @Thomas, is it OK?
Yes, I mark this patch as rejected.
See how it is added in the new table:
https://patches.dpdk.org/project/dpdk/patch/20210518132844.3779728-3-thomas@monjalon.net/
prev parent reply other threads:[~2021-05-18 13:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 12:52 [dpdk-dev] [PATCH] doc: add new feature for connection tracking Bing Zhao
2021-05-18 13:16 ` Ferruh Yigit
2021-05-18 13:18 ` Thomas Monjalon
2021-05-18 13:49 ` Bing Zhao
2021-05-18 13:33 ` Bing Zhao
2021-05-18 13:44 ` 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=13627037.LXhn9qPFKt@thomas \
--to=thomas@monjalon.net \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=viacheslavo@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.