From: Jay Vosburgh <fubar@us.ibm.com>
To: netdev@vger.kernel.org
Cc: Jeff Garzik <jgarzik@pobox.com>
Subject: [PATCH 0/4] bonding: fixes for 2.6.25
Date: Fri, 21 Mar 2008 22:29:32 -0700 [thread overview]
Message-ID: <12061637763004-git-send-email-fubar@us.ibm.com> (raw)
Included are patches for 2.6.25, two bug fixes, a patch for a
couple of compiler warnings, and an update to the version, as
follows:
1. Fix deadlock in 802.3ad due to lack of _bh on lock. Can
deadlock if LACPDU arrives at just the wrong time.
2. Fix two compilers warnings that show up with gcc >= 4.2.
3. Fix error in sysfs cleanup during module removal
4. Bump driver version to 3.2.5.
Please apply for 2.6.25.
Thanks,
-J
---
-Jay Vosburgh, IBM Linux Technology Center, fubar@us.ibm.com
next reply other threads:[~2008-03-22 5:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-22 5:29 Jay Vosburgh [this message]
2008-03-22 5:29 ` [PATCH 1/4] bonding: Fix locking in 802.3ad mode Jay Vosburgh
2008-03-22 5:29 ` [PATCH 2/4] bonding: fix two compiler warnings Jay Vosburgh
2008-03-22 5:29 ` [PATCH 3/4] bonding: Fix sysfs attribute handling Jay Vosburgh
2008-03-22 5:29 ` [PATCH 4/4] bonding: update version Jay Vosburgh
2008-03-26 3:18 ` [PATCH 1/4] bonding: Fix locking in 802.3ad mode Jeff Garzik
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=12061637763004-git-send-email-fubar@us.ibm.com \
--to=fubar@us.ibm.com \
--cc=jgarzik@pobox.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).