linux-kernel - Re: [PATCH] Staging: tm6000: fixed some coding style issues

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: <20110201140913.491912fd@endymion.delvare>
Date:	Tue, 1 Feb 2011 14:09:13 +0100
From:	Jean Delvare <khali@...ux-fr.org>
To:	Timo von Holtz <tvh@...ormatik.uni-kiel.de>
Cc:	gregkh@...e.de, mchehab@...hat.com, d.belimov@...il.com,
	stefan.ringel@...or.de, michel.ludwig@...il.com,
	c.pascoe@...e.uq.edu.au, ruslan@...sarev.org.ua,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Staging: tm6000: fixed some coding style issues

On Tue,  1 Feb 2011 13:49:07 +0100, Timo von Holtz wrote:
> Fixed all of the following coding style issues:
> 
> ERROR: return is not a function, parentheses are not required
> WARNING: __func__ should be used instead of gcc specific __FUNCTION__
> ERROR: trailing whitespace
> ERROR: spaces required around that '=' (ctx:VxV)
> WARNING: please, no space before tabs
> WARNING: please, no spaces at the start of a line
> ERROR: space required after that ',' (ctx:VxV)
> WARNING: space prohibited between function name and open parenthesis '('
> ERROR: spaces required around that '<' (ctx:VxV)
> ERROR: spaces required around that '==' (ctx:VxV)
> 
> Signed-off-by: Timo von Holtz <tvh@...ormatik.uni-kiel.de>

Acked-by: Jean Delvare <khali@...ux-fr.org>

Thanks, Timo.

-- 
Jean Delvare
--
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/