mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kuznet@ms2.inr.ac.ru
To: andrewm@uow.edu.au (Andrew Morton)
Cc: davem@redhat.COM, linux-kernel@vger.kernel.org
Subject: Re: NETDEV_CHANGE events when __LINK_STATE_NOCARRIER is modified
Date: Mon, 14 May 2001 21:47:41 +0400 (MSK DST)	[thread overview]
Message-ID: <200105141747.VAA15542@ms2.inr.ac.ru> (raw)
In-Reply-To: <3AFF384B.7382B436@uow.edu.au> from "Andrew Morton" at May 14, 1 11:43:39 am

Hello!

> Jeff has introduced `alloc_etherdev()' which allocates storage
> for a netdev but doesn't register it.  The one quirk with this
> approach (and why it's vastly simpler than my thing) 

I do not see where it is simpler. The only difference is that
name is unknown. 8)


> Not many drivers have been converted to the new interface yet.

Paaardon! It is the only place where it takes sense to tell: "simpler"
and it was sense of your patch! Of course, it is much "simpler" to leave
all the devices in buggy state, no doubts. 8)

What's about dev_probe_lock, I again do not understand why it is not deleted.
Please, shed some light.


> is a bit foggy.  ISTR that the init() method was inherently
> immune to this race.

8) Imagine, I believed that all the devices use this method for years.
The discovery that init_etherdev does some shit was real catharsis. 8)

Alexey

  reply	other threads:[~2001-05-14 17:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <15091.23655.488243.650394@pizda.ninka.net>
2001-05-13 18:19 ` kuznet
2001-05-14  1:43   ` Andrew Morton
2001-05-14 17:47     ` kuznet [this message]
2001-05-14 18:12       ` Jeff Garzik
2001-05-14 18:40         ` kuznet
2001-05-14 19:27           ` Jeff Garzik
2001-05-14 19:42             ` kuznet
2001-05-14 20:34               ` Jeff Garzik
2001-05-14 23:51           ` Andrew Morton
2001-05-15  9:02             ` kuznet
2001-05-15 11:00               ` Andrew Morton
2001-05-15 11:15               ` David S. Miller

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=200105141747.VAA15542@ms2.inr.ac.ru \
    --to=kuznet@ms2.inr.ac.ru \
    --cc=andrewm@uow.edu.au \
    --cc=davem@redhat.COM \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®