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: pull request (net-next): ipsec-next 2021-08-27
Date: Fri, 27 Aug 2021 10:20:06 +0000 [thread overview]
Message-ID: <163005960695.4453.11461822658020938423.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210827075015.2584560-1-steffen.klassert@secunet.com>
Hello:
This pull request was applied to netdev/net-next.git (refs/heads/master):
On Fri, 27 Aug 2021 09:50:12 +0200 you wrote:
> 1) Remove an unneeded extra variable in esp4 esp_ssg_unref.
> From Corey Minyard.
>
> 2) Add a configuration option to change the default behaviour
> to block traffic if there is no matching policy.
> Joint work with Christian Langrock and Antony Antony.
>
> [...]
Here is the summary with links:
- pull request (net-next): ipsec-next 2021-08-27
https://git.kernel.org/netdev/net-next/c/fe50893aa86e
- [2/3] xfrm: Add possibility to set the default to block if we have no policy
https://git.kernel.org/netdev/net-next/c/2d151d39073a
- [3/3] net: xfrm: fix shift-out-of-bounce
https://git.kernel.org/netdev/net-next/c/5d8dbb7fb82b
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:[~2021-08-27 10:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 7:50 pull request (net-next): ipsec-next 2021-08-27 Steffen Klassert
2021-08-27 7:50 ` [PATCH 1/3] ipsec: Remove unneeded extra variable in esp4 esp_ssg_unref() Steffen Klassert
2021-08-27 7:50 ` [PATCH 2/3] xfrm: Add possibility to set the default to block if we have no policy Steffen Klassert
2021-08-27 7:50 ` [PATCH 3/3] net: xfrm: fix shift-out-of-bounce Steffen Klassert
2021-08-27 10: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=163005960695.4453.11461822658020938423.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).