From: Stephen Hemminger <shemming@brocade.com>
To: Ani Sinha <ani@arista.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: iproute2 compatibility
Date: Thu, 1 Oct 2015 15:02:53 -0700 [thread overview]
Message-ID: <20151001150253.3c1d695f@urahara> (raw)
In-Reply-To: <998e657b10fc41d286bf372de59969b3@HQ1WP-EXMB11.corp.brocade.com>
On Thu, 1 Oct 2015 20:06:00 +0000
Ani Sinha <ani@arista.com> wrote:
> Hi Stephen :
>
> I was looking around but could not find clear evidence that a later
> version of iproute2 is compatible with an older kernel. Specifically,
> we are wondering if iproute2 v 3.6 is compatible with linux kernel
> 3.4. Highly appreciate any pointers on this.
>
> thanks
> ani
Yes. iproute2 is supposed to compatible with older kernels.
Obviously, if you try to use some new feature on older kernel, an error
will result.
next parent reply other threads:[~2015-10-01 22:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <998e657b10fc41d286bf372de59969b3@HQ1WP-EXMB11.corp.brocade.com>
2015-10-01 22:02 ` Stephen Hemminger [this message]
2015-10-01 20:06 iproute2 compatibility Ani Sinha
2015-10-01 20:48 ` Eric Dumazet
2015-10-01 21:30 ` Ani Sinha
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=20151001150253.3c1d695f@urahara \
--to=shemming@brocade.com \
--cc=ani@arista.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