public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mateusz Kulikowski <mateusz.kulikowski@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 10/11] staging: rtl8192e: Decrease nesting of rtllib_rx_auth_resp()
Date: Mon, 30 Mar 2015 01:21:02 +0200	[thread overview]
Message-ID: <551888DE.1050003@gmail.com> (raw)
In-Reply-To: <1427670839.2715.44.camel@perches.com>

Hi Joe, 

Thanks for reviewing my patches.

On 30.03.2015 01:13, Joe Perches wrote:
> On Mon, 2015-03-30 at 00:41 +0200, Mateusz Kulikowski wrote:
>> Return from rtllib_rx_auth_resp() if auth_parse() fails.
> 
> Hello Mateusz.  Here are some trivial notes.
> 
>> diff --git a/drivers/staging/rtl8192e/rtllib_softmac.c b/drivers/staging/rtl8192e/rtllib_softmac.c
> []
>> +		/* Dummy wirless mode setting to avoid
>> +		 * encryption issue */
> 
> Please use the typical networking comment style
> (and correct the typo too)
> 
> 		/* Dummy wireless mode setting to avoid
> 		 * encryption issue
> 		 */

It was like that already - is it ok with you if I fix all the comments (in whole rtl8192e) in separate patch 
(I can add it as #12 to v2) ?

> 
>> +		if (bSupportNmode) {
>> +			ieee->SetWirelessMode(ieee->dev,
>> +			   ieee->current_network.mode);
>> +		} else {
>> +			/*TODO*/
>> +			ieee->SetWirelessMode(ieee->dev,
>> +					      IEEE_G);
> 
> Many of these multiple line statements can be single line.

I wanted to split change of logic and re-indentation;
If you insist - I can merge patches #10 and #11 (#11 does what you ask for)


Regards,
Mateusz


  reply	other threads:[~2015-03-29 23:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-29 22:40 [PATCH 00/11] staging: rtl8192e: checkpatch.pl cleanups Mateusz Kulikowski
2015-03-29 22:40 ` [PATCH 01/11] staging: rtl8192e: Fix UNNECESSARY_ELSE warning Mateusz Kulikowski
2015-03-29 22:40 ` [PATCH 02/11] staging: rtl8192e: Fix RETURN_VOID warnings Mateusz Kulikowski
2015-03-29 22:40 ` [PATCH 03/11] staging: rtl8192e: remove unused EXPORT_SYMBOL_RSL macro Mateusz Kulikowski
2015-03-29 22:41 ` [PATCH 04/11] staging: rtl8192e: Fix UNNECESSARY_PARENTHESES warnings Mateusz Kulikowski
2015-03-29 22:41 ` [PATCH 05/11] staging: rtl8192e: Fix LINE_CONTINUATIONS warning Mateusz Kulikowski
2015-03-29 22:41 ` [PATCH 06/11] staging: rtl8192e: Fix BRACES warning Mateusz Kulikowski
2015-03-29 22:41 ` [PATCH 07/11] staging: rtl8192e: Fix DO_WHILE_MACRO_WITH_TRAILING_SEMICOLON warning Mateusz Kulikowski
2015-03-29 22:41 ` [PATCH 08/11] staging: rtl8192e: Fix PRINTK_WITHOUT_KERN_LEVEL warnings Mateusz Kulikowski
2015-03-29 22:41 ` [PATCH 09/11] staging: rtl8192e: Divide rtllib_rx_auth() Mateusz Kulikowski
2015-03-29 22:41 ` [PATCH 10/11] staging: rtl8192e: Decrease nesting of rtllib_rx_auth_resp() Mateusz Kulikowski
2015-03-29 23:13   ` Joe Perches
2015-03-29 23:21     ` Mateusz Kulikowski [this message]
2015-03-29 23:28       ` Joe Perches
2015-03-29 22:41 ` [PATCH 11/11] staging: rtl8192e: Fix indentation in rtllib_rx_auth_resp() Mateusz Kulikowski

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=551888DE.1050003@gmail.com \
    --to=mateusz.kulikowski@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --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