This patch removes typedef from the struct tstrHostIFSetChan and ranames it to set_channel in order to comply with the Linux coding style. Signed-off-by: Tony Cho <tony.cho@xxxxxxxxx> --- drivers/staging/wilc1000/host_interface.c | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/drivers/staging/wilc1000/host_interface.c b/drivers/staging/wilc1000/host_interface.c index d863a8c..2f86a3b 100644 --- a/drivers/staging/wilc1000/host_interface.c +++ b/drivers/staging/wilc1000/host_interface.c @@ -216,7 +216,7 @@ struct rcvd_async_info { }; /*! - * @struct tstrHostIFSetChan + * @struct set_channel * @brief Set Channel message body * @details * @todo @@ -225,9 +225,9 @@ struct rcvd_async_info { * @date 25 March 2012 * @version 1.0 */ -typedef struct _tstrHostIFSetChan { +struct set_channel { u8 u8SetChan; -} tstrHostIFSetChan; +}; /*! * @struct tstrHostIFSetChan @@ -423,7 +423,7 @@ union message_body { struct rcvd_async_info strRcvdGnrlAsyncInfo; /*!< Received General Asynchronous Info message body */ struct key_attr strHostIFkeyAttr; /*!<>*/ struct cfg_param_attr strHostIFCfgParamAttr; /*! <CFG Parameter message Body> */ - tstrHostIFSetChan strHostIFSetChan; + struct set_channel strHostIFSetChan; tstrHostIFGetChan strHostIFGetChan; tstrHostIFSetBeacon strHostIFSetBeacon; /*!< Set beacon message body */ tstrHostIFDelBeacon strHostIFDelBeacon; /*!< Del beacon message body */ @@ -635,13 +635,14 @@ static tstrWILC_WFIDrv *get_handler_from_id(int id) /** * @brief Handle_SetChannel * @details Sending config packet to firmware to set channel - * @param[in] tstrHostIFSetChan* pstrHostIFSetChan + * @param[in] struct set_channel *pstrHostIFSetChan * @return Error code. * @author * @date * @version 1.0 */ -static s32 Handle_SetChannel(tstrWILC_WFIDrv *drvHandler, tstrHostIFSetChan *pstrHostIFSetChan) +static s32 Handle_SetChannel(tstrWILC_WFIDrv *drvHandler, + struct set_channel *pstrHostIFSetChan) { s32 s32Error = 0; -- 1.9.1 -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html