From: patchwork-bot+netdevbpf@kernel.org
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: davem@davemloft.net, kuba@kernel.org,
herbert@gondor.apana.org.au, netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] xfrm: update outdated comment
Date: Thu, 09 Apr 2026 02:00:39 +0000 [thread overview]
Message-ID: <177570003932.953143.16846855459954358608.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260408094258.148555-2-steffen.klassert@secunet.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Steffen Klassert <steffen.klassert@secunet.com>:
On Wed, 8 Apr 2026 11:42:40 +0200 you wrote:
> From: kexinsun <kexinsun@smail.nju.edu.cn>
>
> The function __xfrm4_bundle_create() was refactored into
> xfrm_bundle_create() (among others) by commit 25ee3286dcbc
> ("xfrm: Merge common code into xfrm_bundle_create"). The
> responsibility for setting dst->obsolete to DST_OBSOLETE_FORCE_CHK
> now lives in xfrm_bundle_create(). Update the comment accordingly.
>
> [...]
Here is the summary with links:
- [1/2] xfrm: update outdated comment
https://git.kernel.org/netdev/net-next/c/be14d13625c9
- [2/2] xfrm: Drop support for HMAC-RIPEMD-160
https://git.kernel.org/netdev/net-next/c/05d42dc8ab92
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-04-09 2:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 9:42 [PATCH 0/2] pull request (net-next): ipsec-next 2026-04-08 Steffen Klassert
2026-04-08 9:42 ` [PATCH 1/2] xfrm: update outdated comment Steffen Klassert
2026-04-09 2:00 ` patchwork-bot+netdevbpf [this message]
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=177570003932.953143.16846855459954358608.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.