From: Greg KH <gregkh@linuxfoundation.org>
To: Avinash kumar <avi.kp.137@gmail.com>
Cc: forest@alittletooquiet.net, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: staging: vt6655: wpactl.c checkpatch clean-up
Date: Fri, 15 Aug 2014 14:27:40 +0800 [thread overview]
Message-ID: <20140815062740.GA19324@kroah.com> (raw)
In-Reply-To: <1407736978-15814-1-git-send-email-avi.kp.137@gmail.com>
On Mon, Aug 11, 2014 at 11:32:58AM +0530, Avinash kumar wrote:
> Cleaned all C99 comments related warnings
>
> Signed-off-by: Avinash kumar <avi.kp.137@gmail.com>
>
> ---
> drivers/staging/vt6655/wpactl.c | 40 +++++++++++++++++++--------------------
> 1 file changed, 20 insertions(+), 20 deletions(-)
>
> diff --git a/drivers/staging/vt6655/wpactl.c b/drivers/staging/vt6655/wpactl.c
> index 8392d4d..96d2562 100644
> --- a/drivers/staging/vt6655/wpactl.c
> +++ b/drivers/staging/vt6655/wpactl.c
> @@ -299,7 +299,7 @@ int wpa_set_keys(PSDevice pDevice, void *ctx,
> else
> byKeyDecMode = KEY_CTL_WEP;
>
> - // Fix HCT test that set 256 bits KEY and Ndis802_11Encryption3Enabled
> + /* Fix HCT test that set 256 bits KEY and Ndis802_11Encryption3Enabled*/
Why not a ' ' at the end of this line, before the '*/' part? Yes, it
pushes you over the 80 character limit, but that's ok, it's something to
fix up later.
> if (pDevice->eEncryptionStatus == Ndis802_11Encryption3Enabled) {
> if (param->u.wpa_key.key_len == MAX_KEY_LEN)
> byKeyDecMode = KEY_CTL_TKIP;
> @@ -314,23 +314,23 @@ int wpa_set_keys(PSDevice pDevice, void *ctx,
> byKeyDecMode = KEY_CTL_WEP;
> }
>
> - // Check TKIP key length
> + /* Check TKIP key length*/
Ok, no excuse this time :)
Please fix this all up and resend.
thanks,
greg k-h
next prev parent reply other threads:[~2014-08-15 15:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 6:02 [PATCH] drivers: staging: vt6655: wpactl.c checkpatch clean-up Avinash kumar
2014-08-15 6:27 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-08-10 17:58 Avinash kumar
2014-08-11 5:45 ` Greg KH
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=20140815062740.GA19324@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=avi.kp.137@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=forest@alittletooquiet.net \
--cc=linux-kernel@vger.kernel.org \
/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