From: David Miller <davem@davemloft.net>
To: alexey.kodanev@oracle.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/4] geneve: verify user specified MTU or adjust with a lower device
Date: Fri, 20 Apr 2018 11:19:32 -0400 (EDT) [thread overview]
Message-ID: <20180420.111932.1583415364221949348.davem@davemloft.net> (raw)
In-Reply-To: <1524141752-25789-1-git-send-email-alexey.kodanev@oracle.com>
From: Alexey Kodanev <alexey.kodanev@oracle.com>
Date: Thu, 19 Apr 2018 15:42:28 +0300
> The first two patches don't introduce any functional changes and
> contain minor cleanups for code readability.
>
> The last one adds a new function geneve_link_config() similar to the
> other tunnels. The function will be used on a new link creation or
> when 'remote' parameter is changed. It adjusts a user specified MTU
> or, if it finds a lower device, tunes the tunnel MTU using it.
Ok, series applied, thanks.
prev parent reply other threads:[~2018-04-20 15:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 12:42 [PATCH net-next 0/4] geneve: verify user specified MTU or adjust with a lower device Alexey Kodanev
2018-04-19 12:42 ` [PATCH net-next 1/4] geneve: remove white-space before '#if IS_ENABLED(CONFIG_IPV6)' Alexey Kodanev
2018-04-19 12:42 ` [PATCH net-next 2/4] geneve: cleanup hard coded value for Ethernet header length Alexey Kodanev
2018-04-19 12:42 ` [PATCH net-next 3/4] geneve: check MTU for a minimum in geneve_change_mtu() Alexey Kodanev
2018-04-19 12:42 ` [PATCH net-next 4/4] geneve: configure MTU based on a lower device Alexey Kodanev
2018-04-20 15:19 ` 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=20180420.111932.1583415364221949348.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexey.kodanev@oracle.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).