From: Jeff Garzik <jgarzik@pobox•com>
To: Jay Vosburgh <fubar@us•ibm.com>
Cc: netdev@vger•kernel.org, David Miller <davem@davemloft•net>,
Phil Oester <kernel@linuxace•com>
Subject: Re: [PATCH 5/5] bonding: Allow setting max_bonds to zero
Date: Tue, 17 Jun 2008 23:31:16 -0400 [thread overview]
Message-ID: <48588184.5030808@pobox.com> (raw)
In-Reply-To: <12134059271179-git-send-email-fubar@us.ibm.com>
Jay Vosburgh wrote:
> Permit bonding to function rationally if max_bonds is set to
> zero. This will load the module, but create no master devices (which can
> be created via sysfs).
>
> Requires some change to bond_create_sysfs; currently, the
> netdev sysfs directory is determined from the first bonding device created,
> but this is no longer possible. Instead, an interface from net/core is
> created to create and destroy files in net_class.
>
> Based on a patch submitted by Phil Oester <kernel@linuxaces•com>.
> Modified by Jay Vosburgh to fix the sysfs issue mentioned above and to
> update the documentation.
>
> Signed-off-by: Phil Oester <kernel@linuxace•com>
> Signed-off-by: Jay Vosburgh <fubar@us•ibm.com>
applied 1-5
prev parent reply other threads:[~2008-06-18 3:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-14 1:11 [PATCH net-next-2.6 0/5] bonding: Fixes and updates Jay Vosburgh
2008-06-14 1:12 ` [PATCH 1/5] net/core: add NETDEV_BONDING_FAILOVER event Jay Vosburgh
2008-06-14 1:12 ` [PATCH 2/5] bonding: bond_change_active_slave() cleanup under active-backup Jay Vosburgh
2008-06-14 1:12 ` [PATCH 3/5] bonding: deliver netdev event for fail-over under the active-backup mode Jay Vosburgh
2008-06-14 1:12 ` [PATCH 4/5] bonding: Rework / fix multiple gratuitous ARP support Jay Vosburgh
2008-06-14 1:12 ` [PATCH 5/5] bonding: Allow setting max_bonds to zero Jay Vosburgh
2008-06-18 3:31 ` 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=48588184.5030808@pobox.com \
--to=jgarzik@pobox$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=fubar@us$(echo .)ibm.com \
--cc=kernel@linuxace$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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