Subject: Re: Staging tree status for the .32 kernel merge
From: Marcel Holtmann <marcel@holtmann.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
In-Reply-To: <20090903185546.GB29945@kroah.com>
References: <20090903041429.GA29875@kroah.com>
	 <1251967786.3336.19.camel@johannes.local>
	 <20090903161734.GA9722@infradead.org> <20090903175511.GA24943@kroah.com>
	 <20090903184017.GA9784@infradead.org>  <20090903185546.GB29945@kroah.com>
Content-Type: text/plain
Date: Sat, 05 Sep 2009 02:16:00 +0200
Message-Id: <1252109760.27694.0.camel@violet>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1094
Lines: 31

Hi Greg,

> > > > > 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.
> 
> Ok, does vt6656_crap.ko sound good to you?  :)

can we suffix all of the staging drivers with _crap actually? At least
for the wireless ones.

Regards

Marcel


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/