From: Michael Buesch <mb@bu3sch.de>
To: Jiri Benc <jbenc@suse.cz>
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 14:49:45 +0200 [thread overview]
Message-ID: <200604301449.46431.mb@bu3sch.de> (raw)
In-Reply-To: <20060430141520.5f0ef66a@logostar.upir.cz>
[-- Attachment #1: Type: text/plain, Size: 490 bytes --]
On Sunday 30 April 2006 14:15, you wrote:
> Sat, 29 Apr 2006 13:00:25 +0200, Johannes Berg pise:
> > This didn't look too good to me, maybe someone can investigate?
> >
> > [24070.841580] Badness in remove_proc_entry at fs/proc/generic.c:732
> > [24070.841593] Call Trace:
> > [...]
>
> I know about this (also mentioned it at Wireless summit), I'm working on
> it.
Hm, seems like I did not listen to you. :P
How does this happen? I never saw it.
--
Greetings Michael.
[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-04-30 12:44 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 [this message]
2006-04-30 19:18 ` Jiri Benc
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=200604301449.46431.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=bcm43xx-dev@berlios.de \
--cc=jbenc@suse.cz \
--cc=johannes@sipsolutions.net \
--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).