From: Petr Machata <petrm@mellanox.com>
To: Serhey Popovych <serhe.popovych@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next v2] ip: link_gre6.c: Support IP6_TNL_F_ALLOW_LOCAL_REMOTE flag
Date: Wed, 21 Feb 2018 13:21:34 +0200 [thread overview]
Message-ID: <wihd10ysi4h.fsf@dev-r-vrt-156.mtr.labs.mlnx> (raw)
In-Reply-To: <9c10d7d8-467a-eeef-87a4-5a8c84891d64@gmail.com> (Serhey Popovych's message of "Wed, 21 Feb 2018 08:45:20 +0200")
Serhey Popovych <serhe.popovych@gmail.com> writes:
> Petr Machata wrote:
>> For IP-in-IP tunnels, one can specify the [no]allow-localremote command
>> when configuring a device. Under the hood, this flips the
>> IP6_TNL_F_ALLOW_LOCAL_REMOTE flag on the netdevice. However, ip6gretap
>> and ip6erspan devices, where the flag is also relevant, are not IP-in-IP
>> tunnels, and thus there's no way to configure the flag on these
>> netdevices. Therefore introduce the command to link_gre6 as well.
>>
>> The original support was introduced in commit
>> 21440d19d957 ("ip: link_ip6tnl.c/ip6tunnel.c: Support IP6_TNL_F_ALLOW_LOCAL_REMOTE flag")
>
> This would produce following checkpatch.pl error:
>
> ----------------------------------------------------------------------------------
> Commit b7a2f4a74cd0 ("ip: link_gre6.c: Support
> IP6_TNL_F_ALLOW_LOCAL_REMOTE flag")
> ----------------------------------------------------------------------------------
> WARNING: Possible unwrapped commit description (prefer a maximum 75
> chars per line)
> #14:
> 21440d19d957 ("ip: link_ip6tnl.c/ip6tunnel.c: Support
> IP6_TNL_F_ALLOW_LOCAL_REMOTE flag")
>
> ERROR: Please use git commit description style 'commit <12+ chars of
> sha1> ("<title line>")' - ie: 'commit 21440d19d957 ("ip:
> link_ip6tnl.c/ip6tunnel.c: Support IP6_TNL_F_ALLOW_LOCAL_REMOT'
> #14:
> 21440d19d957 ("ip: link_ip6tnl.c/ip6tunnel.c: Support
> IP6_TNL_F_ALLOW_LOCAL_REMOTE flag")
>
> You probably should address it. In general change looks good to me.
v3 sent. The "unwrapped commit description" warning stays on the commit
reference line, but I don't see a way to shorten it without triggering
the above error again.
Thanks,
Petr
prev parent reply other threads:[~2018-02-21 11:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 0:47 [PATCH iproute2-next v2] ip: link_gre6.c: Support IP6_TNL_F_ALLOW_LOCAL_REMOTE flag Petr Machata
2018-02-21 6:45 ` Serhey Popovych
2018-02-21 11:21 ` Petr Machata [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=wihd10ysi4h.fsf@dev-r-vrt-156.mtr.labs.mlnx \
--to=petrm@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=serhe.popovych@gmail.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