All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pontus Fuchs <pontus.fuchs@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-wireless@vger.kernel.org, hch@lst.de, s.L-H@gmx.de,
	linville@tuxdriver.com
Subject: Re: [PATCH 0/4] Driver for the ar5523 chipset
Date: Fri, 12 Oct 2012 08:52:51 +0200	[thread overview]
Message-ID: <5077BE43.7050200@gmail.com> (raw)
In-Reply-To: <20121011203112.GB3317@kroah.com>

Hi,

> But what is keeping this driver from going to the "proper" place in the
> kernel tree (i.e. drivers/net/...)?  I don't have a problem adding it to
> the staging tree, but it would need a TODO file to list what is needed
> to get it out of the staging tree.

I couldn't decide myself so I asked John and he suggested staging. 
Perhaps it should be in driver/net/wireless after all. Can you and John 
give some advice?

Here's a list of things to consider:

* The FW API is reverse engineered and no real documentation is available.
* Limited functionality (notably no HW crypto offload).
* I'm committed to maintaining the driver and fix problems, but only as 
a hobbist.
* It has received very limited testing. S L-H is the only one except 
myself that has run it.

Cheers,

Pontus

  reply	other threads:[~2012-10-12  6:53 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-11 20:01 [PATCH 0/4] Driver for the ar5523 chipset Pontus Fuchs
2012-10-11 20:01 ` [PATCH 1/4] ar5523: Add main driver file Pontus Fuchs
2012-10-15 20:54   ` Luis R. Rodriguez
2012-10-11 20:01 ` [PATCH 2/4] ar5523: Add driver header file Pontus Fuchs
2012-10-13  5:41   ` Kalle Valo
2012-10-13 10:14     ` Pontus Fuchs
2012-10-13 15:45       ` Christoph Hellwig
2012-10-21 19:58       ` Kalle Valo
2012-10-11 20:01 ` [PATCH 3/4] ar5523: Add Firmware API " Pontus Fuchs
2012-10-11 20:01 ` [PATCH 4/4] ar5523: Add Kconfig and Makefile Pontus Fuchs
2012-10-11 20:31 ` [PATCH 0/4] Driver for the ar5523 chipset Greg KH
2012-10-12  6:52   ` Pontus Fuchs [this message]
2012-10-12  7:28     ` Mohammed Shafi
2012-10-12  8:36       ` Pontus Fuchs
2012-10-12  8:23     ` Julian Calaby
2012-10-12  8:33       ` Pontus Fuchs
2012-10-12 11:45         ` Chadd, Adrian
2012-10-30 17:08         ` Adrian Chadd
2012-11-01 17:41           ` Pontus Fuchs
2012-10-12  7:11   ` Kalle Valo
2012-10-12 14:33     ` John W. Linville
2012-10-13  5:38       ` Kalle Valo
2012-10-13 10:25         ` Pontus Fuchs
2012-10-21 16:35           ` Kalle Valo
2012-10-13 15:41         ` Christoph Hellwig
2012-10-13 15:39 ` Christoph Hellwig
2012-10-22 22:43   ` Greg KH

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=5077BE43.7050200@gmail.com \
    --to=pontus.fuchs@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=s.L-H@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.