From: "Clément Calmels" <clement.calmels@free.fr>
To: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH] staging: vt6655: correct coding style issue
Date: Sun, 4 May 2014 21:52:09 +0200 [thread overview]
Message-ID: <1399233129-13436-1-git-send-email-clement.calmels@free.fr> (raw)
Remove C99 comment and rewrite lines over 80 characters.
Warnings and error found by checkpatch.pl script.
Signed-off-by: Clément Calmels <clement.calmels@free.fr>
---
drivers/staging/vt6655/tmacro.h | 13 +++++++++----
1 file changed, 9 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/vt6655/tmacro.h b/drivers/staging/vt6655/tmacro.h
index 59c6e72..264c6ed 100644
--- a/drivers/staging/vt6655/tmacro.h
+++ b/drivers/staging/vt6655/tmacro.h
@@ -44,17 +44,22 @@
#define LOWORD(d) ((unsigned short)(d))
#endif
#if !defined(HIWORD)
-#define HIWORD(d) ((unsigned short)((((unsigned long)(d)) >> 16) & 0xFFFF))
+#define HIWORD(d) \
+ ((unsigned short)((((unsigned long)(d)) >> 16) & 0xFFFF))
#endif
#define LODWORD(q) ((q).u.dwLowDword)
#define HIDWORD(q) ((q).u.dwHighDword)
#if !defined(MAKEWORD)
-#define MAKEWORD(lb, hb) ((unsigned short)(((unsigned char)(lb)) | (((unsigned short)((unsigned char)(hb))) << 8)))
+#define MAKEWORD(lb, hb)\
+ ((unsigned short)(((unsigned char)(lb)) \
+ | (((unsigned short)((unsigned char)(hb))) << 8)))
#endif
#if !defined(MAKEDWORD)
-#define MAKEDWORD(lw, hw) ((unsigned long)(((unsigned short)(lw)) | (((unsigned long)((unsigned short)(hw))) << 16)))
+#define MAKEDWORD(lw, hw)\
+ ((unsigned long)(((unsigned short)(lw)) \
+ | (((unsigned long)((unsigned short)(hw))) << 16)))
#endif
-#endif // __TMACRO_H__
+#endif /* __TMACRO_H__ */
--
2.0.0.rc0
next reply other threads:[~2014-05-04 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 19:52 Clément Calmels [this message]
2014-05-04 21:26 ` [PATCH] staging: vt6655: correct coding style issue Greg KH
2014-05-05 19:16 ` Clément Calmels
2014-05-05 21:10 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1399233129-13436-1-git-send-email-clement.calmels@free.fr \
--to=clement.calmels@free.fr \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).