Netdev List
 help / color / mirror / Atom feed
From: Steffen Klassert <steffen.klassert@secunet.com>
To: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Cc: <davem@davemloft.net>, <netdev@vger.kernel.org>
Subject: Re: [PATCH ipsec v2 0/4] xfrm interface: bugs fixes
Date: Thu, 18 Jul 2019 09:37:39 +0200	[thread overview]
Message-ID: <20190718073739.GT17989@gauss3.secunet.de> (raw)
In-Reply-To: <20190715100023.8475-1-nicolas.dichtel@6wind.com>

On Mon, Jul 15, 2019 at 12:00:19PM +0200, Nicolas Dichtel wrote:
> 
> Here is a bunch of bugs fixes. Some have been seen by code review and some when
> playing with x-netns.
> The details are in each patch.
> 
> v1 -> v2:
>  - add patch #3 and #4

Series applied, thanks Nicolas!


      parent reply	other threads:[~2019-07-18  7:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-10  7:45 [PATCH ipsec 0/2] xfrm interface: bug fix on changelink Nicolas Dichtel
2019-07-10  7:45 ` [PATCH ipsec 1/2] xfrm interface: avoid corruption " Nicolas Dichtel
2019-07-10  7:45 ` [PATCH ipsec 2/2] xfrm interface: ifname may be wrong in logs Nicolas Dichtel
2019-07-15  9:52 ` [PATCH ipsec 0/2] xfrm interface: bug fix on changelink Nicolas Dichtel
2019-07-15 10:00   ` [PATCH ipsec v2 0/4] xfrm interface: bugs fixes Nicolas Dichtel
2019-07-15 10:00     ` [PATCH ipsec v2 1/4] xfrm interface: avoid corruption on changelink Nicolas Dichtel
2019-07-15 10:00     ` [PATCH ipsec v2 2/4] xfrm interface: ifname may be wrong in logs Nicolas Dichtel
2019-07-15 10:00     ` [PATCH ipsec v2 3/4] xfrm interface: fix list corruption for x-netns Nicolas Dichtel
2019-07-15 10:00     ` [PATCH ipsec v2 4/4] xfrm interface: fix management of phydev Nicolas Dichtel
2019-07-18  7:37     ` Steffen Klassert [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=20190718073739.GT17989@gauss3.secunet.de \
    --to=steffen.klassert@secunet.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.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