From: Triplehx3 <ginge264@gmail.com>
To: gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
Triplehx3 <ginge264@gmail.com>
Subject: [PATCH] Staging: ralink-gdma: ralink-gdma: Fix a blank line coding style issue
Date: Thu, 10 Dec 2020 01:32:28 +0000 [thread overview]
Message-ID: <20201210013228.9371-1-ginge264@gmail.com> (raw)
Fix a coding style issue as identified by checkpatch.pl
Signed-off-by: Triplehx3 <ginge264@gmail.com>
---
drivers/staging/ralink-gdma/ralink-gdma.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/staging/ralink-gdma/ralink-gdma.c b/drivers/staging/ralink-gdma/ralink-gdma.c
index 655df317d0ee..a6181a167814 100644
--- a/drivers/staging/ralink-gdma/ralink-gdma.c
+++ b/drivers/staging/ralink-gdma/ralink-gdma.c
@@ -122,6 +122,7 @@ struct gdma_dma_dev {
struct gdma_data *data;
void __iomem *base;
struct tasklet_struct task;
+
volatile unsigned long chan_issued;
atomic_t cnt;
--
2.28.0
next reply other threads:[~2020-12-10 0:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 1:32 Triplehx3 [this message]
2020-12-10 7:57 ` [PATCH] Staging: ralink-gdma: ralink-gdma: Fix a blank line coding style issue Greg KH
2020-12-10 10:06 Chris Bloomfield
2020-12-10 9:28 ` 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=20201210013228.9371-1-ginge264@gmail.com \
--to=ginge264@gmail.com \
--cc=devel@driverdev.osuosl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).