diff options
| author | Jeff Johnson <jjohnson@qca.qualcomm.com> | 2013-12-27 15:01:38 -0800 |
|---|---|---|
| committer | Prakash Dhavali <pdhavali@codeaurora.org> | 2014-01-18 02:43:13 -0800 |
| commit | a64bac5faf93d24508103270e6bf24a5e2ccad1d (patch) | |
| tree | 21a87bd7aedd51a59f1d04b1ffbbd509307960b5 | |
| parent | 32bf1d22fea19da48e6f3e30eb88f9b226f5638f (diff) | |
wlan: Fix 64-bit type conversion issue in vos_crypto_init()
When built for a 64-bit architecture vos_crypto_init() generates a
"pointer-to-int-cast" warning. The cause is that a 64-bit pointer is
being assigned to a 32-bit crypto handle.
Note that if the crypto handle was actually being used by the crypto
routines, the appropriate fix would be to change the type of the
crypto handle from (v_U32_t) to (void *) so that it could represent an
opaque memory pointer. But since such a change would require
modification to all of the VOSS crypto APIs as well as changes to all
clients of these APIs, and since in reality the crypto handle is not
actually being used, the less intrusive change is to simply modify
vos_crypto_init() to set the crypto context to 0 instead of NULL.
Change-Id: I73a9c6f0f0361eec1bf49d14a1cf6f109acd3432
CRs-fixed: 567258
| -rw-r--r-- | CORE/VOSS/src/vos_utils.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/CORE/VOSS/src/vos_utils.c b/CORE/VOSS/src/vos_utils.c index 4764d2693cfb..598cd06fbfe4 100644 --- a/CORE/VOSS/src/vos_utils.c +++ b/CORE/VOSS/src/vos_utils.c @@ -121,7 +121,7 @@ VOS_STATUS vos_crypto_init( v_U32_t *phCryptProv ) VOS_STATUS uResult = VOS_STATUS_E_FAILURE; // This implementation doesn't require a crypto context - *phCryptProv = (v_U32_t)NULL; + *phCryptProv = 0; uResult = VOS_STATUS_SUCCESS; return ( uResult ); } |