From: Michael Buesch <mb@bu3sch.de>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Jerry McBride <mcbrides9@comcast.net>,
linux-wireless@vger.kernel.org, bcm43xx-dev@lists.berlios.de
Subject: Re: B43 STILL randomly and silently dropping connections...
Date: Wed, 22 Oct 2008 18:11:03 +0200 [thread overview]
Message-ID: <200810221811.03546.mb@bu3sch.de> (raw)
In-Reply-To: <20081022125143.GB15808@tuxdriver.com>
On Wednesday 22 October 2008 14:51:43 John W. Linville wrote:
> I've seen this message a couple of times -- I'm a bit surprised that
> you haven't been getting a response. I am Cc'ing Michael and the
> bcm43xx mailing list just in case they haven't noticed this message.
I know about this issue.
But what am I supposed to do?
Somebody who can reproduce it, fix it please and provide a patch.
--
Greetings Michael.
prev parent reply other threads:[~2008-10-22 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 10:48 B43 STILL randomly and silently dropping connections Jerry McBride
2008-10-22 12:51 ` John W. Linville
2008-10-22 16:11 ` Michael Buesch [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=200810221811.03546.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcbrides9@comcast.net \
/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).