linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: drago01 <drago01@gmail.com>
Cc: Ivo van Doorn <IvDoorn@gmail.com>,
	Gertjan van Wingerde <gwingerde@gmail.com>,
	wireless <linux-wireless@vger.kernel.org>,
	mhilzinger@linuxnewmedia.de, Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: System freezes with rt2860/2870
Date: Mon, 11 Jan 2010 08:31:39 -0600	[thread overview]
Message-ID: <4B4B364B.7010902@lwfinger.net> (raw)
In-Reply-To: <f6ca9fed1001110603w2b9ddffcp840f243a9cce57a3@mail.gmail.com>

On 01/11/2010 08:03 AM, drago01 wrote:
> 
> rt2860/2870 are the legacy drivers in stagging; the rt2x00 maintainers
> aren't the right people to complain to ;)

Sorry.

Larry

      reply	other threads:[~2010-01-11 14:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-11 13:45 System freezes with rt2860/2870 Larry Finger
2010-01-11 14:03 ` drago01
2010-01-11 14:31   ` Larry Finger [this message]

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=4B4B364B.7010902@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=IvDoorn@gmail.com \
    --cc=drago01@gmail.com \
    --cc=gregkh@suse.de \
    --cc=gwingerde@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mhilzinger@linuxnewmedia.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).