linux-kernel - [PATCH] Staging: asus_oled: fix checkpatch.pl issue in asus

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: <1330486491-8699-1-git-send-email-baumanno@cip.ifi.lmu.de>
Date:	Wed, 29 Feb 2012 04:34:51 +0100
From:	"Oliver N. Baumann" <oliver.n.baumann@...glemail.com>
To:	sjakub@...il.com, gregkh@...uxfoundation.org, pq@....fi,
	baumanno@....ifi.lmu.de, kernel@...obrien.org
Cc:	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: [PATCH] Staging: asus_oled: fix checkpatch.pl issue in asus_oled.c

From: "Oliver N. Baumann" <baumanno@....ifi.lmu.de>

This is a patch to asus_oled.c that fixes a parenthesis issue detected by checkpatch.pl tool
Signed-off-by: Oliver N. Baumann <baumanno@....ifi.lmu.de>
---
 drivers/staging/asus_oled/asus_oled.c |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/staging/asus_oled/asus_oled.c b/drivers/staging/asus_oled/asus_oled.c
index 1df9586..b77f225 100644
--- a/drivers/staging/asus_oled/asus_oled.c
+++ b/drivers/staging/asus_oled/asus_oled.c
@@ -44,9 +44,9 @@
 
 #define ASUS_OLED_ERROR			"Asus OLED Display Error: "
 
-#define ASUS_OLED_STATIC		's'
-#define ASUS_OLED_ROLL			'r'
-#define ASUS_OLED_FLASH			'f'
+#define ASUS_OLED_STATIC		('s')
+#define ASUS_OLED_ROLL			('r')
+#define ASUS_OLED_FLASH			('f')
 
 #define ASUS_OLED_MAX_WIDTH		1792
 #define ASUS_OLED_DISP_HEIGHT		32
-- 
1.7.5.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/