From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Steffen Klassert <steffen.klassert@secunet.com>, netdev@vger.kernel.org
Cc: Christophe Gouault <christophe.gouault@6wind.com>
Subject: Re: [PATCH RFC v2 03/12] esp6: Use the IPsec protocol multiplexer API
Date: Wed, 05 Mar 2014 18:52:12 +0400 [thread overview]
Message-ID: <53173A1C.2070002@cogentembedded.com> (raw)
In-Reply-To: <1394023276-2591-4-git-send-email-steffen.klassert@secunet.com>
Hello.
On 05-03-2014 16:41, Steffen Klassert wrote:
> Switch esp6 to use the new IPsec protocol multiplexer.
> Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
> ---
> net/ipv6/esp6.c | 24 ++++++++++++++++--------
> 1 file changed, 16 insertions(+), 8 deletions(-)
> diff --git a/net/ipv6/esp6.c b/net/ipv6/esp6.c
> index 6eef8a7..ec6971f 100644
> --- a/net/ipv6/esp6.c
> +++ b/net/ipv6/esp6.c
> @@ -421,7 +421,7 @@ static u32 esp6_get_mtu(struct xfrm_state *x, int mtu)
> net_adj) & ~(blksize - 1)) + net_adj - 2;
> }
>
> -static void esp6_err(struct sk_buff *skb, struct inet6_skb_parm *opt,
> +static int esp6_err(struct sk_buff *skb, struct inet6_skb_parm *opt,
> u8 type, u8 code, int offset, __be32 info)
You should realign this line again to start under *struct*.
WBR, Sergei
next prev parent reply other threads:[~2014-03-05 14:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 12:41 [PATCH RFC v2 0/12] vti6: prepare namespace and interfamily support Steffen Klassert
2014-03-05 12:41 ` [PATCH RFC v2 01/12] xfrm: Introduce xfrm_input_afinfo to access the the callbacks properly Steffen Klassert
2014-03-05 12:41 ` [PATCH RFC v2 02/12] xfrm6: Add IPsec protocol multiplexer Steffen Klassert
2014-03-05 12:41 ` [PATCH RFC v2 03/12] esp6: Use the IPsec protocol multiplexer API Steffen Klassert
2014-03-05 14:52 ` Sergei Shtylyov [this message]
2014-03-05 12:41 ` [PATCH RFC v2 04/12] ah6: " Steffen Klassert
2014-03-05 14:54 ` Sergei Shtylyov
2014-03-05 12:41 ` [PATCH RFC v2 05/12] ipcomp6: " Steffen Klassert
2014-03-05 12:41 ` [PATCH RFC v2 06/12] vti6: Remove dst_entry caching Steffen Klassert
2014-03-05 12:41 ` [PATCH RFC v2 07/12] vti6: Remove caching of flow informations Steffen Klassert
2014-03-05 12:41 ` [PATCH RFC v2 08/12] vti6: Update the ipv6 side to use its own receive hook Steffen Klassert
2014-03-05 12:41 ` [PATCH RFC v2 09/12] xfrm6: Remove xfrm_tunnel_notifier Steffen Klassert
2014-03-05 12:41 ` [PATCH RFC v2 10/12] vti6: Support inter address family tunneling Steffen Klassert
2014-03-05 12:41 ` [PATCH RFC v2 11/12] vti6: Check the tunnel endpoints of the xfrm state and the vti interface Steffen Klassert
2014-03-05 12:41 ` [PATCH RFC v2 12/12] vti6: Enable namespace changing Steffen Klassert
2014-03-14 9:54 ` [PATCH RFC v2 0/12] vti6: prepare namespace and interfamily support Steffen Klassert
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=53173A1C.2070002@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=christophe.gouault@6wind.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.