From: Greg KH <gregkh@linuxfoundation.org>
To: Shivani Bhardwaj <shivanib134@gmail.com>
Cc: outreachy-kernel@googlegroups.com
Subject: Re: [Outreachy kernel] [PATCH 1/2] Staging: wilc1000: coreconfigurator: Remove irrelevant wrapper function
Date: Tue, 27 Oct 2015 14:28:15 +0900 [thread overview]
Message-ID: <20151027052815.GA27052@kroah.com> (raw)
In-Reply-To: <a636533cae194224d97d3ef1290fd299ae6bc8f8.1445607754.git.shivanib134@gmail.com>
On Mon, Oct 26, 2015 at 08:21:05PM +0530, Shivani Bhardwaj wrote:
> Remove the function get_current_channel() and replace its calls by
> get_current_channel_802_11n() as the former function's definition
> involves only returning the value of latter function.
> Semantic patch used to find out the issue:
>
> @@
> identifier f,g;
> @@
>
> *f(...) {
> return g(...); }
>
> Signed-off-by: Shivani Bhardwaj <shivanib134@gmail.com>
> ---
> drivers/staging/wilc1000/coreconfigurator.c | 15 ++++++---------
> 1 file changed, 6 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/staging/wilc1000/coreconfigurator.c b/drivers/staging/wilc1000/coreconfigurator.c
> index 6dfe26d..1403a33 100644
> --- a/drivers/staging/wilc1000/coreconfigurator.c
> +++ b/drivers/staging/wilc1000/coreconfigurator.c
> @@ -331,13 +331,6 @@ u8 get_current_channel_802_11n(u8 *pu8msa, u16 u16RxLen)
> return 0; /* no MIB here */
> }
>
> -u8 get_current_channel(u8 *pu8msa, u16 u16RxLen)
> -{
> - /* Extract current channel information from */
> - /* the beacon/probe response frame */
> - return get_current_channel_802_11n(pu8msa, u16RxLen);
> -}
> -
> /**
> * @brief parses the received 'N' message
> * @details
> @@ -425,8 +418,12 @@ s32 parse_network_info(u8 *pu8MsgBuffer, tstrNetworkInfo **ppstrNetworkInfo)
> /* Get BSSID */
> get_BSSID(pu8msa, pstrNetworkInfo->au8bssid);
>
> - /* Get the current channel */
> - pstrNetworkInfo->u8channel = get_current_channel(pu8msa, (u16RxLen + FCS_LEN));
> + /*
> + * Extract current channel information from
> + * the beacon/probe response frame
> + */
Trailing whitespace :(
Always check your patches with checkpatch.pl so you don't get grumpy
emails from maintainers telling you to run your patches through
checkpatch.pl before sending them out...
thanks,
greg k-h
next prev parent reply other threads:[~2015-10-27 5:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 13:45 [PATCH 0/2] Remove wrapper functions and neat up code Shivani Bhardwaj
2015-10-23 13:46 ` [PATCH 1/2] Staging: wilc1000: coreconfigurator: Remove irrelevant wrapper function Shivani Bhardwaj
2015-10-25 1:25 ` [Outreachy kernel] " Greg KH
2015-10-25 9:10 ` Shivani Bhardwaj
2015-10-27 5:28 ` Greg KH [this message]
2015-10-23 13:46 ` [PATCH 2/2] Staging: wilc1000: coreconfigurator: Remove unnecessary parentheses Shivani Bhardwaj
2015-10-27 5:28 ` [Outreachy kernel] " Greg KH
2015-10-27 17:20 ` Shivani Bhardwaj
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=20151027052815.GA27052@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=outreachy-kernel@googlegroups.com \
--cc=shivanib134@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.