linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Chaehyun Lim <chaehyun.lim@gmail.com>
Cc: rachel.kim@atmel.com, devel@driverdev.osuosl.org,
	chris.park@atmel.com, linux-wireless@vger.kernel.org,
	johnny.kim@atmel.com, tony.cho@atmel.com, leo.kim@atmel.com
Subject: Re: [PATCH 06/10] staging: wilc1000: rename hWFIDrv of host_int_set_mac_chnl_num
Date: Sun, 4 Oct 2015 09:41:58 +0100	[thread overview]
Message-ID: <20151004084158.GB21313@kroah.com> (raw)
In-Reply-To: <1443789896-7082-6-git-send-email-chaehyun.lim@gmail.com>

On Fri, Oct 02, 2015 at 09:44:52PM +0900, Chaehyun Lim wrote:
> This patch replaces hWFIDrv with wfi_drv that is first argument of
> host_int_set_mac_chnl_num to avoid camelcase.
> 
> Signed-off-by: Chaehyun Lim <chaehyun.lim@gmail.com>
> ---
>  drivers/staging/wilc1000/host_interface.c | 6 +++---
>  drivers/staging/wilc1000/host_interface.h | 2 +-
>  2 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/staging/wilc1000/host_interface.c b/drivers/staging/wilc1000/host_interface.c
> index 133bb2d..d23d2dd 100644
> --- a/drivers/staging/wilc1000/host_interface.c
> +++ b/drivers/staging/wilc1000/host_interface.c
> @@ -5315,10 +5315,10 @@ s32 host_int_get_rx_power_level(tstrWILC_WFIDrv *hWFIDrv, u8 *pu8RxPowerLevel,
>   *  @date		8 March 2012
>   *  @version		1.0
>   */
> -int host_int_set_mac_chnl_num(tstrWILC_WFIDrv *hWFIDrv, u8 channel)
> +int host_int_set_mac_chnl_num(tstrWILC_WFIDrv *wfi_drv, u8 channel)
>  {
>  	int result = 0;
> -	tstrWILC_WFIDrv *pstrWFIDrv = (tstrWILC_WFIDrv *)hWFIDrv;
> +	tstrWILC_WFIDrv *pstrWFIDrv = (tstrWILC_WFIDrv *)wfi_drv;

Not the issue here, but in the future, why is this cast needed?  Heck,
why is this local variable even needed, why not just use wifi_drv
everywhere in this function?

thanks,

greg k-h

  reply	other threads:[~2015-10-04  8:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02 12:44 [PATCH 01/10] staging: wilc1000: fix return type of host_int_set_mac_chnl_num Chaehyun Lim
2015-10-02 12:44 ` [PATCH 02/10] staging: wilc1000: fix NULL comparison style Chaehyun Lim
2015-10-02 12:44 ` [PATCH 03/10] staging: wilc1000: rename s32Error in host_int_set_mac_chnl_num Chaehyun Lim
2015-10-04 23:50   ` Julian Calaby
2015-10-02 12:44 ` [PATCH 04/10] staging: wilc1000: replace PRINT_ER with pr_err Chaehyun Lim
2015-10-04  8:40   ` Greg KH
2015-10-02 12:44 ` [PATCH 05/10] staging: wilc1000: rename u8ChNum of host_int_set_mac_chnl_num Chaehyun Lim
2015-10-02 12:44 ` [PATCH 06/10] staging: wilc1000: rename hWFIDrv " Chaehyun Lim
2015-10-04  8:41   ` Greg KH [this message]
2015-10-02 12:44 ` [PATCH 07/10] staging: wilc1000: fix return type of host_int_wait_msg_queue_idle Chaehyun Lim
2015-10-02 12:44 ` [PATCH 08/10] staging: wilc1000: rename s32Error in host_int_wait_msg_queue_idle Chaehyun Lim
2015-10-04 23:51   ` Julian Calaby
2015-10-02 12:44 ` [PATCH 09/10] staging: wilc1000: use pr_err " Chaehyun Lim
2015-10-04  8:42   ` Greg KH
2015-10-02 12:44 ` [PATCH 10/10] staging: wilc1000: remove blank lines before close brace Chaehyun Lim

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151004084158.GB21313@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=chaehyun.lim@gmail.com \
    --cc=chris.park@atmel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=johnny.kim@atmel.com \
    --cc=leo.kim@atmel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rachel.kim@atmel.com \
    --cc=tony.cho@atmel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).