From: Larry Finger <Larry.Finger@lwfinger.net>
To: Christian Resell <christian.resell@gmail.com>,
devel@driverdev.osuosl.org
Cc: florian.c.schilhabel@googlemail.com, gregkh@linuxfoundation.org,
marcus.farkas@finitebox.com, dan.carpenter@oracle.com,
sudipm.mukherjee@gmail.com, paul.gortmaker@windriver.com,
tapaswenipathak@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: rtl8712: fix coding style warning
Date: Sat, 15 Nov 2014 09:31:25 -0600 [thread overview]
Message-ID: <546771CD.3020307@lwfinger.net> (raw)
In-Reply-To: <20141115142535.GB15904@Kosekroken.jensen.com>
On 11/15/2014 08:25 AM, Christian Resell wrote:
> Simple style fix ("else is not generally useful after a break or return").
> For the eudyptula challenge (http://eudyptula-challenge.org/).
>
> Signed-off-by: Christian F. Resell <christian.resell@gmail.com>
> ---
This patch leads to the following build warnings:
CC [M] drivers/staging/rtl8712/rtl871x_security.o
In file included from drivers/staging/rtl8712/osdep_service.h:43:0,
from drivers/staging/rtl8712/rtl871x_security.c:45:
drivers/staging/rtl8712/rtl871x_security.c: In function ‘crc32_init’:
drivers/staging/rtl8712/basic_types.h:35:14: warning: ISO C90 forbids mixed
declarations and code [-Wdeclaration-after-statement]
#define sint signed int
^
drivers/staging/rtl8712/rtl871x_security.c:129:2: note: in expansion of macro ‘sint’
sint i, j;
^
The previous code had braces around the code in question. Either you need to
leave those braces, or you need to move the declarations.
Please compile test your patches!
Larry
> diff --git a/drivers/staging/rtl8712/rtl871x_security.c b/drivers/staging/rtl8712/rtl871x_security.c
> index c653ad6..cc3a446 100644
> --- a/drivers/staging/rtl8712/rtl871x_security.c
> +++ b/drivers/staging/rtl8712/rtl871x_security.c
> @@ -126,26 +126,24 @@ static void crc32_init(void)
> {
> if (bcrc32initialized == 1)
> return;
> - else {
> - sint i, j;
> - u32 c;
> - u8 *p = (u8 *)&c, *p1;
> - u8 k;
> -
> - c = 0x12340000;
> - for (i = 0; i < 256; ++i) {
> - k = crc32_reverseBit((u8)i);
> - for (c = ((u32)k) << 24, j = 8; j > 0; --j)
> - c = c & 0x80000000 ? (c << 1) ^ CRC32_POLY :
> - (c << 1);
> - p1 = (u8 *)&crc32_table[i];
> - p1[0] = crc32_reverseBit(p[3]);
> - p1[1] = crc32_reverseBit(p[2]);
> - p1[2] = crc32_reverseBit(p[1]);
> - p1[3] = crc32_reverseBit(p[0]);
> - }
> - bcrc32initialized = 1;
> + sint i, j;
> + u32 c;
> + u8 *p = (u8 *)&c, *p1;
> + u8 k;
> +
> + c = 0x12340000;
> + for (i = 0; i < 256; ++i) {
> + k = crc32_reverseBit((u8)i);
> + for (c = ((u32)k) << 24, j = 8; j > 0; --j)
> + c = c & 0x80000000 ? (c << 1) ^ CRC32_POLY :
> + (c << 1);
> + p1 = (u8 *)&crc32_table[i];
> + p1[0] = crc32_reverseBit(p[3]);
> + p1[1] = crc32_reverseBit(p[2]);
> + p1[2] = crc32_reverseBit(p[1]);
> + p1[3] = crc32_reverseBit(p[0]);
> }
> + bcrc32initialized = 1;
> }
>
> static u32 getcrc32(u8 *buf, u32 len)
>
prev parent reply other threads:[~2014-11-15 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-15 14:25 Christian Resell
2014-11-15 15:31 ` Larry Finger [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=546771CD.3020307@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=christian.resell@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=florian.c.schilhabel@googlemail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcus.farkas@finitebox.com \
--cc=paul.gortmaker@windriver.com \
--cc=sudipm.mukherjee@gmail.com \
--cc=tapaswenipathak@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome