From: James Chapman <jchapman@katalix.com>
To: netdev@vger.kernel.org
Subject: [PATCH 0/2] l2tp: l2tp_ip socket fixes
Date: Tue, 10 Apr 2012 11:10:41 +0100 [thread overview]
Message-ID: <1334052643-10910-1-git-send-email-jchapman@katalix.com> (raw)
A couple of small fixes for the l2tp_ip socket support. This is for
L2TPv3 IP link encapsulation.
[PATCH 1/2] l2tp: fix refcount leak in l2tp_ip sockets
[PATCH 2/2] l2tp: don't overwrite source address in l2tp_ip_bind()
net/l2tp/l2tp_ip.c | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
next reply other threads:[~2012-04-10 10:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 10:10 James Chapman [this message]
2012-04-10 10:10 ` [PATCH 1/2] l2tp: fix refcount leak in l2tp_ip sockets James Chapman
2012-04-10 10:10 ` [PATCH 2/2] l2tp: don't overwrite source address in l2tp_ip_bind() James Chapman
2012-04-13 15:06 ` [PATCH 0/2] l2tp: l2tp_ip socket fixes David Miller
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=1334052643-10910-1-git-send-email-jchapman@katalix.com \
--to=jchapman@katalix.com \
--cc=netdev@vger.kernel.org \
/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).