From: Johannes Berg <johannes@sipsolutions.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Daniel Drake <dsd@gentoo.org>,
Bcm43xx-dev@lists.berlios.de, netdev@vger.kernel.org
Subject: Re: bcm43xx driver unstable behaviour (and linux wireless is junk btw)
Date: Mon, 25 Sep 2006 12:00:47 +0200 [thread overview]
Message-ID: <1159178447.4509.17.camel@ux156> (raw)
In-Reply-To: <1159178281.13140.5.camel@localhost.localdomain>
On Mon, 2006-09-25 at 19:58 +1000, Benjamin Herrenschmidt wrote:
> Doh ! Scary... locking is hard ... if the stuff was written without
> locking in mind in the first place, it might end up being a nightmare...
Yeah, I've actually suggested "rewriting" it from its own pieces :) But
Jiri says he understands it well enough now to not have to do that.
johannes
next prev parent reply other threads:[~2006-09-25 10:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-24 2:43 bcm43xx driver unstable behaviour (and linux wireless is junk btw) Benjamin Herrenschmidt
[not found] ` <1159065798.5924.8.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2006-09-24 3:45 ` Daniel Drake
[not found] ` <4515FF5D.4080602-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2006-09-24 6:18 ` Benjamin Herrenschmidt
[not found] ` <1159078683.5924.16.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2006-09-24 8:05 ` Michael Buesch
[not found] ` <200609241005.02024.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2006-09-24 8:12 ` Benjamin Herrenschmidt
2006-09-24 8:43 ` Michael Buesch
2006-09-24 8:47 ` Benjamin Herrenschmidt
2006-09-24 15:34 ` Daniel Drake
2006-09-24 16:38 ` Michael Buesch
2006-09-25 9:02 ` Johannes Berg
2006-09-25 9:58 ` Benjamin Herrenschmidt
2006-09-25 10:00 ` Johannes Berg [this message]
2006-09-24 3:50 ` Dan Williams
[not found] ` <1159069857.2748.5.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2006-09-24 6:13 ` Benjamin Herrenschmidt
2006-09-24 16:02 ` Dan Williams
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=1159178447.4509.17.camel@ux156 \
--to=johannes@sipsolutions.net \
--cc=Bcm43xx-dev@lists.berlios.de \
--cc=benh@kernel.crashing.org \
--cc=dsd@gentoo.org \
--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).