All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Daniel Machon <dmachon.dev@gmail.com>
Cc: gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] wilc1000: wilc_wfi_cfgoperations.c: fixed brace coding style issues
Date: Wed, 5 Aug 2015 11:04:31 +0530	[thread overview]
Message-ID: <20150805053431.GC4958@sudip-pc> (raw)
In-Reply-To: <20150804220814.GA9405@gmail.com>

On Wed, Aug 05, 2015 at 12:08:16AM +0200, Daniel Machon wrote:
> Fixed brace coding styles issues
> 
> Signed-off-by: Daniel Machon <dmachon.dev@gmail.com>
> ---
>  drivers/staging/wilc1000/wilc_wfi_cfgoperations.c | 11 +++++------
>  1 file changed, 5 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/staging/wilc1000/wilc_wfi_cfgoperations.c b/drivers/staging/wilc1000/wilc_wfi_cfgoperations.c
> index 92064db..23097ee 100644
> --- a/drivers/staging/wilc1000/wilc_wfi_cfgoperations.c
> +++ b/drivers/staging/wilc1000/wilc_wfi_cfgoperations.c
> @@ -1216,8 +1216,8 @@ static int WILC_WFI_add_key(struct wiphy *wiphy, struct net_device *netdev, u8 k
>  
>  
>  
> -			if (!pairwise)
> -			{
> +			if (!pairwise) {
> +
>  				if (params->cipher == WLAN_CIPHER_SUITE_TKIP)
>  					u8gmode = ENCRYPT_ENABLED | WPA | TKIP;
>  				else
> @@ -1315,8 +1315,8 @@ static int WILC_WFI_add_key(struct wiphy *wiphy, struct net_device *netdev, u8 k
>  
>  		{
>  			u8mode = 0;
> -			if (!pairwise)
> -			{
> +			if (!pairwise) {
> +
This blank line and the one above it are not required.

regards
sudip

      reply	other threads:[~2015-08-05  5:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-04 22:08 [PATCH 1/1] wilc1000: wilc_wfi_cfgoperations.c: fixed brace coding style issues Daniel Machon
2015-08-05  5:34 ` Sudip Mukherjee [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=20150805053431.GC4958@sudip-pc \
    --to=sudipm.mukherjee@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=dmachon.dev@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --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 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.