From: Guillaume Nault <g.nault@alphalink.fr>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 0/3] l2tp: remove unused fields in struct l2tp_parm
Date: Fri, 27 Jul 2018 17:15:21 +0200 [thread overview]
Message-ID: <20180727151521.GD1487@alphalink.fr> (raw)
In-Reply-To: <20180727075712.65dbc416@xeon-e3>
On Fri, Jul 27, 2018 at 07:57:12AM -0700, Stephen Hemminger wrote:
> On Fri, 27 Jul 2018 12:26:28 +0200
> Guillaume Nault <g.nault@alphalink.fr> wrote:
>
> > Several fields of struct l2tp_parm are handled by create_session() but
> > can't actually be set by user.
> > Most of these fields can also be set by get_response(), but are ignored
> > afterwards.
> >
> > Since these fields can't have any visible effect, let's just remove
> > them.
> >
> > Guillaume Nault (3):
> > l2tp: drop data_seq
> > l2tp: drop mtu
> > l2tp: drop lns_mode
> >
> > ip/ipl2tp.c | 13 -------------
> > 1 file changed, 13 deletions(-)
> >
>
> These make sense for iproute2 next
These patches haven't been rejected in patchwork. Does that mean that
David A. will pick them up? Or should I repost to iproute2-next anyway?
prev parent reply other threads:[~2018-07-27 16:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 10:26 [PATCH iproute2 0/3] l2tp: remove unused fields in struct l2tp_parm Guillaume Nault
2018-07-27 10:26 ` [PATCH iproute2 1/3] l2tp: drop data_seq Guillaume Nault
2018-07-27 10:26 ` [PATCH iproute2 2/3] l2tp: drop mtu Guillaume Nault
2018-07-27 10:26 ` [PATCH iproute2 3/3] l2tp: drop lns_mode Guillaume Nault
2018-07-27 14:57 ` [PATCH iproute2 0/3] l2tp: remove unused fields in struct l2tp_parm Stephen Hemminger
2018-07-27 15:15 ` Guillaume Nault [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=20180727151521.GD1487@alphalink.fr \
--to=g.nault@alphalink.fr \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).