All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Tahia Khan <tahia.khan@gmail.com>
Cc: outreachy-kernel@googlegroups.com, aditya.shankar@microchip.com,
	ganesh.krishna@microchip.com
Subject: Re: [PATCH 2/3] staging: wilc1000: Fixes camel-casing in wilc_network_info_received
Date: Tue, 7 Mar 2017 06:49:15 +0100	[thread overview]
Message-ID: <20170307054915.GC14438@kroah.com> (raw)
In-Reply-To: <c708607f19bd4cd0338bbecd20cba63890d20da6.1488838177.git.tahia.khan@gmail.com>

On Mon, Mar 06, 2017 at 05:23:20PM -0500, Tahia Khan wrote:
> Fixes checkpatch warning by renaming pu8Buffer to buffer
> and u32Length to length in wilc_network_info_received.
> 
> Signed-off-by: Tahia Khan <tahia.khan@gmail.com>
> ---
>  drivers/staging/wilc1000/coreconfigurator.h |  4 ++--
>  drivers/staging/wilc1000/host_interface.c   | 12 ++++++------
>  2 files changed, 8 insertions(+), 8 deletions(-)
> 
> diff --git a/drivers/staging/wilc1000/coreconfigurator.h b/drivers/staging/wilc1000/coreconfigurator.h
> index 616bd21..c4c5f3b 100644
> --- a/drivers/staging/wilc1000/coreconfigurator.h
> +++ b/drivers/staging/wilc1000/coreconfigurator.h
> @@ -126,8 +126,8 @@ s32 wilc_parse_assoc_resp_info(u8 *buffer, u32 buffer_len,
>  			       struct connect_resp_info **ret_connect_resp_info);
>  void wilc_scan_complete_received(struct wilc *wilc, u8 *buffer,
>  				 u32 length);
> -void wilc_network_info_received(struct wilc *wilc, u8 *pu8Buffer,
> -				u32 u32Length);
> +void wilc_network_info_received(struct wilc *wilc, u8 *buffer,
> +				u32 length);

Again, one line please.  I'll let you fix up the others in this series
this way as well.

thanks,

greg k-h


  reply	other threads:[~2017-03-07  5:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-06 22:23 [PATCH 0/3] staging: wilc1000: renames multiple camel-cased parameters in wilc methods Tahia Khan
2017-03-06 22:23 ` [PATCH 1/3] staging: wilc1000: Fixes camel-casing in wilc_scan_complete_received Tahia Khan
2017-03-07  5:48   ` Greg KH
2017-03-07  6:54     ` [Outreachy kernel] " Julia Lawall
2017-03-06 22:23 ` [PATCH 2/3] staging: wilc1000: Fixes camel-casing in wilc_network_info_received Tahia Khan
2017-03-07  5:49   ` Greg KH [this message]
2017-03-06 22:23 ` [PATCH 3/3] staging: wilc1000: Fixes camel-casing in wilc_gnrl_info_received Tahia Khan

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=20170307054915.GC14438@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=aditya.shankar@microchip.com \
    --cc=ganesh.krishna@microchip.com \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=tahia.khan@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.