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]

Message-ID: <20090903184017.GA9784@infradead.org>
Date:	Thu, 3 Sep 2009 14:40:17 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Greg KH <greg@...ah.com>
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 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.

--
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/