All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alison Schofield <amsfield22@gmail.com>
To: Tamara Diaconita <diaconitatamara@gmail.com>
Cc: aditya.shankar@microchip.com, ganesh.krishna@microchip.com,
	gregkh@linuxfoundation.org, outreachy-kernel@googlegroups.com,
	Tamara Diaconita <diaconita.tamara@gmail.com>
Subject: Re: [Outreachy kernel] [PATCH 3/4] staging: wilc1000: Align the code
Date: Fri, 10 Mar 2017 11:37:02 -0800	[thread overview]
Message-ID: <20170310193701.GC23892@d830.WORKGROUP> (raw)
In-Reply-To: <20170310165905.4131-1-diaconita.tamara@gmail.com>

On Fri, Mar 10, 2017 at 06:59:05PM +0200, Tamara Diaconita wrote:
> Improve code readability by deleting tabs and adding spaces to align the code.
> 
> Fixed the checkpath.pl issue:
> CHECK: Aligment should match open paranthesis.
> 
> Signed-off-by: Tamara Diaconita <diaconita.tamara@gmail.com>
Hi Tamara,
This is a virtual v2, because I've seen it before.

These would need to be corrected - (if you keep this in set)
CHECK: 'Aligment' may be misspelled - perhaps 'Alignment'?
CHECK: 'paranthesis' may be misspelled - perhaps 'parenthesis'?
checkpath.pl -> checkpatch.pl

It seems like we're removing CHECK's on alignment and gaining
WARNINGs on lines over 80.

What did you think about reworking that else block, as per
yesterday email.  That would be more of a code logic change
and wouldn't belong in this patchset.  How about tossing this
patch from the set and plan to come back to it another time
and look at that else block.

alisons

> ---
>  drivers/staging/wilc1000/linux_wlan.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/staging/wilc1000/linux_wlan.c b/drivers/staging/wilc1000/linux_wlan.c
> index 2eebc62..c65c5e8 100644
> --- a/drivers/staging/wilc1000/linux_wlan.c
> +++ b/drivers/staging/wilc1000/linux_wlan.c
> @@ -870,12 +870,12 @@ static int wilc_mac_open(struct net_device *ndev)
>  				if (memcmp(wl->vif[i ^ 1]->bssid,
>  					   wl->vif[i ^ 1]->src_addr, 6))
>  					wilc_set_wfi_drv_handler(vif,
> -							 wilc_get_vif_idx(vif),
> -							 0);
> +								 wilc_get_vif_idx(vif),
> +								 0);
>  				else
>  					wilc_set_wfi_drv_handler(vif,
> -							 wilc_get_vif_idx(vif),
> -							 1);
> +								 wilc_get_vif_idx(vif),
> +								 1);
>  			}
>  			wilc_set_operation_mode(vif, vif->iftype);
>  
> -- 
> 2.9.3
> 
> -- 
> You received this message because you are subscribed to the Google Groups "outreachy-kernel" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to outreachy-kernel+unsubscribe@googlegroups.com.
> To post to this group, send email to outreachy-kernel@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/outreachy-kernel/20170310165905.4131-1-diaconita.tamara%40gmail.com.
> For more options, visit https://groups.google.com/d/optout.


      reply	other threads:[~2017-03-10 19:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-10 16:59 [PATCH 3/4] staging: wilc1000: Align the code Tamara Diaconita
2017-03-10 19:37 ` Alison Schofield [this message]

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=20170310193701.GC23892@d830.WORKGROUP \
    --to=amsfield22@gmail.com \
    --cc=aditya.shankar@microchip.com \
    --cc=diaconita.tamara@gmail.com \
    --cc=diaconitatamara@gmail.com \
    --cc=ganesh.krishna@microchip.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=outreachy-kernel@googlegroups.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.