>-----Original Message----- >From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap- >owner@xxxxxxxxxxxxxxx] On Behalf Of Hebbar, Shivananda >Sent: Tuesday, February 02, 2010 6:44 PM >To: linux-omap >Subject: [Patch 1/8] DSPBRIDGE: typedef cleanup -DSP RTOS > >From 5855acc38e699f9abfcdd11f1dbd5d648feecb74 Mon Sep 17 00:00:00 2001 >From: Shivananda Hebbar <x0hebbar@xxxxxx> >Date: Thu, 28 Jan 2010 18:57:02 -0600 >Subject: [PATCH] DSPBRIDGE: Remove typedef used for DSPRTOS type and >replace it with normal C type. > >This patch removes the typdef used for DSPRTOS type and replaces it with >normal C type. > >Signed-off-by: Shivananda Hebbar <x0hebbar@xxxxxx> >--- > arch/arm/plat-omap/include/dspbridge/dbdefs.h | 3 +-- > 1 files changed, 1 insertions(+), 2 deletions(-) > >diff --git a/arch/arm/plat-omap/include/dspbridge/dbdefs.h b/arch/arm/plat- >omap/include/dspbridge/dbdefs.h >index fc9fdc8..049fcee 100644 >--- a/arch/arm/plat-omap/include/dspbridge/dbdefs.h >+++ b/arch/arm/plat-omap/include/dspbridge/dbdefs.h >@@ -115,7 +115,6 @@ > > typedef u32 DSP_PROCFAMILY; /* Processor family */ > typedef u32 DSP_PROCTYPE; /* Processor type (w/in family) */ >- typedef u32 DSP_RTOSTYPE; /* Type of DSP RTOS */ > > /* Handy Macros */ > #define IsValidProcEvent(x) (((x) == 0) || (((x) & >(DSP_PROCESSORSTATECHANGE | \ @@ -422,7 +421,7 @@ > u32 ulInternalMemSize; > u32 ulExternalMemSize; > u32 uProcessorID; >- DSP_RTOSTYPE tyRunningRTOS; >+ long tyRunningRTOS; Why was it changed to long and not to unsigned int as it as defined before (u32) or int which is the tiye return by Atoi? pGenObj->objData.procObj.tyRunningRTOS = Atoi(token); > s32 nNodeMinPriority; > s32 nNodeMaxPriority; > } ; >-- >-- >To unsubscribe from this list: send the line "unsubscribe linux-omap" in >the body of a message to majordomo@xxxxxxxxxxxxxxx >More majordomo info at http://vger.kernel.org/majordomo-info.html Regards, Fernando. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
