netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Cc: stephen@networkplumber.org, dsahern@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next v2] xfrm: enable to manage default policies
Date: Thu, 28 Oct 2021 15:00:07 +0000	[thread overview]
Message-ID: <163543320753.10329.14599195153341139094.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211025081706.6381-1-nicolas.dichtel@6wind.com>

Hello:

This patch was applied to iproute2/iproute2-next.git (main)
by David Ahern <dsahern@kernel.org>:

On Mon, 25 Oct 2021 10:17:06 +0200 you wrote:
> Two new commands to manage default policies:
>  - ip xfrm policy setdefault
>  - ip xfrm policy getdefault
> 
> And the corresponding part in 'ip xfrm monitor'.
> 
> Signed-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
> 
> [...]

Here is the summary with links:
  - [iproute2-next,v2] xfrm: enable to manage default policies
    https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git/commit/?id=76b30805f9f6

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2021-10-28 15:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-23  6:13 [PATCH iproute2] xfrm: enable to manage default policies Nicolas Dichtel
2021-10-18  8:30 ` [PATCH iproute2 v2] " Nicolas Dichtel
2021-10-21 14:55   ` David Ahern
2021-10-21 21:23     ` Nicolas Dichtel
2021-10-21 22:10       ` David Ahern
2021-10-22  7:52         ` Nicolas Dichtel
2021-10-21 22:25       ` Stephen Hemminger
2021-10-25  8:17     ` [PATCH iproute2-next " Nicolas Dichtel
2021-10-28 15:00       ` 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=163543320753.10329.14599195153341139094.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=dsahern@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    --cc=stephen@networkplumber.org \
    /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).