linux-kernel - [PATCH] Staging: csr: csr_wifi_router_sef.c: fixed a brace coding style issue

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130711064518.GA10611@gmail.com>
Date:	Thu, 11 Jul 2013 09:45:19 +0300
From:	Aldo Iljazi <neonsync1@...il.com>
To:	gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
	devel@...verdev.osuosl.org
Subject: [PATCH] Staging: csr: csr_wifi_router_sef.c: fixed a brace coding
 style issue

On Sat, Jul 06, 2013 at 12:03:14AM +0300, Aldo Iljazi wrote:
> Fixed a coding style issue.
> 
> Signed-off-by: Aldo Iljazi <neonsync1@...il.com>
> ---
>  drivers/staging/csr/csr_wifi_router_sef.c |    3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/drivers/staging/csr/csr_wifi_router_sef.c b/drivers/staging/csr/csr_wifi_router_sef.c
> index 45a10fb..bdb7d3b 100644
> --- a/drivers/staging/csr/csr_wifi_router_sef.c
> +++ b/drivers/staging/csr/csr_wifi_router_sef.c
> @@ -9,8 +9,7 @@
>   *****************************************************************************/
>  #include "csr_wifi_router_sef.h"
>  
> -const CsrWifiRouterStateHandlerType CsrWifiRouterDownstreamStateHandlers[CSR_WIFI_ROUTER_PRIM_DOWNSTREAM_COUNT] =
> -{
> +const CsrWifiRouterStateHandlerType CsrWifiRouterDownstreamStateHandlers[CSR_WIFI_ROUTER_PRIM_DOWNSTREAM_COUNT] = {
>      /* 0x0000 */ CsrWifiRouterMaPacketSubscribeReqHandler,
>      /* 0x0001 */ CsrWifiRouterMaPacketUnsubscribeReqHandler,
>      /* 0x0002 */ CsrWifiRouterMaPacketReqHandler,
> -- 
> 1.7.9.5
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/