All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aleksa Vučković" <aleksav013@gmail.com>
To: gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, "Aleksa Vučković" <aleksav013@gmail.com>
Subject: [PATCH 4/4] drivers: dio: Fixed spaces coding style issue
Date: Tue, 25 Jan 2022 11:33:10 +0100	[thread overview]
Message-ID: <20220125103310.13893-4-aleksav013@gmail.com> (raw)
In-Reply-To: <20220125103310.13893-1-aleksav013@gmail.com>

Added or removed spaces in the code according to the checkpatch.pl script.

Signed-off-by: Aleksa Vučković <aleksav013@gmail.com>
---
 drivers/dio/dio.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/dio/dio.c b/drivers/dio/dio.c
index 0f29d4903012..020a3d6219ae 100644
--- a/drivers/dio/dio.c
+++ b/drivers/dio/dio.c
@@ -64,7 +64,7 @@ struct dioname {
 
 /* useful macro */
 #define DIONAME(x) { DIO_ID_##x, DIO_DESC_##x }
-#define DIOFBNAME(x) { DIO_ENCODE_ID( DIO_ID_FBUFFER, DIO_ID2_##x), DIO_DESC2_##x }
+#define DIOFBNAME(x) { DIO_ENCODE_ID(DIO_ID_FBUFFER, DIO_ID2_##x), DIO_DESC2_##x }
 
 static struct dioname names[] = {
 	DIONAME(DCA0), DIONAME(DCA0REM), DIONAME(DCA1), DIONAME(DCA1REM),
@@ -236,7 +236,7 @@ static int __init dio_init(void)
 			dev->id = prid;
 
 		dev->ipl = DIO_IPL(va);
-		strcpy(dev->name,dio_getname(dev->id));
+		strcpy(dev->name, dio_getname(dev->id));
 		printk(KERN_INFO "select code %3d: ipl %d: ID %02X", dev->scode, dev->ipl, prid);
 		if (DIO_NEEDSSECID(prid))
 			printk(":%02X", secid);
-- 
2.34.1


  parent reply	other threads:[~2022-01-25 10:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-25 10:33 [PATCH 1/4] drivers: dio: fixed spaces to tabs coding style issue Aleksa Vučković
2022-01-25 10:33 ` [PATCH 2/4] drivers: dio: Fixed unwanted spaces " Aleksa Vučković
2022-01-25 10:33 ` [PATCH 3/4] drivers: dio: Fixed braces " Aleksa Vučković
2022-01-25 10:33 ` Aleksa Vučković [this message]
2022-01-26 17:52 ` [PATCH 1/4] drivers: dio: fixed spaces to tabs " 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=20220125103310.13893-4-aleksav013@gmail.com \
    --to=aleksav013@gmail.com \
    --cc=gregkh@linuxfoundation.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 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.