From: patchwork-bot+netdevbpf@kernel.org
To: Eric Biggers <ebiggers@kernel.org>
Cc: netdev@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, edumazet@google.com,
ncardwell@google.com, kuniyu@google.com, davem@davemloft.net,
dsahern@kernel.org, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, ardb@kernel.org, Jason@zx2c4.com,
herbert@gondor.apana.org.au, 0x7f454c46@gmail.com
Subject: Re: [PATCH net-next] Documentation/tcp_ao: Document the supported MAC algorithms and lengths
Date: Sat, 02 May 2026 18:20:27 +0000 [thread overview]
Message-ID: <177774602754.3903048.8237803495851364172.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260429210856.725667-1-ebiggers@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 29 Apr 2026 21:08:56 +0000 you wrote:
> Update the TCP-AO documentation to fix some incorrect terminology and
> claims regarding the MAC algorithms, and document which MAC algorithms
> and lengths the Linux implementation supports.
>
> Signed-off-by: Eric Biggers <ebiggers@kernel.org>
> ---
> Documentation/networking/tcp_ao.rst | 38 ++++++++++++++++++++---------
> 1 file changed, 27 insertions(+), 11 deletions(-)
>
> [...]
Here is the summary with links:
- [net-next] Documentation/tcp_ao: Document the supported MAC algorithms and lengths
https://git.kernel.org/netdev/net-next/c/34d67417c8cf
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-05-02 18:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 21:08 [PATCH net-next] Documentation/tcp_ao: Document the supported MAC algorithms and lengths Eric Biggers
2026-05-02 18:20 ` 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=177774602754.3903048.8237803495851364172.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=0x7f454c46@gmail.com \
--cc=Jason@zx2c4.com \
--cc=ardb@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=ebiggers@kernel.org \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ncardwell@google.com \
--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