Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Christian Schäfer" <schaefer@in.tum.de>, linux-wireless@vger.kernel.org
Subject: Re: [BUG] timer.h
Date: Mon, 06 Aug 2007 08:35:46 +0200	[thread overview]
Message-ID: <1186382146.21957.40.camel@johannes.berg> (raw)
In-Reply-To: <20070803123240.519c5a38.akpm@linux-foundation.org>

[-- Attachment #1: Type: text/plain, Size: 859 bytes --]

On Fri, 2007-08-03 at 12:32 -0700, Andrew Morton wrote:

> > I was able to reproduce the bug without a tainted kernel (i.e. without 
> > the nvidia binary module). Please let me know if you need more infos.

What sort of wireless code are you using? That _rtl suffix *looks* like
some weird vendor driver added _rtl to all function and module names.
It's definitely not pristine upstream source; looks to me like vendor
source to that r8187 module you have since the official driver is called
rtl8187.

> >   [<f8e4600c>] ieee80211_associate_procedure_wq_rtl7+0x0/0x78  [ieee80211_rtl]

> You'll need to hunt down the authors of ieee80211_rtl (where'd that come
> from?) and tell them not do do add_timer() or an already-pending timer.

There's no such nor any similar function in any code I know. No use
blaming linux-wireless.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

  reply	other threads:[~2007-08-06  8:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <46B1F896.8090005@in.tum.de>
     [not found] ` <46B2EA43.8070305@in.tum.de>
2007-08-03 19:32   ` [BUG] timer.h Andrew Morton
2007-08-06  6:35     ` Johannes Berg [this message]
2007-08-06  8:44       ` Christian Schäfer
2007-08-06  9:12         ` Johannes Berg

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=1186382146.21957.40.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=schaefer@in.tum.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