From: Christoph Hellwig <hch@infradead.org>
To: Greg KH <greg@kroah.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Johannes Berg <johannes@sipsolutions.net>,
linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org
Subject: Re: Staging tree status for the .32 kernel merge
Date: Thu, 3 Sep 2009 14:40:17 -0400 [thread overview]
Message-ID: <20090903184017.GA9784@infradead.org> (raw)
In-Reply-To: <20090903175511.GA24943@kroah.com>
On Thu, Sep 03, 2009 at 10:55:11AM -0700, Greg KH wrote:
> On Thu, Sep 03, 2009 at 12:17:34PM -0400, Christoph Hellwig wrote:
> > On Thu, Sep 03, 2009 at 10:49:46AM +0200, Johannes Berg wrote:
> > > > - vt66* wireless drivers. These VIA drivers are being actively
> > > > worked on to get into a much better shape. Nice job.
> > >
> > > And do they come with their own wireless stack too?
> >
> > Please don't put in the vendor vt6656 driver, it will conflict with a
> > proper mac80211 vt6656 driver a group mentored by me will submit late in
> > the 2.6.32 cycle.
>
> It's already in the linux-next tree, and is almost merged with the
> vt6655 driver from what I can see. When your driver goes in I will be
> glad to disable the device ids that it covers, just let me know.
vt665_6_ has just one usb device id. And please make sure to rename the
crap driver to something else than vt6656.ko so that it does not get in
way for the proper driver.
next prev parent reply other threads:[~2009-09-03 18:40 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 [this message]
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
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=20090903184017.GA9784@infradead.org \
--to=hch@infradead.org \
--cc=devel@driverdev.osuosl.org \
--cc=greg@kroah.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@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