From: David Miller <davem@davemloft.net>
To: g.nault@alphalink.fr
Cc: netdev@vger.kernel.org, jchapman@katalix.com
Subject: Re: [PATCH net-next 0/4] l2tp: remove unused code
Date: Wed, 01 Nov 2017 10:57:46 +0900 (KST) [thread overview]
Message-ID: <20171101.105746.150911072675707358.davem@davemloft.net> (raw)
In-Reply-To: <cover.1509466904.git.g.nault@alphalink.fr>
From: Guillaume Nault <g.nault@alphalink.fr>
Date: Tue, 31 Oct 2017 17:36:41 +0100
> Patch #1 removes the ref/deref mechanism that was originally used to
> prevent ppp pseudowires from dropping their sockets. This mechanism
> was error prone and isn't used anymore.
>
> Patch #2 removes some module specific refcount debugging.
> Patches #3 and #4 take care of some dead code.
Series applied, thanks.
prev parent reply other threads:[~2017-11-01 1:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 16:36 [PATCH net-next 0/4] l2tp: remove unused code Guillaume Nault
2017-10-31 16:36 ` [PATCH net-next 1/4] l2tp: remove ->ref() and ->deref() Guillaume Nault
2017-10-31 16:36 ` [PATCH net-next 2/4] l2tp: remove l2tp specific refcount debugging Guillaume Nault
2017-10-31 16:36 ` [PATCH net-next 3/4] l2tp: remove l2tp_tunnel_count and l2tp_session_count Guillaume Nault
2017-10-31 16:36 ` [PATCH net-next 4/4] l2tp: remove field 'dev' from struct l2tp_eth Guillaume Nault
2017-11-01 1:57 ` 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=20171101.105746.150911072675707358.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=g.nault@alphalink.fr \
--cc=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).