Since "SYNC_InitializeCS()" allocates "struct SYNC_CSOBJECT" for
"hProcLock", "MEM_AllocObject()" shouldn't be called for
"hProcLock". This was double allocation for the same pointer.
Signed-off-by: Hiroshi DOYU <[EMAIL PROTECTED]>
---
drivers/dsp/bridge/rmgr/proc.c | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/drivers/dsp/bridge/rmgr/proc.c b/drivers/dsp/bridge/rmgr/proc.c
index 3f9a371..082bea3 100644
--- a/drivers/dsp/bridge/rmgr/proc.c
+++ b/drivers/dsp/bridge/rmgr/proc.c
@@ -1006,7 +1006,6 @@ bool PROC_Init(void)
DBC_Assert(!PROC_DebugMask.flags);
GT_create(&PROC_DebugMask, "PR"); /* "PR" for Processor */
- MEM_AllocObject(hProcLock, struct SYNC_CSOBJECT, SIGNATURECS);
(void)SYNC_InitializeCS(&hProcLock);
}
--
1.6.0.3.613.g9f8f13
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
