From: Jeff Garzik <jgarzik@pobox.com>
To: David Miller <davem@davemloft.net>
Cc: fubar@us.ibm.com, netdev@vger.kernel.org, andy@greyhouse.net,
akpm@linux-foundation.org
Subject: Re: [PATCH 0/7] bonding: 7 fixes for 2.6.24
Date: Sun, 20 Jan 2008 20:57:46 -0500 [thread overview]
Message-ID: <4793FC1A.4090401@pobox.com> (raw)
In-Reply-To: <20080120.171538.12566715.davem@davemloft.net>
David Miller wrote:
> From: Jay Vosburgh <fubar@us.ibm.com>
> Date: Thu, 17 Jan 2008 16:24:56 -0800
>
>> Following are seven patches to fix locking problems,
>> silence locking-related warnings and resolve one recent regression
>> in the current 2.6.24-rc.
>
> Jeff, are you going to merge this stuff in?
>
> I'll drop that rtnl_lock() one-liner if so...
Linus has this series in linux-2.6.git, even...
Jeff
prev parent reply other threads:[~2008-01-21 1:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 0:24 [PATCH 0/7] bonding: 7 fixes for 2.6.24 Jay Vosburgh
2008-01-18 0:24 ` [PATCH 1/7] bonding: fix locking in sysfs primary/active selection Jay Vosburgh
2008-01-18 0:24 ` [PATCH 2/7] bonding: fix ASSERT_RTNL that produces spurious warnings Jay Vosburgh
2008-01-18 0:24 ` [PATCH 3/7] bonding: fix locking during alb failover and slave removal Jay Vosburgh
2008-01-18 0:25 ` [PATCH 4/7] bonding: release slaves when master removed via sysfs Jay Vosburgh
2008-01-18 0:25 ` [PATCH 5/7] bonding: Fix up parameter parsing Jay Vosburgh
2008-01-18 0:25 ` [PATCH 6/7] bonding: fix lock ordering for rtnl and bonding_rwsem Jay Vosburgh
2008-01-18 0:25 ` [PATCH 7/7] bonding: Don't hold lock when calling rtnl_unlock Jay Vosburgh
2008-01-18 0:38 ` [PATCH 6/7] bonding: fix lock ordering for rtnl and bonding_rwsem Andrew Morton
2008-01-18 19:39 ` [PATCH 1/7] bonding: fix locking in sysfs primary/active selection Jeff Garzik
2008-01-21 1:15 ` [PATCH 0/7] bonding: 7 fixes for 2.6.24 David Miller
2008-01-21 1:36 ` Andrew Morton
2008-01-21 3:58 ` David Miller
2008-01-21 1:57 ` 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=4793FC1A.4090401@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@linux-foundation.org \
--cc=andy@greyhouse.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.