linux-kernel - Re: [PATCH] Staging:wilc1000 :Remove typedef from struct

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]

Date:	Fri, 31 Jul 2015 13:52:13 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Shraddha Barke <shraddha.6596@...il.com>
Cc:	Dean Lee <dean.lee@...el.com>, Rachel Kim <rachel.kim@...el.com>,
	Johnny Kim <johnny.kim@...el.com>,
	Chris Park <chris.park@...el.com>,
	linux-wireless@...r.kernel.org, devel@...verdev.osuosl.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Staging:wilc1000 :Remove typedef from struct

On Fri, Jul 31, 2015 at 11:08:47AM +0530, Shraddha Barke wrote:
> This patch fixes the following checkpatch.pl warning:
> 
> WARNING: do not add new typedefs
> 
> Signed-off-by: Shraddha Barke <shraddha.6596@...il.com>
> ---
>  drivers/staging/wilc1000/coreconfigurator.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/wilc1000/coreconfigurator.c b/drivers/staging/wilc1000/coreconfigurator.c
> index 54eb8a1..d6ef6e1 100644
> --- a/drivers/staging/wilc1000/coreconfigurator.c
> +++ b/drivers/staging/wilc1000/coreconfigurator.c
> @@ -88,7 +88,7 @@ typedef enum {
>  } tenuFrmSubtype;
>  
>  /* Basic Frame Classes */
> -typedef enum {
> +enum {
>  	CLASS1_FRAME_TYPE      = 0x00,
>  	CLASS2_FRAME_TYPE      = 0x01,
>  	CLASS3_FRAME_TYPE      = 0x02,

Did you test-build this change?
--
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/