Linux wireless drivers development
 help / color / mirror / Atom feed
From: Kalle Valo <kalle.valo@iki.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFC] staging wireless crap: tell people not to work on it
Date: Sun, 22 Mar 2009 12:33:37 +0200	[thread overview]
Message-ID: <87ocvtg83i.fsf@litku.valot.fi> (raw)
In-Reply-To: <1237714803.5100.770.camel@johannes.local> (Johannes Berg's message of "Sun\, 22 Mar 2009 10\:40\:03 +0100")

Johannes Berg <johannes@sipsolutions.net> writes:

> Any objections from anyone on this? We've had somebody clean out otus
> because he thought it was a good idea...
>
> johannes
> ---
>  drivers/staging/at76_usb/TODO  |    4 ++--
>  drivers/staging/otus/TODO      |    7 +++----
>  drivers/staging/rt2860/TODO    |    4 ++--
>  drivers/staging/rt2870/TODO    |    9 ++++++++-
>  drivers/staging/wlan-ng/README |    4 +++-
>  5 files changed, 18 insertions(+), 10 deletions(-)
>
> --- wireless-testing.orig/drivers/staging/at76_usb/TODO	2009-03-22 10:31:37.000000000 +0100
> +++ wireless-testing/drivers/staging/at76_usb/TODO	2009-03-22 10:31:37.000000000 +0100
> @@ -1,2 +1,2 @@
> -rewrite the driver to use the proper in-kernel wireless stack
> -instead of using its own.
> +Work on at76c50x-usb instead, possibly using
> +this driver as a reference.

I already sent a similar patch to Greg:

http://kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-05-staging/staging-at76_usb-mention-mac80211-port-in-todo-file.patch

But there's no mention of at76c50x-usb. I'll send an updated version
to him.

(I hope this mail manages to go to the linux-wireless list. All my
emails from yesterday got lost for some strange reason.)

-- 
Kalle Valo

  reply	other threads:[~2009-03-22 10:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-22  9:40 [RFC] staging wireless crap: tell people not to work on it Johannes Berg
2009-03-22 10:33 ` Kalle Valo [this message]
2009-03-22 10:39   ` Johannes Berg
2009-03-22 15:51 ` Marcel Holtmann

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=87ocvtg83i.fsf@litku.valot.fi \
    --to=kalle.valo@iki.fi \
    --cc=johannes@sipsolutions.net \
    --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