All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Hood <jdthood@ubishops.ca>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] to deal with bad dev->refcnt in unregister_netdevice()
Date: Wed, 21 Feb 2001 11:22:41 -0500	[thread overview]
Message-ID: <3A93EB51.C9D10316@ubishops.ca> (raw)
In-Reply-To: <20010214092251.D1144@e-trend.de> <3A8AA725.7446DEA0@ubishops.ca> <20010214165758.L28359@e-trend.de> <20010214122244.H7859@conectiva.com.br>

Update on the "unregister_netdevice" bug ...

Arnaldo Carvalho de Melo found one bug but there
remains another one that makes the dev->refcnt too
high instead of too low.

To be continued ...

Thomas

  parent reply	other threads:[~2001-02-21 16:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20010214092251.D1144@e-trend.de>
     [not found] ` <3A8AA725.7446DEA0@ubishops.ca>
     [not found]   ` <20010214165758.L28359@e-trend.de>
     [not found]     ` <20010214122244.H7859@conectiva.com.br>
2001-02-15 21:13       ` [PATCH] to deal with bad dev->refcnt in unregister_netdevice() Thomas Hood
2001-02-19 15:27         ` [PATCH] fix bad dev->refcnt in unregister_netdevice was " Arnaldo Carvalho de Melo
2001-02-21 16:22       ` Thomas Hood [this message]
2001-02-25 23:42       ` Should isa-pnp utilize the PnP BIOS? Thomas Hood
2001-02-25 23:49         ` Jeremy Jackson
2001-02-26  0:24         ` Jonathan Morton
2001-03-03  0:33       ` Thomas Hood
2001-07-20  2:48       ` [BUG] "unregister_netdevice: waiting for eth0 to become free. Usage count = 2" Thomas Hood
2001-07-28  5:44       ` Multiple apm resume events Thomas Hood
2001-03-10  2:46 [PATCH] to deal with bad dev->refcnt in unregister_netdevice() Thomas Hood
  -- strict thread matches above, loose matches on Subject: below --
2001-02-12 18:56 Thomas Hood
2001-02-12 17:27 ` Arnaldo Carvalho de Melo
2001-02-12 12:53 Thomas Hood
2001-02-10  6:01 Thomas Hood
2001-02-09  5:44 Thomas Hood
2001-02-08  0:46 Thomas Hood
2001-02-08 19:31 ` kuznet

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=3A93EB51.C9D10316@ubishops.ca \
    --to=jdthood@ubishops.ca \
    --cc=jdthoodREMOVETHIS@yahoo.co.uk \
    --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 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.