From: Thomas Monjalon <thomas@monjalon.net>
To: Robin Jarry <rjarry@redhat.com>
Cc: dev@dpdk.org, "Aman Singh" <aman.deep.singh@intel.com>,
"Stephen Hemminger" <stephen@networkplumber.org>,
"Ferruh Yigit" <ferruh.yigit@amd.com>,
"Morten Brørup" <mb@smartsharesystems.com>
Subject: Re: [PATCH dpdk v2] net: add more icmp types and code
Date: Fri, 18 Oct 2024 17:13:47 +0200 [thread overview]
Message-ID: <3439960.0oRPG1VZx4@thomas> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35E9F7F6@smartserver.smartshare.dk>
18/10/2024 02:39, Morten Brørup:
> > From: Robin Jarry [mailto:rjarry@redhat.com]
> > Sent: Friday, 18 October 2024 00.42
> >
> > Add more ICMP message types and codes based on RFC 792. Change the
> > namespace prefix from RTE_IP_ICMP_ to RTE_ICMP_ to allow
> > differentiation
> > between types and codes.
> >
> > Do not include deprecated message types as described in RFC 6918.
> >
> > Link: https://www.rfc-editor.org/rfc/rfc792
> > Link: https://www.rfc-editor.org/rfc/rfc6918
> > Signed-off-by: Robin Jarry <rjarry@redhat.com>
> > Acked-by: Stephen Hemminger <stephen@networkplumber.org>
> > Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>
>
> Acked-by: Morten Brørup <mb@smartsharesystems.com>
Highlighted the API changes in the release notes,
and applied, thanks.
prev parent reply other threads:[~2024-10-18 15:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 8:33 [PATCH dpdk] " Robin Jarry
2024-10-17 16:02 ` Stephen Hemminger
2024-10-17 22:22 ` Ferruh Yigit
2024-10-17 22:33 ` Robin Jarry
2024-10-17 22:48 ` Ferruh Yigit
2024-10-17 22:41 ` [PATCH dpdk v2] " Robin Jarry
2024-10-18 0:39 ` Morten Brørup
2024-10-18 15:13 ` 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=3439960.0oRPG1VZx4@thomas \
--to=thomas@monjalon.net \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=mb@smartsharesystems.com \
--cc=rjarry@redhat.com \
--cc=stephen@networkplumber.org \
/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).