From: Jakub Kicinski <kuba@kernel.org>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: Leon Romanovsky <leon@kernel.org>,
Leon Romanovsky <leonro@nvidia.com>,
Eric Dumazet <edumazet@google.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
Saeed Mahameed <saeedm@nvidia.com>,
Simon Horman <simon.horman@corigine.com>,
Ilia Lin <quic_ilial@quicinc.com>
Subject: Re: [PATCH net-next 4/4] xfrm: Support UDP encapsulation in packet offload mode
Date: Mon, 24 Jul 2023 15:22:56 -0700 [thread overview]
Message-ID: <20230724152256.32812a67@kernel.org> (raw)
In-Reply-To: <051ea7f99b08e90bedb429123bf5e0a1ae0b0757.1689757619.git.leon@kernel.org>
On Wed, 19 Jul 2023 12:26:56 +0300 Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> Since mlx5 supports UDP encapsulation in packet offload, change the XFRM
> core to allow users to configure it.
>
> Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
Steffen, any opinion on this one? Would you like to take the whole series?
next prev parent reply other threads:[~2023-07-24 22:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 9:26 [PATCH net-next 0/4] Support UDP encapsulation in packet offload mode Leon Romanovsky
2023-07-19 9:26 ` [PATCH net-next 1/4] net/mlx5: Add relevant capabilities bits to support NAT-T Leon Romanovsky
2023-07-19 9:26 ` [PATCH net-next 2/4] net/mlx5e: Check for IPsec NAT-T support Leon Romanovsky
2023-07-19 9:26 ` [PATCH net-next 3/4] net/mlx5e: Support IPsec NAT-T functionality Leon Romanovsky
2023-07-19 9:26 ` [PATCH net-next 4/4] xfrm: Support UDP encapsulation in packet offload mode Leon Romanovsky
2023-07-24 22:22 ` Jakub Kicinski [this message]
2023-07-25 2:21 ` Steffen Klassert
2023-07-25 13:14 ` Paolo Abeni
2023-07-25 13:16 ` Leon Romanovsky
2023-07-25 13:40 ` [PATCH net-next 0/4] " patchwork-bot+netdevbpf
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=20230724152256.32812a67@kernel.org \
--to=kuba@kernel.org \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=quic_ilial@quicinc.com \
--cc=saeedm@nvidia.com \
--cc=simon.horman@corigine.com \
--cc=steffen.klassert@secunet.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).