From: Steffen Klassert <steffen.klassert@secunet.com>
To: David Miller <davem@davemloft.net>, Jakub Kicinski <kuba@kernel.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Steffen Klassert <steffen.klassert@secunet.com>,
<netdev@vger.kernel.org>
Subject: [PATCH 0/8] pull request (net-next): ipsec-next 2022-05-13
Date: Fri, 13 May 2022 17:12:10 +0200 [thread overview]
Message-ID: <20220513151218.4010119-1-steffen.klassert@secunet.com> (raw)
1) Cleanups for the code behind the XFRM offload API. This is a
preparation for the extension of the API for policy offload.
From Leon Romanovsky.
Please pull or let me know if there are problems.
Thanks!
The following changes since commit 949dfdcf343c1646d26ee0ef320d6b2a4a39af28:
Merge branch 'mptcp-improve-mptcp-level-window-tracking' (2022-05-05 19:00:20 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git master
for you to fetch changes up to 0f9008e5c5103e32e788d260558d170c2fc9c2be:
Merge branch 'Be explicit with XFRM offload direction' (2022-05-07 09:19:47 +0200)
----------------------------------------------------------------
Leon Romanovsky (8):
xfrm: free not used XFRM_ESP_NO_TRAILER flag
xfrm: delete not used number of external headers
xfrm: rename xfrm_state_offload struct to allow reuse
xfrm: store and rely on direction to construct offload flags
ixgbe: propagate XFRM offload state direction instead of flags
netdevsim: rely on XFRM state direction instead of flags
net/mlx5e: Use XFRM state direction instead of flags
xfrm: drop not needed flags variable in XFRM offload struct
Steffen Klassert (1):
Merge branch 'Be explicit with XFRM offload direction'
drivers/net/ethernet/intel/ixgbe/ixgbe_ipsec.c | 9 ++++-----
drivers/net/ethernet/intel/ixgbe/ixgbe_ipsec.h | 2 +-
drivers/net/ethernet/intel/ixgbevf/ipsec.c | 6 +++---
drivers/net/ethernet/intel/ixgbevf/ipsec.h | 2 +-
.../net/ethernet/mellanox/mlx5/core/en_accel/ipsec.c | 10 +++++-----
drivers/net/netdevsim/ipsec.c | 2 +-
include/net/xfrm.h | 20 ++++++++++++--------
net/ipv4/esp4.c | 6 ------
net/ipv6/esp6.c | 6 ------
net/xfrm/xfrm_device.c | 15 ++++++++-------
net/xfrm/xfrm_state.c | 4 ++--
net/xfrm/xfrm_user.c | 5 +++--
12 files changed, 40 insertions(+), 47 deletions(-)
next reply other threads:[~2022-05-13 15:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 15:12 Steffen Klassert [this message]
2022-05-13 15:12 ` [PATCH 1/8] xfrm: free not used XFRM_ESP_NO_TRAILER flag Steffen Klassert
2022-05-13 20:20 ` patchwork-bot+netdevbpf
2022-05-13 15:12 ` [PATCH 2/8] xfrm: delete not used number of external headers Steffen Klassert
2022-05-13 15:12 ` [PATCH 3/8] xfrm: rename xfrm_state_offload struct to allow reuse Steffen Klassert
2022-05-13 15:12 ` [PATCH 4/8] xfrm: store and rely on direction to construct offload flags Steffen Klassert
2022-05-13 15:12 ` [PATCH 5/8] ixgbe: propagate XFRM offload state direction instead of flags Steffen Klassert
2022-05-13 15:12 ` [PATCH 6/8] netdevsim: rely on XFRM " Steffen Klassert
2022-05-13 15:12 ` [PATCH 7/8] net/mlx5e: Use " Steffen Klassert
2022-05-13 15:12 ` [PATCH 8/8] xfrm: drop not needed flags variable in XFRM offload struct Steffen Klassert
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=20220513151218.4010119-1-steffen.klassert@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.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).