linux-kernel - [PATCH v2 0/6] staging: goldfish: fix coding style

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: <1409775795-12521-1-git-send-email-loic@loicp.eu>
Date:	Wed,  3 Sep 2014 22:23:09 +0200
From:	Loic Pefferkorn <loic@...cp.eu>
To:	gregkh@...uxfoundation.org, alan@...ux.intel.com
Cc:	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: [PATCH v2 0/6] staging: goldfish: fix coding style

Hi,

This patchset fixes several coding style warnings detected by checkpatch.pl:
-CHECK: Please don't use multiple blank lines
-CHECK: No space is necessary after a cast
-CHECK: spinlock_t definition without comment
-CHECK: Alignment should match open parenthesis
-CHECK: struct mutex definition without comment
-CHECK: multiple assignments should be avoided

v2 changes:
-document more specifically the usage of mutex and spinlock

Loic Pefferkorn (6):
  staging: goldfish: suppress consecutive blank lines
  staging: goldfish: remove useless space after a cast
  staging: goldfish: document spinlock usage
  staging: goldfish: fix alignment to match open parenthesis
  staging: goldfish: document mutex usage
  staging: goldfish: avoid multiple assignments

 drivers/staging/goldfish/goldfish_audio.c | 24 ++++++++----------
 drivers/staging/goldfish/goldfish_nand.c  | 42 ++++++++++++++++---------------
 2 files changed, 33 insertions(+), 33 deletions(-)

-- 
2.0.4

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