From: Greg KH <greg@kroah.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Christian Lamparter <chunkeey@web.de>,
"John W. Linville" <linville@tuxdriver.com>,
Stephen Chen <Stephen.Chen@atheros.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: Staging tree status for the .32 kernel merge
Date: Thu, 3 Sep 2009 12:41:21 -0700 [thread overview]
Message-ID: <20090903194121.GA4953@kroah.com> (raw)
In-Reply-To: <43e72e890909031235t17543020leb3d19b17d955d01@mail.gmail.com>
On Thu, Sep 03, 2009 at 12:35:11PM -0700, Luis R. Rodriguez wrote:
> >> - otus. This is sitting here until a "real" wireless driver
> >> will be merged through the wireless tree. Hopefully that
> >> happens soon.
> >
> > ar9170 has been in for a while now, it's just not quite at feature
> > parity yet -- however that also means otus will get no work whatsoever
> > from any of the wireless folks. Draw your own conclusions. Personally, I
> > would drop it and let the users figure out whether they can live with
> > ar9170 or need to support work on it.
>
> Greg, as Johannes noted otus has lacked focus as Johannes whipped out
> a port for it in a few weeks and then Christian gave it some final
> love taps for inclusion, we just still use otus as just a source of
> documentation for any yet missing feature, but for that I guess I can
> just refer people to my git tree. Chris would know better where we're
> at as far as feature-parity is concerned though so I'll leave it up to
> him to judge whether or not having otus gets some users anything
> ar9170 doesn't yet have.
Ok, as I've said before, just let me know when you want the otus driver
removed from the tree and I'll be glad to do so.
thanks,
greg k-h
next prev parent reply other threads:[~2009-09-03 19:43 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 4:14 Staging tree status for the .32 kernel merge Greg KH
2009-09-03 8:49 ` Johannes Berg
2009-09-03 12:48 ` Stefan Lippers-Hollmann
2009-09-03 17:57 ` Greg KH
2009-09-03 18:35 ` Kalle Valo
2009-09-03 19:01 ` Greg KH
2009-09-03 13:14 ` Bartlomiej Zolnierkiewicz
2009-09-03 16:17 ` Christoph Hellwig
2009-09-03 17:55 ` Greg KH
2009-09-03 18:40 ` Christoph Hellwig
2009-09-03 18:55 ` Greg KH
2009-09-03 19:16 ` Christoph Hellwig
2009-09-05 0:16 ` Marcel Holtmann
2009-09-05 0:29 ` Greg KH
2009-09-03 19:35 ` Luis R. Rodriguez
2009-09-03 19:41 ` Greg KH [this message]
2009-09-04 10:20 ` Wolfram Sang
2009-09-04 18:25 ` Belisko Marek
2009-09-05 12:39 ` Willy Tarreau
2009-09-05 14:50 ` Greg KH
2009-09-10 21:57 ` Peter Huewe
2009-09-06 5:28 ` Pavel Machek
2009-09-07 15:55 ` Daniel Walker
2009-09-09 9:57 ` Pavel Machek
2009-09-09 14:19 ` Daniel Walker
2009-09-09 8:01 ` Pavel Machek
2009-09-09 21:47 ` Pavel Machek
2009-09-09 21:53 ` Brian Swetland
2009-09-09 22:25 ` Huntsman, Bryan
2009-09-07 23:12 ` Mauro Carvalho Chehab
2009-09-09 8:10 ` Pavel Machek
2009-09-07 23:21 ` Mauro Carvalho Chehab
2009-09-08 1:14 ` Greg KH
2009-09-12 19:40 ` Frontier USB Drivers (Was: Staging tree status for the .32 kernel merge) Dave Taht
2009-09-14 17:35 ` Greg KH
2009-09-15 9:29 ` Clemens Ladisch
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=20090903194121.GA4953@kroah.com \
--to=greg@kroah.com \
--cc=Stephen.Chen@atheros.com \
--cc=chunkeey@web.de \
--cc=devel@driverdev.osuosl.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.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