All of lore.kernel.org
 help / color / mirror / Atom feed
From: Huiquan Deng <denghuiquan@cdjrlc.com>
To: linux-kernel@vger.kernel.org
Cc: ojeda@kernel.org, Huiquan Deng <denghuiquan@cdjrlc.com>
Subject: [PATCH] auxdisplay: code indent should use tabs where possible
Date: Thu, 29 Jul 2021 00:26:28 -0700	[thread overview]
Message-ID: <20210729072628.68838-1-denghuiquan@cdjrlc.com> (raw)

Resolves the checkpatch error.

Signed-off-by: Huiquan Deng <denghuiquan@cdjrlc.com>
---
 drivers/auxdisplay/cfag12864bfb.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/auxdisplay/cfag12864bfb.c b/drivers/auxdisplay/cfag12864bfb.c
index d66821adf453..1e040e83d1c1 100644
--- a/drivers/auxdisplay/cfag12864bfb.c
+++ b/drivers/auxdisplay/cfag12864bfb.c
@@ -41,8 +41,8 @@ static const struct fb_var_screeninfo cfag12864bfb_var = {
 	.yres_virtual = CFAG12864B_HEIGHT,
 	.bits_per_pixel = 1,
 	.red = { 0, 1, 0 },
-      	.green = { 0, 1, 0 },
-      	.blue = { 0, 1, 0 },
+	.green = { 0, 1, 0 },
+	.blue = { 0, 1, 0 },
 	.left_margin = 0,
 	.right_margin = 0,
 	.upper_margin = 0,
@@ -69,8 +69,8 @@ static const struct fb_ops cfag12864bfb_ops = {
 
 static int cfag12864bfb_probe(struct platform_device *device)
 {
+	struct fb_info *info = framebuffer_alloc(0, &device->dev);
 	int ret = -EINVAL;
- 	struct fb_info *info = framebuffer_alloc(0, &device->dev);
 
 	if (!info)
 		goto none;
-- 
2.17.1


             reply	other threads:[~2021-07-29  7:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-29  7:26 Huiquan Deng [this message]
2021-10-21 22:17 ` [PATCH] auxdisplay: code indent should use tabs where possible Miguel Ojeda
  -- strict thread matches above, loose matches on Subject: below --
2021-07-29  6:39 Huiquan Deng

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=20210729072628.68838-1-denghuiquan@cdjrlc.com \
    --to=denghuiquan@cdjrlc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ojeda@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.