Linux wireless drivers development
 help / color / mirror / Atom feed
From: "u2@whoplays.asia" <u2@whoplays.asia>
To: sedat.dilek@gmail.com
Cc: Sedat Dilek <sedat.dilek@googlemail.com>,
	Gertjan van Wingerde <gwingerde@gmail.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [Driver] NEC WL300NU-G
Date: Sun, 16 Jan 2011 08:38:43 +0900	[thread overview]
Message-ID: <4D323003.9070606@whoplays.asia> (raw)
In-Reply-To: <AANLkTincDG82pmYAixgQnMjPJvc4EWPS2jzU=mKX2PxH@mail.gmail.com>

-------- Message --------:
>> I will wait for the 2.6.34~ appears in dist because of maintain-ability.
>
> Give 2.6.37 kernel from Debian/experimental a try?

No thanks!! I'm almost a stable(not experimental) user..
It's not a "try" but a "big challenge"! And I have a physical LAN cable 
now, instead.

      reply	other threads:[~2011-01-15 23:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-15 15:49 [Driver] NEC WL300NU-G u2
2011-01-15 17:39 ` Gertjan van Wingerde
2011-01-15 22:47   ` u2
2011-01-15 23:14     ` Sedat Dilek
2011-01-15 23:38       ` u2 [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=4D323003.9070606@whoplays.asia \
    --to=u2@whoplays.asia \
    --cc=gwingerde@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sedat.dilek@gmail.com \
    --cc=sedat.dilek@googlemail.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