From: Walt Feasel <waltfeasel@gmail.com>
To: w.d.hubbs@gmail.com
Cc: chris@the-brannons.com, kirk@reisers.ca,
samuel.thibault@ens-lyon.org, speakup@linux-speakup.org,
gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, Walt Feasel <waltfeasel@gmail.com>
Subject: [PATCH v2 3/6] staging: speakup: speakup_soft.c Multiple blank lines
Date: Mon, 21 Nov 2016 10:19:22 -0500 [thread overview]
Message-ID: <1479741565-19419-4-git-send-email-waltfeasel@gmail.com> (raw)
In-Reply-To: <1479741565-19419-1-git-send-email-waltfeasel@gmail.com>
Make suggested checkpatch modification for
CHECK: Please don't use multiple blank lines
Signed-off-by: Walt Feasel <waltfeasel@gmail.com>
---
v2 makes changes to correct for email format patch submission
drivers/staging/speakup/speakup_soft.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/staging/speakup/speakup_soft.c b/drivers/staging/speakup/speakup_soft.c
index de6b35a..9308b7e 100644
--- a/drivers/staging/speakup/speakup_soft.c
+++ b/drivers/staging/speakup/speakup_soft.c
@@ -310,7 +310,6 @@ static const struct file_operations softsynth_fops = {
.release = softsynth_close,
};
-
static int softsynth_probe(struct spk_synth *synth)
{
--
2.1.4
next prev parent reply other threads:[~2016-11-21 15:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 15:19 [PATCH v2 0/6] staging: speakup: speakup_soft.c checkpatch modifications Walt Feasel
2016-11-21 15:19 ` [PATCH v2 1/6] staging: speakup: speakup_soft.c Space around operator Walt Feasel
2016-11-21 15:19 ` [PATCH v2 2/6] staging: speakup: speakup_soft.c Logical continuation Walt Feasel
2016-11-21 15:19 ` Walt Feasel [this message]
2016-11-21 15:19 ` [PATCH v2 4/6] staging: speakup: speakup_soft.c Blank line after { Walt Feasel
2016-11-21 15:19 ` [PATCH v2 5/6] staging: speakup: speakup_soft.c comment modifications Walt Feasel
2016-11-21 15:19 ` [PATCH v2 6/6] staging: speakup: speakup_soft.c Align parenthesis Walt Feasel
2016-11-23 9:09 ` [PATCH v2 0/6] staging: speakup: speakup_soft.c checkpatch modifications Greg KH
[not found] ` <CACfmeC=-NKgX4QKF0Btj6OTvOxSjZgcoQ4BrNLq5NEpPSZ+1Ww@mail.gmail.com>
2016-11-23 15:56 ` Greg KH
2016-11-23 16:24 ` Walt Feasel
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=1479741565-19419-4-git-send-email-waltfeasel@gmail.com \
--to=waltfeasel@gmail.com \
--cc=chris@the-brannons.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=kirk@reisers.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=samuel.thibault@ens-lyon.org \
--cc=speakup@linux-speakup.org \
--cc=w.d.hubbs@gmail.com \
/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
Powered by JetHome