All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: shmulik.hen@intel.com
Cc: bonding-devel@lists.sourceforge.net, netdev@oss.sgi.com
Subject: Re: [bonding][1/3] Synchronizing 2.4-2.6
Date: Wed, 27 Aug 2003 17:32:05 -0400	[thread overview]
Message-ID: <3F4D2355.8010803@pobox.com> (raw)
In-Reply-To: <200308272000.39229.shmulik.hen@intel.com>

Shmulik Hen wrote:
> This is set 1 that handles backporting bonding stuff from 2.6 into 2.4 
> while fixing some implementation bugs.
> 
> Applies on 2.4.22.
> 
> patch set can be downloaded from:
> http://osdn.dl.sourceforge.net/sourceforge/bonding/patch_set_1_backport.tar.bz2
> 
> This will update the following files:
> 
> 	Documentation/networking/ifenslave.c
> 	drivers/net/bonding/bonding.h
> 	drivers/net/bonding/bond_main.c
> 	drivers/net/net_init.c
> 	include/linux/list.h
> 	include/linux/netdevice.h
> 
> Description:
> patch 1 - Add list_for_each_entry_safe()

applied


> patch 2 - Export alloc_netdev()

already applied and upstream


> patch 3 - Fix /proc read function

applied


> patch 4 - Put the bond's net_device_stats inside the bond struct

already applied and upstream


> patch 5 - Use a linked list to handle multiple bond devices

applied


> patch 6 - Update versions/contributions in header and bump version

applied... even though a non-described ifenslave.c change snuck into 
this patch.

  reply	other threads:[~2003-08-27 21:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-27 17:00 [bonding][1/3] Synchronizing 2.4-2.6 Shmulik Hen
2003-08-27 21:32 ` Jeff Garzik [this message]
2003-08-30 19:01   ` 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=3F4D2355.8010803@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=bonding-devel@lists.sourceforge.net \
    --cc=netdev@oss.sgi.com \
    --cc=shmulik.hen@intel.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.