netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Amir Noam <amir.noam@intel.com>
Cc: fubar@us.ibm.com, bonding-devel@lists.sourceforge.net,
	netdev@oss.sgi.com
Subject: Re: [PATCH 4/5] [bonding] backport 2.6 changes to 2.4
Date: Thu, 07 Aug 2003 20:28:19 -0400	[thread overview]
Message-ID: <3F32EEA3.2000507@pobox.com> (raw)
In-Reply-To: <200307302007.21369.amir.noam@intel.com>

Amir Noam wrote:
> Backported from 2.6:
> Don't dynamically allocate a net_device_stats structure for each bond,
> instead allocate it with the bonding structure.
> 
> Since they are always allocated together anyway, we might as well put
> the stats struct within the bond.


applied to 2.4.

      reply	other threads:[~2003-08-08  0:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-30 17:07 [PATCH 4/5] [bonding] backport 2.6 changes to 2.4 Amir Noam
2003-08-08  0:28 ` Jeff Garzik [this message]

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=3F32EEA3.2000507@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=amir.noam@intel.com \
    --cc=bonding-devel@lists.sourceforge.net \
    --cc=fubar@us.ibm.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).