All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Andrew Morton <andrewm@uow.edu.au>,
	"Stephen E. Clark" <sclark46@gte.net>,
	lk <linux-kernel@vger.kernel.org>,
	"David S. Miller" <davem@redhat.com>
Subject: Re: RTNL assert
Date: Mon, 30 Oct 2000 11:43:52 -0500	[thread overview]
Message-ID: <39FDA548.7CDDF63A@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0010301505550.14004-100000@imladris.demon.co.uk>

David Woodhouse wrote:
> 
> On Sat, 28 Oct 2000, Andrew Morton wrote:
> 
> > The rtnetlink lock needs to be taken around
> > register_netdevice().  There should be a function
> > which does these three common steps, but there isn't.
> 
> I thought the only difference between register_netdev() and
> register_netdevice() was that one took the rtnl_lock and the other didn't?

And, register_netdev allocates a name for you if necessary...

-- 
Jeff Garzik             | "Mind if I drive?"  -Sam
Building 1024           | "Not if you don't mind me clawing at the
MandrakeSoft            |  dash and shrieking like a cheerleader."
                        |                     -Max
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-10-30 16:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-28  3:35 RTNL assert Stephen E. Clark
2000-10-28 10:52 ` Andrew Morton
2000-10-28 14:14   ` Stephen E. Clark
2000-10-28 16:18     ` Andrew Morton
2000-10-28 17:05       ` David S. Miller
2000-10-30 15:11   ` David Woodhouse
2000-10-30 16:43     ` Jeff Garzik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-10-28  3:33 Stephen E. Clark

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=39FDA548.7CDDF63A@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=andrewm@uow.edu.au \
    --cc=davem@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sclark46@gte.net \
    /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.