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/2] pull request (net-next): ipsec-next 2026-04-08
Date: Wed, 8 Apr 2026 11:42:39 +0200 [thread overview]
Message-ID: <20260408094258.148555-1-steffen.klassert@secunet.com> (raw)
1) Update outdated comment in xfrm_dst_check().
From kexinsun.
2) Drop support for HMAC-RIPEMD-160 from IPsec.
From Eric Biggers.
Please pull or let me know if there are problems.
Thanks!
The following changes since commit d2adf01780b8957b31f4954d56646b02de956f65:
net: freescale: ucc_geth: call of_node_put once (2026-02-24 18:26:30 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git tags/ipsec-next-2026-04-08
for you to fetch changes up to 05d42dc8ab92aa54aaeb1c033927c88fd2accba4:
xfrm: Drop support for HMAC-RIPEMD-160 (2026-04-07 10:47:58 +0200)
----------------------------------------------------------------
ipsec-next-2026-04-08
----------------------------------------------------------------
Eric Biggers (1):
xfrm: Drop support for HMAC-RIPEMD-160
kexinsun (1):
xfrm: update outdated comment
net/xfrm/xfrm_algo.c | 20 --------------------
net/xfrm/xfrm_policy.c | 2 +-
tools/testing/selftests/net/ipsec.c | 8 ++------
3 files changed, 3 insertions(+), 27 deletions(-)
next reply other threads:[~2026-04-08 9:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 9:42 Steffen Klassert [this message]
2026-04-08 9:42 ` [PATCH 1/2] xfrm: update outdated comment Steffen Klassert
2026-04-08 9:42 ` [PATCH 2/2] xfrm: Drop support for HMAC-RIPEMD-160 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=20260408094258.148555-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