From: David Ahern <dsahern@gmail.com>
To: Vadim Fedorenko <vfedorenko@novek.ru>,
David Ahern <dsahern@kernel.org>,
netdev@vger.kernel.org
Cc: Jakub Kicinski <kuba@kernel.org>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
"David S. Miller" <davem@davemloft.net>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Florian Westphal <fw@strlen.de>
Subject: Re: [PATCH net-next 1/2] net: ipv6: introduce ip6_dst_mtu_maybe_forward
Date: Sun, 11 Jul 2021 10:23:44 -0600 [thread overview]
Message-ID: <897c968b-866f-b5c3-7f59-eab0c92f166b@gmail.com> (raw)
In-Reply-To: <20210705213617.18317-2-vfedorenko@novek.ru>
On 7/5/21 3:36 PM, Vadim Fedorenko wrote:
> Replace ip6_dst_mtu_forward with ip6_dst_mtu_maybe_forward and
> reuse this code in ip6_mtu. Actually these two functions were
> almost duplicates, this change will simplify the maintaince of
> mtu calculation code.
>
> Signed-off-by: Vadim Fedorenko <vfedorenko@novek.ru>
> ---
> include/net/ip6_route.h | 5 +++--
> net/ipv6/ip6_output.c | 2 +-
> net/ipv6/route.c | 20 +-------------------
> net/netfilter/nf_flow_table_core.c | 2 +-
> 4 files changed, 6 insertions(+), 23 deletions(-)
>
Reviewed-by: David Ahern <dsahern@kernel.org>
next prev parent reply other threads:[~2021-07-11 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 21:36 [PATCH net-next 0/2] Remove duplicate code around MTU Vadim Fedorenko
2021-07-05 21:36 ` [PATCH net-next 1/2] net: ipv6: introduce ip6_dst_mtu_maybe_forward Vadim Fedorenko
2021-07-11 16:23 ` David Ahern [this message]
2021-07-05 21:36 ` [PATCH net-next 2/2] net: ipv4: Consolidate ipv4_mtu and ip_dst_mtu_maybe_forward Vadim Fedorenko
2021-07-11 16:31 ` David Ahern
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=897c968b-866f-b5c3-7f59-eab0c92f166b@gmail.com \
--to=dsahern@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=fw@strlen.de \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=vfedorenko@novek.ru \
--cc=yoshfuji@linux-ipv6.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).