netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amir Noam <amir.noam@intel.com>
To: "Jeff Garzik" <jgarzik@pobox.com>
Cc: <davem@redhat.com>, <bonding-devel@lists.sourceforge.net>,
	<netdev@oss.sgi.com>
Subject: Re: [Bonding-devel] Re: [PATCH 2/10] [bonding 2.6] fix monitoring functions
Date: Thu, 30 Oct 2003 10:56:07 +0200	[thread overview]
Message-ID: <200310301056.07221.amir.noam@intel.com> (raw)
In-Reply-To: <E6F7D288B394A64585E67497E5126BA601F99143@hasmsx403.iil.intel.com>

On Wednesday 29 October 2003 10:01 pm, Jeff Garzik wrote:
> applied to 2.6.  does this need to go into 2.4, too?

As Jay has pointed out this is already in 2.4.

However, the following patch that restores backward compatibility with
old ifenslave is still needed for 2.6. I see that it's already been
applied by David Miller to 2.4.

Amir

diff -Naurp a/drivers/net/bonding/bond_main.c b/drivers/net/bonding/bond_main.c
--- a/drivers/net/bonding/bond_main.c	Thu Oct 30 10:38:34 2003
+++ b/drivers/net/bonding/bond_main.c	Thu Oct 30 10:45:02 2003
@@ -3047,6 +3047,10 @@ static int bond_ioctl(struct net_device 
 		case SIOCBONDRELEASE:	
 			ret = bond_release(master_dev, slave_dev); 
 			break;
+		case BOND_SETHWADDR_OLD:
+		case SIOCBONDSETHWADDR:
+			res = bond_sethwaddr(bond_dev, slave_dev);
+			break;
 		case BOND_CHANGE_ACTIVE_OLD:
 		case SIOCBONDCHANGEACTIVE:
 			if (USES_PRIMARY(bond_mode)) {

       reply	other threads:[~2003-10-30  8:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E6F7D288B394A64585E67497E5126BA601F99143@hasmsx403.iil.intel.com>
2003-10-30  8:56 ` Amir Noam [this message]
2003-10-30 17:12   ` [Bonding-devel] Re: [PATCH 2/10] [bonding 2.6] fix monitoring functions Jay Vosburgh
     [not found] <E6F7D288B394A64585E67497E5126BA601F99145@hasmsx403.iil.intel.com>
2003-11-02 14:53 ` Amir Noam

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=200310301056.07221.amir.noam@intel.com \
    --to=amir.noam@intel.com \
    --cc=bonding-devel@lists.sourceforge.net \
    --cc=davem@redhat.com \
    --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).