From: Ben Magistro <koncept1@gmail.com>
To: dev@dpdk.org, Olivier Matz <olivier.matz@6wind.com>
Cc: ben.magistro@trinitycyber.com
Subject: Confirm if rte_ipv4_udptcp_cksum_verify should be experimental
Date: Thu, 26 May 2022 17:39:49 -0400 [thread overview]
Message-ID: <CAKx8PBh1zNOKaDRzv1kE-0a8Js9BjjzOM5482-5GryW84R0UEw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 542 bytes --]
This may simply be a docs and signature mismatch (or macro wasn't available
at the time, didn't check that aspect) but the function
rte_ipv4_udptcp_cksum_verify() is marked as experimental in the signature
but not in the associated function comments (doxygen). Should this
function be considered experimental and the docs section updated or is this
considered a stable function and the signature should updated?
Introduced in
https://patches.dpdk.org/project/dpdk/patch/20210630135158.8108-4-olivier.matz@6wind.com/
Thanks,
Ben Magistro
[-- Attachment #2: Type: text/html, Size: 751 bytes --]
next reply other threads:[~2022-05-26 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 21:39 Ben Magistro [this message]
2022-05-30 10:43 ` 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=CAKx8PBh1zNOKaDRzv1kE-0a8Js9BjjzOM5482-5GryW84R0UEw@mail.gmail.com \
--to=koncept1@gmail.com \
--cc=ben.magistro@trinitycyber.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.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).