linux-kernel - Re: Staging tree status for the .32 kernel merge

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 4 Sep 2009 17:29:26 -0700
From:	Greg KH <greg@...ah.com>
To:	Marcel Holtmann <marcel@...tmann.org>
Cc:	Christoph Hellwig <hch@...radead.org>,
	Johannes Berg <johannes@...solutions.net>,
	linux-kernel@...r.kernel.org, devel@...uxdriverproject.org
Subject: Re: Staging tree status for the .32 kernel merge

On Sat, Sep 05, 2009 at 02:16:00AM +0200, Marcel Holtmann wrote:
> 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.

Heh, no, the "crap" name is internal only, we don't expose that to
users.

thanks,

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