From: David Miller <davem@davemloft.net>
To: kalash@arista.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Set rtm_table to RT_TABLE_COMPAT for ipv6 for tables > 255
Date: Fri, 22 Feb 2019 15:22:26 -0800 (PST) [thread overview]
Message-ID: <20190222.152226.1935918245873046733.davem@davemloft.net> (raw)
In-Reply-To: <20190221002304.GA24732@us178.sjc.aristanetworks.com>
From: Kalash Nainwal <kalash@arista.com>
Date: Wed, 20 Feb 2019 16:23:04 -0800
> Set rtm_table to RT_TABLE_COMPAT for ipv6 for tables > 255 to
> keep legacy software happy. This is similar to what was done for
> ipv4 in commit 709772e6e065 ("net: Fix routing tables with
> id > 255 for legacy software").
>
> Signed-off-by: Kalash Nainwal <kalash@arista.com>
Applied and queued up for -stable.
next prev parent reply other threads:[~2019-02-22 23:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 0:23 [PATCH] Set rtm_table to RT_TABLE_COMPAT for ipv6 for tables > 255 Kalash Nainwal
2019-02-22 23:22 ` David Miller [this message]
2019-02-22 23:28 ` Kalash Nainwal
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=20190222.152226.1935918245873046733.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kalash@arista.com \
--cc=linux-kernel@vger.kernel.org \
--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).