All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amir Noam <amir.noam@intel.com>
To: bonding-devel@lists.sourceforge.net, netdev@oss.sgi.com
Subject: [PATCH 0/10] [bonding 2.6] propagating master's settings to slaves
Date: Thu, 11 Sep 2003 17:37:15 +0300	[thread overview]
Message-ID: <200309111737.15424.amir.noam@intel.com> (raw)

The following set ports to 2.6 the propagation patch set that went into
2.4.23-pre3. Also, fix a free_netdev() error that the previous patch set
introduced and fix a compile error using ipx_hdr().

Patches should be applied after the previous patch set (sent 2003/09/04)
that ported bug fixes from 2.4.


patch1:  Distinguish between modes that use a primary slave from
	 those that don't, and propagate settings accordingly; Consolidate
	 change_active operations and add reselect_active and find_best
	 opeartions.
patch2:  Change monitoring function use the above functionality.
patch3:  Modes that don't use primary don't use the above functionality.
patch4:  Decouple promiscuous handling from the multicast mode setting.
patch5:  Add support for changing HW address and MTU with proper unwind
	 in old modes.
patch6:  Same thing for ALB/TLB modes.
patch7:  Consolidate /proc code, add CHANGENAME handler.
patch8:  Enhance netdev notification handling.
	 Add comment block and bump version.
patch9:  Add missing free_netdev().
patch10: Fix ipx_hdr compile error.

-- 
Amir

 

             reply	other threads:[~2003-09-11 14:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-11 14:37 Amir Noam [this message]
2003-09-11 14:55 ` [PATCH 0/10] [bonding 2.6] propagating master's settings to slaves Jeff Garzik
2003-09-11 18:58 ` Jeff Garzik

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=200309111737.15424.amir.noam@intel.com \
    --to=amir.noam@intel.com \
    --cc=bonding-devel@lists.sourceforge.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.