The Linux kernel coding style states that braces should only be used
when necessary.

This fixes the checkpatch warning

WARNING: line over 80 characters
+       } else if (display->regwidth == 8 && display->buswidth == 9 && 
par->spi) {

introduced by patch #1.

Signed-off-by: Luis Gerhorst <linux-ker...@luisgerhorst.de>
Acked-by: Jonny Schaefer <schaefer.jo...@gmail.com>
Acked-by: Alexander Wuerstlein <a...@cs.fau.de>
---
 drivers/staging/fbtft/fbtft-core.c | 11 +++++------
 1 file changed, 5 insertions(+), 6 deletions(-)

diff --git a/drivers/staging/fbtft/fbtft-core.c 
b/drivers/staging/fbtft/fbtft-core.c
index 66b46b2..34b1c81 100644
--- a/drivers/staging/fbtft/fbtft-core.c
+++ b/drivers/staging/fbtft/fbtft-core.c
@@ -1367,19 +1367,18 @@ int fbtft_probe_common(struct fbtft_display *display,
        }
 
        /* write register functions */
-       if (display->regwidth == 8 && display->buswidth == 8) {
+       if (display->regwidth == 8 && display->buswidth == 8)
                par->fbtftops.write_register = fbtft_write_reg8_bus8;
-       } else if (display->regwidth == 8 && display->buswidth == 9 && 
par->spi) {
+       else if (display->regwidth == 8 && display->buswidth == 9 && par->spi)
                par->fbtftops.write_register = fbtft_write_reg8_bus9;
-       } else if (display->regwidth == 16 && display->buswidth == 8) {
+       else if (display->regwidth == 16 && display->buswidth == 8)
                par->fbtftops.write_register = fbtft_write_reg16_bus8;
-       } else if (display->regwidth == 16 && display->buswidth == 16) {
+       else if (display->regwidth == 16 && display->buswidth == 16)
                par->fbtftops.write_register = fbtft_write_reg16_bus16;
-       } else {
+       else
                dev_warn(dev,
                        "no default functions for regwidth=%d and 
buswidth=%d\n",
                        display->regwidth, display->buswidth);
-       }
 
        /* write_vmem() functions */
        if (display->buswidth == 8)
-- 
2.7.4

_______________________________________________
devel mailing list
de...@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

Reply via email to