linux-kernel - [PATCHv2 0/3] staging: silicom: fix code styling according to checkpatch

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-next>] [day] [month] [year] [list]

Message-Id: <1387547475-7135-1-git-send-email-michael.hoefler@studium.uni-erlangen.de>
Date:	Fri, 20 Dec 2013 14:51:10 +0100
From:	Michael Hoefler <michael.hoefler@...dium.uni-erlangen.de>
To:	michael.hoefler@...dium.uni-erlangen.de
Cc:	linux-kernel@...cs.fau.de,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Christoph Kohl <christoph.kohl@...nline.de>,
	Rupert Muchembled <rupert@...ch.net>,
	Chad Williamson <chad@...c.us>,
	devel@...verdev.osuosl.org (open list:STAGING SUBSYSTEM),
	linux-kernel@...r.kernel.org (open list)
Subject: [PATCHv2 0/3] staging: silicom: fix code styling according to checkpatch

This patch series fixes most issues discovered by checkpatch. That includes
whitespaces, indentation, the wrong use of parenthesis and some more. Please
refer to the specific patch description to get more details.

Besides some minor issues not discovered by checkpatch are fixed. E.g. i moved some empty lines for a better readability and added missing braces.

This series does not perform functional changes to the code because i do not
have any hardware to test it.


Michael Hoefler (3):
  silicom: fix whitespace issues in bypass.c
  silicom: fix coding style issues in bypass.c
  silicom: remaining checkpatch issues in bypass.c

 drivers/staging/silicom/bypasslib/bypass.c | 158 ++++++++++++++++-------------
 1 file changed, 85 insertions(+), 73 deletions(-)

-- 
1.8.1.2

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