From: "John W. Linville" <linville@tuxdriver.com>
To: Roger While <simrw@sim-basis.de>
Cc: netdev@vger.kernel.org
Subject: Re: Re. Please pull 'upstream' branch of wireless-2.6
Date: Wed, 8 Nov 2006 14:46:00 -0500 [thread overview]
Message-ID: <20061108194554.GA25484@tuxdriver.com> (raw)
In-Reply-To: <6.1.1.1.2.20061108182728.02b11300@192.168.6.12>
On Wed, Nov 08, 2006 at 06:27:54PM +0100, Roger While wrote:
> John, you just broke a considerable number of prism54 users.
> It is NOT an error if the MWI set fails. This is just a
> performance tweak and has NO effect on the driver working.
Yeah, looks like I was a bit overzealous on the warning squelch...
I'll cook-up a new patch that doesn't error-out.
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2006-11-08 19:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 17:27 Re. Please pull 'upstream' branch of wireless-2.6 Roger While
2006-11-08 19:46 ` John W. Linville [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-09 8:24 Roger While
2006-12-29 10:28 Roger While
2007-01-20 11:28 Roger While
2007-01-20 22:35 ` John W. Linville
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=20061108194554.GA25484@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=simrw@sim-basis.de \
/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).