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: delete duplicated functions that calls same xfrm_api_check()
Date: Sat, 19 Mar 2022 15:10:13 +0000 [thread overview]
Message-ID: <164770261354.11599.16611522183353497205.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220319074240.554227-2-steffen.klassert@secunet.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Steffen Klassert <steffen.klassert@secunet.com>:
On Sat, 19 Mar 2022 08:42:39 +0100 you wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> The xfrm_dev_register() and xfrm_dev_feat_change() have same
> implementation of one call to xfrm_api_check(). Instead of doing such
> indirection, call to xfrm_api_check() directly and delete duplicated
> functions.
>
> [...]
Here is the summary with links:
- [1/2] xfrm: delete duplicated functions that calls same xfrm_api_check()
https://git.kernel.org/netdev/net-next/c/2ecda181682e
- [2/2] xfrm: rework default policy structure
https://git.kernel.org/netdev/net-next/c/b58b1f563ab7
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:[~2022-03-19 15:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-19 7:42 [PATCH 0/2] pull request (net-next): ipsec-next 2022-03-19 Steffen Klassert
2022-03-19 7:42 ` [PATCH 1/2] xfrm: delete duplicated functions that calls same xfrm_api_check() Steffen Klassert
2022-03-19 15:10 ` patchwork-bot+netdevbpf [this message]
2022-03-19 7:42 ` [PATCH 2/2] xfrm: rework default policy structure 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=164770261354.11599.16611522183353497205.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.