From: Ivan Malov <ivan.malov@oktetlabs.ru>
To: dev@dpdk.org
Cc: David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] [PATCH v2 0/2] RTE flow support logging improvements
Date: Fri, 16 Jul 2021 05:20:41 +0300 [thread overview]
Message-ID: <20210716022043.3161-1-ivan.malov@oktetlabs.ru> (raw)
In-Reply-To: <20210707105628.16705-1-ivan.malov@oktetlabs.ru>
Changes in v2:
* [2/2] RTE flow item and action type macros are spelled out in full
Ivan Malov (2):
net/sfc: extend logging in MAE backend of RTE flow support
net/sfc: improve logging in MAE backend of RTE flow support
drivers/net/sfc/sfc_flow.c | 34 +++++----
drivers/net/sfc/sfc_flow.h | 12 ++-
drivers/net/sfc/sfc_mae.c | 149 +++++++++++++++++++++++++++++--------
3 files changed, 145 insertions(+), 50 deletions(-)
--
2.20.1
next prev parent reply other threads:[~2021-07-16 2:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 10:56 [dpdk-dev] [PATCH 1/2] net/sfc: extend logging in MAE backend of RTE flow support Ivan Malov
2021-07-07 10:56 ` [dpdk-dev] [PATCH 2/2] net/sfc: improve " Ivan Malov
2021-07-15 12:55 ` David Marchand
2021-07-15 13:43 ` Thomas Monjalon
2021-07-16 2:20 ` Ivan Malov [this message]
2021-07-16 2:20 ` [dpdk-dev] [PATCH v2 1/2] net/sfc: extend " Ivan Malov
2021-07-20 15:45 ` David Marchand
2021-07-16 2:20 ` [dpdk-dev] [PATCH v2 2/2] net/sfc: improve " Ivan Malov
2021-07-21 4:15 ` [dpdk-dev] [PATCH v3 0/2] RTE flow support logging improvements Ivan Malov
2021-07-21 4:15 ` [dpdk-dev] [PATCH v3 1/2] net/sfc: extend logging in MAE backend of RTE flow support Ivan Malov
2021-07-21 4:15 ` [dpdk-dev] [PATCH v3 2/2] net/sfc: improve " Ivan Malov
2021-07-23 21:31 ` [dpdk-dev] [PATCH v3 0/2] RTE flow support logging improvements 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=20210716022043.3161-1-ivan.malov@oktetlabs.ru \
--to=ivan.malov@oktetlabs.ru \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).