From: Larry Finger <Larry.Finger@lwfinger.net>
To: samuel@sortiz.org
Cc: "John W. Linville" <linville@tuxdriver.com>,
Kalle Valo <kalle.valo@iki.fi>,
linux-wireless@vger.kernel.org
Subject: Re: iwl3945 regression: associates but no data is transfered
Date: Thu, 22 Jan 2009 19:06:38 -0600 [thread overview]
Message-ID: <4979181E.1070401@lwfinger.net> (raw)
In-Reply-To: <a0ea5baee379a280e5a06e81facbb631@localhost>
samuel@sortiz.org wrote:
> Have you tried reverting that commit ?
> I actually found that it does break ath5k as well...
No - as I was bisecting, I thought I'd keep going; however, that sounds like a good idea
that might save some time.
I'll report ASAP.
Larry
next prev parent reply other threads:[~2009-01-23 1:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 18:26 iwl3945 regression: associates but no data is transfered Kalle Valo
2009-01-22 18:34 ` John W. Linville
2009-01-22 23:41 ` samuel
2009-01-22 23:55 ` Larry Finger
2009-01-23 0:42 ` samuel
2009-01-23 1:06 ` Larry Finger [this message]
2009-01-23 5:32 ` Harvey Harrison
2009-01-23 0:07 ` Sedat Dilek
2009-01-23 1:20 ` Sedat Dilek
2009-01-22 19:41 ` Sedat Dilek
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=4979181E.1070401@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=kalle.valo@iki.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=samuel@sortiz.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).