netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steffen Klassert <steffen.klassert@secunet.com>
To: Antony Antony <antony@phenome.org>
Cc: <netdev@vger.kernel.org>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"David S . Miller" <davem@davemloft.net>,
	Richard Guy Briggs <rgb@tricolour.ca>
Subject: Re: [PATCH v2 2/2] xfrm: add UDP encapsulation port in migrate message
Date: Wed, 7 Jun 2017 13:02:33 +0200	[thread overview]
Message-ID: <20170607110233.GW2631@secunet.com> (raw)
In-Reply-To: <1496743934-12697-2-git-send-email-antony@phenome.org>

On Tue, Jun 06, 2017 at 12:12:14PM +0200, Antony Antony wrote:
> Add XFRMA_ENCAP, UDP encapsulation port, to km_migrate announcement
> to userland. Only add if XFRMA_ENCAP was in user migrate request.
> 
> Signed-off-by: Antony Antony <antony@phenome.org>
> Reviewed-by: Richard Guy Briggs <rgb@tricolour.ca>

Both patches applied to ipsec-next, thanks a lot!

      reply	other threads:[~2017-06-07 11:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-05 21:56 [PATCH 0/2] add udp encapsulation port to xfrm_do_migrate Antony Antony
2017-06-05 21:56 ` [PATCH 1/2] xfrm: extend MIGRATE with UDP encapsulation port Antony Antony
2017-06-06  0:05   ` Richard Guy Briggs
2017-06-05 21:56 ` [PATCH 2/2] xfrm: add UDP encapsulation port in migrate message Antony Antony
2017-06-06  0:05   ` Richard Guy Briggs
2017-06-06  4:53   ` kbuild test robot
2017-06-06  6:04   ` kbuild test robot
2017-06-06 10:12 ` [PATCH v2 1/2] xfrm: extend MIGRATE with UDP encapsulation port Antony Antony
2017-06-06 10:12 ` [PATCH v2 2/2] xfrm: add UDP encapsulation port in migrate message Antony Antony
2017-06-07 11:02   ` 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=20170607110233.GW2631@secunet.com \
    --to=steffen.klassert@secunet.com \
    --cc=antony@phenome.org \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.org \
    --cc=rgb@tricolour.ca \
    /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).