From: Jeff Garzik <jgarzik@pobox.com>
To: Jay Vosburgh <fubar@us.ibm.com>
Cc: netdev@vger.kernel.org, bonding-devel@lists.sourceforge.net,
Patrick McHardy <kaber@trash.net>,
mitch.a.williams@intel.com
Subject: Re: [PATCH 1/4] bonding: fix device name allocation error
Date: Tue, 23 Jan 2007 00:49:18 -0500 [thread overview]
Message-ID: <45B5A1DE.4030906@pobox.com> (raw)
In-Reply-To: <200701200215.l0K2FV22021761@death.nxdomain.ibm.com>
Jay Vosburgh wrote:
> The code to select names for the bonding interfaces was, for the
> non-sysfs creation case, always using a hard-coded set of bond0, bond1,
> etc, up to max_bonds. This caused conflicts for the second or
> subsequent loads of the module.
>
> Changed the code to obtain device names from dev_alloc_name().
>
> Signed-off-by: Jay Vosburgh <fubar@us.ibm.com>
applied 1-4 to #upstream
prev parent reply other threads:[~2007-01-23 5:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-20 2:15 [PATCH 1/4] bonding: fix device name allocation error Jay Vosburgh
2007-01-23 5:49 ` 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=45B5A1DE.4030906@pobox.com \
--to=jgarzik@pobox.com \
--cc=bonding-devel@lists.sourceforge.net \
--cc=fubar@us.ibm.com \
--cc=kaber@trash.net \
--cc=mitch.a.williams@intel.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).