netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Chad N. Tindel" <chad@tindel.net>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: netdev@oss.sgi.com, bonding-devel@lists.sourceforge.net
Subject: Re: [bonding] compatibilty issues
Date: Mon, 29 Sep 2003 20:23:31 -0400	[thread overview]
Message-ID: <20030930002331.GA4156@calma.pair.com> (raw)
In-Reply-To: <3F78C262.30109@pobox.com>

> Well, if that's David's sentiment, then I respectfully disagree with that.

And in all actuality, I might have misunderstood it anyway.  ;-)

> I'm realistic.  I'm not advocating that you support 2.2 through 2.8 
> kernels in the same binary.  What I'm talking about is common sense -- 
> you see 2.4 and 2.6 mixing in the field.  As I said, that's the common 
> case for the near future.
> 
> The common case should be supported.   :)

Agreed.  Is there some point at which we can stop supporting 2.4 from the 2.6
ifenslave?  I mean, its kind of nebulous to just say the "common case"...
you gotta realize, most of us work in big companies like HP, IBM, Intel and
concepts of support life have real meaning to us.

This is a very interestng discussion.  Do you have any insights into what
the other parts of the kernel are doing wrt to this problem?

Chad

  reply	other threads:[~2003-09-30  0:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-29 23:25 [bonding] compatibilty issues Chad N. Tindel
2003-09-29 23:38 ` Jeff Garzik
2003-09-30  0:23   ` Chad N. Tindel [this message]
2003-09-30  5:54   ` David S. Miller
     [not found] <E791C176A6139242A988ABA8B3D9B38A02A464F1@hasmsx403.iil.intel.com>
2003-09-30 11:42 ` Shmulik Hen

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=20030930002331.GA4156@calma.pair.com \
    --to=chad@tindel.net \
    --cc=bonding-devel@lists.sourceforge.net \
    --cc=jgarzik@pobox.com \
    --cc=netdev@oss.sgi.com \
    /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).