linux-kernel - [PATCH] Fixing coding style issues in android alarm-dev.c

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]

Date:	Wed, 30 Apr 2014 22:05:53 +0100
From:	Karim Raslan <karim.allah.ahmed@...il.com>
To:	unlisted-recipients:; (no To-header on input)
Cc:	Karim Raslan <karim.allah.ahmed@...il.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	SeongJae Park <sj38.park@...il.com>,
	Dan Carpenter <dan.carpenter@...cle.com>,
	John Stultz <john.stultz@...aro.org>,
	Cruz Julian Bishop <cruzjbishop@...il.com>,
	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: [PATCH] Fixing coding style issues in android alarm-dev.c

fixing "Missing a blank line after declarations" found by checkpatch.pl script

Signed-off-by: Karim Raslan <karim.allah.ahmed@...il.com>
---
 drivers/staging/android/alarm-dev.c |    1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/staging/android/alarm-dev.c b/drivers/staging/android/alarm-dev.c
index 2fc7cdd..f200e8a 100644
--- a/drivers/staging/android/alarm-dev.c
+++ b/drivers/staging/android/alarm-dev.c
@@ -329,6 +329,7 @@ static int alarm_release(struct inode *inode, struct file *file)
 	if (file->private_data) {
 		for (i = 0; i < ANDROID_ALARM_TYPE_COUNT; i++) {
 			uint32_t alarm_type_mask = 1U << i;
+
 			if (alarm_enabled & alarm_type_mask) {
 				alarm_dbg(INFO,
 					  "%s: clear alarm, pending %d\n",
-- 
1.7.9.5

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