From: Timo Aranjo <timo.aranjo@aol.com>
To: linux-fbdev@vger.kernel.org
Subject: [PATCH] Staging: sm750fb: Fixed a coding style issue
Date: Mon, 24 Aug 2020 23:02:26 +0000 [thread overview]
Message-ID: <1b596369-7c83-73ff-fd4e-ed0d7a714219@aol.com> (raw)
From 56c5eed5b0a3d299530264509a6a81594c4fb791 Mon Sep 17 00:00:00 2001
From: "Timo A. Aranjo" <timo.aranjo@aol.com>
Date: Mon, 24 Aug 2020 17:24:16 -0500
Subject: [PATCH] Staging: sm750fb: Fixed a coding style issue
I added a new-line because checkpatch gave a warning about there not being
a new line after declarations.
Signed-off-by: Timo Alejandro Aranjo <timo.aranjo@aol.com>
---
drivers/staging/sm750fb/sm750.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/sm750fb/sm750.c
b/drivers/staging/sm750fb/sm750.c
index 84fb585a5739..3da87387867e 100644
--- a/drivers/staging/sm750fb/sm750.c
+++ b/drivers/staging/sm750fb/sm750.c
@@ -411,6 +411,7 @@ static int __maybe_unused lynxfb_suspend(struct
device *dev)
{
struct fb_info *info;
struct sm750_dev *sm750_dev;
+
sm750_dev = dev_get_drvdata(dev);
console_lock();
--
2.25.1
next reply other threads:[~2020-08-24 23:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 23:02 Timo Aranjo [this message]
2020-08-25 9:27 ` [PATCH] Staging: sm750fb: Fixed a coding style issue Dan Carpenter
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=1b596369-7c83-73ff-fd4e-ed0d7a714219@aol.com \
--to=timo.aranjo@aol.com \
--cc=linux-fbdev@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