From: Stephen Hemminger <shemminger@vyatta•com>
To: David Miller <davem@davemloft•net>
Cc: benve@cisco•com, bhutchings@solarflare•com,
gregory.v.rose@intel•com, jeffrey.t.kirsher@intel•com,
netdev@vger•kernel.org, gospo@redhat•com
Subject: Re: [net-next] iproute2: Add new command to IP link to enable/disable VF spoof check
Date: Mon, 26 Sep 2011 14:19:59 -0700 [thread overview]
Message-ID: <20110926141959.58d310c0@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <20110926.170049.1943390151354224651.davem@davemloft.net>
On Mon, 26 Sep 2011 17:00:49 -0400 (EDT)
David Miller <davem@davemloft•net> wrote:
> From: "Christian Benvenuti (benve)" <benve@cisco•com>
> Date: Mon, 26 Sep 2011 15:54:53 -0500
>
> > Does it mean that a Netlink interface becomes official (and backward
> > compatibility should not be broken) only once iproute2 starts
> > supporting it?
>
> It needs to be analyzed on a case-by-case basis. Sometimes we can quickly
> fix a poorly designed netlink interface is no major tool takes on use of
> the feature.
If an interface changes before an official release, there is no
problem. I.e. if an interface goes through multiple versions while
in net-next (or a bug fix during 3.X-rc*) that's fine.
next prev parent reply other threads:[~2011-09-26 21:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-25 8:23 [net-next] iproute2: Add new command to IP link to enable/disable VF spoof check Jeff Kirsher
2011-09-25 17:23 ` Stephen Hemminger
2011-09-26 16:21 ` Rose, Gregory V
2011-09-26 16:41 ` Ben Hutchings
2011-09-26 16:47 ` Stephen Hemminger
2011-09-26 16:58 ` Rose, Gregory V
2011-09-26 20:54 ` Christian Benvenuti (benve)
2011-09-26 21:00 ` David Miller
2011-09-26 21:19 ` Stephen Hemminger [this message]
2011-09-26 21:27 ` David Miller
2011-11-17 23:39 ` Greg Rose
2011-11-18 0:40 ` Stephen Hemminger
2011-11-18 0:43 ` Greg Rose
2011-11-18 0:45 ` Stephen Hemminger
2011-11-18 17:06 ` Greg Rose
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=20110926141959.58d310c0@nehalam.linuxnetplumber.net \
--to=shemminger@vyatta$(echo .)com \
--cc=benve@cisco$(echo .)com \
--cc=bhutchings@solarflare$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=gospo@redhat$(echo .)com \
--cc=gregory.v.rose@intel$(echo .)com \
--cc=jeffrey.t.kirsher@intel$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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