From: "John W. Linville" <linville@tuxdriver.com>
To: Heinz Diehl <htd@fancy-poultry.org>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: 2.6.32-rc2: wlan rt73 dead
Date: Tue, 29 Sep 2009 15:19:48 -0400 [thread overview]
Message-ID: <20090929191948.GE2678@tuxdriver.com> (raw)
In-Reply-To: <20090929191125.GA5640@fancy-poultry.org>
On Tue, Sep 29, 2009 at 09:11:25PM +0200, Heinz Diehl wrote:
> And that's it. Tha adapter is "off", and no connection is possible. It's
> strongly 2.6.32-rc2 related, no problems with any other kernel before.
Could you do a git bisect? Also, please Cc:
linux-wireless@vger.kernel.org for your response...
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next parent reply other threads:[~2009-09-29 19:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090929170615.GA5539@fancy-poultry.org>
[not found] ` <20090929191125.GA5640@fancy-poultry.org>
2009-09-29 19:19 ` John W. Linville [this message]
2009-09-29 20:04 ` 2.6.32-rc2: wlan rt73 dead Heinz Diehl
2009-09-29 23:32 ` Johannes Berg
2009-09-29 23:39 ` Rafael J. Wysocki
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=20090929191948.GE2678@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=htd@fancy-poultry.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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).