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, gregkh@linuxfoundation.org,
speakup@linux-speakup.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org, Walt Feasel <waltfeasel@gmail.com>
Subject: [PATCH v2 0/5] staging: speakup: synth.c checkpatch modifications
Date: Sat, 19 Nov 2016 12:35:42 -0500 [thread overview]
Message-ID: <1479576947-3605-1-git-send-email-waltfeasel@gmail.com> (raw)
Make Linux kernel coding style modifications for XGI_main_26.c to include:
Spaces around operators
Blank lines before }
Logical continuation
Comment modifications
Align on parenthesis
Walt Feasel (5):
staging: speakup: synth.c Spaces around operators
staging: speakup: synth.c Blank line before }
staging: speakup: synth.c Logical continuation
staging: speakup: synth.c Comment modifications
staging: speakup: synth.c Align parenthesis
drivers/staging/speakup/synth.c | 24 ++++++++++++------------
1 file changed, 12 insertions(+), 12 deletions(-)
--
v2 makes changes to correct for email format patch submission
2.1.4
next reply other threads:[~2016-11-19 17:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-19 17:35 Walt Feasel [this message]
2016-11-19 17:35 ` [PATCH v2 1/5] staging: speakup: synth.c Spaces around operators Walt Feasel
2016-11-19 18:06 ` kbuild test robot
2016-11-19 18:48 ` kbuild test robot
2016-11-19 19:34 ` [PATCH v3 " Walt Feasel
2016-11-25 13:10 ` [PATCH v2 " Dan Carpenter
2016-11-19 17:35 ` [PATCH v2 2/5] staging: speakup: synth.c Blank line before } Walt Feasel
2016-11-19 17:35 ` [PATCH v2 3/5] staging: speakup: synth.c Logical continuation Walt Feasel
2016-11-19 17:35 ` [PATCH v2 4/5] staging: speakup: synth.c Comment modifications Walt Feasel
2016-11-19 17:35 ` [PATCH v2 5/5] staging: speakup: synth.c Align parenthesis 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=1479576947-3605-1-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 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.