From: Bing Zhao <bingz@nvidia.com>
To: Elena Agostini <eagostini@nvidia.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Olivier Matz <olivier.matz@6wind.com>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Cc: "statble@dpdk.org" <statble@dpdk.org>
Subject: RE: [PATCH] net: fix return type of IPv6 L4 packet checksum
Date: Thu, 6 Apr 2023 09:35:47 +0000 [thread overview]
Message-ID: <DM4PR12MB518433B654D0B81B52C40EECD0919@DM4PR12MB5184.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230406092129.820449-1-eagostini@nvidia.com>
Hi Elena,
Maybe it is better to add a fixline here.
BR. Bing
> -----Original Message-----
> From: eagostini@nvidia.com <eagostini@nvidia.com>
> Sent: Thursday, April 6, 2023 5:21 PM
> To: dev@dpdk.org
> Cc: statble@dpdk.org; Elena Agostini <eagostini@nvidia.com>
> Subject: [PATCH] net: fix return type of IPv6 L4 packet checksum
>
> External email: Use caution opening links or attachments
>
>
> From: Elena Agostini <eagostini@nvidia.com>
>
> Function returns 0 or -1 but the return type is uint16_t.
>
> Signed-off-by: Elena Agostini <eagostini@nvidia.com>
> ---
> lib/net/rte_ip.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/net/rte_ip.h b/lib/net/rte_ip.h index a310e9d498..e7106256aa
> 100644
> --- a/lib/net/rte_ip.h
> +++ b/lib/net/rte_ip.h
> @@ -514,7 +514,7 @@ rte_ipv4_udptcp_cksum_verify(const struct
> rte_ipv4_hdr *ipv4_hdr,
> * Return 0 if the checksum is correct, else -1.
> */
> __rte_experimental
> -static inline uint16_t
> +static inline int
> rte_ipv4_udptcp_cksum_mbuf_verify(const struct rte_mbuf *m,
> const struct rte_ipv4_hdr *ipv4_hdr,
> uint16_t l4_off)
> --
> 2.34.1
next prev parent reply other threads:[~2023-04-06 9:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 9:21 eagostini
2023-04-06 9:35 ` Bing Zhao [this message]
2023-04-06 9:49 ` [PATCH v2] " eagostini
2023-04-12 8:22 ` Thomas Monjalon
2023-04-12 8:26 ` Thomas Monjalon
2023-04-12 8:24 ` [PATCH v3] net: fix return type of IPv4 " eagostini
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=DM4PR12MB518433B654D0B81B52C40EECD0919@DM4PR12MB5184.namprd12.prod.outlook.com \
--to=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=eagostini@nvidia.com \
--cc=olivier.matz@6wind.com \
--cc=statble@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).