netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: tparkin@katalix.com
Cc: netdev@vger.kernel.org, jchapman@katalix.com, celston@katalix.com
Subject: Re: [PATCH v3 0/3] l2tp: fix ancillary data handling in ipv6 recv
Date: Thu, 31 Jan 2013 13:53:23 -0500 (EST)	[thread overview]
Message-ID: <20130131.135323.1045623088532919420.davem@davemloft.net> (raw)
In-Reply-To: <1359630146-8305-1-git-send-email-tparkin@katalix.com>

From: Tom Parkin <tparkin@katalix.com>
Date: Thu, 31 Jan 2013 11:02:23 +0000

> Resubmitting to fix up whitespace issues.
> 
> This patchset:
> 
>         * Renames the ipv6-specific datagram_send_ctl and datagram_recv_ctl
>           functions as ip6_datagram_*.  Since datagram_send_ctl is publicly
>           exported it should be named such that it's clearly IPv6-specific.
> 
>         * Exports ip6_datagram_recv_ctl, so that modules may use it in their
>           receive paths.
> 
>         * Changes l2tp_ip6 from using the IPv4-specific ip_cmsg_recv to use the
>           IPv6 version ip6_datagram_recv_ctl.

Series applied, thanks a lot Tom.

      parent reply	other threads:[~2013-01-31 18:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-31 11:02 [PATCH v3 0/3] l2tp: fix ancillary data handling in ipv6 recv Tom Parkin
2013-01-31 11:02 ` [PATCH v3 1/3] ipv6: rename datagram_send_ctl and datagram_recv_ctl Tom Parkin
2013-01-31 11:02 ` [PATCH v3 2/3] ipv6: export ip6_datagram_recv_ctl Tom Parkin
2013-01-31 11:02 ` [PATCH v3 3/3] l2tp: correctly handle ancillary data in the ip6 recv path Tom Parkin
2013-01-31 18:53 ` 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=20130131.135323.1045623088532919420.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=celston@katalix.com \
    --cc=jchapman@katalix.com \
    --cc=netdev@vger.kernel.org \
    --cc=tparkin@katalix.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).