public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: "Chad N. Tindel" <chad@tindel•net>
To: Shmulik Hen <shmulik.hen@intel•com>
Cc: "David S. Miller" <davem@redhat•com>,
	"Chad N. Tindel" <chad@tindel•net>,
	fubar@us•ibm.com, jgarzik@pobox•com,
	bonding-devel@lists•sourceforge.net, netdev@oss•sgi.com
Subject: Re: [Bonding-devel] Re: [bonding] compatibilty issues
Date: Wed, 1 Oct 2003 14:26:10 -0400	[thread overview]
Message-ID: <20031001182610.GA25218@calma.pair.com> (raw)
In-Reply-To: <200310011149.04612.shmulik.hen@intel.com>

> So here is what I did in the meantime:
> * Created a version for 2.4 that puts back all old compatibility stuff 
>   that was removed either during the propagation set or the cleanup 
>   set.
> * Created a version for 2.6 that puts back just the compatibility 
>   stuff that was removed in the propagation set (BOND_SETHWADDR, since 
>   we got a complaint from a RH9 user).
> * Removed the mention of the multicast param from the read-me.
> * Raised the ABI version to 2 so the new ifenslave keeps propagating 
>   IP settings to slaves for older drivers, and doesn't do that for new 
>   ones that contain Willy Tarreau's panic fix.

I like this.

Chad

  reply	other threads:[~2003-10-01 18:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E791C176A6139242A988ABA8B3D9B38A02A464F2@hasmsx403.iil.intel.com>
2003-10-01  8:49 ` [Bonding-devel] Re: [bonding] compatibilty issues Shmulik Hen
2003-10-01 18:26   ` Chad N. Tindel [this message]
2003-10-01 19:25     ` Jay Vosburgh
     [not found] <E791C176A6139242A988ABA8B3D9B38A02A464F9@hasmsx403.iil.intel.com>
2003-10-02  6:37 ` Shmulik Hen
2003-10-03 19:57   ` Jay Vosburgh
2003-10-02  7:57 ` Shmulik Hen
2003-09-30 11:42 Shmulik Hen
2003-09-30 16:39 ` [Bonding-devel] " Jay Vosburgh
2003-09-30 21:36   ` Chad N. Tindel
2003-10-01  7:05     ` David S. Miller

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=20031001182610.GA25218@calma.pair.com \
    --to=chad@tindel$(echo .)net \
    --cc=bonding-devel@lists$(echo .)sourceforge.net \
    --cc=davem@redhat$(echo .)com \
    --cc=fubar@us$(echo .)ibm.com \
    --cc=jgarzik@pobox$(echo .)com \
    --cc=netdev@oss$(echo .)sgi.com \
    --cc=shmulik.hen@intel$(echo .)com \
    /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