netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Benc <jbenc@suse.cz>
To: Michael Buesch <mb@bu3sch.de>
Cc: netdev@vger.kernel.org, Broadcom Linux <bcm43xx-dev@berlios.de>,
	Johannes Berg <johannes@sipsolutions.net>
Subject: Re: wireless-dev: warnings while removing bcm43xx-d80211
Date: Sun, 30 Apr 2006 21:18:04 +0200	[thread overview]
Message-ID: <20060430211804.14751754@logostar.upir.cz> (raw)
In-Reply-To: <200604301449.46431.mb@bu3sch.de>

Sun, 30 Apr 2006 14:49:45 +0200, Michael Buesch pise:
> Hm, seems like I did not listen to you. :P
> How does this happen? I never saw it.

Usually when a net interface is renamed (by udev for example). The stack
then tries to remove wrong procfs directory.

 Jiri

-- 
Jiri Benc
SUSE Labs

      reply	other threads:[~2006-04-30 19:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-29 11:00 wireless-dev: warnings while removing bcm43xx-d80211 Johannes Berg
2006-04-30 12:15 ` Jiri Benc
2006-04-30 12:49   ` Michael Buesch
2006-04-30 19:18     ` Jiri Benc [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=20060430211804.14751754@logostar.upir.cz \
    --to=jbenc@suse.cz \
    --cc=bcm43xx-dev@berlios.de \
    --cc=johannes@sipsolutions.net \
    --cc=mb@bu3sch.de \
    --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).