From: "Nicolas de Pesloüan" <nicolas.2p.debian@gmail.com>
To: Flavio Leitner <fbl@redhat.com>
Cc: David Miller <davem@davemloft.net>,
fubar@us.ibm.com, jpirko@redhat.com, netdev@vger.kernel.org,
andy@greyhouse.net
Subject: Re: [patch net-next-2.6] bonding: allow resetting slave failure counters
Date: Wed, 01 Jun 2011 21:34:45 +0200 [thread overview]
Message-ID: <4DE69455.3080203@gmail.com> (raw)
In-Reply-To: <4DE68ECB.70802@redhat.com>
Le 01/06/2011 21:11, Flavio Leitner a écrit :
> On 06/01/2011 04:03 PM, David Miller wrote:
>> From: Jay Vosburgh<fubar@us.ibm.com>
>> Date: Wed, 01 Jun 2011 09:13:39 -0700
>>
>>> The "this dingus was added in version X.Y.Z" is there because
>>> users sometimes read the most recent version of the documentation (that
>>> they get from the internet) and then would become confused when their
>>> older distro driver lacked some option described in the documentation.
>>
>> I disagree with this whole concept, because distros backport features
>> like this into their kernel and therefore the feature is showing up in
>> version X.Y.$(Z-20).
>
> It doesn't matter the version if the user can find the feature, so
> distros backporting features works and that info is not useful at all.
> However, when the user doesn't find the feature and search the internet,
> then that info is helpful.
There are *many* new features that get included into the kernel without documenting the exact first
version that provide them. Why should we need this for bonding? Also, because we lack a table that
gives the kernel version matching a bonding version, the user is not really helped by "you need
version X.Y.Z of bonding to have this feature".
So, I'm not sure it helps...
Nicolas.
next prev parent reply other threads:[~2011-06-01 19:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 9:40 [patch net-next-2.6] bonding: allow resetting slave failure counters Jiri Pirko
2011-06-01 13:28 ` Flavio Leitner
2011-06-01 13:53 ` Jiri Pirko
2011-06-01 16:13 ` Jay Vosburgh
2011-06-01 16:31 ` [patch net-next-2.6 v2] " Jiri Pirko
2011-06-01 16:41 ` Flavio Leitner
2011-06-01 19:23 ` Nicolas de Pesloüan
2011-06-01 20:08 ` Jiri Pirko
2011-06-01 20:12 ` David Miller
2011-06-01 20:27 ` Jiri Pirko
2011-06-01 19:03 ` [patch net-next-2.6] " David Miller
2011-06-01 19:11 ` Flavio Leitner
2011-06-01 19:22 ` David Miller
2011-06-01 19:53 ` Jay Vosburgh
2011-06-01 20:22 ` Flavio Leitner
2011-06-01 19:34 ` Nicolas de Pesloüan [this message]
2011-06-01 20:07 ` Jiri Pirko
2011-06-01 13:51 ` WANG Cong
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=4DE69455.3080203@gmail.com \
--to=nicolas.2p.debian@gmail.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=fbl@redhat.com \
--cc=fubar@us.ibm.com \
--cc=jpirko@redhat.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).