From: "John W. Linville" <linville@tuxdriver.com>
To: Tomas Winkler <tomasw@gmail.com>
Cc: stefano.brivio@polimi.it,
Larry Finger <Larry.Finger@lwfinger.net>,
Johannes Berg <johannes@sipsolutions.net>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: mac80211 crash in ieee80211_sta_scan_work
Date: Mon, 28 Jan 2008 10:12:00 -0500 [thread overview]
Message-ID: <20080128151200.GC5835@tuxdriver.com> (raw)
In-Reply-To: <1ba2fa240801280148r27fac26ep5403bc8ccfc6d37a@mail.gmail.com>
On Mon, Jan 28, 2008 at 11:48:51AM +0200, Tomas Winkler wrote:
> On Jan 28, 2008 11:37 AM, <stefano.brivio@polimi.it> wrote:
> > Quoting Tomas Winkler <tomasw@gmail.com>:
> >
> > > There are too many issues with API change patch. I think it is a good
> > > direction but it's really unstable I think we need to give another
> > > round before it can be applied.
> >
> > That has already been applied. I suggest that you point out the
> > iwl4965 bugs you generically reported so that they can be fixed as well.
> >
> We've seen already patches to be un-applied, reverted.
> I'll fix the bugs that's not problem but it takes time. I'm just
> worried about the other users that find driver unusable.
I'm going to hold it back from 2.6.25. We can work on it for 2.6.26.
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2008-01-28 15:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 9:07 mac80211 crash in ieee80211_sta_scan_work Larry Finger
2008-01-28 9:29 ` Tomas Winkler
2008-01-28 9:37 ` stefano.brivio
2008-01-28 9:48 ` Tomas Winkler
2008-01-28 15:12 ` John W. Linville [this message]
2008-01-28 17:07 ` Michael Buesch
2008-01-28 17:46 ` Larry Finger
2008-01-28 18:19 ` John W. Linville
2008-01-28 18:39 ` Michael Buesch
2008-01-28 15:18 ` Michael Buesch
2008-01-28 12:35 ` Bas Hulsken
2008-01-28 17:25 ` Jory A. Pratt
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=20080128151200.GC5835@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Larry.Finger@lwfinger.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=stefano.brivio@polimi.it \
--cc=tomasw@gmail.com \
/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).