linux-kernel - [PATCH] Staging: android: fix parantheses coding style issue in 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]

Message-Id: <1386455752-17600-1-git-send-email-preetamjdsouza@gmail.com>
Date:	Sat,  7 Dec 2013 14:35:52 -0800
From:	Preetam D'Souza <preetamjdsouza@...il.com>
To:	gregkh@...uxfoundation.org
Cc:	swetland@...gle.com, devel@...verdev.osuosl.org,
	linux-kernel@...r.kernel.org,
	Preetam D'Souza <preetamjdsouza@...il.com>
Subject: [PATCH] Staging: android: fix parantheses coding style issue in alarm-dev.c

This patch fixes an unecessary return statement parantheses error
found in alarm-dev.c by the checkpatch.pl tool -- alarm-dev.c now has
no more errors/warnings!

Signed-off-by: Preetam D'Souza <preetamjdsouza@...il.com>
---
 drivers/staging/android/alarm-dev.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/staging/android/alarm-dev.c b/drivers/staging/android/alarm-dev.c
index 647694f..ccf74ee 100644
--- a/drivers/staging/android/alarm-dev.c
+++ b/drivers/staging/android/alarm-dev.c
@@ -68,8 +68,8 @@ static struct devalarm alarms[ANDROID_ALARM_TYPE_COUNT];
  */
 static int is_wakeup(enum android_alarm_type type)
 {
-	return (type == ANDROID_ALARM_RTC_WAKEUP ||
-		type == ANDROID_ALARM_ELAPSED_REALTIME_WAKEUP);
+	return type == ANDROID_ALARM_RTC_WAKEUP ||
+		type == ANDROID_ALARM_ELAPSED_REALTIME_WAKEUP;
 }
 
 
-- 
1.7.10.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/