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] [day] [month] [year] [list]
Message-ID: <20101005200649.GA4228@kroah.com>
Date:	Tue, 5 Oct 2010 13:06:49 -0700
From:	Greg KH <greg@...ah.com>
To:	"Savoy, Pavan" <pavan_savoy@...com>
Cc:	"gregkh@...e.de" <gregkh@...e.de>,
	"alan@...rguk.ukuu.org.uk" <alan@...rguk.ukuu.org.uk>,
	"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/3] prepare TI_ST to move out of staging

On Wed, Oct 06, 2010 at 12:27:46AM +0530, Savoy, Pavan wrote:
> > So, on to moving the drivers out of the staging tree, right?  Care to
> > send me patches for them?  Have you gotten the bluetooth driver reviewed
> > yet?
> 
> No not yet.
> I had planned to put up a patch to move the st_core.c, st_kim.c and
> st_ll.c to drivers/misc/ first.

That is fine.

> Then put together Bluetooth header and driver where in I will bring in
> Marcel/Johan & linux-bluetooth into the loop.  Then move the unified
> bt_drv.c to something like ti_st_bt.c to drivers/bluetooth/
> 
> Does this sound OK?

Yes it does.  Feel free to send patches for the first part above on if
you want to.

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ