Omar Ramirez Luna 44c5435064 staging: tidspbridge: fix incorrect free to drv_datap ... This structure is still used after it has been freed, since it is being allocated in probe, calls to free it have been moved to module's remove routine. This should fix the follwoing messages when attempting to remove the module: drv_get_first_dev_extension: Failed to retrieve the object handle drv_get_first_dev_extension: Failed to retrieve the object handle drv_destroy: Failed to store DRV object mgr_destroy: Failed to store MGR object Signed-off-by: Omar Ramirez Luna <omar.ramirez@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2012-02-08 14:14:14 -08:00
..
core	staging: tidspbridge: fix incorrect free to drv_datap	2012-02-08 14:14:14 -08:00
Documentation
dynload	Revert wrong fixes for common misspellings	2011-04-26 23:31:11 -07:00
gen	staging: tidspbridge: dont cast void* from kmalloc()	2011-08-23 15:22:57 -07:00
hw	staging: tidspbridge: MMU2 registers are limited to 32-bit data access	2011-10-19 13:42:49 -07:00
include/dspbridge	atomic: use <linux/atomic.h>	2011-07-26 16:49:47 -07:00
pmgr	Fix common misspellings	2011-03-31 11:26:23 -03:00
rmgr	staging: tidspbridge: fix incorrect free to drv_datap	2012-02-08 14:14:14 -08:00
Kconfig	treewide: Fix typos in various parts of the kernel, and fix some comments.	2011-12-02 14:57:31 +01:00
Makefile
TODO