From: Al Viro <viro@ftp.linux.org.uk>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Andrew Morton <akpm@osdl.org>, Florin Malita <fmalita@gmail.com>,
linux-kernel@vger.kernel.org, ctindel@users.sourceforge.net,
fubar@us.ibm.com, "David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH] bond_main.c: fix device deregistration in init exception path
Date: Thu, 22 Sep 2005 03:43:39 +0100 [thread overview]
Message-ID: <20050922024339.GD7992@ftp.linux.org.uk> (raw)
In-Reply-To: <43321922.70707@pobox.com>
On Wed, Sep 21, 2005 at 10:38:26PM -0400, Jeff Garzik wrote:
> >+ rtnl_unlock();
> >+ rtnl_lock();
> >+
>
>
> Don't we want a schedule() or schedule_timeout(1) in between?
No. rtnl_unlock() does the needed calls directly.
prev parent reply other threads:[~2005-09-22 2:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <432D0612.7070408@gmail.com>
2005-09-18 6:32 ` [PATCH] bond_main.c: fix device deregistration in init exception path Andrew Morton
2005-09-18 7:25 ` David S. Miller
2005-09-22 2:38 ` Jeff Garzik
2005-09-22 2:42 ` Andrew Morton
2005-09-22 2:43 ` Al Viro [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=20050922024339.GD7992@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=akpm@osdl.org \
--cc=ctindel@users.sourceforge.net \
--cc=davem@davemloft.net \
--cc=fmalita@gmail.com \
--cc=fubar@us.ibm.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--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).