From: Guillaume Nault <g.nault@alphalink.fr>
To: netdev@vger.kernel.org
Cc: James Chapman <jchapman@katalix.com>
Subject: [PATCH net-next 0/7] l2tp: trivial cleanups
Date: Mon, 25 Jun 2018 16:07:17 +0200 [thread overview]
Message-ID: <cover.1529935024.git.g.nault@alphalink.fr> (raw)
Just a set of unrelated trivial cleanups (remove unused code, make
local functions static, etc.).
Guillaume Nault (7):
l2tp: remove pppol2tp_session_close()
l2tp: remove .show from struct l2tp_tunnel
l2tp: remove l2tp_tunnel_priv()
l2tp: don't export l2tp_session_queue_purge()
l2tp: don't export l2tp_tunnel_closeall()
l2tp: avoid duplicate l2tp_pernet() calls
l2tp: make l2tp_xmit_core() return void
net/l2tp/l2tp_core.c | 15 +++++----------
net/l2tp/l2tp_core.h | 12 ------------
net/l2tp/l2tp_debugfs.c | 3 ---
net/l2tp/l2tp_ppp.c | 7 -------
4 files changed, 5 insertions(+), 32 deletions(-)
--
2.18.0
next reply other threads:[~2018-06-25 14:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 14:07 Guillaume Nault [this message]
2018-06-25 14:07 ` [PATCH net-next 1/7] l2tp: remove pppol2tp_session_close() Guillaume Nault
2018-06-25 14:07 ` [PATCH net-next 2/7] l2tp: remove .show from struct l2tp_tunnel Guillaume Nault
2018-06-25 14:07 ` [PATCH net-next 3/7] l2tp: remove l2tp_tunnel_priv() Guillaume Nault
2018-06-25 14:07 ` [PATCH net-next 4/7] l2tp: don't export l2tp_session_queue_purge() Guillaume Nault
2018-06-25 14:07 ` [PATCH net-next 5/7] l2tp: don't export l2tp_tunnel_closeall() Guillaume Nault
2018-06-25 14:07 ` [PATCH net-next 6/7] l2tp: avoid duplicate l2tp_pernet() calls Guillaume Nault
2018-06-25 14:07 ` [PATCH net-next 7/7] l2tp: make l2tp_xmit_core() return void Guillaume Nault
2018-06-26 13:56 ` [PATCH net-next 0/7] l2tp: trivial cleanups 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=cover.1529935024.git.g.nault@alphalink.fr \
--to=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