From: patchwork-bot+netdevbpf@kernel.org
To: Eric Biggers <ebiggers@kernel.org>
Cc: netdev@vger.kernel.org, linux-crypto@vger.kernel.org,
ardb@kernel.org, Jason@zx2c4.com, dsahern@kernel.org,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org
Subject: Re: [PATCH net-next 0/2] Remove low-level SHA-1 functions
Date: Wed, 28 Jan 2026 00:10:09 +0000 [thread overview]
Message-ID: <176955900959.1450890.12872654962892844333.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260123051656.396371-1-ebiggers@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 22 Jan 2026 21:16:54 -0800 you wrote:
> This series updates net/ipv6/addrconf.c to use the regular SHA-1
> functions, then removes sha1_init_raw() and sha1_transform().
>
> Please consider these for net-next.
>
> (These were originally patches 25-26 of the series
> https://lore.kernel.org/linux-crypto/20250712232329.818226-1-ebiggers@kernel.org/ )
>
> [...]
Here is the summary with links:
- [net-next,1/2] ipv6: Switch to higher-level SHA-1 functions
https://git.kernel.org/netdev/net-next/c/5023479627e3
- [net-next,2/2] lib/crypto: sha1: Remove low-level functions from API
https://git.kernel.org/netdev/net-next/c/9ddfabcc1ed8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-01-28 0:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 5:16 [PATCH net-next 0/2] Remove low-level SHA-1 functions Eric Biggers
2026-01-23 5:16 ` [PATCH net-next 1/2] ipv6: Switch to higher-level " Eric Biggers
2026-01-26 3:46 ` David Ahern
2026-01-23 5:16 ` [PATCH net-next 2/2] lib/crypto: sha1: Remove low-level functions from API Eric Biggers
2026-01-28 0:10 ` patchwork-bot+netdevbpf [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=176955900959.1450890.12872654962892844333.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=dsahern@kernel.org \
--cc=ebiggers@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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