From: David Miller <davem@davemloft.net>
To: steffen.klassert@secunet.com
Cc: herbert@gondor.apana.org.au, netdev@vger.kernel.org
Subject: Re: pull request (net-next): ipsec-next 2013-04-11
Date: Thu, 11 Apr 2013 16:15:22 -0400 (EDT) [thread overview]
Message-ID: <20130411.161522.88291238581541801.davem@davemloft.net> (raw)
In-Reply-To: <1365666969-22645-1-git-send-email-steffen.klassert@secunet.com>
From: Steffen Klassert <steffen.klassert@secunet.com>
Date: Thu, 11 Apr 2013 09:56:07 +0200
> 1) Allow to avoid copying DSCP during encapsulation
> by setting a SA flag. From Nicolas Dichtel.
>
> 2) Constify the netlink dispatch table, no need to modify it
> at runtime. From Mathias Krause.
>
> Please pull or let me know if there are problems.
Pulled, thanks a lot Steffen.
prev parent reply other threads:[~2013-04-11 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 7:56 pull request (net-next): ipsec-next 2013-04-11 Steffen Klassert
2013-04-11 7:56 ` [PATCH 1/2] xfrm: allow to avoid copying DSCP during encapsulation Steffen Klassert
2013-04-11 7:56 ` [PATCH 2/2] xfrm_user: constify netlink dispatch table Steffen Klassert
2013-04-11 20:15 ` David Miller [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=20130411.161522.88291238581541801.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--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).