netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Holger Eitzenberger <holger@eitzenberger.org>
To: Jay Vosburgh <fubar@us.ibm.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: [patch 0/9] [RFC] bonding updates for net-next-2.6
Date: Wed, 17 Dec 2008 22:28:27 +0100	[thread overview]
Message-ID: <20081217212827.080073908@jonathan.eitzenberger.org> (raw)

Hi Jay,

what follows are some bonding updates to 802.3ad mode.  They introduce          
the port_params struct as part of the port struct, which helps in handling      
the port parameter values in various places.                                    
                                                                                
Hopefully they are usefull to you.                                              

Thanks.

  /holger


             reply	other threads:[~2008-12-17 21:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-17 21:28 Holger Eitzenberger [this message]
2008-12-17 21:28 ` [patch 1/9] bonding: improve elaborate port_state assignment Holger Eitzenberger
2008-12-17 21:28 ` [patch 2/9] bonding: introduce and use port_params structure Holger Eitzenberger
2008-12-17 21:28 ` [patch 3/9] bonding: use port_params in __record_pdu() Holger Eitzenberger
2008-12-17 21:28 ` [patch 4/9] bonding: use plain memcpy in __record_default() Holger Eitzenberger
2008-12-17 21:28 ` [patch 5/9] bonding: init port_params from template Holger Eitzenberger
2008-12-17 21:28 ` [patch 6/9] bonding: remove various function declarations Holger Eitzenberger
2008-12-17 21:28 ` [patch 7/9] bonding: use port_params in __update_selected() Holger Eitzenberger
2008-12-17 21:28 ` [patch 8/9] bonding: use port_params in __update_default_selected() Holger Eitzenberger
2008-12-17 21:28 ` [patch 9/9] bonding: use port_params in __update_lacpdu_from_port Holger Eitzenberger
2008-12-18  3:14 ` [patch 0/9] [RFC] bonding updates for net-next-2.6 David 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=20081217212827.080073908@jonathan.eitzenberger.org \
    --to=holger@eitzenberger.org \
    --cc=davem@davemloft.net \
    --cc=fubar@us.ibm.com \
    --cc=netdev@vger.kernel.org \
    /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).