From: Mamta Shukla <mamtashukla555@gmail.com>
To: outreachy-kernel@googlegroups.com
Cc: gregkh@linuxfoundation.org, mamtashukla555@gmail.com
Subject: [PATCH] staging: fbtft: Adding spaces around '<<'
Date: Wed, 3 Oct 2018 18:59:17 +0530 [thread overview]
Message-ID: <20181003132917.GA29977@armorer> (raw)
Adding spaces around '<<' to fix checkpatch issue.
CHECK: spaces preferred around that '<<' (ctx:VxV)
Signed-off-by: Mamta Shukla <mamtashukla555@gmail.com>
---
drivers/staging/fbtft/fbtft.h | 56 +++++++++++++++++++++----------------------
1 file changed, 28 insertions(+), 28 deletions(-)
diff --git a/drivers/staging/fbtft/fbtft.h b/drivers/staging/fbtft/fbtft.h
index 25302ff..a3db23b 100644
--- a/drivers/staging/fbtft/fbtft.h
+++ b/drivers/staging/fbtft/fbtft.h
@@ -355,39 +355,39 @@ static void __exit fbtft_driver_module_exit(void) \
#define DEBUG_LEVEL_6 (DEBUG_LEVEL_4 | DEBUG_LEVEL_5)
#define DEBUG_LEVEL_7 0xFFFFFFFF
-#define DEBUG_DRIVER_INIT_FUNCTIONS (1<<3)
-#define DEBUG_TIME_FIRST_UPDATE (1<<4)
-#define DEBUG_TIME_EACH_UPDATE (1<<5)
-#define DEBUG_DEFERRED_IO (1<<6)
-#define DEBUG_FBTFT_INIT_FUNCTIONS (1<<7)
+#define DEBUG_DRIVER_INIT_FUNCTIONS (1 << 3)
+#define DEBUG_TIME_FIRST_UPDATE (1 << 4)
+#define DEBUG_TIME_EACH_UPDATE (1 << 5)
+#define DEBUG_DEFERRED_IO (1 << 6)
+#define DEBUG_FBTFT_INIT_FUNCTIONS (1 << 7)
/* fbops */
-#define DEBUG_FB_READ (1<<8)
-#define DEBUG_FB_WRITE (1<<9)
-#define DEBUG_FB_FILLRECT (1<<10)
-#define DEBUG_FB_COPYAREA (1<<11)
-#define DEBUG_FB_IMAGEBLIT (1<<12)
-#define DEBUG_FB_SETCOLREG (1<<13)
-#define DEBUG_FB_BLANK (1<<14)
+#define DEBUG_FB_READ (1 << 8)
+#define DEBUG_FB_WRITE (1 << 9)
+#define DEBUG_FB_FILLRECT (1 << 10)
+#define DEBUG_FB_COPYAREA (1 << 11)
+#define DEBUG_FB_IMAGEBLIT (1 << 12)
+#define DEBUG_FB_SETCOLREG (1 << 13)
+#define DEBUG_FB_BLANK (1 << 14)
-#define DEBUG_SYSFS (1<<16)
+#define DEBUG_SYSFS (1 << 16)
/* fbtftops */
-#define DEBUG_BACKLIGHT (1<<17)
-#define DEBUG_READ (1<<18)
-#define DEBUG_WRITE (1<<19)
-#define DEBUG_WRITE_VMEM (1<<20)
-#define DEBUG_WRITE_REGISTER (1<<21)
-#define DEBUG_SET_ADDR_WIN (1<<22)
-#define DEBUG_RESET (1<<23)
-#define DEBUG_MKDIRTY (1<<24)
-#define DEBUG_UPDATE_DISPLAY (1<<25)
-#define DEBUG_INIT_DISPLAY (1<<26)
-#define DEBUG_BLANK (1<<27)
-#define DEBUG_REQUEST_GPIOS (1<<28)
-#define DEBUG_FREE_GPIOS (1<<29)
-#define DEBUG_REQUEST_GPIOS_MATCH (1<<30)
-#define DEBUG_VERIFY_GPIOS (1<<31)
+#define DEBUG_BACKLIGHT (1 << 17)
+#define DEBUG_READ (1 << 18)
+#define DEBUG_WRITE (1 << 19)
+#define DEBUG_WRITE_VMEM (1 << 20)
+#define DEBUG_WRITE_REGISTER (1 << 21)
+#define DEBUG_SET_ADDR_WIN (1 << 22)
+#define DEBUG_RESET (1 << 23)
+#define DEBUG_MKDIRTY (1 << 24)
+#define DEBUG_UPDATE_DISPLAY (1 << 25)
+#define DEBUG_INIT_DISPLAY (1 << 26)
+#define DEBUG_BLANK (1 << 27)
+#define DEBUG_REQUEST_GPIOS (1 << 28)
+#define DEBUG_FREE_GPIOS (1 << 29)
+#define DEBUG_REQUEST_GPIOS_MATCH (1 << 30)
+#define DEBUG_VERIFY_GPIOS (1 << 31)
#define fbtft_init_dbg(dev, format, arg...) \
do { \
--
1.9.1
next reply other threads:[~2018-10-03 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 13:29 Mamta Shukla [this message]
2018-10-03 13:40 ` [Outreachy kernel] [PATCH] staging: fbtft: Adding spaces around '<<' Julia Lawall
2018-10-03 13:37 ` Mamta Shukla
2018-10-03 13:58 ` Julia Lawall
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=20181003132917.GA29977@armorer \
--to=mamtashukla555@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=outreachy-kernel@googlegroups.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.