From: Thomas Monjalon <thomas@monjalon.net>
To: Konstantin Ananyev <konstantin.ananyev@intel.com>
Cc: dev@dpdk.org, bruce.richardson@intel.com
Subject: Re: [dpdk-dev] [PATCH v5] ip_frag: add namespace
Date: Wed, 17 Nov 2021 10:25:22 +0100 [thread overview]
Message-ID: <44249060.4o4iJyymgP@thomas> (raw)
In-Reply-To: <20211109123204.3296-1-konstantin.ananyev@intel.com>
09/11/2021 13:32, Konstantin Ananyev:
> Update public macros to have RTE_IP_FRAG_ prefix.
> Update DPDK components to use new names.
> Keep obsolete macro for compatibility reasons.
> Renamed experimental function ``rte_frag_table_del_expired_entries``to
> ``rte_ip_frag_table_del_expired_entries`` to comply with other public
> API naming convention.
>
> Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
Applied, thanks.
I've fixed few doxygen formatting.
Note: we still have some config macros with a different namespace:
config/rte_config.h:#define RTE_LIBRTE_IP_FRAG_MAX_FRAG 8
config/rte_config.h:#undef RTE_LIBRTE_IP_FRAG_TBL_STAT
prev parent reply other threads:[~2021-11-17 9:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 12:24 [dpdk-dev] [PATCH] ip_frag: hide internal structures Konstantin Ananyev
2021-11-01 12:49 ` [dpdk-dev] [PATCH v2] " Konstantin Ananyev
2021-11-04 18:30 ` Thomas Monjalon
2021-11-08 11:51 ` [dpdk-dev] [PATCH v3] " Konstantin Ananyev
2021-11-08 13:55 ` [dpdk-dev] [PATCH v4 0/2] ip_frag cleanup patches Konstantin Ananyev
2021-11-08 13:55 ` [dpdk-dev] [PATCH v4 1/2] ip_frag: hide internal structures Konstantin Ananyev
2021-11-08 21:39 ` Thomas Monjalon
2021-11-08 13:55 ` [dpdk-dev] [PATCH v4 2/2] ip_frag: add namespace Konstantin Ananyev
2021-11-08 21:36 ` Thomas Monjalon
2021-11-09 12:32 ` [dpdk-dev] [PATCH v5] " Konstantin Ananyev
2021-11-17 9:25 ` 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=44249060.4o4iJyymgP@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@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).